21Data Preparation for Siebel Migration

Data Preparation for Siebel Migration

This chapter provides initial preparatory information for migrating your data with Siebel Migration. This chapter includes the following topics:

• Process of Preparing Siebel Application Data for Migration

• Creating Migration Rules

• Process of Transforming Data with Siebel Application Deployment Manager

• Customizing Siebel Migration Execution and Resource Sequencing

• Setting Up File Prepare and Deploy

Process of Preparing Siebel Application Data for Migration

Environments: All environments.

Before you use the Siebel Migration to migrate your data, you must perform the following tasks:

1. Configure and deploy your Migration Profile using Siebel Management Console. For more information about using Siebel Management Console to configure and deploy your Migration Profile, see Siebel Installation Guide for Microsoft Windows.

2. Create Migration Rules. For more information about creating migration rules, see Creating Migration Rules.

3. Create ADM Data Maps to transform the data with Application Deployment Manager. For more information about creating ADM Data Maps to transform the data with Application Deployment Manager, see Process of Transforming Data with Siebel Application Deployment Manager.

4. Customize Siebel Migration Execution and Resource Sequencing. For more information about customizing Siebel Migration Server Execution and Resource Sequencing, see Customizing Siebel Migration Execution and Resource Sequencing.

5. Setup File Prepare and Deploy. For more information, see Setting Up File Prepare and Deploy.

Creating Migration Rules

For migration, the Migration Input (INP) file and the Transformation (RUL) file are the input files required to do the initial data export and import of data. For more information about the INP and RUL files, see About Siebel Rules Expression Designer.

After you create your migration rules and export them, the datamig.inp file is generated and the datamig.rule file is generated only if you select an Update Action during the process of creating your rules with the Expression Designer.

This procedure describes how to create a migration rule using the Migration Rules Expressions Designer.

To create a migration rule

1. Navigate to Site Map, then Administration - Application, then Migration Rule.

2. In the Migration Rule Expressions applet, click New.

3. Click the icon next to the Table column.

4. Select the table to migrate the data from the source environment to the target environment.

5. To migrate only selective data from the table, perform the following steps:

   1. Click the icon next to the Condition column.

   2. In the Expression Designer, the Table Category is automatically selected.

   3. Select items in Sub Categories. Column names appear in Elements that match the selected subcategory.

   4. Choose the appropriate column name in Elements and click Add Element.

   5. Enter a value to filter the data.

   6. Click Validate and verify there are no syntax error in the Expression.

   7. Click Save.

6. To transform only the data on selective columns when migrating the data from the source environment to the target environment, perform the following steps:

   1. Click the icon next to the Update Action field.

   2. Select the appropriate column and the value.

      The values assigned to the columns chosen will be updated on the target environment regardless of the value specified in the source environment.

7. Select the Select Flag.

8. Click Save.

9. To add another table, repeat steps 1-8.

10. Once you add the records for all the tables that you wanted, click Export.

    Once the data is exported, the datamig.inp file and the datamig.rul file are generated.

Process of Transforming Data with Siebel Application Deployment Manager

Application Deployment Manager (ADM) is a Siebel tool that you can use to deploy data from the source environment to the target environments. For more information about Application Deployment Manager, see Siebel Application Deployment Manager Guide.

For your data migration, you can use ADM to:

• Create ADM Projects that can be migrated by Siebel Migration. For more information about creating ADM projects, see Application Deployment Manager Guide.

  When you create your ADM Project, you can configure the Sequence Number. The Sequence Number is populated in the Project Items. ADM migrates the Project Items in the sequence order according to the value of the Sequence Number parameter. If the sequence number is not provided, ADM will follow the default behavior.

• Create an ADM Data Map to transform data before importing into the target environment. For more information about creating ADM maps, see Creating an ADM Data Map.

• Associate your data map to your project item. For more information about associating data maps to ADM projects, see Associating a Data Map to a Project Item.

Creating an ADM Data Map

This topic provides procedures for creating an ADM Data Map.

This task is a step in Process of Preparing Siebel Application Data for Migration.

To create an ADM data map

1. Navigate to the Site Map, Administration - Integration, and then Data Map Editor.

2. In the Data Map Editor applet, create a new record.

3. Enter a Name for the data map.

4. Choose the Integration Object that is used in the Data Type for both the Source Object Name and the Target Object Name.

5. Click Auto-Map to populate the Integration Component Map and Integration Field Map fields.

6. In the Integration Component Map applet, select the Integration Component to transform the data.

7. In the Integration Field Map applet, select the Field to transform the data.

8. In the Source Expression column, enter the expression to transform the data. For more information about supported expressions, see Siebel Application Deployment Manager Guide.

9. Click Save.

Associating a Data Map to a Project Item

This topic provides procedures for associating an ADM Data Map to a Project Item.

This task is a step in Process of Preparing Siebel Application Data for Migration.

To associate a Data Map to a project item

1. Navigate to the Site Map, Application Deployment Manager, and then Deployment Projects.

2. Choose an existing Deployment Project or create a new Deployment Project and fill the necessary details. To create a new Deployment Project, see Siebel Application Deployment Manager Guide.

3. Choose an existing Project Item or create a new Project Item and fill the necessary details. To create a new Project Item, see Siebel Application Deployment Manager Guide.

4. Click the Data Map column on the Project Items applet and select the Data Map that will be used to transform the data.

5. Click Save.

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\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|Input 
Y\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.

Setting Up File Prepare and Deploy

Siebel Migration File Prepare and Deploy service does the following:

• Migrates file artifacts from the source environment to the target environment.

• Migrates only file artifacts from Siebel Application Interface (AI) and the Siebel File System.

• If the target environment has multiple Application Interface nodes, it migrates all file artifacts to all the Application Interface nodes.

• Supports incremental file Migration (migrates only new or modified files).

• Uses the Checksum utility to check whether the file is modified or not.

The list of directories considered for Migration are configured in the filemig_config.properties file. The filemig_config.properties file is located in the following directory:

<Application Interface Home>\applicationcontainer\webapps

The filemig_config.properties file:

• Contains three properties:

  • inclusion-dir

  • exclude-dir

  • exclude-extension

• Considers all the files from the list of directories provided in the inclusion-dir property.

• Ignores all the directories mentioned in the exclude-dir from the include-dir only.

• Ignores the files whose extensions are part of exclude-extension property

Sample filemig_config.properties file:

inclusion-dir=%ORACLE_HOME%/applicationcontainer/webapps/siebel/files, %FS_HOME%/
att
exclude-dir=%ORACLE_HOME%/applicationcontainer/webapps/siebel/files/3rdParty
exclude-extension=xps, pdf

Where:

• %ORACLE_HOME% is the AI installation directory.

• %FS_HOME% is the Siebel File System Path.

You can add multiple directories separated by a comma.