Components required for documents over JMS transport

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.

  1. Make sure you are using the Adapter for JMS Version 2.3.1 (or higher), which provides support for custom header properties. Refer to the adapter documentation to make sure that the version of the adapter is compatible with the version of InterChange Server you are using.
  2. The Adapter for JMS supports JMS Text messages only. If you intend to use JMS Byte messages, use the Adapter for JMS Version 2.5.0.

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.

Sending documents over JMS transport

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.

Figure 20. Message flow from Business Integration Connect to a collaboration through 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:

  1. Business Integration Connect posts a message to its JMS outbound queue.

    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.

    Note:
    Within Business Integration Connect, you must configure a gateway that identifies the JMS queue to which Business Integration Connect sends the message and on which the Adapter for JMS is polling. For more information, see Configuring for outgoing documents over JMS transport protocol.
  2. When the Adapter for JMS sees a message on one of its input queues, it retrieves the message.

    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.

  3. The Adapter for JMS moves the message to its in-progress queue.
  4. The Adapter for JMS extracts the body of the JMS message and invokes a data handler with the body of the message. This data handler converts the body of the JMS message to a business object.
    Note:
    If your messages have attachments, you can install the Attachment data handler and then configure the Adapter for JMS to call it to convert the body of the JMS message to a business object. For more information, see Handling documents with attachments.

    When Backend Integration is the packaging type and the document contains attachments, the configured data handler is responsible for handling the payload and attachments.

  5. The data handler returns the business object to the Adapter for JMS.
    Note:
    If the Attachment data handler was used, this business object contains the payload as well as the attachments.
  6. If the Adapter for JMS finds a child dynamic meta-object (specified using cw_mo_conn in the business-object level application specific information), the adapter populates the user-defined JMS headers present in the business object with the headers present in the JMS message.
  7. The Adapter for JMS delivers the business object to the InterChange Server as part of a subscription delivery.

Receiving documents over JMS transport

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.

Figure 21. Message flow from a collaboration to Business Integration Connect through 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:

  1. The collaboration within InterChange Server makes a service call to the Adapter for JMS, sending it the request business object.

    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.

  2. The Adapter for JMS uses a data handler to convert the business object that the collaboration has sent it into a JMS message.

    The adapter reads the DataHandlerMimeType and DataHandlerConfigMO properties to determine the data handler to use. For more information, see Specifying the payload data handler.

    Note:
    If your documents have attachments, install the Attachment data handler and then configure the Adapter for JMS to call it to convert the request business object to a document with attachments. For more information, see Handling documents with attachments.
  3. The data handler converts the business object to a string and returns it to the Adapter for JMS.
  4. The Adapter for JMS determines, from the request business object, the name of the dynamic meta-object for custom JMS properties.

    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.

  5. The Adapter for JMS searches the dynamic meta-object for the JMSProperties attribute.

    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.

  6. The Adapter for JMS creates a JMS message, using the string returned by the data handler. It also sets any custom properties, as defined in the dynamic meta-object.
    Note:
    Versions of the Adapter for JMS before 2.4.1 can write only JMS text messages.
  7. The Adapter for JMS sends the resulting request message to an output queue.

    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.

  8. Business Integration Connect receives the message from its JMS inbound queue, as configured in its target.

Note:
Business Integration Connect supports only asynchronous interaction with InterChange Server over JMS. Therefore, you might not want to wait for the response. The response from the community participant or Business Integration Connect can come on a different queue. You can configure the Adapter for JMS to poll that queue. The response that comes on the queue can be delivered to InterChange Server as part of the event delivery.

Copyright IBM Corp. 2003, 2004