Exporting physical MDM extension model

Use this procedure to export a physical MDM extension model to InfoSphere® Information Server version 9.1. Both tailored and untailored service project exports are supported.

1. In MDM Workbench, open the Export wizard by using one of these options.
   • From the Navigation perspective, right-click the physical MDM project folder that you want to export and select Export.
   • From the menu bar, select File > Export.
   • Under the Model Actions tab, select the extension point in your physical project.
2. On the Export window, expand Master Data Management and select Metadata for IBM InfoSphere Information Server . Click Next.
3. On the Export configuration window, select Extension Model and click Next .
4. On the next Export configuration window, complete these steps.
   1. Select the Operational server database connection or click New to create a new connection.
   2. Provide an MDM database schema name or use the database connection default schema name. After you create the database connection, the default schema name (as specified) is automatically added as the schema name in this file. If a default schema name is not was specified, then the name DB2ADMIN is used as the schema name.
   3. Under the Filter selection group, choose one of the options.
      • For an unfiltered export (export all objects and services from the schema), select Export from the workspace
      • For a filtered export (tailored project), select Export from the selected projectand select the Service tailoring project from the drop-down list
   4. Type the full path to the Target folder where you want to place the export files.
   5. Type the name of the Extension object file. This file must have a .csv extension.
   6. Type the name of Extension mapping file. This file must also have a .csv extension.
   7. If object and mapping files exist with the same names you provided in the previous steps and you want to replace them, check the Replace existing files box. If the files exist and you do not check this box, a message prompts you to check the box or to provide new file names.
   8. Click Next.
5. On the Substitution parameters window, you have the option of overwriting the following fields or accepting the defaults.
   1. Application name: The default is MDMApplication. This value becomes a label in InfoSphere Information Server and is used as a root category under which all MDM object and service definitions are grouped. The application name serves as a container in InfoSphere Metadata Workbench. You can customize this name as you want.
   2. Host name: This value is automatically populated from the project database connection information and is used in the generated mapping file. One class of mappings is generated to link the exported service and object definitions with any previously imported physical MDM database schema information. If the host name was changed during the physical database import, it must be modified here to supply the same value. Otherwise, you can accept the default.
   3. Database name: This value is automatically populated from the project database connection information. The database name is part of the identity path for an MDM physical table. If the value was changed during a previous import of the database schema, you must provide the same value. Otherwise, you can accept the default.
   4. Click Finish.