For Business Integration Connect to communicate with InterChange Server
over the JMS transport protocol requires that these two components be
configured to work with JMS. Table 70 summarizes these configuration steps.
Table 70. Configuring Business Integration Connect and InterChange Server for JMS transport protocol
Component | Version | For more information |
---|---|---|
WebSphere Business Integration Connect | 4.2.2 |
Configuring for outgoing documents over JMS transport protocol Configuring for incoming documents over JMS transport protocol
|
WebSphere InterChange Server | 4.1.1, 4.2.0, 4.2.1, 4.2.2 | Creating ICS artifacts for JMS |
In addition, to send or receive a document between Business Integration
Connect and InterChange Server over the JMS transport protocol, you also use
the ICS-compatible components listed in Table 71..
Table 71. Components required to transfer documents to and from InterChange Server through JMS
Component | Description | Notes and restrictions |
---|---|---|
WebSphere Business Integration Adapter for JMS (Adapter for JMS)
|
This adapter allows InterChange Server to exchange business objects with
applications that send or receive data in the form of JMS messages. The
Adapter for JMS and Business Integration Connect communicate through JMS
queues.
|
|
A payload data handler | This data handler converts the payload between its document format and its business-object representation. | For more information, see Specifying the payload data handler. |
Attachment data handler |
This data handler converts documents with attachments into business
objects.
| This data handler is required only if your documents include attachments. For more information, see Handling documents with attachments. |
The following sections describe how the components in Table 71 work together to send and receive documents between Business Integration Connect and InterChange Server over the JMS transport protocol.
For Business Integration Connect to send a document to InterChange Server using the JMS transport protocol, you use the Adapter for JMS to retrieve the message that Business Integration Connect has put on a JMS queue. The adapter then routes the message to InterChange Server. Figure 20 provides an overview of how Business Integration Connect sends documents to InterChange Server over the JMS transport protocol.
The following steps describe how Business Integration Connect participates in event notification by sending a document to a collaboration within InterChange Server over the JMS transport protocol:
If the packaging type of the document was Backend Integration, Business Integration Connect has provided custom properties in this message. The JMS message header, JMSType, is set with the content type of the payload.
The JMS queue that Business Integration Connect uses as its outbound queue is the same queue that the Adapter for JMS uses as its input queue. For information on how to set up this queue, see Configuring the JMS queues. For detailed information on the processing of the Adapter for JMS, see the Adapter for JMS User Guide.
When Backend Integration is the packaging type and the document contains attachments, the configured data handler is responsible for handling the payload and attachments.
For Business Integration Connect to receive a document from InterChange Server using the JMS transport protocol, you use the Adapter for JMS, which places the message it receives from InterChange Server on a JMS queue for Business Integration Connect to retrieve. Figure 21 provides an overview of how Business Integration Connect receives documents from InterChange Server over the JMS transport protocol.
The following steps describe how Business Integration Connect participates in request processing by receiving a document from a collaboration within InterChange Server over the JMS transport protocol:
The request business object contains application-specific information pointing to a dynamic meta-object that contains the JMS transport-level header information, which Business Integration Connect expects.
The adapter reads the DataHandlerMimeType and DataHandlerConfigMO properties to determine the data handler to use. For more information, see Specifying the payload data handler.
The adapter searches the application-specific information of the request business object for the cw_mo_conn tag, which identifies the attribute that contains the dynamic meta-object. If you are using Backend Integration packaging for your document, you can specify transport-level header information in this dynamic meta-object.
If this attribute is populated, the adapter sets the transport-level header fields in the request document. Within the JMSProperties attribute, you can also specify the content-type standard JMS header. For more information, see Creating JMS header information.
The queue can be specified in the static meta-object or the dynamic meta-object. For information on specifying queues, see Identifying the JMS queues. Business Integration Connect listens on this JMS queue, which is configured as its inbound queue in its target definition. For more information, see Configuring for incoming documents over JMS transport protocol.