8.3 Object Migration

Object Migration is the process to define, export and import objects across environments (prod and non-prod)/instances. This feature also facilitates to migrate within the same setup or different setups.

Objects refer to the various metadata definitions defined for various domains. You may want to migrate objects for several reasons such as manage global deployments on multiple environments or to create multiple environments so that you can separate the development, testing, and production processes.

For example, you can use the object migration feature to define PMF process object such as balance computation on your testing environment. After successful testing, you can use this feature to export the object to production/non-production environment.

You can migrate the following object types:

• Schedule - Schedule provides the instruction to schedule the execution of defined processes. When a schedule is migrated, the associated batch is also migrated.
• Batch - Batch is a group of jobs. When a batch is migrated, the batch and the associated pipeline information are also migrated. Note that the dependent objects used in the batch are not exported. All the objects used in the batch must be present in the target environment before the batch definition is imported.
• Batch_Group - A set of individual batches are consolidated to form a single Batch_Group. When we migrate a Batch_Group all the batches, tasks and pipeline information associated with that Batch_Group are also migrated.
• Roles - Roles are used to map functions to a defined set of groups to ensure user access system security.
• Groups - Groups are used to map Roles. Specific User Groups can perform only set of functions associated with that group.

  Note:

  System can successfully import any object if both Code/Name do not exist in the target. If either code or name of the object being migrated is already available in target, import will fail. Even if overwrite option is selected, object will only be overwritten in target if both object code/name matches in target environment.

  For example, if an interest rate curve is being migrated, and either code or name is already available in target environment, import will fail.