About the Process Flow for Migration Resources

The orchestration.json file defines the migration process flow for all the migration resources. The file has the following sections:

• PreProcessing_Export: This section contains the steps to be executed before the resources are exported.

• PostProcessing_Export: This section contains the (user defined) steps to be executed after the resources are exported.

• PreProcessing_Import: This section contains the steps to be executed before the resources are imported.

• PostProcessing_Import: This section contains the steps to be executed after the resources are imported.

• Export: This section contains the resources and the corresponding steps to be exported.

• Import: This section contains the resources and corresponding steps to be imported.

Note: If you made any changes to the ResourceSequence.txt file, then those changes must be added to the orchestration.json file after you complete the upgrade process.

Each Migration resource has a section in the orchestration.json file that describes its process flow. The process flow is made up of a number of sub-processes or steps. Each step in the migration process flow has the following attributes:

• ResType: Specifies the type of resource for migration, such as, pre or postprocessing, Business Service Export, or Import. The value for ResType is Process. This attribute applies only for the PreProcessing_Export, PostProcessing_Export, PreProcessing_Import, and PostProcessing_Import resources.

• PlanType: Specifies the plan type for migration. Possible values are:

  • ["Export"]: This applies for Export Only Asynchronous Migration Execution.

  • ["Import"]: This applies for Import Only Asynchronous Migration Execution.

  • ["Export-Import"]: This applies only for Export and Import Synchronous Migration.

• Business Service. The name of the Siebel Business Service.

• Step Name: The name of the step in the Resource.

• ApplyToResource: Specifies the actual resource for migration. A valid value for ApplyToResource is one or more comma-separated Business Service names, as defined in the Import or Export sections. If this attribute has a value defined, then this step is executed only for the business services mentioned in the Import and Export sections. If this attribute is empty, then this step is executed for all business services. This attribute applies only for the PreProcessing_Export, PostProcessing_Export, PreProcessing_Import, and PostProcessing_Import resources.

• Method. The Siebel Business Service method.

• Location. The location where the Siebel Business Service will be executed. Values are either Source or Target.

• LogMethod: The method used to obtain the logs for the method.

• InArg. The Siebel Business Service input arguments.

• OutArg. The Siebel Business Service output arguments.

• Async. This section contains details if the method is Asynchronous.

  • Async Business Service. The Siebel Business Service Name

  • Async Method. The Siebel Business Service method.

An example of the step sequence in a migration process flow from the orchestration.json file follows:

"Steps": [
          {
           "ResType": "Process",
           "PlanType": ["Export"],
           "Business Service": "Application Migration Utility Service",
           "StepName": "GetWatermarkFromFile",
           "ApplyToResource": ["Migration Schema Service",
                               "Migration Incremental Application Workspace Data Service",
                               "Migration Incremental Runtime Repository Data Service"],
           "Method": "GetWatermarks",
           "Location": "Source",
           "LogMethod": "GetStatus",
           "InArg": ["sharedPath", "filename", "migrationid"],
           "OutArg": ["watermark"],
           "Async": {}
         ] 

For more information about the (preprocessing and postprocessing) operations involved and methods invoked during the execution of a migration plan, see Executing a Siebel Migration Plan.