The processes that execute within WebSphere InterChange Server to choreograph automated interactions across distributed EISs are called collaborations. Collaborations interact with each adapter through a connector controller, which is a runtime service that mediates communication between collaborations and adapters.
While all connector controllers are identical except for their configuration, WebSphere InterChange Server instantiates a separate connector controller for each adapter. The connector controller exchanges business objects with the adapter to support all the interaction patterns described previously. The connector controller also exchanges administrative messages with the adapter, such as the adapter status, and commands to pause, start, or shutdown.
The communication transport between WebSphere InterChange Server and the adapter may be provided through Java Messaging Service (JMS) queues, IIOP, or a combination of the two. When used in combination, JMS is used for asynchronous event notification, and IIOP is used for WebSphere InterChange Server-initiated request processing and administrative messages.
Business object definitions are represented as XML schemas, but because both WebSphere InterChange Server and the adapters use business objects, they are simply serialized in communication. The adapter is configured through the WebSphere Business Integration System Manager perspective within the Eclipse Workbench, which deploys the adapter artifacts together with other integration artifacts to WebSphere InterChange Server.
The adapter may be configured to receive all of its configuration information from WebSphere InterChange Server upon start-up, or from a local repository of XML schemas.
Figure 4shows how the adapter is deployed with WebSphere InterChange Server.
Figure 4.
Adapter deployed with WebSphere InterChange Server