Identity parameters for imported assets

You specify values for identity parameters when you import database assets, logical data models, or physical data models. Specifying identity values helps prevent duplicate assets in the metadata repository and ensures that you do not overwrite assets by mistake.

When you use consistent values for identity parameters, suite users can readily identify which assets to use for such tasks as creating jobs, designating stewards, or assigning to terms.

You specify values on the Identity Parameters screen when you import database assets, logical data models, or physical data models by using InfoSphere® Metadata Asset Manager.

Database assets

The bridges and connectors that import metadata from remote databases and repositories occasionally provide incomplete or inconsistent information about the host systems and databases that contain the assets that you are importing.

The identity of a database table has the following components:
  • Host system name
  • Database identity, consisting of database name, DBMS name, and DBMS server instance name
  • Database schema name
  • Database table name

Thus, host name, database name, database management system (DBMS) name, and DBMS server instance name are critical parts of the identity of the tables and schemas that they contain. If you were to import the same database assets by two different methods, and each method produced a different DBMS name, you could create duplicate assets in the metadata repository. Assets that have technically different identities but have identical content or contain the same child assets are potential duplicates.

To avoid duplicates and to ensure that your database assets are correctly identified, you specify values for identity parameters during the import process. Identity parameters are also valuable when you want the imported assets to be associated with a different host system, database, or DBMS than you imported them from. For example, you might want the assets to be identified with the host system and database that you use for test and production. For the host system, database, and schema parameters you can either type a name or select a host, database, or schema that is already in the metadata repository to associate the imported assets with.

Depending on the bridge or connector that you choose for import, you can specify values for the following identity parameters for database assets:
Host system name
The name of the computer that hosts the database. If you are importing from a database, you can specify a different name than the name of the source computer. For example, you might specify the computer that will host this database during development or production.
Database name
The name of the database that contains the imported schemas and tables. You can specify a different name than the name of the source database.
For database imported via Business intelligence bridge, and
  • If you want to specify different names for the databases that you import, which is applicable only in case of multiple database being imported, specify a semicolon separated list of database name and their replacement values. The format of this parameter <originalDatabase1>::<replacementDatabase1>;<originalDatabase2>::<replacementDatabase2>.
  • Use two consecutive colons to delimit the original database name and replacement database name value. Use a semicolon to delimit the multiple database and their replacement name value.You can also specify a default database name. This is optional and should be specified if the bridge gets an empty name for the database. The DefaultDatabaseName is case sensitive. The format of this parameter is <DefaultDatabaseName>::<replacementDatabase>.
  • Use two consecutive colons to delimit the DefaultDatabaseName and replacement database name value. Use a semicolon to delimit the multiple database and their replacement name value. For example: DefaultDatabaseName::DBName;OriginalDBName1::ReplaceDBName1;OriginalDBName2::ReplaceDBName2.
If a database is not found, it is ignored.
DBMS name
The name of the DBMS that is associated with database. The DBMS name is part of the identity of the target database. You can specify a different DBMS name than the one associated with source database. The DBMS name should be appropriate for the value that you enter for database name.
If the DBMS name is imported via Business intelligence bridge, and
  • If you want to specify different DBMS names for the databases that you import, which is applicable only in case of multiple database being imported, specify a semicolon separated list of DBMS names and the corresponding Database name separated by two colons. The format of this parameter is<originalDBMSName1>::<DatabaseName1>;<originalDBMSName2>::<DatabaseName2>.
  • If multiple databases exist with the same DBMS name, specify the DBMS name and comma separated list of database names. The format of this parameter is <originalDBMSName>::<DatabaseName1>,<DatabaseName2>. Use two consecutive colons to delimit the original DBMS name and a list of database name values separated by commas.
  • If you want to delimit the multiple DBMS names, use a semicolon. For example: DBMSName1::DatabaseName1,DatabaseName2;DBMSName2::DatabaseName3. If a database is not found, it is ignored.
DBMS server instance name
The name of the DBMS server instance, if it exists. Some database management systems do not have the concept of DBMS server instance. DBMS server instance name is part of the identity of the target database. You can specify a different DBMS server instance name than the one that hosts the source database. The DBMS server instance name should be appropriate for the value that you enter for database name.
If the DBMS server instance is imported via Business intelligence bridge, and
  • If you want to specify a different DBMS server instance names for the databases that you import, which is applicable only in case of multiple database being imported, specify a semicolon separated list of DBMS server instance names and the corresponding Database name separated by two colons. The format of this parameter is <originalDBMSServer1>::<DatabaseName1>;<originalDBMSServer2>::<DatabaseName2>.
  • If multiple database are from the same DBMS server instance, specify the DBMS server name and comma separated list of database names. The format of this parameter is <originalDBMSServer1>::<DatabaseName1>,<DatabaseName2>.
  • Use two consecutive colons to delimit the original database server name and a list of database name value separated by commas. Use a semicolon to delimit the multiple DBMS server instance. For example, DBMSServerInstance1::DatabaseName1,DatabaseName2;DBMSServerInstance3::DatabaseName3.
If a Database name not found, it is ignored.
Schema name
The name of the schema that the imported tables belong to.

Logical data model and physical data model assets

If you import a physical data model from a design tool, you can choose to create a database schema and database tables from the physical data model. This is necessary for InfoSphere DataStage® and QualityStage® users who want to create table definitions from these shared tables for use in jobs. You specify identity parameters for host system, database, and optionally DBMS to create a valid identity for the database schema. Both the physical data model and the database schema are stored in the metadata repository on import.

In the metadata repository, the identity of a logical data model or physical data model is a combination of the name of the model and a namespace value. You specify the value for the Model namespace parameter on the Identity Parameters screen when you import the model.

You can specify whatever value you want. The value does not have to correspond to an actual namespace structure. You can type a namespace value or browse to use an existing namespace value that is in the metadata repository.

By specifying a unique namespace value, you can distinguish between two different logical or physical models that have the same name. If you are importing logical and physical data models at the same time, the namespace value that you specify is used for each of them.

Important: In imports that are created by using design tool bridges in version 8.7 of InfoSphere Information Server, the identity of an imported logical or physical data model includes a namespace value that contains the path of the model file. If you imported the same data model with version 8.7, take either of the following actions:
  • To merge the new data model with the previously imported data model, use the same value for Model namespace that was provided for you in the original import. You can copy this namespace value by browsing to the previously imported logical or physical data model and displaying the model on the Repository Management tab.
  • To create a different identity for the current data model, specify a value for Model namespace that is different from the namespace value of the previously imported data model. The current data model is imported as a unique asset, while the previously imported model remains in the metadata repository. If desired, a Common Metadata Administrator can delete the previously imported data model on the Repository Management tab.