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 an ISO
15022 SWIFT message from an integration broker. For IBM WebSphere
Business Integration Server Express and Express Plus, the integration broker
in Figure 2 is WebSphere InterChange Server Express.
- The connector passes the business object to the data handler.
- The data handler converts the ISO 15022 business object into an ISO
15022-compliant SWIFT message.
- The connector dispatches the ISO 15022 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 ISO 15022 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 data handler converts the message into an ISO 15022 business
object.
- The SWIFT data handler receives the ISO 15022 business object and sets the
verb in it to the default verb specified in the data handler-specific
meta-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. For IBM WebSphere Business Integration Server
Express and Express Plus, the integration broker in Figure 3 is WebSphere InterChange Server Express.
Figure 3. Application-connector communication method: Event delivery

