Building custom batch jobs for the InfoSphere MDM Server WebSphere Extended Deployment batch processor

The InfoSphere® MDM Server WebSphere® Extended Deployment batch processor framework supports custom batch job development, in conjunction with the Request/Response and Extension framework.

Two reasons to consider custom development are:

• The required batch input or output is not supported by out-of-the-box components.

  The solution to this scenario requires building one, all, or a combination of input batch data stream, output batch data stream, parser and constructor components. Depending on your requirements, some prebuilt components can be used with ones you develop for your requirements.

  See Configuring the Request and Response Framework for information on developing a custom parser and constructor.

• The available transactions do not meet the requirements for the batch transaction

  The InfoSphere MDM Server WebSphere Extended Deployment batch processor does not prescribe or depend on any specific back-end transaction. If the back-end does not support the transaction required by the batch job, to solve this scenario you must develop a custom transaction. This is done in one of two ways:

  • Write an addition transaction using the extension framework provided in the common services
  • Write a custom business proxy, a composite business proxy, or both, which use existing back-end transactions internally.

    Each of these extension mechanisms are defined in their respective sections in this guide. See Customizing InfoSphere MDM Server and Creating composite XML transactions.