Customizing Siebel Migration Execution and Resource Sequencing

Siebel Migration executes a set of business service methods for each migration resource. The execution sequence of these methods is defined by an external sequence text file, ResourceSequence.txt.

The ResourceSequence.txt file is located in the following directory:

<Application Interface Home>\applicationcontainer_external\webapps\siebel\WEB-INF

Siebel Migration reads through this file during the execution process and executes the services in a sequential order. The ResourceSequence.txt file lists the names of the Business Services for each resource and the supported methods for Export, Import and Status.

You can customize Siebel Migration execution and resource sequencing by adding business services to the ResourceSequence.txt file. For more information about guidelines for adding business services to the ResourceSequence.txt file, see About Migration Process Orchestration During the Siebel Migration Process.

In the ResourceSequence.txt file, business services have the following structure:

<Service Name>, 
<Method:Source/Target:Sync\Async:FT:trackingIdMethod:{Watermark Method Name|Source\Target|InputY\N}>, 
<Method:Source/Target:Sync\Async:FT:trackingId:{Watermark MethodName|Source\Target|InputY\N}>, 
GetStatusMethod

Where:

• <Service Name> indicates the name of the business service.

• <Method> indicates the method name.

• Source\Target indicates whether the method will be executed on the migration source or target.

• Sync\Async indicates whether the method is sync or async.

• <FT> indicates whether a file transfer is required Y\N.

• trackingIdMethod indicates the MethodName whose trackingId should be the input for the GetStatus and Import methods.

• Watermark details:

  • Watermark Method Name

  • Source\Target

  • Input required Y\N

• GetStatusMethod indicates the status method for async methods.

Note: Existing business service entries and sequence must not be modified.

File Transfer Service is a another service which is not part of Migration discovery.

The details of the File Transfer Service are as follows:

[File Transfer Resource]
Dock Migration File Transfer Service,GetConnectString,ImportFile,GetStatus

Example of adding a new business service in the resource sequence file:

Migration Schema Service,Export:Source:Async:::Y,Import:Target:Async:Export::N,GetStatus

In this example:

Business Service Name is Migration Schema Service with 2 async methods. Export method should be run on Source and requires File Transfer. Import method should be run on Target and does not require File Transfer. GetStatus method is used to poll the status of these methods.

For sync methods, GetStatusMethod is not required. Execution will continue based on the HTTP response code.