Planning queue manager settings

Use this task to plan queue manager settings.

Why and when to perform this task

To achieve the best performance for long-running processes, tune the message queuing system for maximum performance of persistent messages.

If you use default messaging, follow the instructions given in Service integration in the WebSphere Application Server Network Deployment information center, to set up and tune the data stores for the messaging engines.

If you use the IBM® WebSphere® MQ messaging product, rather than the default messaging services, complete the following steps.

Steps for this task

  1. Tune MQ parameter settings.
    Tune the following MQ parameter settings:
    • Log file pages
    • Log buffer page
    • Log primary files
    • Log secondary files
    • Log default path
    • Maximum channels
    • Channel application bind type

    The default locations for both the persistent queue data and the MQ logs is the MQ installation directory. Put the data storage for the persistent queues and the WebSphere MQ logs on different disk drives. By changing the path to the log file to refer to another disk drive, you can change the location for the MQ logs. Make these changes before you create the queue managers for Business Process Choreographer.

  2. Tune WebSphere MQ service properties for Business Process Choreographer.
    These values must be set before you create the queue managers that are used by Business Process Choreographer. Set each parameter to its maximum value, as shown in the following table:
    Table 1. Tuning WebSphere MQ service properties for Business Process Choreographer
    Parameter Value Comment
    Log file pages 16384 On Windows® systems, not all versions of WebSphere MQ support setting the number of log file pages to 16384 by using the MQ administration tools. In this case, change the value of the Windows registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\
        CurrentVersion\Configuration\LogDefaults
    to:

    16384

    Log primary files 10
    Log secondary files 53
    Log buffer pages 512
  3. Tune the queue manager properties.
    Specify the queue manager properties for the maximum number of channels and the type of binding for the channel application, as shown in the following table:
    Table 2. Tuning queue manager properties
    Queue manager properties Value
    Maximum channels Use the default
    Channel application bind type FASTPATH

Result

Your queue manager is operating optimally.
Related tasks
Fine-tuning WebSphere MQ Messaging Provider

Terms of use |

Last updated: Tue Feb 21 17:59:22 2006

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