Configuring the queue resources for the business process container using WebSphere MQ

Why and when to perform this task

Each business process container needs a JMS provider, and message listener ports defined for it. This topic explains how to create these resources.

Steps for this task

  1. Make sure that you know the password for a user ID that has the authority to create WebSphere MQ queues.
  2. Change to the process choreographer directory:
    On Windows, enter:
    cd install_root\ProcessChoreographer
    On UNIX systems, enter:
    cd install_root/ProcessChoreographer
  3. Configure the queue resources by running script config_queue_mq.jacl with the appropriate parameters:
    On Windows, enter:
    install_root\bin\wsadmin -f  config_queue_mq.jacl
        [-node <nodeName>] -server <serverName>
        -mqPath <MQPath> [-qmName <queue manager name>] 
        [-qmNamePut <cluster queue manager name>
        [-internalQueue <internalQueueName>] [-apiQueue <apiQueueName>] 
        [-holdQueue <holdQueueName>] [-retentionQueue <retentionQueueName>]
    For example, for a Windows configuration based on the defaults:
    install_root\bin\wsadmin -f config_queue_mq.jacl
        -server server1 -mqPath C:\Progra~1\MQSeries 
    On UNIX systems, enter:
    install_root/bin/wsadmin.sh -f config_queue_mq.jacl 
        [-node <nodeName>] -server <serverName>
        -mqPath <MQPath> [-qmName <queue manager name>] 
        [-qmNamePut <cluster queue manager name>]
        [-internalQueue <internalQueueName>] [-apiQueue <apiQueueName>] 
        [-holdQueue <holdQueueName>] [-retentionQueue <retentionQueueName>]
    For example, for an AIX configuration based on the defaults:
    install_root/bin/wsadmin.sh -f  config_queue_mq.jacl
    	 -server server1 -mqPath /usr/mqm
    The default values for the optional parameters are:
    node
    <local node>
    qmName
    WAS_<nodeName>_<serverName>
    qmNamePut
    WAS_<nodeName>_<serverName>. This parameter is only required if you are configuring a cluster setup that uses a WebSphere MQ cluster with separate "put" and "get" queue managers.
    internalQueueName
    BPEIntQueue
    apiQueueName
    BPEApiQueue
    holdQueueName
    BPEHldQueue
    retentionQueueName
    BPERetQueue
  4. If you have problems using the script config_queue_mq.jacl, you can also configure the resources manually using the administrative console.
  5. You can check or change the configuration settings using the administrative console.

Results

The queue resources needed by the business process container have been created.

What to do next

Create and configure the scheduler.




Searchable topic ID:   t2coqjms
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/workflow/tasks/t2coqjms.html

Library | Support | Terms of Use | Feedback