DBMS connectivity properties
The Transaction Server uses a database management system (DBMS) for data management. The
following table shows the properties that are used to configure connectivity to the DBMS.
| Property | Default value | Range | Description |
|---|---|---|---|
| dbName | jdbc:db2://%DBHOST%:%DBPORT%/%DBNAME% |
N/A | FTM
database name. Use a database that is available on the Transaction Server, such as, MYFTMDB, or refer to a database on another server by using the full URL. A full
URL is specified as jdbc:db2://dbserver.example.com[:port]//MYFTMDB where:
Notes:
|
| dbSchema | %DBSCHEMA% | N/A | Name of the schema under which the FTM database was installed. |
| dbConnectId | %DBUSER% | N/A | User ID that is used for all database connectivity. This user ID requires connect access to the database and insert, delete, update, and select access to all FTM database tables. If not specified, the current signed-on user ID and password are used. |
| dbConnectPwd | %DBPASS% | N/A | Password for the dbConnectId user ID. |
| dbConnectionIdleTimeout | 300000 | 5000-7200000 | The timeout, in milliseconds, that the Transaction Server connection monitor waits between connection invocation usage before it is reported as an abandoned connection. This value is ignored if dbConnectionMode is set to standard. |
| dbConnectionInUseTimeout | 60000 | 1000-1800000 | The timeout, in milliseconds, that the Transaction Server connection monitor waits during a connection invocation before it is reported as a deadlock connection. This value is ignored if dbConnectionMode is set to standard. |
| dbConnectionMode | standard | N/A | Configures the Transaction Server to use a specific type of database connection.
The following database connection types are available:
|
| dbConnectionRefreshTimer | 2 hours | N/A | When a database connection is idle for this amount of time, the Transaction Server tests to see whether it must be refreshed. Refreshing might be necessary if the connection is closed or if its remote connection was ended by a system timeout. In this situation, the connection is referred to as stale. Refreshing involves discarding the old database connection and replacing it with a new one. The connection is only refreshed if Transaction Server determines it is stale. |
| dbConnectionTracing | false | true/false | Turns on verbose mode in the database connection debug mode. This option increases the number of messages that are logged during database debugging, showing all created statements and more. This option is ignored if dbConnectionMode is set to standard. |
| dbConnectionWaitTime | 1000 | 10-120000 | The length of time that the Transaction Server waits for a connection to the DBMS. |
| dbExceptionMonitoring | false | true/false | Turns on database exception monitoring. When specified as true, debug connections output extra logs that are related to certain database exceptions to aid in debugging. This value is ignored if dbConnectionMode is set to standard. |
| dbExecutionStackSize | 16 | 4-1024 | Specifies the number of SQL statement executions that are retained for exception monitoring. This option is useful when debugging database deadlock and read timeout exceptions. This value is ignored if dbConnectionMode is set to standard or dbExceptionMonitoring is set to false. |
| dbLoginTimeout | 1000 | 10-120000 | The length of time that the Transaction Server waits to log on to the DBMS. |
| enableSQLCheckData | false | true/false | Enables detailed SQL tracing for Transaction Server. |