Extension and addition development in the MDM Workbench

IBM® InfoSphere® MDM Workbench allows you to create, implement, store, and maintain InfoSphere MDM extensions and additions.

There are a number of basic steps involved in creating and implementing an InfoSphere MDM extension or addition using the Workbench:

Preparing a workspace in IBM Rational® Application Developer
Creating the modification using the Workbench
Implementing the business logic for the modification
Packaging and deploying the modification
Testing the modification
Releasing the modification for general use

For more general information about creating InfoSphere MDM extensions and additions, see Customizing physical MDM capabilities.

Extension and addition development planning
In order to use the InfoSphere MDM Workbench effectively, you must first determine the business results you want to achieve, and plan the extensions and additions you will need to get those results.
MDM development projects for extending Physical MDM services
Before creating modifications, an InfoSphere MDM module project for modifications must be created.
Maintenance of code in the workspace
When code generation is performed, files are created that reflect the names of elements present in the MDM development models.
Data additions
You can create data additions using the model editor.
Entity attributes
After creating data addition entities, you can add attributes to them.
Generated code for data additions
When you create data additions, additional associated code is generated in support of the created data additions.
Subtype hierarchies in the model editor
The InfoSphere MDM Workbench enables you to establish subtype hierarchy relationships between data additions, allowing entity subtypes to inherit attributes and services from a supertype.
Data extensions
You can create a data extension (or entity type extension) using the model editor.
Model editor created code tables
You can define a code table in the module model and use it to define entity attributes. Code tables are created within a folder.
Generated code for code tables
When you define code tables, additional associated code is generated in support of the defined code tables.
Reference definitions using the model editor
You can define references and choose how they are implemented.
Containment relationship definitions using the model editor
You can define containment relationships and choose how they are implemented using the Containment wizard.
Containment relationships
Containment relationships between persistent entities can be implemented in two different ways.
Get Record inquiry transaction definitions using the model editor
You can create additional Get Record inquiry transactions as needed.
Overview of transactions in InfoSphere MDM
Transactions are atomic operations which can retrieve and manipulate data held by InfoSphere MDM.
Request or response objects for custom transactions
You can define new entities in the module model to be used as request or response objects in a custom transaction.
Error reason creation using the model editor
Error reasons are used to provide the context for any errors returned to the user. Error reasons can be specified at a folder, attribute, entity, or transaction level within the module model.
Query extensions
You can create query extensions in the module model by using the model editor.
Generated code for query extensions
When you create query extensions, additional associated code is generated in support of the created query extensions.
Behavior extensions created using the model editor
A behavior extension is a rule that is invoked whenever a transaction that matches the extension conditions is run.
Generated code for behavior extensions
When you create behavior extensions, additional associated code is generated in support of the created behavior extensions.
Data standardizer definitions
You can define data standardizers in a module model using the model editor.
Generated code for data standardizers
When you add a data standardizer with the editor, the Workbench generates the necessary code and associated metadata to support the new standardizer.
Module model library content additions
The template library allows you to add predefined objects to a model in a single step, enabling you to add predefined model content, such as new entities or services, directly to a model.
Module model file validation
You must validate the model files in order to avoid errors being generated in code.
Artifact generation using the model
You can generate and customize artifacts created from the model.
Probabilistic Matching Engine bundle generator wizard
The InfoSphere MDM Probabilistic Matching Engine (PME) is an engine that can be used to perform probabilistic matching and comparison on record data.
Addition and extension deployment
After you have completed development of an extension or addition, you must deploy it to an InfoSphere MDM instance.
Deployed addition and extension updating and removal
This is an overview of what is involved in updating or removing previously deployed additions and extensions.

Last updated: 23 October 2014