Migrating Configuration Data and Incremental Changes

When migrating configuration data (such as LOVs, runtime events, and data mapper) and incremental changes, note the following:

• LOVs are versioned and may change from one incremental migration to the next.

• Performing a full migration creates a single instance of all repository objects and LOVs with version 0.

• During incremental migrations, new and/or modified LOVs from the DR are created in the RR with new version numbers.

• To seed a new Target environment with all the LOVs and repository objects, the first migration that you perform must always be a full migration.

  Note: After a flatten Workspace operation, the next migration must always be a full migration. For more information about flattening Workspaces, see Using Siebel Tools.

• Since LOVs are Workspace-enabled, use the Application Workspace Data Service and Incremental Application Workspace Data Service to migrate LOV data including incremental changes.

  For all other configuration data (bar incremental changes), use the Application Data Service, Application Data Service with Transformation, or Application Deployment Manager Projects to migrate data.

  • For example, to perform a full migration of LOVs using Siebel Migration Application, select the following resource options:

    • Schema Service

    • Runtime Repository Data Service

    • Application Workspace Data Service

  • For example, to perform an incremental migration of LOVs using Siebel Migration Application, select the following resource options:

    • Schema Service

    • Incremental Runtime Repository Data Service

    • Incremental Application Workspace Data Service