Tuning the application server

Use this task to tune the application server.

Before you begin

Before you start this task, you must have specified the initial settings for the database, as described in Specifying initial database settings.

Why and when to perform this task

To ensure that the business process container can preform optimally, you need to adjust the server settings.

Steps for this task

  1. Estimate the application server resources that you need for each business process container.
    1. One data source, to read and write business process state information to a database: jdbc/BPEDB
    2. Calculate the maximum concurrency of transactions, t, for the process navigation by adding the following:
      • The maximum number of clients concurrently connected through the Business Process Choreographer API
      • The number of concurrent endpoints defined in the JMS activation specification BPEInternalActivationSpec
      • The number of concurrent endpoints defined in the JMS activation specification HTMInternalActivationSpec
      Note: To view the activation specifications for the process server, in the administrative console, click Resources > JMS Providers > Default messaging > JMS activation specification.
    3. Calculate the number of parallel JDBC connections required to the process server database, p = 1.1 * t
      Note: The value of p must not be greater than the number of connections allowed by the database.
    4. Calculate the number of parallel JDBC connections required to the messaging database, m = 2 * t + x, where x is the number of additional JMS sessions to allow for overloads situations where additional messages are generated and must be served
  2. Tune the JDBC provider settings for the process server database (BPEDB).
    1. Set Max Connections to the value p. The value of p must not be greater than the number of connections allowed by the database.
    2. Set the SQL Statement cache size to 500.
  3. Tune the JDBC provider settings for the messaging database.

    Set Max Connections to the value m.

  4. Tune the heap size.
    Here are some guidelines for the size of the server heap:
    • 256 MB is too low, and results in poor performance.
    • 512 MB is adequate as an initial heap size for many systems.
    • 1024 MB is a reasonable upper limit.
  5. Tune any services that are used by your business processes. Make sure that your supporting services are tuned to cope with the degree of concurrency and load demands that Business Process Choreographer makes on the service.

Result

The application server is tuned for improved performance.

Terms of use |

Last updated: Thu Apr 27 14:54:57 2006

(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)