MDM Implementation styles

Implementation styles

Custom transactions can be implemented in two different ways, either as a business proxy transactions or as component transactions. These styles correspond to adding the custom logic at different points in the InfoSphere MDM request handling process.

Business proxy transactions add logic just before the controller level. They call other transactions at the controller level, but they cannot call other business proxies. Business proxy transactions can only call other transactions at the controller level and cannot call other business proxies.

Business proxy transactions have the following properties:

• They can add logic just before the controller level.
• They only call other transactions at the controller level.
• They cannot call other business proxies

Component transactions are called at the component level. Component transactions can only call other transactions at the component level and can call other custom component transactions.

Component transactions:

• are called at the component level
• can only call other transactions at the component level
• can call other custom component transactions

The distinction between calling transactions at the controller level and the component level is important when calling the out-of-the-box transactions since some of them have different semantics at the controller level. In general, for transactions with both coarse-grained and fine-grained variants, the coarse-grained variant is only available at the controller level.