Default Value

No

Possible Values

Yes/No

Selection Criteria

To activate this property after any change, you need to restart the Adeptia Suite server.

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 Suite not on individual Data Mapper applet.

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 Suite's environment.

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.

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.

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.

Default Value

yes

Possible Values

Yes/No

Comments

To activate this property after any change, you need to Restart Server.

Default Value

5000

Possible Values

Any valid positive integer.

Comments

To activate this property after any change, you need to restart the Adeptia Suite server.

Default Value

7200

Possible Values

Any valid positive integer.

Comments

To activate this property after any change, you need to restart the Adeptia Suite server.

Default Value

86400

Possible Values

Any valid positive integer.

Comments

To activate this property after any change, you need to restart the Adeptia Suite server.

Default Value

3

Possible Values

Any integer

Selection Criteria

NA

Comments

Number of retries to connect to the mbean server, if it is down

Default Value

2000

Possible Values

Any integer

Selection Criteria

NA

Default Value

yes

Possible Values

yes/no

Selection Criteria

It should always be enabled to optimize the connection with backend database.

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.

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.

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.

Default Value

3600000

Possible Values

Any integer

Selection Criteria

NA

Default Value

1

Possible Values

Either 1 or 2

Selection Criteria

NA

Comments

Specify 1 for READ UNCOMMITTED and 2 for READ COMMITTED.

Default Value

com.adeptia.indigo.pool.datasources.c3p0.connectionCustomizer.IsolationLevelBackendConnectionCustomizer

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.

Default Value

NA

Comments

Works when the abpm.jdo.testOnBorrow property is set as true.

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.

Default Value

yes

Possible Values

yes/no

Selection Criteria

NA

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.

Default Value

20

Possible Values

Any positive integer/ 0 to create none

Default Value

600000

Possible Values

Any positive integer/ -1 to wait indefinitely

Default Value

3600000

Possible Values

Any integer

Selection Criteria

NA

Comments

Zero means idle connections never expire.

Default Value

1

Possible Values

Any integer

Selection Criteria

NA

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.

Default Value

NA

Possible Values

NA

Comments

Works when the abpm.logdb.pool.testOnBorrow property is set as true.

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.

Default Value

25

Possible Values

Any integer

Selection Criteria

NA

Default Value

5

Possible Values

Any integer

Selection Criteria

NA

Default Value

600000

Possible Values

Any integer

Selection Criteria

NA

Default Value

3600000

Possible Values

Any integer

Selection Criteria

NA

Comments

Zero means idle connections never expire.

Default Value

1

Possible Values

Either 1 or 2

Selection Criteria

NA

Comments

Specify 1 for READ UNCOMMITTED and 2 for READ COMMITTED.

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.

Default Value

NA

Selection Criteria

NA

Comments

It works when the abpm.webrunner.jdo.testOnBorrow property is set as true.

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.

Default Value

25

Possible Values

Any integer

Selection Criteria

NA

Comments

Depends on the maximum number of connection allowed by the log database server.

Default Value

5

Possible Values

Any integer

Selection Criteria

NA

Comments

Any positive integer/ 0 to create none

Default Value

600000

Possible Values

Any integer

Selection Criteria

NA

Comments

Any positive integer/ -1 to wait indefinitely

Default Value

3600000

Possible Values

Any integer

Selection Criteria

NA

Comments

Zero means idle connections never expire.

Default Value

1

Possible Values

Any integer

Selection Criteria

NA

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.

Default Value

NA

Selection Criteria

NA

Comments

It works when the abpm.webrunner.logdb.pool.testOnBorrow property is set as true.

Default Value

0

Possible Values

Any integer

Comments

Defines the total number of PreparedStatements a DataSource will cache.

Default Value

yes

Possible Values

Yes/no

Default Value

3

Possible Values

Any integer

Default Value

0

Possible Values

Any integer

Default Value

600000

Possible Values

Any integer

Selection Criteria

NA

Default Value

3600000

Possible Values

Any integer

Selection Criteria

NA

Comments

Zero means idle connections never expire.

Default Value

1

Possible Values

Either 1 or 2

Selection Criteria

NA

Comments

Specify 1 for READ UNCOMMITTED and 2 for READ COMMITTED.

Default Value

0

Possible Values

Any integer

Selection Criteria

NA

Comments

Defines the total number of PreparedStatements a DataSource will cache.

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.

Default Value

30

Possible Values

Any integer

Selection Criteria

NA

Comments

The time interval between two retries of connecting to the backend server.

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.

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.

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.

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.

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.

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.

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.