Enabling Database Connection Pooling

For greater scalability you can pool database connections. With this feature, the server creates a pool of connections for each database defined to the webMethods Integration Server. The server maintains these connections, creating and dropping them as needed.

The pool controls the number of connections a server can have to the database at any given time. For example, if your database allows 50 connections and you have five servers that connect to the database, you can limit each server’s database connection pool to 10. This way, the number of connections to the database never exceeds 50 and no requests will be rejected due to lack of available slots. If the number of connection requests to a server exceeds 10, that server will block the request and try it again later. The request will not be rejected.

Without database connection pooling, each server will obtain as many connections to the database as requested until the database reaches its limit of 50. Subsequent requests will be rejected by the database until the number of database connections drops down below 50.

When you enable database connection pooling, it applies to all databases defined to the server. In other words, the server will maintain a connection pool for each database for which an alias is defined. You can, however, control the characteristics of each pool individually. For example, you might specify more connections for a large, busy database than for a small, relatively quiet one.

Use the following procedure to enable database connection pooling for your server.

2. Go to Settings > Extended. The server displays a page that lists configuration parameters specified in the server.cnf file.

If the Extended Settings lists watt.server.db.connectionCache=server then connection pooling is already enabled for your server.

If the watt.server.db.connectionCache property is not set to server or does not appear in the Extended Settings list, click Edit Extended Settings and specify the following:

5. If you want to change the alias parameters for the minimum and maximum number of connections in the connection pool and the connection expiration time, see Updating Information for Database Aliases.