The messaging engine needs to have the correct configuration for
JDBC data source to achieve messaging performance on a service integration
bus.
Before you begin
Consider whether you must configure the connection pool for the
JDBC data source to achieve your requirements for messaging performance.
About this task
The messaging engine uses the connection pool to obtain its connections
to the database. With a heavy workload, a messaging engine might require a
large number of concurrent connections to avoid delays waiting for connections
to become available in the pool. For example, a very heavily loaded messaging
engine might need 50 or more connections. Complete the following steps to configure
the connection pool to meet your performance requirements:
Procedure
- Ensure that the configuration of your relational database management
system (RDBMS) permits the number of connections that you require.
Refer
to the documentation for your RDBMS for more information.
- Use the administrative console to set the connection pool parameters
for your data source.
Navigate to .
- Set Maximum connections to the number
of connections you require, for example, at least 50.
The default
number of connections is 10.
Tip: If your messaging engine times
out when requesting a database connection, check the error log. If the error
log contains error message CWSIS1522E, increase the number
of connections and ensure that the configuration of your RDBMS permits that
number of connections.
- Set Purge policy to
EntirePool
.
This policy enables the connection pool to release all connections when
the messaging engine stops.
Important: You
must set this value if the messaging engine can failover in a cluster.