Understanding behavior extensions

A transaction equates to a published service, or Controller Component operation. An action equates to an operation on a business logic component. There may be other predefined points that can be extended and they are documented as part of the service specification. Clients can write extensions to InfoSphere MDM Custom Domain Hub behavior as Java™ code or in a rules engine language. Extensions are organized into extension sets, which are similar to the rule sets within a rules engine. Examples include generic prospective client rules or line of business specific rules like life insurance client rules. The Extension Controller is the gateway from the core application to behavior extensions and is invoked at extension points listed above. It is provided with:

• Data about extension point that invoked it
• The transaction's object hierarchy
• The action's object hierarchy, in the case of an action extension point
• The transaction header that was provided in the original InfoSphere MDM Custom Domain Hub request

The Extension Controller uses the parameters to determine if any extension sets must be further evaluated. Relevant extension sets are then interrogated and qualified extensions, either Java or rules sets, are invoked.