Roadmap for Planning a Migration with Siebel Migration

Environments: All environments

Platforms: All platforms.

This topic provides an overview of the recommended guidelines for planning and managing the data migration process.

Use the following steps to help plan your migration.

Install Siebel Migration. Siebel Migration is installed with Siebel Application Interface as part of the Siebel Enterprise Server software installation. For more information about installing Siebel Application Interface, see Siebel Installation Guide for Microsoft Windows.
Configure Siebel Migration with Siebel Management Console. Siebel Management Console is installed with Siebel Application Interface as part of the Siebel Enterprise Server software installation. Configuring Siebel Migration consists of the following tasks:
1. Create the Siebel Migration Profile. The Siebel Migration Profile is created with the Siebel Management Console. For more information about creating the Siebel Migration profile, see Siebel Installation Guide for Microsoft Windows.
  
  Optionally, you can enter a Migration Package Location when you create a Siebel Migration Profile. You must give a network file share path. If the Migration Package Location is configured in the Migration Profile in Siebel Management Console, the Export, Import and Generate Watermark actions use the Migration Package Location instead of using the migration folder in the file system. If the Migration Package Location field is provided, Siebel Migration copies the exported package file in the Migration Package Location and imports the specified package file from this Migration Package Location instead of the migration folder.
  
  Note: The process running the Siebel Object Manager must have read-write access to the network file share path for the Migration Package Location.
2. Configure Siebel Migration. Siebel Management Console comes with a pre-seed profile. You can either edit the existing pre-seed profile, create a new profile, or create a new profile by cloning the pre-seed profile. For more information about configuring Siebel Migration, see Siebel Installation Guide for Microsoft Windows.
3. Deploy the Siebel Migration Profile. The Siebel Migration Profile is deployed with the Siebel Management Console. For more information about deploying the Siebel Migration Profile, see Siebel Installation Guide for Microsoft Windows.
Configure Authentication for Siebel Migration. Siebel Migration supports Basic and SSO authentication. You select the authentication when creating the Siebel Migration profile in Siebel Management Console. For more information, see Siebel Installation Guide for Microsoft Windows.
- Basic Authentication: Siebel REST services authenticate Siebel Migration users. Basic authentication internally uses the AuthenticateUser method from the Authentication Service For Migration RESTful Service to ensure whether the user has a permission to access the application.
- SSO Authentication: The User is authenticated by the SSO server. Once the user is successfully authenticated, the request is forwarded to Siebel Migration. Siebel Migration uses the AuthenticateUser method from Authentication Service For Migration RESTful services to ensure whether a user has a permission to access Siebel Migration.
- Migration REST Endpoint for Authentication and Data Store: This setting specifies the REST endpoint URL for the Siebel Migration Application. The REST endpoint URL is used to authenticate the Siebel Migration user and to store the Siebel Migration Application data. The format of the URL is as follows where AI_HOST is the Application Interface host name and AI_PORT is the port number: https://AI_HOME:AI_PORT/siebel/v1.0. You can optionally replace the keyword siebel as described in Customizing URLs for Siebel CRM Applications in Siebel Installation Guide for Microsoft Windows.
The Siebel Migration invokes Authentication Service For Migration business service to authenticate a user. You must configure the Authentication Service for Migration business service to restrict the access to the Siebel Migration Application by adding responsibilities to the AuthenticateUser method. For more information about configuring responsibilities and access control for business services, see Siebel Security Guide.
Configure REST Inbound in Siebel Management Console. Siebel Migration uses RESTful service. REST Authentication and REST Inbound Defaults are configured in Siebel Management Console as part of the Siebel Application Interface Profile. For more information about configuring REST Inbound in Siebel Management Console, see Siebel REST API Guide and Siebel Installation Guide for Microsoft Windows.
Setting Up the Siebel Environments. The source and target environments must have several Siebel Server components enabled. For more information about Siebel Server components, see Siebel System Administration Guide.

The source Siebel environment must have the following Siebel Server components enabled.
- Workflow Management Component Group - Workflow Process Manager
- Enterprise Application Integration Component Group - EAI Object Manager
- Siebel Remote Component Group - Synchronization Manager
The target Siebel environment must have the following Siebel Server components enabled.
- Workflow Management Component Group - Workflow Process Manager
- Enterprise Application Integration Component Group - EAI Object Manager
The username requirements for migration are that both source and target environments should have the same username and password.
Set the LDR_CNTRL environment variable for AIX environments. For AIX environments, you must set the value of the LDR_CNTRL environment variable to the following:
```
LDR_CNTRL=LOADPUBLIC@MAXDATA=0x60000000
```
For more information about the LDR_CNTRL environment value, see Siebel Performance Tuning Guide.
Generate the storage control file. Log into the target Siebel Server and navigate to the <Siebel Server Home>/bin directory. Execute the following command:
```
trgxtrct /u <database username> /p <database password> /c <ODBC Data Source> /d <Table Owner> /o <output path>/storage.ctl /4 BP2 /7 <DB Encoding Schema>
```
Once the storage control file is generated, copy the newly generated storage.ctl file to the following location:
```
<Target Siebel File System path>/migration/control/storage.ctl
```
Prepare the migration data. Siebel Migration exposes Database Utilities that you can use to prepare your data for migration. For more information about preparing data for migration, see Process of Preparing Siebel Application Data for Migration.
1. Create Application Deployment Manager projects. Use Siebel Application Deployment Manager to create Application Deployment projects. For more information about creating Application Deployment Manager projects, see Siebel Application Deployment Manager Guide.
  
  Note: To export the ADM Package on the source environment, you must create a Deployment Project with the Export to File flag set to TRUE in the Deployment Projects view in the Application Deployment Manager screen. However, the Export to File flag must not be set to TRUE for Export and Import together.
  In the Source environment, to export the ADM Project into a file, the EAIFileTransportFolders parameter should have the <Siebel File System>\migration folder configured. Otherwise, the export file fails due to a write permission issue. For more information about enabling write access for the EAI File Transport, see Transports and Interfaces: Siebel Enterprise Application Integration.
  To import the exported package on the Destination environment, the Deployment Project Name must be same as the Source Deployment Project Name or the import will fail.
2. Use Application Deployment Manager to transform data. Use Application Deployment Manager to create data maps to transform your migration data. For more information about transforming data with Application Deployment Manager, see Process of Transforming Data with Siebel Application Deployment Manager.
3. Customize Migration Process Orchestration. You can add new migration resources to the ResourceSequence.txt file. The Siebel Migration Application reads through this file during the execution process and executes the services in a sequential order. You can customize the sequence of the migration process by modifying the ResourceSequence.txt file. For more information about customizing the migration process orchestration, see About Migration Process Orchestration During the Siebel Migration Process.
Use Siebel Migration. Use Siebel Migration to add connections to a migration, create migration plans, execute migration plans, and review migration history. For more information about using Siebel Migration, see Data Migration Using Siebel Migration.
Review Migration Log Files. Use Siebel Migration to review migration log files. For more information about migration log files, see About the Siebel Migration Log Files.