Type of database that hosts the eMessage system tables.

Name of the database schema for the eMessage system tables. This is the same as the schema name for the Campaign system tables.

JDBC driver for system tables as defined in your Campaign web server.

JDBC connection URI for system tables as defined in your Campaign web server.

Use this property to specify an IBM® EMM user that will be allowed to access the eMessage system tables.

Any user defined in the Marketing Platform. This should typically be the name of the system user for Campaign

Use this property to specify the data source that defines login credentials for the database that contains the eMessage system tables. This can be the same as the data source for the Campaign system tables.

A Marketing Platform data source associated with the IBM® EMM user you specify in asmUserForDBCredentials

The data source specifies a database user and credentials used to access the eMessage system tables. If the default schema for the database user is not the schema that contains the system tables you must specify the system table schema in the JDBC connection used to access the system tables.

When the database connection pool runs out of connections, the number of new connections eMessage creates for the system tables. eMessage creates new connections up to the number specified in poolMaxSize.

The number of seconds eMessage waits between testing idle connections to the eMessage system tables for activity.

The maximum number of connections eMessage makes to the system tables. A value of zero (0) indicates there is no maximum.

The minimum number of connections eMessage makes to the system tables.

The maximum number of statements that eMessage stores in the PrepareStatement cache per connection to the system tables. Setting poolMaxStatements to zero (0) disables statement caching.

The number of seconds eMessage maintains an idle database connection before dropping the connection.

If poolIdleTestPeriod is greater than 0, eMessage tests all idle, pooled, but unchecked-out connections, every timeout number of seconds.

If poolIdleTestPeriod is greater than timeout, the idle connections are dropped.