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.
Figure 2 illustrates a message request communication.
- The connector framework receives a business object representing a SWIFT
message from an integration broker.
- The connector passes the business object to the data handler.
- The data handler converts the business object to a SWIFT message.
- The connector dispatches the SWIFT message to the WebSphere MQ output
queue.
- 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

Figure 3 illustrates the message return communication.
- The polling method retrieves the next applicable SWIFT message from the
WebSphere MQ input queue.
- The message is staged in the in-progress queue, where it remains until
processing is complete.
- The connector passes the SWIFT message to the data handler.
- The data handler converts the message into a business object.
- 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

