How to Configure the Veeva Vault Connector Using Web.config
ThrottleSleepMinutes and BurstLimit
Burst Limit and Throttle Sleep Minutes settings can be modified to change the way the connector behaves when approaching the Veeva Vault API call quota.
The connector will monitor the remaining requests available under the current VV burst limit and will stop issuing requests if the number of requests available under the burst limit drops below the value configured here.
- To change the Burst Limit or the Throttle Sleep Time (in minutes), open the web.config file.
- Change the values of the settings
BurstLimitandThrottleSleepMinutes.- The default values are 100 for
BurstLimitand 1 (minute) forThrottle Sleep Time.
- The default values are 100 for
RequestTimeoutValue
This setting should be used if you experience timeouts during crawls or jobs, to allow more time for Veeva Vault to respond.
-
To modify the web request timeout value, open the web.config file.
-
Change the
requestTimeoutValuevalue.- The default value is 300000 (300 seconds).
SessionCacheExpiration
The value that sets the session cache expiration time can be modified according to the setting selected in Veeva Vault.
-
By default the value is 20 minutes.
ApiLimitExceededSleepMinutes
When the API call quota is exceeded, the connector will stop making requests to Veeva and sleep for a certain amount of time before retrying.
-
Unlike the Throttle Sleep Minutes setting (which triggers when the number of used calls approaches the limit), this setting comes into action when the limit is already reached.
-
This usually happens during a busy period, when multiple clients make requests to Veeva.
-
That amount can be modified using this setting.
-
The default value is 5 minutes.
VeevaVaultClientID
The format of the ClientId in a Veeva Vault API request header can be set using this setting.
-
It is used to allow the customization of the requests that the Veeva Vault Connector makes, so they can easily be found.
-
The default value is BAInsight-connector-%connid%.
RenditionStates
Enumerate the document states that have the Viewable Rendition option enabled.
-
For these states, the connector will try to get the rendition instead of the actual file when retrieving the binary data during indexing.
-
By default, the configured states are Approved Effective,Approved,Effective.