Adapter architecture

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:

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.

Architectural overview

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

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.

  1. The integration broker issues a request to the adapter in the form of a business object, which contains type information and a business object verb.
  2. The adapter processes the business object by invoking the appropriate eMatrix ADK calls.
  3. Each time an eMatrix ADK call is made, the collaboration server performs the specified action on the corresponding object in the eMatrix system and returns the result to the connector.
  4. Once the adapter has finished processing the request, it returns a status code and if required, a business object with the resulting changes, to the integration broker.

Event notification

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.

Note:
For polling to work, you must first configure an eMatrix trigger for the event or events you wish to monitor. This is done during the initial setup. For details, refer to "Configuring the adapter".

Figure 2. Event notification in the eMatrix adapter


Event notification takes place as follows.

  1. An action is performed in the eMatrix system, causing a trigger to fire.
    Triggers can be invoked in many different ways, for example, such as modifying an eMatrix object with a configured trigger.
  2. When the trigger is fired, the eMatrix system executes the associated Java Program Object (JPO), which creates a new event object in eMatrix.
  3. At specified intervals, the adapter polls eMatrix for any new event objects that the JPO has created.
  4. The adapter retrieves the event object.
  5. It then retrieves the relevant eMatrix entities, translates them to business objects, and publishes them to the integration broker. The adapter can retrieve both eMatrix business objects and relationships.

Copyright IBM Corp. 1997, 2004