The parameters in the DB_CONNECTIVITY section of the file govern InterChange Server's overall interactions with the database management system (DBMS).
Specifies how many simultaneous connections InterChange Server can establish with DBMS servers. This parameter governs InterChange Server's total number of connections; similar parameters in the Event Management, Repository, Transactions, and Flow Monitoring sections govern the number of connections allotted to specific services.
If you do not specify a value for this parameter, InterChange Server uses as many connections as it needs, timing them out after they become idle for the default of two minutes or the time specified using the IDLE_TIMEOUT parameter.
Example: MAX_CONNECTIONS = 100
MAX_CONNECTIONS = 20
Specifies the maximum number of connection pools that InterChange Server creates for connections in InterChange Server's connection cache. The server currently creates one connection pool each for the repository, event management, transaction, and flow monitoring databases.
When creating relationships between objects, you can specify the database to be used for storage of the relationship runtime data. Connections to this database are managed in the same way as the repository, event management, transaction, and flow monitoring databases. If you specify more databases than the number used in the MAX_CONNECTION_POOLS parameter, an error message appears stating that the maximum number of connection pools has been reached.
Use the MAX_CONNECTION_POOLS parameter to accommodate the number of databases you are using. The minimum value is eight.
Example: MAX_CONNECTION_POOLS = 60
MAX_CONNECTION_POOLS = 50
Specifies the maximum number of times a transaction will be retried before throwing an exception. The recommended retry count is 5. If the value is set to 0, a warning will be printed by the InterChange Server at start up, and if a deadlock occurs, the transaction will not be retried. This can cause the InterChange Server to shut down.
Use the DEADLOCK_RETRY_INTERVAL parameter to specify the time to wait between retries. The recommended time is 20 seconds.
MAX_DEADLOCK_RETRY_COUNT = 5
Specifies the time to wait between retries. The recommended time is 20 seconds. Setting the retry time too high will slow the system down unnecessarily.
Set this value in the InterchangeSystem.cfg file in the [DB_CONNECTIVITY] section.
DEADLOCK_RETRY_INTERVAL = 20
Specifies the maximum time a connection between InterChange Server and DBMS server can be idle, before the connection is disconnected. This parameter works with the MAX_CONNECTIONS parameter in that it frees up idle connections and returns them to the available connections cache.
If you do not specify a value for this parameter, InterChange Server uses the default of two minutes. The value you specify is in minutes.
Example: IDLE_TIMEOUT = 4
IDLE_TIMEOUT = 2
Specifies an output file for JDBC logging. The file is placed in the $HOME/IBM/WebSphereICS/bin directory, unless you specify a full path.
If the parameter does not appear in the file, or if it is commented out, logging does not take place.
Example:
JDBC_LOG = jdbc.out (in the $HOME/IBM/WebSphereICS/bin directory)
There is no default value for this parameter.
Specifies the database server type. The value can be DB2, SQLSERVER (Microsoft SQL Server) or ORACLE (Oracle Server):
UNIX |
---|
You can use Oracle Server, DB2 Server, or Microsoft SQL Server. The only compatible database servers on a UNIX machine are Oracle and DB2; however, you can run Microsoft SQL Server on a Windows machine with your InterChange Server on UNIX. |
Linux |
---|
You can use Oracle Server, DB2 Server, or Microsoft SQL Server. The only supported database server on a Linux machine is DB2; however, you can run Oracle or Microsoft SQL Server on a different machine with your InterChange Server on Linux. |
Windows |
---|
You can use Oracle Server, DB2 Server, or Microsoft SQL Server for your database server. |
Example:
DBMS = ORACLE DBMS = SQLSERVER DBMS = DB2
Specifies the name of the driver that supports the DBMS. The
possible values are:
Table 35. Drivers used with supported DBMS Types
DBMS type | Driver name | Driver class name |
---|---|---|
MS SQL Server | IBM-branded Type 4 Driver | com.ibm.crossworlds.jdbc. sqlserver.SQLServerDriver |
Oracle | IBM-branded Type 4 Driver | com.ibm.crossworlds.jdbc.
oracle.OracleDriver |
DB2 Server | DB2 JDBC type 2 driver | COM.ibm.db2.jdbc.app.DB2Driver |
Specifies the maximum number of times that the server will try to reconnect to the database after the connection is found to be broken. The recommended retry count is 3. If the value is set to 0, this is equivalent to switching off the database connectivity resilience.
Use the DB_CONNECT_INTERVAL parameter to specify the time to wait between retries. The recommended time is 60 seconds.
This parameter and DB_CONNECT_INTERVAL determine the connectivity resilience for databases used by relationships. These two parameters are also used to set the default values for the equivalent parameters under other database-related sections (such as event management, repository, transaction management, flow monitoring, and user registry). If the two parameters are not explicitly defined under those sections, the values defined in this section will be used.
DB_CONNECT_RETRIES = 3
Specifies the time to wait between database connection retries. The recommended time is 60 seconds.
Set this value in the InterchangeSystem.cfg file in the [DB_CONNECTIVITY] section. The value you specify is in seconds.
DB_CONNECT_INTERVAL = 60