Creating clustered queue managers and queues for the business process container

Why and when to perform this task

If you are creating a WebSphere cluster setup of process choreographer using a WebSphere MQ cluster, you must create the queue managers, queues, cluster, repositories, channels, and listeners.

Steps for this task

  1. If your WebSphere cluster consists of UNIX nodes, perform the following actions on each node:
    1. Make sure that your user ID has the authority to create WebSphere MQ queues.
    2. Create the "get" and "put" queue managers, make them members of the WebSphere MQ cluster, and create the queues by entering the commands:
      cd install_root/ProcessChoreographer
      createQueues.sh getQueueManager clusterName putQueueManagerName 

      where:

      getQueueManager
      The unique name to give to the "get" queue manager. This queue manager will host all the local queues.
      clusterName
      The name of the WebSphere MQ cluster.
      putQueueManager
      The unique name to give to the "put" queue manager.

      If the queue managers already exist they are used. If the queue managers do not exist they are created and used.

    3. Start the WebSphere MQ command processor by entering the command:
      runmqsc getQueueManager
    4. For complex setups, it is recommended to enable remote administration of the queue manager by entering the following MQ command:
      DEFINE CHANNEL('SYSTEM.ADMIN.SVRCONN') TYPE(CHLTYPE)
    5. If this queue manager is to be a repository for the WebSphere MQ cluster enter the MQ command:
      ALTER QMGR REPOS('clusterName') REPOSNL(' ')
    6. Define a sender and a receiver channel for the queue manager to each repository that is not hosted on this machine, by entering the following MQ commands.
      For each cluster receiver channel:
      DEFINE CHANNEL('TO.repositoryQueueManager.TCP') +
           CHLTYPE(CLUSRCVR) +
           CLUSTER('clusterName') +
           CLUSNL(' ') +
           CONNAME('repositoryIP-Address(port)') +
           DESCR('Cluster receiver channel at repositoryQueueManager TCPIP') +
           MAXMSGL(4194304) +
           TRPTYPE(TCP) +
           MCAUSER('principal') +
           REPLACE

      For each cluster sender channel:

      DEFINE CHANNEL('TO.repositoryQueueManager.TCP') +
           CHLTYPE(CLUSSDR) +
           CONNAME('repositoryIP-Address(port)') +
           CLUSTER('clusterName') +
           CLUSNL(' ') +
           DESCR('Cluster sender channel to repositoryQueueManager TCPIP') +
           MAXMSGL(4194304) +
           TRPTYPE(TCP) +
           MCAUSER('targetPrincipal') +
           REPLACE +
           NPMSPEED (NORMAL)

      where:

      repositoryQueueManager
      The name of the queue manager hosting a repository.
      clusterName
      The name of the WebSphere MQ cluster of which all the queue managers are a member.
      repositoryIP-Address
      The IP address of the node where the repository queue manager resides.
      port
      The IP port that the repository queue manager is using.
      principal, targetPrincipal
      The MCAUSER to use for the receive and send channels. For more information about this value refer to the WebSphere MQ documentation.

    7. For each queue manager, start a listener by entering the MQ command:
      runmqlsr -t tcp -p port -m QueueManager
  2. If your WebSphere cluster consists of Windows nodes, perform the following actions on each node:
    1. Make sure that your user ID has the authority to create WebSphere MQ queues.
    2. Create the "get" queue manager, make it a member of the WebSphere MQ cluster, and create the queues by entering the commands:
      cd install_root\ProcessChoreographer
      createQueues.bat queueManager clusterName putQueueManager

      where:

      getQueueManager
      The unique name to give to the "get" queue manager.
      clusterName
      The name of the WebSphere MQ cluster that the WebSphere cluster nodes will use.
      putQueueManager
      The unique name to give to the "put" queue manager.

      If the queues already exist they are used. If the queues do not exist, they are created and used.

    3. Start the WebSphere MQ command processor by entering the command:
      runmqsc queueManager
    4. For complex setups, it is recommended that you enable remote administration of the queue manager by entering the following MQ command:
      DEFINE CHANNEL('SYSTEM.ADMIN.SVRCONN') TYPE(CHLTYPE)
    5. If this queue manager is to be a repository for the WebSphere MQ cluster enter the MQ command:
      ALTER QMGR REPOS('clusterName') REPOSNL(' ')
    6. Define a sender and a receiver channel for the queue manager to each repository that is not hosted on this machine, by entering the following MQ commands.
      For each cluster receiver channel:
      DEFINE CHANNEL('TO.repositoryQueueManager.TCP') +
           CHLTYPE(CLUSRCVR) +
           CLUSTER('clusterName') +
           CLUSNL(' ') +
           CONNAME('repositoryIP-Address(port)') +
           DESCR('Cluster receiver channel at repositoryQueueManager TCPIP') +
           MAXMSGL(4194304) +
           TRPTYPE(TCP) +
           MCAUSER('principal') +
           REPLACE

      For each cluster sender channel:

      DEFINE CHANNEL('TO.repositoryQueueManager.TCP') +
           CHLTYPE(CLUSSDR) +
           CONNAME('repositoryIP-Address(port)') +
           CLUSTER('clusterName') +
           CLUSNL(' ') +
           DESCR('Cluster sender channel to repositoryQueueManager TCPIP') +
           MAXMSGL(4194304) +
           TRPTYPE(TCP) +
           MCAUSER('principal') +
           REPLACE +
           NPMSPEED (NORMAL)

      where:

      repositoryQueueManager
      The name of the queue manager hosting a repository.
      clusterName
      The name of the WebSphere MQ cluster to which all the queue managers are a member.
      repositoryIP-Address
      The IP address of the node where the repository queue manager resides.
      port
      The IP port that the repository queue manager is using.
      principal
      The MCAUSER to use. For more information about this value, refer to the WebSphere MQ documentation.

    7. For each queue manager, start a listener by entering the MQ command:
      runmqlsr -t tcp -p port -m QueueManager
  3. To verify the status of the channels on a machine, enter the MQ command:
    display chstatus(*)

Results

The queue manager, queues, cluster, repositories, channels, and listeners exist.




Searchable topic ID:   t2creqNDcluster
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/t2creqNDcluster.html

Library | Support | Terms of Use | Feedback