Note: | Typically, you will use the Settings > Extended screen from the Integration Server Administrator to update this file, but there might be times when you need to edit the file directly using a text editor. If you edit the file directly, you should first shut down the Integration Server before updating the file. After you make the changes, restart the server. |
This parameter... | Specifies... |
watt.server.db.connectionCache | How the server manages connections to a database. Specifying server tells the server to maintain a pool of connections for each database that is defined to the server through an alias. If a request cannot be satisfied because the pool has reached its maximum number of connections, the server blocks the request and tries again later. Specifying session tells the server to treat requests from each service individually. That is, when it receives a request, the server immediately requests a connection from the database. If the database has no available connections, the request fails. This is the default. Although enabling database connection pooling creates a pool for each database defined to your server, you can control the characteristics of each pool individually by using the Edit Alias Information screen of the Integration Server Administrator. For more information, see
Enabling Database Connection Pooling. |
watt.server.jdbc.defaultDriver | The name of the Java class for the driver you want to use to connect to databases when no driver name is supplied for a database alias. For more information, see
Identifying Database Aliases. |
watt.server.jdbc.driverList | A comma-delimited list of JDBC drivers you want the server to load when it initializes. There is no default. For more information, see Preloading JDBC Drivers at Server
Initialization. |