3 Provider Services Configuration
The Provider Services configuration properties are available in the Essbase web interface to help you manage network timeout parameters.
You can set the values for Provider Services configurations in the Console. See Set Provider Services Configuration Properties.
essbase.jobs.maxCount
Sets the maximum number of parallel jobs that may be run.
Syntax
essbase.jobs.maxCount n
n—Specifies the number of active jobs that Essbase can run in parallel. The default is 10.
Description
Jobs are operations you can run from the Essbase web interface. Jobs include loading data, building dimensions, exporting cubes, running MaxL scripts, running calculations, and clearing data. Jobs are asynchronous, meaning they are run in the background as a unique thread. Each job has a unique id.
This property is case-sensitive, so be sure to specify its name just as shown in the example.
Example
essbase.jobs.maxCount 15
olap.server.netRetryCount
Specifies the number of times an API can retry a unsuccessful network operation before failing and reporting an error. If olap.server.netSocketTryInfinite is set to true, then olap.server.netRetryCount is ineffective.
Syntax
olap.server.netRetryCount n
n—An integer value. The default is 600 retries. Every five tries gives a timeout of one second. The default value, 600, gives a timeout of two minutes.
olap.server.netSocketTimeOut
Sets the maximum time that an Essbase network operation (read/write) can be blocked before the operation I/O times out.
Syntax
olap.server.netSocketTimeOut n
n—Specifies the number of miliseconds an Essbase network operation can be blocked before the operation I/O times out.
Note:
This value affects overall request timeout behavior and should not be changed arbitrarily.Example
olap.server.netSocketTimeOut 200
olap.server.netSocketTryInfinite
Specifies whether the client will keep trying infinitely on a network operation. If set to true, then olap.server.netRetryCount is ineffective. The default is false.
Syntax
olap.server.netSocketTryInfinite true|false
system.cluster.monitorInterval
Defines the interval at which Essbase polls the Essbase nodes in active-active (read only) clusters to see if the nodes are down or active.
Syntax
system.cluster.monitorInterval n
n—The interval, in seconds, at which Essbase polls the Essbase nodes in active-active (read only) clusters to see if the nodes are down or active. The default interval is 30s.
Example
system.cluster.monitorInterval 30