Configuring a local connection to WebSphere MQ

You can configure a local connection to WebSphere® MQ by specifying the Connection properties on the MQInput, MQOutput, MQGet, or MQReply node.

Before you begin

Complete the following tasks:
  • Read the topic Configuring connections to WebSphere MQ.
  • Ensure that the required queue manager has been created, and that the user ID that is running the integration node has the necessary permissions to access the queue manager.
  • Decide how you want to connect to the queue manager. You can either configure the connection properties on the MQ Connection tab of the MQ node, or you can use an MQEndpoint policy on the Policy tab. The steps in this topic explain how to configure connections by using the properties on the MQ Connection tab. The properties that you can set in a policy are listed in the MQ node topics, such as the MQInput node; for more information about using an MQEndpoint policy, see MQEndpoint policy.

About this task

WebSphere MQ is available as a separate installation package, and your IBM Integration Bus license entitles you to install and use WebSphere MQ with IBM Integration Bus. For more information, see Enhanced flexibility in interactions with WebSphere MQ and Installing WebSphere MQ.

If your WebSphere MQ queue manager is running on the same machine as your integration node, you can specify a local connection to enable your IBM Integration Bus message flows to access messages on WebSphere MQ queues.

If an MQ node does not have connection properties set on the node or in an MQEndpoint policy, it will use the connection details of the queue manager that is associated with the integration node at run time. If no connection details are set on the node or in a policy, and if no queue manager is specified for the integration node, the message flow cannot deploy.

Procedure

  1. On the MQ Connection tab, select the Local queue manager property to specify a local connection to a named local queue manager.
    If you do not set any MQ Connection properties, the queue manager that is specified on the integration node is used by default. If the MQ Connection properties are not set and no queue manager is specified on the integration node, the flow fails to deploy.
  2. Specify the name of the required queue manager in the Destination queue manager name property.
  3. Optional: Configure the connection to use a security identity for authentication. For more information, see Connecting to a secured WebSphere MQ queue manager.

What to do next

For MQInput nodes, the connection is made when the flow is deployed. For MQOutput, MQGet, and MQReply nodes, the connection is made when the first message is sent or received.

If you later decide that you want to control connection properties by using an MQEndpoint policy, property values that are set on the MQ Connection tab are ignored when a policy is attached to the message flow node. If you want to revert to using the connection details of the queue manager that was specified on the integration node, remove the settings for the Policy URL and MQ Connection tab properties.