Siebel Database Upgrade Guide for DB2 for z/OS > Planning for a Dev to Test to Production Using Siebel Migration >

About Migration Process Orchestration During the Siebel Migration Process

Environments: Development, production test, production.

Platforms: Windows, UNIX, IBM z/OS.

During the migration process, the Siebel Migration application executes a set of business service methods for each resource. The execution sequence of these service methods is defined by an external sequence text file, the ResourceSequence.txt file. The ResourceSequence.txt file lists the names of the Business Services for each resource and the supported methods for Export, Import, and Status. The ResourceSequence.txt file defines the order of migration execution.

The Siebel Migration application reads through this file during the execution process and executes the services in a sequential order.

The migration will execute a resource only if the resource is present in the ResourceSequence.txt file. If the resource is not defined in the ResourceSequence.txt file, the resource will not appear in the Siebel Migration and will not be executed.

New migration resources can be added to the ResourceSequence.txt file in the required execution order. New business services should adhere to the following standards:

1. The business service must support methods for Import, Export, and GetStatus.
2. Any extra methods or extra Input or Output to these methods are considered as exceptions and requires handling in the Siebel Migration code before inclusion in sequence file.
3. If the methods are Sync methods that do not support GetStatus, then the execution will proceed based on the HTTP response and the output parameters will not be parsed. If parsing is required for the output parameters, then it should be handled in the Siebel Migration code.
4. Oracle recommends that you do not modify the existing data in the ResourceSequence.txt

Related Topics:

Customizing Siebel Migration Execution and Resource Sequencing