Performance optimization
These properties are related to tuning of Adeptia Connect performance.
CACHING
Connect Cache
abpm.connect.cache.enable
| Description | Connect Cache enable or disable option |
|---|---|
| Default Value | No |
| Possible Values | Yes/No |
| Selection Criteria | To activate this property after any change, you need to restart the Adeptia Connect server. |
Data Mapper Cache
abpm.dataMapper.dblookup.cache.limit
| Description | Number of Data Mapper Select Queries and result string pairs to be cached |
|---|---|
| Default Value | 10000 |
| Possible Values | Any integer |
| Selection Criteria | Number of Data Mapper Select Query and result string pair to be cached. This limit applies on whole Adeptia Connect not on individual Data Mapper applet. |
JDO
abpm.jdo.cache.enable
| Description | JDO Cache enable and disable option |
|---|---|
| Default Value | no |
| Possible Values | no/yes |
| Selection Criteria | Change the value of this property from no to yes if you want to enable JDO caching in your Adeptia Connect environment. |
abpm.jdo.cache.maxElementsinMemory
| Description | Maximum number of elements that can be cached |
|---|---|
| Default Value | 5000 |
| Possible Values | Any valid positive integer |
| Selection Criteria | Change the value of this property if you want to increase/decrease the maximum number of objects that your JDO cache memory can hold. |
abpm.jdo.cache.idleTime
| Description | Minimum idle time in seconds |
|---|---|
| Default Value | 7200 |
| Possible Values | Any valid positive integer |
| Selection Criteria | Change the value of this property if you want to increase/decrease the minimum time the objects in the JDO cache can remain idle. After the specified time, the cache removes the idle objects. |
abpm.jdo.cache.timetoLive
| Description | Max time in seconds an object can stay in cache |
|---|---|
| Default Value | 86400 |
| Possible Values | Any valid positive integer |
| Selection Criteria | Change the value of this property if you want to increase/decrease the maximum time an object can stay in the JDO cache. After the specified time, the cache clears its memory and removes the objects. |
abpm.resource.cache.enable
| Description | Resource Cache enable and disable option |
|---|---|
| Default Value | yes |
| Possible Values | Yes/No |
| Comments | To activate this property after any change, you need to Restart Server. |
abpm.resource.cache.maxElementsinMemory
| Description | Resource Cache enable and disable option |
|---|---|
| Default Value | 5000 |
| Possible Values | Any valid positive integer. |
| Comments | To activate this property after any change, you need to restart the Adeptia Connect Server. |
abpm.resource.cache.idleTime
| Description | Minimum idle time in seconds |
|---|---|
| Default Value | 7200 |
| Possible Values | Any valid positive integer. |
| Comments | To activate this property after any change, you need to restart the Adeptia Connect Server. |
abpm.resource.cache.timetoLive
| Description | Resource Cache enable and disable option |
|---|---|
| Default Value | 86400 |
| Possible Values | Any valid positive integer. |
| Comments | To activate this property after any change, you need to restart the Adeptia Connect Server. |
JMX
abpm.mbeanServer.connection.retry.count
| Description | Number of retries if mbean server connection is down |
|---|---|
| Default Value | 3 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Number of retries to connect to the mbean server, if it is down |
abpm.mbeanServer.connection.lookup.time
| Description | The lookup time between two retries of connecting to the mbean Server |
|---|---|
| Default Value | 2000 |
| Possible Values | Any integer |
| Selection Criteria | NA |
KERNEL CONNECTION POOL
Kernel JDO
abpm.jdo.connection.pooling.enable
| Description | Enables or disables connection pooling for backend database. |
|---|---|
| Default Value | yes |
| Possible Values | yes/no |
| Selection Criteria | It should always be enabled to optimize the connection with backend database. |
abpm.jdo.maxActive
| Description | Maximum number of Connections that a pool will maintain at a given time. |
|---|---|
| Default Value | 50 |
| Possible Values | Any integer |
| Selection Criteria | It depends upon the capacity of the backend database and on the amount of processing required. |
abpm.jdo.minIdle
| Description | Minimum number of Connections a pool will maintain at a given time. |
|---|---|
| Default Value | 10 |
| Possible Values | Any integer |
| Selection Criteria | It depends upon the capacity of the backend database and on the amount of processing required. |
abpm.jdo.maxWait
| Description | Limits how long a client will wait for a Connection, if all Connections are checked out and one cannot be supplied immediately. |
|---|---|
| Default Value | 600000 |
| Possible Values | Any integer |
| Selection Criteria | It depends upon the number of connections getting created at a given time. In case, most of the connection are being used then you must use a higher value so that the application can wait for the connection to become available. |
abpm.minEvictableIdleTimeMillis
| Description | Defines the seconds for which a connection is allowed to remain idle, before being pulled out from a connection pool. |
|---|---|
| Default Value | 3600000 |
| Possible Values | Any integer |
| Selection Criteria | NA |
abpm.jdo.isolation.level
| Description | Controls the transaction locking behavior for all statements issued by a connection. |
|---|---|
| Default Value | 1 |
| Possible Values | Either 1 or 2 |
| Selection Criteria | NA |
| Comments | Specify 1 for READ UNCOMMITTED and 2 for READ COMMITTED. |
abpm.jdo.connectionCustomizerClassName
| Description | Defines the Transaction Isolation setting on Connections when they are acquired from the backend database. |
|---|---|
| Default Value | com.adeptia.indigo.pool.datasources.c3p0.connectionCustomizer.IsolationLevelBackend ConnectionCustomizer |
| Comments | The fully qualified class-name of an implementation of the ConnectionCustomizer interface, which users can implement to set up Connections when they are acquired from the database, or on check-out, and potentially to clean things up on check-in and Connection destruction. |
abpm.jdo.validationQuery
| Description | Controls how a Connection will be tested. Defines the query that will be executed for all connection tests, when the default ConnectionTester is being used. |
|---|---|
| Default Value | NA |
| Comments | Works when the abpm.jdo.testOnBorrow property is set as true. |
abpm.jdo.maxStatements
| Description | JDBC's standard parameter for controlling statement pooling. |
|---|---|
| Default Value | 0 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | The size of global PreparedStatement cache. If both maxStatement and maxStatementsPerConnection are zero, statement caching will not be enabled. If maxStatement is zero but maxStatementsPerConnection is a non-zero value, statement caching will be enabled, but no global limit will be enforced, only the per-connection maximum. maxStatement controls the total number of Statements cached, for all connections. If set, it should be a fairly large number, as each pooled connection requires its own, distinct flock of cached statements. As a guide, consider how many distinct PreparedStatements are used frequently in your application, and multiply that number by maxPoolSize to arrive at an appropriate value. Though maxStatement is the JDBC standard parameter for controlling statement caching, users may find alternative maxStatementsPreConenction more intuitive to use. It defines the total number of PreparedStatements a DataSource will cache. |
Kernel Log
abpm.logdb.pool.enable
| Description | Enables or disables connection pooling for the log database. |
|---|---|
| Default Value | yes |
| Possible Values | yes/no |
| Selection Criteria | NA |
abpm.logdb.pool.maxActive
| Description | Maximum number of Connections a pool will maintain at a given time. |
|---|---|
| Default Value | 100 |
| Possible Values | Any positive integer/ -1 for no limit |
| Selection Criteria | Depends on the maximum number of connections allowed by the log database server. |
abpm.logdb.pool.minIdle
| Description | Minimum number of Connections a pool will maintain at a given time. |
|---|---|
| Default Value | 20 |
| Possible Values | Any positive integer/ 0 to create none |
abpm.logdb.pool.maxWait
| Description | Limits how long a client will wait for a Connection, if all Connections are checked out and one cannot be supplied immediately. |
|---|---|
| Default Value | 600000 |
| Possible Values | Any positive integer/ -1 to wait indefinitely |
abpm.logdb.pool.minEvictableIdleTimeMillis
| Description | Defines the number of seconds a connection is allowed to remain idle, before being pulled out from a connection pool. |
|---|---|
| Default Value | 3600000 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Zero means idle connections never expire. |
abpm.logdb.isolation.level
| Description | Controls the transaction locking behavior for all statements issued by a connection. |
|---|---|
| Default Value | 1 |
| Possible Values | Any integer |
| Selection Criteria | NA |
abpm.logdb.pool.testOnBorrow
| Description | It control when will be a Connections tested. |
|---|---|
| Default Value | false |
| Possible Values | true/false |
| Selection Criteria | NA |
| Comments | When true, an operation at every connection checkout is performed to verify if the connection is valid or not. |
abpm.logdb.pool.validationQuery
| Description | Controls how a Connection will be tested. Defines the query that will be executed for all connection tests, when the default ConnectionTester is being used. |
|---|---|
| Default Value | NA |
| Possible Values | NA |
| Comments | Works when the abpm.logdb.pool.testOnBorrow property is set as true. |
abpm.logdb.pool.maxStatements
| Description | JDBC's standard parameter for controlling statement pooling. |
|---|---|
| Default Value | 0 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Defines the total number of PreparedStatements, a DataSource will cache. If both maxStatement and maxStatementsPreConenction are zero, statement caching will not be enabled. If maxStatement is zero but maxStatementsPreConenction is a non-zero value, statement caching will be enabled, but no global limit will be enforced, only the per-connection maximum. maxStatement controls the total number of Statements cached, for all connections. If set, it should be a fairly large number, as each pooled connection requires its own, distinct flock of cached statements. As a guide, consider how many distinct PreparedStatements are used frequently in your application, and multiply that number by maxPoolSize to arrive at an appropriate value. Though maxStatement is the JDBC standard parameter for controlling statement caching, users may find alternative maxStatementsPreConenction more intuitive to use. |
WEBRUNNER CONNECTION POOL
Webrunner JDO
abpm.webrunner.jdo.maxActive
| Description | Maximum number of Connections a pool will maintain at a given time. |
|---|---|
| Default Value | 25 |
| Possible Values | Any integer |
| Selection Criteria | NA |
abpm.webrunner.jdo.minIdle
| Description | Minimum number of Connections a pool will maintain at a given time. |
|---|---|
| Default Value | 5 |
| Possible Values | Any integer |
| Selection Criteria | NA |
abpm.webrunner.jdo.maxWait
| Description | Limits how long a client will wait for a Connection, if all Connections are checked out and one cannot be supplied immediately |
|---|---|
| Default Value | 600000 |
| Possible Values | Any integer |
| Selection Criteria | NA |
abpm.webrunner.minEvictableIdleTimeMillis
| Description | Defines the seconds for which a connection is allowed to remain idle, before being pulled out from a connection pool. |
|---|---|
| Default Value | 3600000 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Zero means idle connections never expire. |
abpm.webrunner.jdo.isolation.level
| Description | Controls the transaction locking behaviour for all statements issued by a connection. |
|---|---|
| Default Value | 1 |
| Possible Values | Either 1 or 2 |
| Selection Criteria | NA |
| Comments | Specify 1 for READ UNCOMMITTED and 2 for READ COMMITTED. |
abpm.webrunner.jdo.testOnBorrow
| Description | Controls when a Connection will be tested. |
|---|---|
| Default Value | false |
| Possible Values | True/false |
| Selection Criteria | NA |
| Comments | When true, an operation at every connection checkout is performed to verify if the connection is valid or not. |
abpm.webrunner.jdo.validationQuery
| Description | Controls how a Connection will be tested. Defines the query that will be executed for all Connection tests, when the default ConnectionTester is being used. |
|---|---|
| Default Value | NA |
| Selection Criteria | NA |
| Comments | It works when the abpm.webrunner.jdo.testOnBorrow property is set as true. |
abpm.webrunner.jdo.maxStatements
| Description | JDBC's standard parameter for controlling statement pooling. |
|---|---|
| Default Value | 0 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | It defines the total number of PreparedStatements a DataSource will cache. The size of global PreparedStatement cache. If both maxStatement and maxStatementsPreConenction are zero, statement caching will not be enabled. If maxStatement is zero but maxStatementsPreConenction is a non-zero value, statement caching will be enabled, but no global limit will be enforced, only the per-connection maximum. maxStatement controls the total number of Statements cached, for all connections. If set, it should be a fairly large number, as each pooled connection requires its own, distinct flock of cached statements. As a guide, consider how many distinct PreparedStatements are used frequently in your application, and multiply that number by maxPoolSize to arrive at an appropriate value. Though maxStatement is the JDBC standard parameter for controlling statement caching, users may find alternative maxStatementsPreConenction more intuitive to use. |
Webrunner Log
abpm.webrunner.logdb.pool.maxActive
| Description | Maximum number of Connections a pool will maintain at a given time. |
|---|---|
| Default Value | 25 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Depends on the maximum number of connection allowed by the log database server. |
abpm.webrunner.logdb.pool.minIdle
| Description | Minimum number of Connections a pool will maintain at a given time. |
|---|---|
| Default Value | 5 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Any positive integer/ 0 to create none |
abpm.webrunner.logdb.pool.maxWait
| Description | Limits how long a client will wait for a Connection, if all Connections are checked out and one cannot be supplied immediately. |
|---|---|
| Default Value | 600000 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Any positive integer/ -1 to wait indefinitely |
abpm.webrunner.logdb.pool.minEvictableIdleTimeMillis
| Description | Defines the seconds for which a connection is allowed to remain idle, before being pulled out from a connection pool. |
|---|---|
| Default Value | 3600000 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Zero means idle connections never expire. |
abpm.webrunner.logdb.isolation.level
| Description | Controls the transaction locking behaviour of all the statements issued by a connection. |
|---|---|
| Default Value | 1 |
| Possible Values | Any integer |
| Selection Criteria | NA |
abpm.webrunner.logdb.pool.testOnBorrow
| Description | Controls when a Connection is tested. |
|---|---|
| Default Value | false |
| Possible Values | true/false |
| Selection Criteria | NA |
| Comments | When true, an operation at every connection checkout is performed to verify if the connection is valid or not. |
abpm.webrunner.logdb.pool.validationQuery
| Description | Controls how a Connection is tested. Defines the query that will be executed for all connection tests, when the default ConnectionTester is being used. |
|---|---|
| Default Value | NA |
| Selection Criteria | NA |
| Comments | It works when the abpm.webrunner.logdb.pool.testOnBorrow property is set as true. |
abpm.webrunner.logdb.pool.maxStatements
| Description | JDBC's standard parameter for controlling statement pooling. |
|---|---|
| Default Value | 0 |
| Possible Values | Any integer |
| Comments | Defines the total number of PreparedStatements a DataSource will cache. |
Webrunner Archive Log
abpm.archive.logdb.pool.enable
| Description | Enables or disables connection pooling for Archive Log Database. |
|---|---|
| Default Value | yes |
| Possible Values | Yes/no |
abpm.archive.logdb.pool.maxActive
| Description | Maximum number of Connections a pool will maintain at any given time. |
|---|---|
| Default Value | 3 |
| Possible Values | Any integer |
abpm.archive.logdb.pool.minIdle
| Description | Minimum number of Connections a pool will maintain at any given time. |
|---|---|
| Default Value | 0 |
| Possible Values | Any integer |
abpm.archive.logdb.pool.maxWait
| Description | Limits how long a client will wait for a Connection, if all Connections are checked out and one cannot be supplied immediately. |
|---|---|
| Default Value | 600000 |
| Possible Values | Any integer |
| Selection Criteria | NA |
abpm.archive.logdb.pool.minEvictableIdleTimeMillis
| Description | Defines the seconds for which a connection is allowed to remain idle, before being pulled out from a connection pool. |
|---|---|
| Default Value | 3600000 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Zero means idle connections never expire. |
abpm.archive.logdb.isolation.level
| Description | Controls the transaction locking behaviour for all statements issued by a connection. |
|---|---|
| Default Value | 1 |
| Possible Values | Either 1 or 2 |
| Selection Criteria | NA |
| Comments | Specify 1 for READ UNCOMMITTED and 2 for READ COMMITTED. |
abpm.archive.logdb.pool.maxStatements
| Description | JDBC's standard parameter for controlling statement pooling. |
|---|---|
| Default Value | 0 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Defines the total number of PreparedStatements a DataSource will cache. |
BACKEND DATABASE
Backend Connection Failure
abpm.jdo.connection.retryCount
| Description | Number of retries to connect to the backend database, if it is down |
|---|---|
| Default Value | -1 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Number of retries to connect to the backend database, if it is down. By default, it is set to infinite retries, as, if the backend database is down, then all GUI operations come to a standstill. |
abpm.jdo.connection.retryTimeInterval
| Description | The time interval (in seconds), between two retries of connecting to the backend server |
|---|---|
| Default Value | 30 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | The time interval between two retries of connecting to the backend server. |
LOG DATABASE
Log Connection Failure
abpm.log.connection.retryCount
| Description | Number of retries to connect to the log database server, if it is down |
|---|---|
| Default Value | -1 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Number of retries to connect to the log database, if it is down. By default, it is set to infinite retries, as, if the log database is down, then logs are not entered into the database, but stored into a file. |
abpm.log.connection.retryTimeInterval
| Description | The time interval (in seconds), between two retries of a connection to the log database server |
|---|---|
| Default Value | 30 |
| Possible Values | Any integer |
| Selection Criteria | NA |
| Comments | Indicates the time interval between two retries of connection to the log database server. |
abpm.log.recovery.log4jfile
| Description | The log file that contains data for table AU_LOG when connection to log database server is lost. |
|---|---|
| Default Value | KernelWebRunner.log |
| Selection Criteria | NA |
| Comments | The log file that contains data for the table AU_LOG when connection to log database server is lost. |
abpm.log.recovery.transactionDataFile
| Description | The log file that contains data for table AU_TRANSACTIONDATA when connection to log database server is lost |
|---|---|
| Default Value | transactiondata.log |
| Selection Criteria | NA |
| Comments | The log file that contains data for the table AU_TRANSACTIONDATA when connection to log database server is lost. |
abpm.log.recovery.taskLogFile
| Description | The log file that contains data for table AU_TASKLOGS when connection to log database server is lost |
|---|---|
| Default Value | tasklog.log |
| Selection Criteria | NA |
| Comments | The log file that contains data for the table AU_TASKLOGS when connection to log database server is lost. |
abpm.log.recovery.processVariableTrackerFile
| Description | The log file that contains data for table AU_PROCESSVARIABLETRACKER when connection to log database server is lost |
|---|---|
| Default Value | processVariableTracker.log |
| Selection Criteria | NA |
| Comments | The log file that contains data for the table AU_ PROCESSVARIABLETRACKER when connection to log database server is lost. |
abpm.log.recovery.temptransactionDataFile
| Description | The log file that contains data for table AU_TRANSACTIONDATA when connection to log database server is lost |
|---|---|
| Default Value | temp_transactiondata.log |
| Selection Criteria | NA |
| Comments | The log file that contains data for the table AU_TRANSACTIONDATA when connection to log database server is lost. |