WAS v8.5 > Tune performance > Tune Service integration

Tune messaging engine data stores

Obtain an overview of improving the performance of messaging engine data stores.

• Tune the JDBC data source of a messaging engine
• Controlling the memory buffers used by a messaging engine
• Share connections to benefit from one-phase commit optimization

Subtopics

• Tune the JDBC data source of a messaging engine
  The messaging engine needs to have the correct configuration for JDBC data source to achieve messaging performance on a service integration bus.
• Controlling the memory buffers used by a messaging engine
  Every messaging engine manages two memory buffers containing messages and message-related data. We can improve the interaction of a messaging engine with its data store by tuning the properties that set the sizes of the two buffers.
• Increasing the number of data store tables to relieve concurrency bottleneck
  Service integration technologies enables users to spread the data store for a messaging engine across several tables. In typical use this is unlikely to have a significant influence. However, if statistics suggest a concurrency bottleneck on the SIBnnn tables for a data store, you might try to solve the problem by increasing the number of tables.
• Tune one-phase commit optimization
  If we have configured your messaging engine to use a data store, we can achieve better performance by configuring both the messaging engine and container-managed persistent (CMP) beans to share the same data source.
• Tune the detection of database connection loss
  If a messaging engine is configured to use a data store and cannot connect to its data store, for example because the database containing the data store is not running, the messaging engine does not start. We can tune your system to increase the chance of a successful start of the messaging engine.

Subtopics

• Tune the JDBC data source of a messaging engine
  The messaging engine needs to have the correct configuration for JDBC data source to achieve messaging performance on a service integration bus.
• Controlling the memory buffers used by a messaging engine
  Every messaging engine manages two memory buffers containing messages and message-related data. We can improve the interaction of a messaging engine with its data store by tuning the properties that set the sizes of the two buffers.
• Increasing the number of data store tables to relieve concurrency bottleneck
  Service integration technologies enables users to spread the data store for a messaging engine across several tables. In typical use this is unlikely to have a significant influence. However, if statistics suggest a concurrency bottleneck on the SIBnnn tables for a data store, you might try to solve the problem by increasing the number of tables.
• Tune one-phase commit optimization
  If we have configured your messaging engine to use a data store, we can achieve better performance by configuring both the messaging engine and container-managed persistent (CMP) beans to share the same data source.
• Tune the detection of database connection loss
  If a messaging engine is configured to use a data store and cannot connect to its data store, for example because the database containing the data store is not running, the messaging engine does not start. We can tune your system to increase the chance of a successful start of the messaging engine.

Related concepts:

Data store performance

Related

Tune the JDBC data source of a messaging engine
Controlling the memory buffers used by a messaging engine

+

Search Tips   |   Advanced Search