Creating package definitions

Edit online

Package definitions specify the configuration content that you want to migrate to another environment.

About this task

Use this procedure only to define Snapshot and Change packages. To define Collection packages, you must use the Migration Collections application.

For Snapshot package definitions, you can filter the data by specifying an SQL WHERE clause so that a package contains a smaller set of configuration content. For example, to create a package that migrates only a specific workflow process, you can filter the workflow process migration object in the package definition to select only that one workflow process.

To include GL records, enter an SQL WHERE clause for the DMDEFGLCONFIGURE and DMGLCONFIGURE object structures.
  • For the DMDEFGLCONFIGURE object structure, enter the SQL WHERE clause: orgid is null order by glorder.
  • For the DMGLCONFIGURE object structure enter, the SQL WHERE clause: orgid is not null order by orgid,glorder.

Procedure

  1. In the Migration Manager application, click New Package Definition.
  2. Specify a name for the package definition.
  3. In the Type field, specify SNAPSHOT or CHANGE.
  4. For a Snapshot package definition, in the Processing Action field, specify AddChange or Replace.
  5. Optional: To track only the changes in a Change package that are made by users that are in a specific role, specify the role in the Change Role field.
  6. Add one or more migration groups to the package definition:
    1. In the Migration Groups table window, click New Row.
    2. Specify a migration group.
      Any dependencies are shown in the Dependencies table window.
    3. Optional: To filter the migration objects for a Snapshot package definition, click Set Where Clause and enter an SQL WHERE clause.
  7. Optional: Add compiled sources to the package definition by adding rows to the Compiled Sources table window and specifying the file location.
  8. On the Distribution tab, associate one or more of the defined target environments with the package definition.
  9. Save the package definition.
  10. When the package definition is ready to be used, change its status to Appr
  11. Optional: To start capturing events in a Change package, activate the package definition.