Application-connector communication method

The subsections below discuss and illustrate how the connector interacts with InterChange Server and an application.

Message request

Figure 1 illustrates a message request communication. When the doVerbFor() method receives a business object from a collaboration, 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 1. Application-connector communication method: Message request



Message return

Figure 2 shows the message return 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 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: Message return



Copyright IBM Corp. 1997, 2003