< Previous | Next >

Lesson 1: Creating a new Development Project and a new entity for it

The first step in creating physical customizations for InfoSphere® MDM is to create a Development Project to contain the modifications you want to make to InfoSphere MDM.

You can modify the model using the model editor and then generate code to implement the objects that you created in the model.

In the General Information section of the Overview tab, the properties supplied when the project was created are displayed.

In the Metadata section of the Overview tab, the following two properties define a numerical range used during code generation to allocate certain unique key values:
  • Start ID: the starting value used for allocating unique IDs.
  • Maximum offset: the maximum offset from the Start ID that can be allocated.
This range is automatically configured when the project is created to ensure that it does not conflict with other projects in the workspace. When projects are imported, you may need to manually adjust the Start ID and Maximum Offset values to ensure a unique range for each project. For the purposes of this tutorial, you do not need to make any changes.

To create a new hub module project and a new entity for it, take the following steps:

  1. Launch Rational® Software Architect.
  2. Ensure that the MDM Development perspective is chosen.
  3. Click File > New > Other > Master Data Management > Development Project to launch the wizard.
  4. In the Master Data Management Development Project window, enter the following details:
    • In the Project name: field, enter DemoModule
    • Select Use default location
    • Ensure that there is an entry in the Application location, or click Configure to select one.
    • In the Base Java package name field, enter com.mdm.demo
    • The Service namespace URI field will be filled in automatically with what you entered in the Base Java package name field, or you can specify another URI. For this tutorial, leave this as the default http://www.demo.com
  5. Click Next. The Master Data Management Development Project Settings window loads.
  6. In the Master Data Management Development Project Settings window, enter an Identifier and specify the Database schema name as the schema you want to use in your database (for example, DB2ADMIN); ensure that the Target runtime is correct, and ensure that the Add development project to composite is selected.
    Note: Development Projects can be associated with an OSGi composite bundle by selecting Add development project to composite and selecting a .cba file from the Composite project dropdown box. For the purposes of this tutorial, a .cba file will be generated based on the Identifier that you specified.
  7. Click Finish. The Model editor is launched automatically.
  8. In the model editor, click the Model tab. Right-click on the DemoModule folder and click New > EntityType.
  9. In the Entity Type section, enter GeneralLedger in the Name field. The Database table name field is filled in automatically. You can expand the GeneralLedger addition to see that a primary key and three transactions have automatically been created to get, add, and update the GeneralLedger addition: getGeneralLedger, addGeneralLedger, and updateGeneralLedger.
  10. Optional: Decide if you want to create a Delete service for the addition. By default, no Delete service is created.
    • If you do not want a delete service for this addition, take no action.
    • If you want a delete service for this addition, select Support soft delete. This creates two new attributes within the GeneralLedger addition:
      • a boolean entityActiveInd, which indicates whether the record is active or soft deleted.
      • a type code resolution_tp_cd, which identifies the reason why the record has been soft deleted. If you click on the attribute you will see that it is mapped to the ResolutionType code table (CdResolutionTp).
You can now proceed to Lesson 2: Creating addition definitions and attributes for the new entity.
< Previous | Next >


Last updated: 6 May 2015