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. When the doVerbFor() method receives an IBM WebSphere InterChange Server business object from a collaboration object, 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.

Figure 2. Application-connector communication method: Message request

Event delivery

Figure 3 illustrates the event delivery direction. The pollForEvents() method retrieves the next applicable message from the input queue. The message is staged in the in-progress queue where it remains until processing is complete. Using either the static or dynamic meta-objects, 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 an IBM WebSphere InterChange Server 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 object. If so, the gotApplEvents() method delivers the business object to InterChange Server, and the message is removed from the in-progress queue.

Figure 3. Application-connector communication method: Event delivery


Copyright IBM Corp. 1997, 2003