The adapter for eMatrix consists of a connector, the Java Program Object (JPO), and an Object Discovery agent (ODA) with the adapter framework. Together they enable eMatrix to exchange information with an integration broker, and thereby to communicate with external applications such as accounting and CRM packages.
The adapter includes three primary components:
Acts as an intermediary between the integration broker and the application in the transfer of data. The connector is metadata-driven.
There may be more than one. They run within eMatrix and they store information about events in the eMatrix database.
A design-time tool that queries the application to determine existing eMatrix business object types and relationships. These form the basis of the WebSphere business object definitions. The connector uses these definitions at run time to convert application data into business objects.
The adapter manipulates eMatrix business objects and connections within eMatrix. It may also execute MQL statements. Through the use of MQL commands, the adapter can perform almost any action supported by eMatrix.
The adapter communicates with the eMatrix application using a Java-based API called the eMatrix adapter development kit (ADK) and a separate eMatrix collaboration server. The eMatrix ADK enables the adapter to query and manipulate objects in the application by passing requests to the application through the eMatrix collaboration server.
The adapter mediates data flows to and from the integration broker and the application. The flows are:
These flows are described in detail below.
Request processing starts with the integration broker. The integration broker passes business objects to the adapter for eMatrix, which communicates with the eMatrix collaboration server using its Java-based eMatrix ADK. Figure 1 provides an architectural overview of the data flow.
Figure 1. Request processing in the eMatrix adapter
Request processing takes place as follows.
The adapter for eMatrix uses event polling to detect events in the eMatrix system at run-time. Figure 2 illustrates the sequence of events that occurs when the application is polled by the integration broker through the adapter.
Figure 2. Event notification in the eMatrix adapter
Event notification takes place as follows.