22Data Migration Using Siebel Migration

Data Migration Using Siebel Migration

This chapter provides guidelines for performing a migration with Siebel Migration. This chapter includes the following topics:

• Before You Begin Migrating with Siebel Migration

• Process of Using Siebel Migration to Migrate Data

• Asynchronous Migration Using Siebel Migration

• Incremental Migration from a Development to a Production Environment Without Using Siebel Migration

• Full RR Migration Without Using Siebel Migration

• Migrating Siebel 18.8 Update or Later Release Repository Changes from a Development to a Production Environment

• Activating Workflows and Tasks in the Production Environment After Full Migration

• Migrating Configuration Data and Incremental Changes

• About Migrating User Preferences

Before You Begin Migrating with Siebel Migration

Before you begin using Siebel Migration:

1. Review and follow the tasks listed in Roadmap for Planning a Migration with Siebel Migration

2. Start Siebel Migration with the following URL format:

   https://<hostname>:<port>/siebel/migration

3. Back up your target database before starting to migrate repository or data using Siebel Migration

Process of Using Siebel Migration to Migrate Data

This procedure describes how use Siebel Migration for migration tasks. Siebel Migration tasks include:

1. Creating Connections. For information on creating connections, see Creating a Connection.

2. Generating Watermarks. For more information on creating watermarks, see Generating a Watermark

3. Creating Migration Plans. For more information on creating migration plans, see Creating a Migration Plan.

4. Executing Migration Plans. For more information on executing migration plans, see Executing a Siebel Migration Plan.

5. Reviewing Migration History. For more information about reviewing migration log history, see Viewing Migration History and Log Files.

Creating a Connection

Use Siebel Migration to create a connection, which registers a Siebel environment to the Siebel Migration. Each connection represents on Siebel environment and numerous connections can be created for a migration.

This procedure describes how use Siebel Migration to create an environment connection for a migration.

This task is a step in Process of Using Siebel Migration to Migrate Data.

To create a connection

1. In Siebel Migration, navigate to the Connection Tab.

2. Click New Connection.

3. Enter a Name for the new connection.

4. Enter a Valid Endpoint for the connection.

   The valid REST Endpoint format is the following:

   https://<hostname>:<port>/siebel/v1.0
   

5. Verify the status of connection. Statuses include:

   • Green: Connection Alive

   • Red: Connection Not Alive

   • Grey: Connection Unknown

Generating a Watermark

Use Siebel Migration to create a watermark. A watermark is useful to see the data that was previously migrated to your database environment. Based on the previously migrated data, you can determine the correct incremental version that you need to migrate.

Siebel Migration obtains the current repository watermark from the Siebel Server. Siebel Migration generates the watermark for the Web artifacts file from the Siebel Application Interface folder and then writes the watermark file into the filename provided by the user in the migration folder under the file system or Shared Package Location if provided. The connection that points to the Siebel Server must be a Runtime Repository environment. If the connection points to a development environment, then Siebel Migration throws an error.

This task is a step in Process of Using Siebel Migration to Migrate Data.

To Generate a Watermark

1. In Siebel Migration, navigate to the Connection Tab.

2. Click the Watermark icon.

3. Enter the Watermark file name.

4. Click OK.

   After creating the watermark file, a window displays a success message with the path and filename for the watermark file.

Creating a Migration Plan

When you create a Migration Plan, you must select connections, including the source environment and the target environment. When you run the Migration Plan, Siebel Migration exports the migration data from the Source environment and imports it into the Target environment.

When you create the Migration plan, you must select the resources that you want to migrate as part of this migration plan. In Siebel Migration, you can select Database Utilities, ADM Projects or File Prepare and Deploy services.

This procedure describes how use Siebel Migration to create a migration plan for a migration.

This task is a step in Process of Using Siebel Migration to Migrate Data.

To create a migration plan

1. In Siebel Migration, navigate to the Migration Plan tab.

2. Click New Migration.

3. Enter the Name of the Migration Plan and Description.

4. Select and move the Source Connection & Target Connection onto the Flow Chart.

   An intersection of Migration Resources (between Source & Target) for Database Utilities and only from Source for ADM Projects will be displayed.

5. Select the Migration Resource that will be executed as part of the Migration Plan.

Siebel Migration Plan Dependencies

The Siebel Migration Discovery services that appear in Siebel Migration depend on the selections that you make. The following table outlines the Siebel Migration plan dependencies.

If You Select this Resource...	Read Only Resources	Auto Selected Resources
Application Workspace Data Service	Incremental Repository Service Incremental Application Workspace Data Service	Runtime Repository Service
Incremental Application Workspace Data Service	Runtime Repository Data Service Application Workspace Data Service	None
Runtime Repository Data Service	Incremental Repository Service Incremental Application Workspace Data Service	Application Workspace Data Service
Incremental Runtime Repository Data Service	Runtime Repository Service Application Workspace Data Service	None

Executing a Siebel Migration Plan

This procedure describes how to use Siebel Migration to execute a migration plan for a migration.

This task is a step in Process of Using Siebel Migration to Migrate Data.

Executing a migration plan

1. In Siebel Migration, navigate to the Execution tab.

2. Identify the Migration Plan to be executed.

3. Click Play next to the Migration Plan to be executed.

   The Execution Details window displays. Depending on the selections you made when you created your Migration Plan, you will see one of the following prompts in the Execution Details window:

   • Database Encoding. You will be prompted for database encoding information if you created your Migration Plan as Import only with a Schema Service selected or if your Migration Plan was created for both Source and Target with a Schema Service selected.

   • Workspace Version Selection. You will be prompted for the Workspace version if you run the Incremental Runtime Repository service.

4. For the Database Encoding Execution Details window, enter the following information:

   1. Enter the User ID. The User ID is the Username for the Target table owner.

   2. Enter the Password for the Target table owner.

   3. Select one of the following Database Encoding options:

      • UNICODE Database. This option is selected by default.

      • NON-UNICODE Database. If you are using a NON-UNICODE Database, then you must select the NON-UNICODE Database option.

   4. Enter the Workspace Version Number. The Workspace Version Number is the range between the next version of the Target and the latest available version on the Source.

      The Workspace Branch Name is a read only field and is populated based on the Workspace Version Number that you enter.

      Note: If the Migration Plan that you are executing has both the Source and Target selected, then the Workspace Branch Name and Workspace Version fields are automatically populated.

   5. Click OK.

5. If you selected the option to run the Incremental Runtime Repository service, the Execution Details window prompts you to enter the following information:

   1. Enter the User ID for the Target Table Owner.

   2. Enter the Password for the Target Table Owner.

   3. Enter the Package Filename (.zip file).

   4. Enter the Watermark (.txt file).

   5. Click the Get Workspace Details button to populate the Workspace Branch Name and Workspace Version fields.

   6. Click OK.

6. While the Migration Plan is running, click Refresh to refresh the Migration Plan or get status for a migration task.

7. While the Migration Plan is running, click Log to view log details for a migration task.

Note: If the Schema Service is part of the Migration Plan, then the application prompts you for Target Database Schema Owner credentials.

After Execution of Runtime Repository Data Service Completes

After execution of the Runtime Repository Data Service completes, you must perform the following steps in the target environment:

1. Rename the Migrated Repository to Siebel Repository, and then restart the Siebel Server - for more information, see Step 10 in Full RR Migration Without Using Siebel Migration.

2. Activate workflow tasks by running ActivateWorkflowsTasks - for more information, see Step 11 in Full RR Migration Without Using Siebel Migration.

Preprocessing and Postprocessing for Migration Execution

The operations involved during the preprocessing and postprocessing of any migration plan execution include for example, Package, Unpackage, Transfer the File (for Sync migration), Create Manifest, GetConnectString, and so on. A number of preprocessing and postprocessing methods are invoked during the execution of a migration plan. The following table describes these methods, which are in the orchestration.json file.

Resource	Operation	Purpose	Applies to Resource	Mode
PreProcessing_Export	GetWatermarks	Gets the watermark details from the watermark file specified during migration execution.	Migration Schema Service. Migration Incremental Application Workspace Data Service. Migration Incremental Runtime Repository Data Service.	Asynchronous
PreProcessing_Export	GetWaterMark	Gets the watermark details by invoking the REST request to the Target.	Migration Schema Service. Migration Incremental Application Workspace Data Service. Migration Incremental Runtime Repository Data Service.	Synchronous
PostProcessing_Export	CreateManifest	Creates the manifest file, which includes all the details of the resource being exported. The manifest file is used to validate credentials during the asynchronous migration import.	All services.	Synchronous Asynchronous
PostProcessing_Export	preparePackage	Creates a compressed package file that contains all the exported resources.	All services.	Synchronous Asynchronous
PostProcessing_Export	GetConnectString	Gets the SynchMgr Object Manager Connect String from Source. This will be used by ImportFile to transfer the file from Source to Target. This operation applies only if the Migration Package Location in the migration profile in Siebel Management Console is not specified.	All services except ADM.	Synchronous
PostProcessing_Export	ImportFile	Transfers the package from Source to Target. This operation applies only if the Migration Package Location in the migration profile in Siebel Mobile Console is not specified.	All services except ADM.	Synchronous
PreProcessing_Import	unPackage	Decompresses the exported package.	All services.	Synchronous

Viewing Migration History and Log Files

You can use Siebel Migration to view migration history and log files for a migration task. You can also view information such as status, Archive ID, and the filename for the migration package.

This task is a step in Process of Using Siebel Migration to Migrate Data.

To view migration history and log files

1. In Siebel Migration, navigate to the History or Execution tab.

2. Select or click the plus (+) icon next to the migration task to show the log generated for the operation.

   For example, if you select the Incremental Runtime Repository Migration task, the task expands to show the Resource and Operation.

3. Click Log next to an operation to view the log details for that migration operation.

   From Siebel CRM 19.7 Update onwards, you can review logs for the following Siebel Migration resource operations:

   • Runtime Repository Data Service: GetWatermark operation.

   • Application Workspace Data Service: GetFullSeedWatermark and GetSeedCopyWatermark operations.

   • Incremental Runtime Repository Data Service: ActivateWorkflowsTasks operation.

   • Incremental Application Workspace Data Service: InvalidateSeedCaches operation.

   • File Prepare and Deploy: generateWatermark, readwatermarkfile, writewatermarkfile operations.

Reviewing Execution Log Messages

Log messages typically record the Archive Id, Resource name, and the Operation name in the log file along with the log message. After an Archive Id is generated, all corresponding log messages will contain the Archive Id.

Log files are generated by the Siebel Migration application but they are not visible in the migration UI. If errors are encountered during migration execution, then you can review the migration.log file located in the migration server’s Application Interface application container’s \logs folder to determine why the migration failed and to decide how to resolve the issue.

• To find and review the logs generated for a particular migration execution, then search for the appropriate Archive Id in the migration.log file.

• To find and review the logs generated by a specific Resource under an Archive Id, then search for the Resource name in the migration.log file.

• To find and review the logs generated by a specific Operation under a Resource Name, then search for the Operation in the migration.log file.

Note: Migration logs are stored in the migration server’s application container’s (Apache Tomcat) log location: <AI_ROOT>\applicationcontainer\logs.

Once Siebel Migration starts executing operations that are part of a resource in the Migration Plan, all resulting log messages will contain the appropriate Archive Id, Resource name, and Operation name as shown in the following examples.

Example Log 1: Archive Id is in Brackets

[DEBUG] 2018-10-25 04:41:24.203 [Thread-33] Migration - com.siebel.migration.server.Transaction:callExecutor [88-1VBW0R] Exporting resource {"name":"Migration Schema Service","URI":["https:\/\/slc04ovj.us.oracle.com:9001\/siebel\/v1.0"],"Source":"https:\/\/slc04ovj.us.oracle.com:9001\/siebel\/v1.0","Target":"https:\/\/slc07fnj.us.oracle.com:9001\/siebel\/v1.0","Steps":[{"StepName":"Export","Business Service":"Migration Schema Service","Method":"Export","InArg":["migrationid"],"OutArg":["trackingid"],"Location":"Source","Async":{"Async Business Service":"Migration Schema Service","Async Method":"GetStatus","Async InArg":["migrationid","trackingid"],"Async OutArg":["error","getlog","log","status"]}}],"TransId":"88-1VBW0R","rowId":["88-1VBW0S"],"Watermark":"","ActivationDate":""} 
[DEBUG] 2018-10-25 04:41:24.212 [Thread-33] Migration - com.siebel.migration.server.ProcessFlow:<init>[88-1VBW0R] Entered process flow for resource : Migration Schema Service

Example Log 2: Archive Id and Resource Name are in Brackets

[DEBUG] 2018-10-25 04:41:24.214 [pool-4-thread-2] Migration - com.siebel.migration.server.ProcessFlow:getResources [88-1VBW0R] [Migration Runtime Repository Data Service] Entered get resources for resource : Migration Runtime Repository Data Service
[DEBUG] 2018-10-25 04:41:24.216 [pool-4-thread-1] Migration - com.siebel.migration.server.ProcessFlow:getResources [88-1VBW0R] [Migration Schema Service] Entered get resources for resource : Migration Schema Service
[DEBUG] 2018-10-25 04:41:24.216 [pool-4-thread-3] Migration - com.siebel.migration.server.ProcessFlow:getResources [88-1VBW0R] [Migration Application Workspace Data Service] Entered get resources for resource : Migration Application Workspace Data Service

Example Log 3: Archive Id, Resource Name and Operation are in Brackets

[DEBUG] 2018-10-25 04:41:24.234 [pool-4-thread-2] Migration - com.siebel.migration.server.Transaction:invokeRestCall [88-1VBW0R] [Migration Runtime Repository Data Service] [GetWatermark] Input PostData : {"body":{"workspace":"MAIN","language":"ENU","version":"0"}}
[DEBUG] 2018-10-25 04:41:24.251 [pool-4-thread-3] Migration - com.siebel.migration.server.ProcessFlow:getResources [88-1VBW0R] [Migration Application Workspace Data Service] [GetFullSeedWatermark] Argument Map constructed : {migrationid=88-1VBW0R, password=, workspace=MAIN, fileName=Migration_88-1VBW0R.txt, filename=, watermark=, isUnicodeDatabase=Y, sharedPath=, language=ENU, ActivationDate=, version=0, username=}

Asynchronous Migration Using Siebel Migration

You can use Siebel Migration to plan and carry out an asynchronous migration. An asynchronous migration essentially involves creating an asynchronous migration plan for the source environment and another (separate) asynchronous migration plan for the target environment. Migration activities that must be completed on the source environment can then be carried out independently of the migration activities that must be completed on the target environment. For asynchronous migration to work, both source and target environments must be in a Repository Upgraded state; otherwise migration execution will be performed in synchronous mode.

According to the source and target environment state, the following table outlines the supported migration scenarios. These migration scenarios are supported. using either the Siebel Migration application or REST API, in Siebel CRM 18.11 Update and later releases.

Source and Target State	Export Only Migration	Import Only Migration	Export and Import Migration
Source is Repository Upgraded, Target is not.	Supported	Not Supported	Supported
Both Source and Target are Repository Upgraded.	Supported	Supported	Supported
Source is not Repository Upgraded, Target is Upgraded	Not Supported	Not Applicable	Supported

Note: A Repository Upgraded state means that the environment (repository and schema) has been upgraded to Siebel 18.8 Update or later release of Siebel CRM.

Caution: It is recommended that you back up your target database before starting to migrate repository or data using Siebel Migration.

The steps to perform an asynchronous migration using Siebel Migration are outlined in the following procedure and involve the following:

• Generating a watermark if required.

• Creating and executing an export only migration plan to export resources from the source environment.

• Creating and executing an import only migration plan to import (exported) resources to the target environment.

Note: If your Runtime Repository Data Service or Incremental Runtime Repository Data Service migration plan does not include the non-mandatory Schema Service, then you must migrate any schema changes before executing the plan.

To perform an asynchronous migration using Siebel Migration

1. Generate a watermark if required. To export an Incremental Runtime Repository, you must get the Watermark file from the target environment where you are planning to import the exported data.

   Note: You must ensure that the watermark you use is the latest watermark. If you export the repository using an old watermark, then the import will fail with an error message similar to the following: Watermark does not match the exported resources watermark.

   1. Navigate to the Connections tab in Siebel Migration.

   2. Click the Watermark icon next to the target connection (that is, the target environment where you want to import the exported data).

   3. In the dialog that appears, enter the Watermark file name and click OK.

      If the Migration Package Location is configured on the Migration Profile in Siebel Management Console, then the Watermark file is generated in the Migration Package Location path. Otherwise the Watermark file is generated in the <File System>\migration folder on the selected connection.

2. Create an export only migration plan on the source environment.

   1. Navigate to the Migration Plan tab in Siebel Migration.

   2. Click New Migration and then enter the Name of the migration plan and a Description.

   3. Select and move the connection, where you want to export data from, to the Source field.

   4. Select the resources that you want to export.

   5. Save the source migration plan.

3. Create an import only migration plan on the target environment.

   1. Navigate to the Migration Plan tab in Siebel Migration.

   2. Click New Migration and then enter the Name of the migration plan and a Description.

   3. Select and move the connection, where you want to import data to, to the Destination field.

   4. Select the resources you want to import.

   5. Save the target migration plan.

4. Execute the export only migration plan on the source environment.

   1. Navigate to the Execute tab in Siebel Migration.

   2. Go to and select the migration plan that you created in Step 2 and want to export, and then click the Play icon in the Action column.

   3. Complete the fields in the Execution Details Window that appears as required, and then click OK. For information on how to complete the fields in the Execution Details Window, see Executing a Siebel Migration Plan.

      Siebel Migration starts to export all the resource data simultaneously. After all data has been exported, it is then packaged into a package file. If the Migration Package Location is configured on the Migration Profile in Siebel Management Console, then the package file will be created in the Migration Package Location path. Otherwise, the package file will be created in the <File System>\migration folder on the source machine.

      The package file contains a list of all the resources that were exported. It also contains the Watermark information if you have chosen the Incremental Runtime Repository or Incremental Workspace Data resource in the migration plan.

5. Execute the import only migration plan on the target environment:

   1. Navigate to the Execute tab in Siebel Migration.

   2. Go to and select the migration plan that you created in Step 3 and want to import, and then click the Play icon in the Action column.

   3. Complete the fields in the Execution Details Window that appears as required, and then click OK. For information about how to complete the fields in the Execution Details Window, see Executing a Siebel Migration Plan.

   Before executing the import only migration plan, you must ensure and do the following:

   • Ensure that the package file (created in Step 4) is accessible to the target connection where you want to import the exported data. If the Migration Package Location is configured on the Migration Profile in Siebel Management Console, then the package file must be in the Migration Package Location path.

   • If the Migration Package Location is not configured, then you must copy the package file (created in Step 4) from the source to the target environment’s <File System>\migration folder.

   Note: Before the import starts, Siebel Migration ensures that the resources selected in the import only migration plan match the resources selected in the export only migration plan. If the resources do not match, then an error message appears and the import will not start. Similarly, if the Incremental Runtime Repository or Incremental Workspace Data is part of the migration plan, then the watermark used during the export must match the watermark in the target environment. Otherwise , an error message appears and the import will not start.
   Note: The File System path must be accessible by all Siebel Servers and application interface machines.

Incremental Migration from a Development to a Production Environment Without Using Siebel Migration

Typically if either source (development) or target (production) environment is not in a Repository Upgraded state, then migration execution is performed in synchronous mode. You can migrate asynchronously only if both environments are in a Repository Upgraded state. However, if you want to avoid synchronous migration altogether, you can manually apply any repository and schema changes to target environments that are not in a Repository Upgraded state by completing the steps in this procedure.

Note: A Repository Upgraded state means that the environment (repository and schema) has been upgraded to Siebel 18.8 Update or later release of Siebel CRM.

Caution: It is recommended that you back up your target database before starting to migrate repository or data using Siebel Migration.

To migrate incrementally from a development (source) to a production (target) environment without using the Siebel Migration application

Note: If your Runtime Repository Data Service or Incremental Runtime Repository Data Service migration plan does not include the non-mandatory Schema Service, then you must migrate any schema changes before executing the plan. If you want to move the schema changes separately, then ignore Step 2 and Step 5 in this procedure.

1. Generate a watermark for the target environment:

   1. Start the target application. For example, Siebel Call Center or any other employee facing application.

   2. Navigate to the Administration - Business Service screen, then the Simulator view.

   3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Incremental Runtime Repository Data Service	GetWatermark

   4. Click Run.

   5. In the Output Arguments applet, copy the value in the Property Value field for the watermark Property Name.

      Save the value in a text file because you will need it in Step 3.

2. Export the schema from the source environment:

   1. Start the source application. For example, Siebel Call Center or any other employee facing application.

   2. Navigate to the Administration - Business Service screen, then the Simulator view.

   3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Schema Service	Export

   4. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        migrationid	schema_export

      • Click OK to close the Property Set Properties applet.

   5. Click Run.

   6. In the Output Arguments applet, copy the value in the Property Value field for the trackingid Property Name.

      Save the value in a text file because you will need it in Step 5.

   7. Make sure that the ddldict process is running.

      To do this, use Task Manager on Windows or the ps command on UNIX.

3. Export the Incremental Runtime Repository from the source environment:

   1. Start the source application.

   2. Navigate to the Administration - Business Service screen, then the Simulator view.

   3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Incremental Runtime Repository Data Service	Export

   4. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name	Value
        migrationid	repo_export

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        watermark	Paste the value that you saved from the Property Value field in the Output Arguments applet in Step 1 into this field.

      • Click OK to close the Property Set Properties applet.

   5. Click Run.

   6. In the Output Arguments applet, copy the value in the Property Value field for the trackingid Property Name.

      Save the value in a text file because you will need it in Step 6.

   7. Make sure that the repimexp process is running.

      To do this, use Task Manager on Windows or the ps command on UNIX.

4. Ensure that the Schema Export and Incremental Runtime Repository Export from the source environment is complete:

   • At regular intervals, check that the ddldict and repimexp processes are running, until they complete.

   • Verify the logs for ddldict and repimexp. The logs for these utilities are stored in the following locations:

     <FS_PATH>\migration\schema_export\log for Schema Export

     <FS_PATH>\migration\repo_export\log for Incremental RR

   • You must wait until these two processes (ddldict and repimexp) are complete.

5. Import the (source) Schema to the target environment:

   1. Copy the schema_export folder from <FS_PATH>\migration\ on the source machine.

   2. Paste the schema_export folder into the <FS_PATH>\migration path on the target machine.

   3. Start the target application. For example: Siebel Call Center or any other employee facing application.

   4. Navigate to the Administration - Business Service screen, then the Simulator view.

   5. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Schema Service	Import

   6. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name	Value
        migrationid	schema_export

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        filename	Paste the value that you saved from the Property Value field in the Output Arguments applet in Step 2 into this field.

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        username	<Target Database Schema User Name> Note: The database schema user name is in plain text format. Contact your Siebel administrator if you do not know what the database schema user name is for the target environment.

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        password	<Target Database Schema Password> Note: The database schema password must be in Base 64 encoded format. Contact your Siebel administrator if you do not know what the database schema password is for the target environment.

      • Click OK to close the Property Set Properties applet.

   7. Click Run.

   8. Make sure that the ddlimp process is running in the target environment.

      To do this, use Task Manager on Windows or the ps command on UNIX.

   9. Wait until the ddlimp process completes successfully.

      Verify the log located in the <FS_PATH>\migration\schema_export\log folder on the Target machine.

6. Import the (source) Incremental Runtime Repository to the target environment:

   Note: Perform this task only if the previous step completes successfully.

   1. Copy the repo_export folder from <FS_PATH>\migration\ on the source machine.

   2. Paste the repo_export folder into the <FS_PATH>\migration path on the target machine.

   3. Start the target application.

   4. Navigate to the Administration - Business Service screen, then the Simulator view.

   5. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Incremental Runtime Repository Data Service	Import

   6. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name	Value
        migrationid	repo_export

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        filename	Paste the value that you saved from the Property Value field in Output Arguments applet in Step 3 into this field.

      • Click OK to close the Property Set Properties applet.

   7. Click Run.

   8. Make sure that the process repimexp is running in the target environment.

      To do this, use Task Manager on Windows or the ps command on UNIX.

   9. Wait until the repimexp process completes successfully.

      Verify the log located in the <FS_PATH>\migration\repo_export\log folder on the Target machine.

After you complete the steps in this procedure, the environment is ready for asynchronous migration.

Full RR Migration Without Using Siebel Migration

Use the following procedure to complete a synchronous full Runtime Repository (RR) migration without using the Siebel Migration application.

Caution: It is recommended that you back up your target database before starting to migrate repository or data.

To perform a full RR migration without using the Siebel Migration application

1. Generate a watermark for the Full RR source environment:

   1. Start the source application.

   2. Navigate to the Administration - Business Service screen, then the Simulator view.

   3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Runtime Repository Data Service	GetWatermark

   4. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name	Value
        workspace	Enter the <Integration_Workspace_Name> of the repository that you want to migrate

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        version	Enter the <Version_Number> of the repository (<Integration_Workspace_Name>) that you want to migrate.

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        language	Enter the <language> or <language1, language2, language3, etc> that you have enabled on the database.

      • Click OK to close the Property Set Properties applet.

   5. Click Run.

   6. In the Output Arguments applet, copy the value in the Property Value field for the watermark Property Name.

      Save the value in a text file because you will need it in the next step.

2. Export the Full RR from the source environment:

   1. Start the source application.

   2. Navigate to the Administration - Business Service screen, then the Simulator view.

   3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Runtime Repository Data Service	Export

   4. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        migrationid	repo_export

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        watermark	Paste the value that you saved from the Property Value field in the Output Arguments applet in the previous step into this field.

      • Click OK to close the Property Set Properties applet.

   5. Click Run.

   6. In the Output Arguments applet, copy the value in the Property Value field for the trackingid Property Name.

      Save the value in a text file because you will need it in Step 6.

   7. Make sure that the repimexp process is running.

      To do this, use Task Manager on Windows or the ps command on UNIX.

3. Generate a watermark for the Full Seed source environment:

   1. Start the source application.

   2. Navigate to the Administration - Business Service screen, then the Simulator view.

   3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Application Workspace Data Service	GetFullSeedWatermark

   4. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name	Value
        Workspace Name	Enter the <Integration_Workspace_Name> of the full seed that you want to migrate

      • Click OK to close the Property Set Properties applet.

   5. Click Run.

   6. In the Output Arguments applet, copy the value in the Property Value field for the watermark Property Name.

      Save the value in a text file because you will need it in the next step.

4. Export the Full Seed from the source environment:

   1. Start the source application.

   2. Navigate to the Administration - Business Service screen, then the Simulator view.

   3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Application Workspace Data Service	FullSeedExport

   4. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        migrationid	seed_export

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        watermark	Paste the value that you saved from the Property Value field in the Output Arguments applet in the previous step into this field.

      • Click OK to close the Property Set Properties applet.

   5. Click Run.

   6. In the Output Arguments applet, copy the value in the Property Value field for the trackingid Property Name.

      Save the value in a text file because you will need it in Step 9.

   7. Make sure that the dataexp process is running.

      To do this, use Task Manager on Windows or the ps command on UNIX.

5. Ensure that the Full RR and Full Seed export from the source environment is complete:

   • At regular intervals, check that the ddldict, repimexp, and dataexp processes are running, until they complete.

   • Verify the logs for ddldict, repimexp, and dataexp. The logs for these utilities are stored in the following locations:

     <FS_PATH>\migration\repo_export\log for Full RR

     <FS_PATH>\migration\seed_export\log for Workspace Data

   • You must wait until these three processes (ddldict, repimexp, and dataexp) are complete.

6. Import the Full RR to the target environment:

   Note: Perform this task only if the previous step completes successfully.

   1. Copy the repo_export folder from <FS_PATH>\migration\ on the source machine.

   2. Paste the repo_export folder into the <FS_PATH>\migration path on the target machine.

   3. Start the target application.

   4. Navigate to the Administration - Business Service screen, then the Simulator view.

   5. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Runtime Repository Data Service	Import

   6. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name	Value
        migrationid	repo_export

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        filename	Paste the value that you saved from the Property Value field in the Output Arguments applet in Step 2 into this field.

      • Click OK to close the Property Set Properties applet.

   7. Click Run.

   8. Make sure that the repimexp process is running in the target environment.

      To do this, use Task Manager on Windows or the ps command on UNIX.

   9. Wait until the repimexp process completes successfully.

      Verify the log located in the <FS_PATH>\migration\repo_export\log folder on the Target machine.

7. Export a SeedCopyExport from the target environment:

   Note: Perform this task only if the previous step completes successfully.

   1. Start the target application.

   2. Navigate to the Administration - Business Service screen, then the Simulator view.

   3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Application Workspace Data Service	SeedCopyExport

   4. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name	Value
        migrationid	seed_copy

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        watermark	Mode=SegCopyFullMigration

      • Click OK to close the Property Set Properties applet.

   5. Click Run.

   6. In the Output Arguments applet, copy the value in the Property Value field for the trackingid Property Name.

      Save the value in a text file because you will need it in the next step.

   7. Make sure that the dataexp.exe process is running in the target environment.

      To do this, use Task Manager on Windows or the ps command on UNIX and wait until the process completes.

   8. Wait until the dataexp.exe process completes successfully.

      Verify the log located in the <FS_PATH>\migration\seed_copy\log folder on the Target machine.

8. Import the SeedCopyImport to the target environment:

   Note: Perform this task only if the previous step completes successfully.

   1. Start the target application.

   2. Navigate to the Administration - Business Service screen, then the Simulator view.

   3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Application Workspace Data Service	SeedCopyImport

   4. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name	Value
        migrationid	seed_copy

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        filename	Paste the value that you saved from the Property Value field in the Output Arguments applet in the previous step into this field.

      • Click OK to close the Property Set Properties applet.

   5. Click Run.

   6. Make sure that the dataimp.exe process is running in the target environment.

      To do this, use Task Manager on Windows or the ps command on UNIX and wait until the process completes.

   7. Wait until the dataimp.exe process completes successfully.

      Verify the log located in the <FS_PATH>\migration\seed_copy\log folder on the Target machine.

9. Import the FullSeedImport to the target environment:

   Note: Perform this task only if the previous step completes successfully.

   1. Copy the seed_export folder from <FS_PATH>\migration\ on the source machine.

   2. Paste the seed_export folder into the <FS_PATH>\migration path on the target machine.

   3. Start the target application.

   4. Navigate to the Administration - Business Service screen, then the Simulator view.

   5. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name	Method Name
      Migration Application Workspace Data Service	FullSeedImport

   6. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name	Value
        migrationid	seed_export

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name	Value
        filename	Paste the value that you saved from the Property Value field in the Output Arguments applet in Step 4 into this field.

      • Click OK to close the Property Set Properties applet.

   7. Click Run.

   8. Make sure that the dataimp.exe process is running in the target environment.

      To do this, use Task Manager on Windows or the ps command on UNIX and wait until the process completes.

   9. Wait until the dataimp.exe process completes successfully.

      Verify the log located in the <FS_PATH>\migration\seed_export\log folder on the Target machine.

10. Rename the Migrated Repository in the target environment:

    1. Log in to the target database.

    2. Rename Siebel Repository to Original Siebel Repository, for example, as follows:

       UPDATE S_REPOSITORY SET NAME='Original Siebel Repository' WHERE NAME='Siebel Repository';

    3. Rename the Migrated Repository to Siebel Repository, for example, as follows:.

       UPDATE S_REPOSITORY SET NAME='Siebel Repository' WHERE NAME='Migrated Repository';

    4. Restart Siebel Server for the changes to take effect.

11. Activate workflow tasks in the target environment:

    Note: This task must be performed after completing the previous step (that is, after restarting Siebel Server).

    1. Start the target application.

    2. Navigate to the Administration - Business Service screen, then the Simulator view.

    3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

       Service Name	Method Name
       Siebel Runtime Metadata Publisher Service	ActivateWorkflowsTasks

    4. Create a new record in the Inputs Arguments list applet:

       • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

       • Enter the following values in the Property Name and Value fields, and then click Save:

         Property Name	Value
         FullMigration	True

       • Click OK to close the Property Set Properties applet.

    5. Click Run.

       It will take some time to activate all workflow tasks. Until this process completes, the UI will remain in a frozen state.

12. Invalidate Seed Caches in the target environment:

    1. Start the target application.

    2. Navigate to the Administration - Business Service screen, then the Simulator view.

    3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

       Service Name	Method Name
       Migration Application Workspace Data Service	InvalidateSeedCaches

    4. Click Run.

       It will take some time to activate all workflow tasks. Until this process completes, the UI will remain in a frozen state.

Migrating Siebel 18.8 Update or Later Release Repository Changes from a Development to a Production Environment

Once the development environment (source Design Time Repository/DR) is upgraded to the Siebel 18.8 Update or later release binary and repository, you must perform the steps in the following procedure to migrate the changes to the production (target Runtime Repository/RR) environment. You can use the asynchronous migration feature to do this only if both source (development) and target (production) environments are in a Repository Upgraded state. If either (source or target) environment is not in a Repository Upgraded state, then the migration execution will be performed in synchronous mode.

Note: A Repository Upgraded state means that the environment (repository and schema) has been upgraded to Siebel 18.8 Update or later release of Siebel CRM.

Caution: It is recommended that you back up your target database before starting to migrate repository or data using Siebel Migration.

To migrate Siebel 18.8 Update or later release repository changes from a development (source) to a production (target) environment

1. Create a connection to the target environment.

   For more information about creating a connection, see Creating a Connection.

2. Create a migration plan with Incremental Runtime Repository Service where source is the Development (DR) environment and target is the Target (RR or production) environment. (You can use the Runtime Repository Service instead of Incremental Runtime Repository Service.)

   For more information about migration planning, see Creating a Migration Plan.

3. Run the migration plan that you created in Step 2.

4. After you complete Steps 1 to 3, you must add the seed data to the target (RR or production) environment.

   For more information, see Adding Seed Data to the Target Environment.

Note: In a migration plan, if you have chosen a target (RR or production) environment that is Repository Upgraded, then the source (DR or development) environment must also be Repository Upgraded. Otherwise, you will not be able to migrate.

Adding Seed Data to the Target Environment

After you complete the steps described in Migrating Siebel 18.8 Update or Later Release Repository Changes from a Development to a Production Environment, you must complete the following procedure to add the seed data to the target environment.

To add seed data to the target environment

1. In Siebel CRM, open the Call Center application from the development environment that is upgraded to the Siebel 18.8 Update or later release binary and repository.

2. Navigate to the Site Map and then Administration Application - Business Service Access.

3. In the Business Service applet, query for the Application Migration Utility Service in the Name field.

4. In the Business Service Method applet, verify that it contains the following methods:

   • CreateManifest

   • GenerateWatermark

   • GetWatermarkForIncrementalImport

   • GetWatermarks

   • ReadManifest

   • ValidateManifest

   • GetWatermarkFrmFile

5. In Siebel CRM on the target environment that you plan to upgrade to the 18.8 Update or later Siebel Runtime Repository, open the Call Center application. This step assumes that the binary is already upgraded to 18.8 Update or later. If not, upgrade the binary.

6. Navigate to the Site Map and then Administration Application - Business Service Access.

7. Create a new record in the Business Service applet.

8. Enter Application Migration Utility Service for the value in the Name field.

9. In the Access By Responsibility applet, add the appropriate responsibility. The default responsibility is Siebel Administrator.

10. In the Business Service Access Method applet, add all the methods listed in Step 4.

11. Save your changes.

12. Restart the EAI Object Manager component (EAIObjMgr_<lang>) to read the newly added data.

Activating Workflows and Tasks in the Production Environment After Full Migration

All workflows and tasks must be activated. You need the design time workflow records to activate the workflows. The design time data for workflows is available after full migration even though the design time data is not stored in the production (target) environment. It is recommended that you activate all workflows immediately after a full migration. When an incremental migration is triggered after a full migration, it deletes all design time data for workflows (so the opportunity to activate any workflows is lost after you run an incremental migration). Activating workflows involves generating a runtime definition of the workflow from the design time records.

Note: A full migration is where the entire Runtime Repository is migrated from a development (source DR) to a production (target RR) environment.

The following procedure shows you how to activate workflows and tasks in the production (target RR) environment after a full migration. This procedure applies for Siebel 17.x, Siebel 18.x and later releases.

To activate workflows and tasks in the production environment after a full migration

1. Rename the migrated repository to Siebel Repository.

   To do this, for example, use an SQL statement on the target environment.

2. Restart the Siebel Server (siebsrvr).

3. Start the Siebel business application, for example, Siebel Call Center.

4. Navigate to the Administration - Business Service screen, then the Simulator view.

5. Run the following business service to activate all workflows and tasks in the target environment:

   Business Service Name	Invocation Method	Input Arguments
   Siebel Runtime Metadata Publisher Service	ActivateWorkflowsTasks	Property Name = “Full Migration” Value = True

Migrating Configuration Data and Incremental Changes

When migrating configuration data (such as LOVs, runtime events, and data mapper) and incremental changes, note the following:

• LOVs are versioned and may change from one incremental migration to the next.

• Performing a full migration creates a single instance of all repository objects and LOVs with version 0.

• During incremental migrations, new and/or modified LOVs from the DR are created in the RR with new version numbers.

• To seed a new Target environment with all the LOVs and repository objects, the first migration that you perform must always be a full migration.

• Since LOV is workspace enabled, use the Application Workspace Data Service and Incremental Application Workspace Data Service to migrate LOV data including incremental changes.

  For all other configuration data (bar incremental changes), use the Application Data Service, Application Data Service with Transformation, or Application Deployment Manager Projects to migrate data. Migrating incremental changes is not supported here.

  • For example, to perform a full migration of LOVs using Siebel Migration application, select the following resource options:

    • Runtime Repository Data Service

    • Application Workspace Data Service

  • For example, to perform an incremental migration of LOVs using Siebel Migration application, select the following resource options:

    • Incremental Runtime Repository Data Service

    • Incremental Application Workspace Data Service

Note: Since Siebel Innovation Pack 2017, you can modify LOVs in DR environments when you create a development workspace. Prior to Siebel Innovation Pack 2017, LOVs were editable in all environments.

About Migrating User Preferences

As of Siebel CRM 8.1.x/8.2.x (including all Siebel Innovation Packs), the migration of user preferences is typically supported between releases provided that existing SPF files are placed in the Siebel File System on the upgraded system. For example, if you set your Default Greeting Template to My Template, then this preference will be preserved across releases.

However, note that if something changes between releases, then old preferences may be ignored. For example, if significant changes are made to Siebel Calendar (like they were in Siebel Innovation Pack 2016), then many of the preferences related to Calendar will change as a result, making the old preferences obsolete. Any addition of new preferences is backward compatible.

Note: Prior to Siebel CRM 8.1.x, the migration of user preferences from one major release to another (for example, from 7.8 to 8.1) is not supported. In such cases, it is recommended that you rename or delete your SPF files with each major upgrade and then reset your user preferences after the upgrade completes. New SPF files are generated during the upgrade.