Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the default messaging provider > Interoperating with a WebSphere MQ network > Use WebSphere MQ links to connect a bus to a WebSphere MQ network

Create a new WebSphere MQ link

A WebSphere MQ link provides a server to server channel connection between a service integration bus and a WebSphere MQ queue manager or queue-sharing group, which acts as the gateway to the WebSphere MQ network. Use the foreign bus connection wizard to create a foreign bus and link it to the WebSphere MQ network through a WebSphere MQ link.

Decide which method to use to configure these resources. We can create a new WebSphere MQ link by using the admin console as described in this task, or you can create a new WebSphere MQ link by using wsadmin. The following resources must be defined in WAS:

• A service integration bus to connect from (known as the local bus) with at least one bus member.

The following resources must be defined in WebSphere MQ:

• A queue manager or queue-sharing group, which acts as the gateway to the WebSphere MQ network.
• A listener that is configured and running.
• (optionally) A sender channel to receive messages on the local bus, a receiver channel to send messages from the local bus, or both.
• (For publish-subscribe messaging) A topic and input queue for broker publish-subscribe flow.

You use the foreign bus connection wizard to connect a bus and a WebSphere MQ network. We can configure the connection for either point-to-point or publish-subscribe messaging.

Specifically, the wizard helps you configure the following resources:

• The bus and messaging engine on which the WebSphere MQ link is defined.
• The foreign bus that represents the WebSphere MQ network.
• The WebSphere MQ link.
• (Optionally) The sender and receiver channels and protocol. Using the wizard you can choose to define no channels (and add them afterward), or one channel if your WebSphere MQ link is to be one-way, or both channels.
• (Optionally) Security for messages flowing across the link.
• (Optionally) A publish/subscribe broker profile and associated topic mappings, to allow publication and subscription with a broker in the WebSphere MQ network.

The wizard does not ask you to set all possible properties of a WebSphere MQ link, and many of the properties are set to default values. We can fine tune these properties afterward if necessary, by modifying the WebSphere MQ link.

For a sample configuration showing a systems view of the setup for a WebSphere MQ link, see WebSphere MQ link sample configuration.

Procedure

1. Use the foreign bus connection wizard to connect a bus and a WebSphere MQ network to use point-to-point messaging or publish-subscribe messaging.

   A WebSphere MQ link is created and configured as part of the action of the wizard.

   We can subsequently convert a point-to-point connection to a publish/subscribe connection, by adding a publish/subscribe broker on the WebSphere MQ link for the connection.

2. Optional: Modify the new WebSphere MQ link.

   When you create a new WebSphere MQ link, the following properties are set to default values:

   • Description
   • Adoptable
   • Exception destination

   • Initial state
   • Nonpersistent message speed

   We can fine tune these properties by modifying the link.

3. Optional: Add or modify the WebSphere MQ receiver channel.

   If you did not choose to Enable Service integration bus to WebSphere MQ message flow in the foreign bus connection wizard, we have not yet defined a WebSphere MQ receiver channel. If you did choose this option in the wizard, we have defined the receiver channel name, host name and communication port, and the wizard has used default values for the following properties:

   • Inbound nonpersistent message reliability

   • Inbound persistent message reliability
   • Prefer queue points local to this link's messaging engine

   • Initial state

   We can fine tune these properties by modifying the channel.

4. Optional: Add or modify the WebSphere MQ sender channel

   If you did not choose to Enable WebSphere MQ to Service integration bus message flow in the foreign bus connection wizard, we have not yet defined a WebSphere MQ sender channel. If you did choose this option in the wizard, we have defined the sender channel name, host name, communication port and transport chain, and the wizard has used default values for the following properties:

   • Disconnect interval
   • Short retry count
   • Short retry interval
   • Long retry count
   • Long retry interval

   • Initial state

   We can fine tune these properties by modifying the channel.

Message exchange through a WebSphere MQ link
High availability of messaging engines that are connected to WebSphere MQ
Configure foreign bus connections
Default messaging provider unified connection factory [Settings]
WebSphere MQ link [Settings]
WebSphere MQ link routing properties [Settings]

+

Search Tips   |   Advanced Search