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 an ISO 7775 SWIFT message from an integration broker.
  2. The connector passes the business object to the data handler.
  3. If specified in the map subscription meta-object, the data handler passes the ISO 7775 object to the mapping engine.
  4. Using a production instruction meta-object (PIMO), the mapping engine transforms the ISO 7775 object into an ISO 15022 business object and passes it to the data handler.
  5. The data handler converts the ISO 15022 business object into an ISO 15022-compliant SWIFT message.
  6. The connector dispatches the ISO 15022 SWIFT message to the WebSphere MQ output queue.
  7. 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 ISO 15022 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 data handler converts the message into an ISO 15022 business object.
  4. Using the map subscription meta-object, the connector determines whether the message type is supported and, if supported, requires transformation into an ISO 7775 business object. If so, the data handler passes the ISO 15022 business object to the mapping engine.
  5. Using a PIMO, the mapping engine processes the sub-fields of business object data, creating an ISO 7775-compliant business object, which is passed to the data handler.
  6. The SWIFT data handler receives the ISO 7775 business object and sets the verb in it to the default verb specified in the data handler-specific meta-object.
  7. 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, 2003