Each business process container needs a JMS provider, and message
listener ports defined for it. This topic explains how to create these resources.
- Make sure that you know the password for a user ID that has the
authority to create WebSphere MQ queues.
- Change to the Business Process Choreographer directory: On Windows platforms, enter:
cd install_root\ProcessChoreographer
On
UNIX and Linux platforms, enter: cd install_root/ProcessChoreographer
- Configure the queue resources by running script config_queue_mq.jacl with
the appropriate parameters: On
Windows platforms, 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 and
Linux platforms, 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
- If you have problems using the script config_queue_mq.jacl,
you can also configure the resources
manually using the administrative console.
- You can check or change the configuration settings using the administrative
console.
The queue resources needed by the business process container have
been created.
Create and configure the scheduler.