Database Connection Configuration Reference

Configure the database connection for database concepts using the CDD file.

Studio Settings

Add the project paths to all JDBC resources used for database concepts, and configure other properties as desired. See Configuring the Database Connection for the procedure.

Property Dafault Value Description
Check Interval 60 The time interval (in seconds) between two consecutive checks of database connection status.
Inactivity Timeout 0 The time period (in seconds) after which the database connection in the pool closes unused connections.
Initial Size 5 The initial pool size in number of connections.
Max Size 5 Maximum number of connections allowed.
Min Size 5 Minimum number of connections to retain.
Property Check Interval 900 After this interval (in seconds), all connections which are already marked as inactive are flushed to the pool.
Retry Count -1 Specifies behavior for reconnecting to the database.
  • If set to 0, the engine does not attempt to reconnect.
  • If set to -1, the engine retries with no limit.
  • If set to an integer greater than 0, the engine tries to connect for the specified number of times.

When a connection is lost or stale, it cannot be recovered, and engine restart would be required.

Wait Timeout 1 The maximum time (in seconds) to wait to retrieve a connection from the connection pool.
Database URIs   Required. Add the project path of all JDBC shared resources used for database concepts in the project. For example: /SharedResources/DBConceptsConnection.sharedjdbc

Properties

These configuration properties can be added in the CDD file. For more details on the CDD configuration see TIBCO BusinessEvents Configuration Guide.

Property Default Value Description
be.dbconcepts.connections.checkall false Specifies whether BusinessEvents checks all connections for validity in DBConcepts. The values are:
  • true - All connections are checked in DBConcepts and if any connection fails then the connection pool is refreshed.
  • false - All connections are not checked in DBConcepts, and only if the test connection fails then the connection pool is refreshed.