Component interactions
The following diagram shows the interactions among the components in the architecture to carry out a basic transaction.
The diagram shows a transaction being processed
by InfoSphere® MDM,
and the interaction of the InfoSphere MDM components.
The component interactions are:
- The service controller receives request from InfoSphere MDM consumer.
- The request is delegated to Request Handler, which gets a parser from a factory.
- The request is parsed into business objects. This is achieved either by invoking a pluggable parser or by transforming the request into a business object using ASI mapping.
- The security component used to authorize transaction.
- The Business Transaction Manager (BTM) gets a business proxy capable of handling the request.
- The business proxy invokes method on required controller component.
- The controller component performs preprocessing, which includes invoking the external validation engine to validate incoming data, and invoking the extension controller to execute any "pre-transaction" extensions.
- The controller component invokes required business logic component methods.
- The business logic component performs preprocessing, which includes invoking the extension controller to run any “pre-action” extensions.
- The business logic component runs business logic, including invoking external business rules component to run the externalized business logic.
- The business logic component invokes the persistency layer to persist data in database.
- The database triggers are used to create history data.
- The business logic component performs post-processing, which includes invoking the extension controller to run any post action extensions.
- The control returns to controller component, which may invoke other business logic component methods. Once this is complete, the control performs post- processing, which includes invoking extension controller to execute any post transaction extensions and invokes the Transaction Audit Information Log component to audit the transaction.
- The Control returns to business proxy. The business proxy can run additional InfoSphere MDM transactions, using controller component methods.
- The control is returned to the request handler. If ASI mapping is used in your solution, then the business objects are transformed into a response XML message. If no ASI mapping is used in your solution, then the business objects are de-serialized into XML by the pluggable response constructor. The response is returned to the InfoSphere MDM consumer.