WebSphere WebSphere Application Server Version 6.1.x Feature Pack for Web Services Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Increasing the number of item tables for a messaging engine when tables are not automatically created

If a concurrency bottleneck had occurred on the item tables, increasing the number of them will in turn increase the throughput of the messaging engine.

Before you begin
Before performing this task you must ensure that the messaging engine is using a data store, and its Create tables automatically option is set to False. The purpose of this task is to relieve concurrency bottleneck, which is documented in Increasing the number of data store tables to relieve concurrency bottleneck. For more information on the creation of tables consult Creating the tables.

Procedure

  1. Relevant performance monitoring tools show that the throughput of a messaging engine is inefficient.
  2. Use your database performance monitoring tools to examine lock statistics for the item tables for evidence of a bottleneck. Consult database documentation on how to interpret the locking statistics.
  3. Create tables and increase data store attributes. You can only increase the number of permanent tables or temporary tables, not decrease them.
  4. Stop and restart the WebSphere Application Server so that configuration changes take effect. The extra tables are used when the messaging engine restarts.
  5. Observe the effect on throughput and lock statistics by checking performance monitoring tools. Consider whether any improvement is sufficient and modifying the data store attributes further would be beneficial

Task topic

Terms of use | Feedback


Timestamp icon Last updated: 27 November 2008
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.wsfep.multiplatform.doc/tasks/tjm0025_.html

Copyright IBM Corporation 2004, 2008. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)