Modes of Operation

Based on the value specified for the argument MIGRATION TYPE, the utility can be operated in different modes:

Note:

Recommended modes are UPGRADE and ONLY_ DEFINITION.

MIGRATION TYPE set as UPGRADE

./DMTUpgradeUtility_806.sh UPGRADE <METADATA_TYPE>

In this scenario, the utility will check for the value set for METADATA TYPE. If it is set as ALL, the XML data of all metadata types will be migrated to the corresponding tables. If METADATA TYPE is set to a specific metadata, then the XML data of only that specific metadata will be migrated.

For example,

./DMTUpgradeUtility_806.sh UPGRADE DMT_DM

Note that INFODOM NAME and DEFINITION NAME will be implicitly set to ALL, irrespective of what the user sets.

If metadata type is not set, it is implicitly set as ALL. For example, if you execute the following command, all metadata types will be migrated:

./DMTUpgradeUtility_806.sh UPGRADE

In case of rerun of the migration utility, if a metadata is already present in the target environment, that metadata will be skipped.

MIGRATION TYPE set as UPGRADE_AS_VERSION

./DMTUpgradeUtility_806.sh UPGRADE_AS_VERSION <METADATA_TYPE>

In this scenario, the specified metadata type will be migrated to the corresponding tables by incrementing the version if the definition already exists in the target environment. If <METADATA_TYPE> is set as ALL, all metadata types will be migrated.

For example,

./DMTUpgradeUtility_806.sh UPGRADE_AS_VERSION DMT_PLC

Note that INFODOM NAME and DEFINITION NAME will be implicitly set to ALL, irrespective of what the user sets.

If metadata type is not set, it is implicitly set as ALL. For example, if you execute the following command, all metadata will be migrated:

./DMTUpgradeUtility_806.sh UPGRADE_AS_VERSION

MIGRATION TYPE set as ONLY_DEFINITION

./DMTUpgradeUtility_806.sh ONLY_DEFINITION <Metadata type> <information domain name> <Definition name>

This mode is used to migrate XML data of a particular definition to the corresponding tables. In this mode, it is mandatory to set METADATA TYPE, INFODOM NAME and DEFINITION NAME arguments. Otherwise, the utility execution will fail.

For example,

./DMTUpgradeUtility_806.sh ONLY_DEFINITION DMT_DM OFSAAINFO <Application Name>~<Source Name>~<Definition Name>

./DMTUpgradeUtility_806.sh ONLY_DEFINITION DMT_DRC <Source Name 1>~<Infodom 1>,<Source Name 2>~<Infodom 2>,<SourceName3>~<Infodom3>

Note:

The Metadata Type DMT_SRC is supported only for table based sources in ONLY_DEFINITION mode. For Metadata Type DMT_DM, <information domain name> should be a valid Infodom name, but the definition will not be migrated to the specified Infodom name. It will be migrated to all its mapped Information Domains, which are listed in the ETLrepository.xml file.

In case of rerun of the migration utility, if a metadata definition is already present in the target environment, that definition will be skipped.

MIGRATION TYPE set as ONLY_DEFINITION_AS_VERSION

./DMTUpgradeUtility_806.sh ONLY_DEFINITION_AS_VERSION <Metadata type> <information domain name> <Definition name>

This mode is used to migrate XML data of a particular definition to the corresponding tables by incrementing the version if the definition already exists in the target environment. In this mode, it is mandatory to set METADATA TYPE, INFODOM NAME and DEFINITION NAME arguments. Otherwise, the utility execution will fail.

For example,

./DMTUpgradeUtility_806.sh ONLY_DEFINITION_AS_VERSION DMT_DM OFSAAINFO F2Tdefinition1

For Metadata Type DMT_DM, <information domain name> should be a valid Infodom name, but the definition is not migrated to the specified Infodom name. It will be migrated to all its mapped Information Domains, which are listed in the ETLrepository.xml file.