Application-connector communication method

The connector makes use of IBM's WebSphere MQ implementation of the Java Message Service (JMS). The JMS is an open-standard API for accessing enterprise-messaging systems. It is designed to allow business applications to asynchronously send and receive business data and events.

Message request

Figure 2 illustrates a message request communication.

  1. The connector framework receives a business object representing a SWIFT message from an integration broker.
  2. The connector passes the business object to the data handler.
  3. The data handler converts the business object to a SWIFT message.
  4. The connector dispatches the SWIFT message to the WebSphere MQ output queue.
  5. The JMS layer makes the appropriate calls to open a queue session and routes the message to the MQSA, which issues the message to the SWIFT Alliance Gateway.

    Figure 2. Application-connector communication method: Message request


Event delivery

Figure 3 illustrates the message return communication.

  1. The polling method retrieves the next applicable SWIFT message from the WebSphere MQ input queue.
  2. The message is staged in the in-progress queue, where it remains until processing is complete.
  3. The connector passes the SWIFT message to the data handler.
  4. The data handler converts the message into a business object.
  5. The connector then determines whether the business object is subscribed to by the integration broker. If so, the connector framework delivers the business object to the integration broker, and the message is removed from the in-progress queue.

    Figure 3. Application-connector communication method: Event delivery


Copyright IBM Corp. 1997, 2004