Customizing the WebSphere MQ JMS resources in a cluster

Use this task to customize the connection factory resources for business process containers that are in a cluster and use the WebSphere MQ JMS provider.

Why and when to perform this task

Do not perform this task if you are using default messaging. If you are using the WebSphere MQ JMS provider, perform the following steps for each application server in the cluster:

Steps for this task

  1. Open the connection factory page: Click Resources > JMS Providers > WebSphere MQ > Scope: Server > Apply > WebSphere MQ connection factories.
  2. Select the business process container connection factory BPECF and set the property values for the type of queue manager configuration that you are using:
    • For a central queue manager:
      Property Description
      Host The host name of the server that is hosting the central queue manager.
      Port The port number that the central queue manager is using.
      Transport Type Client
      Client ID The message channel agent (MCA) user ID to use. This is normally the owner or creator of the queue manager, typically on UNIX® and Linux® systems this is the root user, and on Windows® systems, the administrator user ID.
      CCSID If the central queue manager is running on a Linux or UNIX system, use the value 819. If the central queue manager is running on a Windows system, use the value 437
    • For a cluster of queue managers:
      Property Description
      Transport Type Bindings or Client
      Queue Manager The name of the server get queue manager.

      When using WebSphere® MQ, the local bindings transport type is slightly faster than using the client transport type, but has the effect that you must stop the entire application server to stop the local WebSphere MQ queue manager. If you specify Client, you must also provide the host name and port number for the get queue manager.

  3. Select the business process container connection factory BPECFC and set the property values for the type of queue manager configuration you are using:
    • For a central queue manager:
      Property Description
      Host The host name of the server that is hosting the central queue manager.
      Port The port number that the central queue manager is using.
      Transport Type Client
      Client ID The message channel agent (MCA) user ID to use. This is normally the owner or creator of the queue manager, typically on UNIX and Linux systems this is the root user, and on Windows systems, the administrator user ID.
      CCSID If the central queue manager is running on a Linux or UNIX system, use the value 819. If the central queue manager is running on a Windows system, use the value 437.
    • For a cluster of queue managers on Linux and UNIX:
      Property Description
      Host The host name of the application server node.
      Port The port number used by the put queue manager of this application server's .
      Transport Type Client
      Client ID The message channel agent (MCA) user ID to use. This is normally the owner or creator of the queue manager, typically this is the root user.
      CCSID 819
    • For a cluster of queue managers on Windows systems:
      Property Description
      Transport Type Bindings or Client
      Queue Manager The name of the server put queue manager.

      When using WebSphere MQ, the local bindings transport type is slightly faster than using the client transport type, but has the effect that you must stop the entire application server to stop the local WebSphere MQ queue manager. If you specify Client, you must also provide the host name and port number for the put queue manager.

  4. Select the human task manager connection factory HTMCF and set the property values for the type of queue manager configuration that you are using:
    • For a central queue manager:
      Property Description
      Host The host name of the server that is hosting the central queue manager.
      Port The port number that the central queue manager is using.
      Transport Type Client
      Client ID The message channel agent (MCA) user ID to use. This is normally the owner or creator of the queue manager, typically on UNIX and Linux systems this is the root user, and on Windows systems, the administrator user ID.
      CCSID If the central queue manager is running on a Linux or UNIX system, use the value 819. If the central queue manager is running on a Windows system, use the value 437
    • For a cluster of queue managers:
      Property Description
      Transport Type Bindings or Client
      Queue Manager The name of the server get queue manager.

      When using WebSphere MQ, the local bindings transport type is slightly faster than using the client transport type, but has the effect that you must stop the entire application server to stop the local WebSphere MQ queue manager. If you specify Client, you must also provide the host name and port number for the get queue manager.

Result

The connection factories for the business process containers have been installed in the cluster and are configured.

What to do next

Continue configuring in the parent topic at step 20.

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)