WAS v8.5 > Administer applications and their environment > Welcome to administering Service integration > Administer service integration buses > Configure buses > Connect buses > Configure foreign bus connections

Connect a bus and a WebSphere MQ gateway queue manager to use point-to-point messaging

We can connect a service integration bus to a WebSphere MQ queue manager or (for WebSphere MQ for z/OS ) queue sharing group to send or receive messages using point-to-point messaging.

One way to do this is to create a foreign bus connection, where the WebSphere MQ queue manager or queue-sharing group is configured as a foreign bus.

To connect a service integration bus and a WebSphere MQ queue manager or queue-sharing group to use point-to-point messaging, the following resources must be defined in WAS:

• A service integration bus to connect from, known as the local bus. The bus must have 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.
• A sender channel (to receive messages on the local bus), a receiver channel (to send messages from the local bus), or both.

In point-to-point messaging, the sending application specifies the target destination for the message. To receive the message, the receiving application specifies the same destination when it communicates with the messaging provider. Therefore, there is a one-to-one mapping between the sender and receiver of a message.

This task describes one way to achieve point-to-point messaging between WebSphere MQ queue manager or queue-sharing group. For further information about interoperation with a WebSphere MQ network, see the related tasks.

1. In the navigation pane, click Service integration -> Buses. A list of service integration buses is displayed.
2. In the Buses pane, click the service integration bus to connect from, that is, the local bus.
3. In the configuration tab, under Topology, click Foreign bus connections.
4. In the Foreign bus connections pane, click New to start the Foreign bus connection wizard.
5. In the Bus connection type pane, ensure that Direct connection is selected.
6. In the Foreign bus type pane, select WebSphere MQ.
7. In the Local bus details pane, select the messaging engine to use and enter the name of the virtual queue manager, that is, the name by which the virtual queue manager of the service integration bus is known to the WebSphere MQ network.
8. In the WebSphere MQ details pane, enter a name for the foreign bus, that is, the bus that represents the WebSphere MQ queue manager. Enter a name for the WebSphere MQ link that connects to the foreign bus. Ensure these two names are not the same.
9. Ensure the Configure publish-subscribe messaging for this connection check box is clear.
10. To send messages from the local bus to the WebSphere MQ queue manager, complete the following details:
    1. Ensure that Enable Service integration bus to WebSphere MQ message flow is selected.

    2. Enter the WebSphere MQ receiver channel name, host name and communication port.

    3. If the WebSphere MQ queue manager requires a secure connection, select the Is the WebSphere MQ receiver channel secure? check box. When this option is selected, the WebSphere MQ receiver channel accepts only connections that have SSL based encryption. The connection is successful only if a set of suitably compatible SSL credentials are associated with the service integration bus outbound channel and the WebSphere MQ receiver channel that it connects to.

11. To receive messages on the local bus from the WebSphere MQ queue manager, complete the following details:
    1. Ensure that Enable WebSphere MQ to Service integration bus message flow is selected.

    2. Enter the WebSphere MQ sender channel name.

    3. Optionally, enter the service integration bus inbound user ID. When the local bus is secure, the inbound user ID replaces the user ID in messages from the foreign bus that arrive at the local bus and is used to authorize whether those messages can access their destinations. Specify an inbound user ID for the local service integration bus under the following circumstances:
       • The foreign bus is in a different security domain, so user IDs in the foreign bus are not recognized in the local bus.
       • You want local control of access to inbound messages to the local bus.

       If the local bus is not secure, the inbound user ID has no effect on messages. If the local bus is secure, the foreign bus is not secure, and an inbound user ID is not set, an inbound message from the foreign bus is only authorized to destinations that allow unauthenticated users access.

12. When the Foreign bus connection wizard is finished, save your changes to the master configuration.

Results

You have created a connection between a service integration bus and a WebSphere MQ queue manager to use point-to-point messaging. You have created a direct foreign bus connection, which contains a routing definition, or virtual link. The physical link, a WebSphere MQ link on the messaging engine for the local bus, is created automatically.

We can test the connection.

Related

Connect buses using an indirect connection
Testing foreign bus connections
List the foreign bus connections
Remove a foreign bus connection from a bus
Configure destination defaults for a foreign bus connection
Interoperate with a WebSphere MQ network

+

Search Tips   |   Advanced Search