This section describes how to configure components to send and receive documents between WebSphere Partner Gateway and WebSphere Business Integration Message Broker through the use of the JMS transport protocol. It provides the following information on how to send and receive documents:
To send or receive a document between WebSphere Partner Gateway and version 5.0 Message Broker using the JMS transport protocol, WebSphere MQ must be the JMS provider. The following sections describe how WebSphere Partner Gateway, Message Broker, and WebSphere MQ work together to exchange documents over the HTTP transport protocol.
For WebSphere Partner Gateway to send a document to Message Broker using the JMS transport protocol, you use the JMS queues. WebSphere Partner Gateway sends a document to its JMS output queue, where it is transferred to the JMS input queue on which Message Broker listens. When Message Broker receives a document, it retrieves it from its input queue. Message Broker's message flow contains special WebSphere MQ (JMS) transport nodes, which handle access to the JMS queues. Figure 25 provides an overview of how WebSphere Partner Gateway sends documents to Message Broker over the JMS transport protocol.
The following steps describe how WebSphere Partner Gateway sends a document to a message flow within Message Broker over the JMS transport protocol:
If the packaging type of the document was Backend Integration, WebSphere Partner Gateway has provided custom properties in this message. The JMS message header, JMSType, is set with the content type of the payload.
For information on how to set up this queue, see Setting up the environment for JMS transport.
When business logic is complete, the message flow sends the resulting document to its MQOutput node.
For WebSphere Partner Gateway to receive a document from Message Broker over the JMS transport protocol, you use JMS queues. Message Broker sends a document to its JMS output queue, where it is transferred to the JMS input queue on which WebSphere Partner Gateway listens. When WebSphere Partner Gateway receives a document, it retrieves it from its input queue. Message Broker's message flow contains special WebSphere MQ (JMS) transport nodes, which handle access to the JMS queues. Figure 26 provides an overview of how documents are sent from Message Broker to WebSphere Partner Gateway.
The following steps describe how WebSphere Partner Gateway receives a document from a message flow within Message Broker over the JMS transport protocol:
The message flow receives its incoming message from a JMS input queue.
When business logic is complete, the message flow sends the resulting document to its MQOutput node.
For more information on the target, see Configuring for incoming documents over JMS transport protocol. For information on how to set up this queue, see Setting up the environment for JMS transport.
The sending and receiving of documents to and from Message Broker involves JMS queues (remote and local). For information on how to configure WebSphere Partner Gateway for use with Message Broker over JMS, see Configuring WebSphere Partner Gateway for Message Broker. To use the JMS transport protocol with Message Broker, you can set up the JMS system that WebSphere MQ provides. Version 5.0 of Message Broker uses version 5.3 of WebSphere MQ as a JMS provider. You can use the steps in the Hub Configuration Guide to set up the JMS transport-protocol mechanism.
When you create your JMS queues for use between WebSphere Partner Gateway and Message Broker, consider the following points:
You can use the following command to create this queue manager and a set of named queues:
mqsicreatebroker
Because Message Broker uses a set of predetermined queue names, it requires a separate WebSphere MQ queue manager per broker. Message Broker can share this queue manager hosting with either its Configuration Manager or the optional User Name Server, or both.
For more information, refer to your WebSphere Business Integration Message Broker Installation and Configuration Guide.
For example, if you create the queues listed in the Original queue name column of Table 54, you could rename these queues to indicate the direction of flow, as shown in the Directional queue name column of Table 70.
Original queue name | Directional queue name |
---|---|
inQ | MB2HUB |
outQ | HUB2MB |
For a Message Broker message flow to handle documents over the JMS transport protocol, it uses the following transport nodes:
The order of use for these transport nodes depends on the direction of communication, as follows:
Node type | Purpose | Notes and restrictions |
---|---|---|
MQInput | Receives the document from WebSphere Partner Gateway | The value in the Queue Name field (in the Basic properties) of this transport node is the message flow input queue. WebSphere MQ must be set up so that this JMS queue receives documents from the output queue of WebSphere Partner Gateway. For more information, see Configuration for receiving documents over the JMS transport protocol. |
Compute | Performs business-logic tasks, such as removing header information | None |
MQOutput | Receives the document from the compute node and sends it as the message-flow output | This transport node sends the resulting document to a JMS output queue, which routes it to its next destination. |
Node type | Purpose | Notes and restrictions |
---|---|---|
MQInput | Receives the document into the message flow | This transport node receives the incoming document from a JMS input queue. |
Compute | Performs business-logic tasks, such as updating header information | None |
MQOutput | Receives the document from the compute node and sends it to WebSphere Partner Gateway | The value in the Queue Name field (in the Basic properties) of this transport node is the message flow output queue. WebSphere MQ must be set up so that this JMS queue sends documents to the input queue of WebSphere Partner Gateway. For more information, see Configuring for incoming documents over JMS transport protocol. |
For more detailed information on how to create and configure message flow nodes, see your WebSphere Business Integration Message Broker documentation.