You 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 by 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.
Before you begin
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
WebSphere Application Server:
- A service integration bus that you want 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.
About this task
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.
Procedure
- In the navigation pane, click . A list of service integration buses is displayed.
- In the Buses pane, click the service integration bus that you want
to connect from, that is, the local bus.
- In the configuration tab, under Topology,
click Foreign bus connections.
- In the Foreign bus connections pane, click New to
start the Foreign bus connection wizard.
- In the Bus connection type pane, ensure that Direct
connection is selected.
- In the Foreign bus type pane, select WebSphere MQ.
- In the Local bus details pane, select the messaging engine that
you want 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.
- 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 that these two names are not
the same.
- Ensure that the Configure publish-subscribe messaging
for this connection check box is clear.
- To send messages from the local bus to the WebSphere MQ queue
manager, complete the following details:
- Ensure that Enable Service integration bus to WebSphere
MQ message flow is selected.
- Enter the WebSphere MQ receiver channel name, host name and
communication port.
- 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 secure sockets layer (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.
- To receive messages on the local bus from the WebSphere MQ queue
manager, complete the following details:
- Ensure that Enable WebSphere MQ to Service integration
bus message flow is selected.
- Enter the WebSphere MQ sender channel name.
- 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.
- 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.
What to do next
You can test the connection.