Consider a scenario where you develop a mapping in the development organization and you then migrate the mapping to the production organization.
When you run the mapping in the migrated environment, you might want to use the same or different object path. Based on your requirement, follow the guidelines in this chapter before you migrate to new environment.
The following table lists the override properties that you can configure for an object type before you migrate a mapping:
Object Type
Advanced properties
Single object
Database, table
Multiple objects
Database
Migrate a mapping within the same path
If you want the migrated mapping to use the same object path as in the earlier environment, you must maintain the same database and table in the Hive account for both the organizations.
For example, if you have two different accounts, Account1 used for Org 1 and Account2 used for Org 2, the object path for the database and table name must be the same in both the accounts:
Account1: DB1//TABLE1
Account2: DB1//TABLE1
Migrate a mapping to a different path
You can use a different object path to run the mapping from the new environment. You can override an object if the object specified in the override contains the same metadata as the object specified at design time.
Before you migrate the mapping, you can change the object metadata and runtime attributes to reflect the object path in the migrated environment. You do not have to edit or update the mapping in the new environment.
When you specify the database or table in the advanced properties or object properties, Data Integration honors the attributes in the following order of precedence:
1Runtime advanced attributes. The advanced properties such as database and table in the Source or Target transformation in a mapping.
2Object metadata. The object selected in the Source or Target transformation in a mapping.
Migration options
When you migrate to a different path, you can choose from one of the following options to update the object path:
Option 1. Override the properties from the advanced properties
Before the migration, specify the required database and table name for the object from Org 2 in the advanced properties of the Org 1 mapping.
After the migration, when you run the mapping, the Secure Agent uses the configured advanced parameters to override the object specified in the mapping imported from Org 1.
Option 2. Parameterize the properties in the mapping
You can choose to parameterize the advanced attributes, such as the database and table name before the migration. You can configure input parameters, in-out parameters, and parameter files in the mapping. When you use a parameter file, you can save the parameter file on a local machine or in a cloud-hosted directory. After you migrate the mapping, do not edit or update the mapping. If you have used in-out parameters for the advanced attributes such as for the database and table name, you can update these from the parameter file.
Parameterizing only the advanced properties, but not the object
If you want to parameterize only the advanced properties and use them at runtime, select a placeholder object in the object properties in the mapping and then specify an override to this placeholder object from the advanced properties. Ensure that the placeholder object contains the same metadata as the corresponding table that you specify as an override. When you run the mapping, the value specified in the advanced property overrides the placeholder object.
Parameterizing both the object and the advanced properties
If you want to keep both the Hive object type and the advanced fields parameterized, you must leave the Allow parameter to be overridden at runtime option unselected in the input parameter window while adding the parameters, and then select the required object at the task level. When you run the task, the values specified in the advanced properties take precedence.