Executing a Siebel Full Migration Plan

This topic describes how to use Siebel migration to execute a full migration plan.

As migration plans are intended to be re-usable, they define only the source, target, and the resources (such as Schema Service, ADM Projects, and so on). The selection of Source Workspace and Version are selected at the time of execution.

When you execute a synchronous full migration plan, the migration application prompts for the source workspace, along with the target database schema owner and password.

For an asynchronous full migration export job, the prompt is similar, but doesn't require the target schema owner and password, as shown in this image.

Creating and Executing Migration Plans Through REST

This change affects REST calls to both create and execute migration plans for full migration. Information about the workspace name and version are passed to the execution call.

Note:

You don't have to change any existing scripts that create full migration plans that include the parameters integrationBranchName (Workspace Branch Name) and irrEndVersion (Workspace Version). This information will now be ignored when you create a migration plan for full migration. You simply must adjust the execution plan to include this information.

The new JSON payload for executing a full migration plan includes the two parameters required to specify the Workspace and Version.

Example of synchronous migration plan execution:

{  
   "integrationBranchName": "MAIN",
   "schemaUser":"orarnr138",
   "schemaPassword":"TVNTUUw=",
   "watermarkFilename":"frr_watermark.txt",
   "irrEndVersion":"7",
   "packageFilename":"frr_export_package.zip",
   "isUnicodeDatabase":"Y"
}

Example of asynchronous Migration Plan Execution (export):
{  
   "integrationBranchName": "MAIN",
   "irrEndVersion":"7",
   "packageFilename":"frr_export_package.zip",
}