The basic process for creating extensions and additions
includes high level design, coding, deployment, and testing.
About this task
Table 1. Process for creating extensions and additions
| |
Procedure |
| High Level Design |
|
| Coding |
- Code the classes, interfaces, and methods. Based on the plan you
have created, use the MDM Workbench to create the classes and interfaces.
Finish implementing all the non-generated parts of the classes that
are required. See Extension and addition development in the MDM Workbench for
more information.
- Ensure that all custom names are prefixed with a three letter
abbreviation followed by an underscore, for example,
ABC_getItem.
These naming guidelines apply to all custom business objects, database
tables, and transaction names.
- When creating extensions, new entity additions, new services and
new code table values, please use value greater than 1,000,000 as
primary key for database entities describing metadata. All values
less than 1,000,000 are reserved for InfoSphere® MDM as
integer PK values.
- When configuring new inquiry levels (tale INQLVL, column inqlvl),
please use values 100 and up. Values range from 0 to 99 are reserved
for InfoSphere MDM.
|
| Deploy and Test |
- Deploy the extension or addition
- Ensure the InfoSphere MDM application
can see the EJB project with the addition or extension.
- Test the extension or addition.
|