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 1 illustrates the flow of a message request communication. When the doVerbFor() method receives a business object from the integration broker (typically from a collaboration running in the ICS), the connector passes the business object to the data handler. The data handler converts the business object into JMS-suitable text and the connector issues it as a message to a queue. There, the JMS layer makes the appropriate calls to open a queue session and route the message. Peer-to-Peer Agent monitors the queue, picks up the message, and sends it to the targeted trading partner.
Figure 1.
Application-Connector Communication Method: Message
Request
Figure 2 illustrates the event delivery direction. The pollForEvents() method retrieves the next applicable message from the input queues. The message is staged in the in-progress queue where it remains until processing is complete. Using the static meta-object, the connector first determines whether the message type is supported. If so, the connector passes the message to the configured data handler, which converts the message into a business object. The verb that is set reflects the conversion properties established for the message type. The connector then determines whether the business object is subscribed to by a collaboration. If so, the gotApplEvents() method delivers the business object to InterChange Server, and the message is removed from the in-progress queue.
Figure 2.
Application-Connector Communication Method: Event
Delivery