Using Siebel Tools > Managing Repositories > Process of Migrating a Repository >

Migrating Nonrepository Configurations and Data

This task is a step in Process of Migrating a Repository.

To successfully complete a repository migration, you must do other tasks to migrate configurations and data that the Database Configuration Wizard does not migrate.

To migrate nonrepository configurations and data

1. Migrate web templates, image files, and style sheets.

   For more information, see Migrating Web Templates, Image Files, and Style Sheets.

2. Migrate any customizations that you have made to the Siebel application or to runtime data.

   You must migrate any customizations that your Siebel Enterprise data contains, such as custom views, responsibilities, assignment rules, and so on. For more information, see Siebel Application Deployment Manager Guide and Siebel Assignment Manager Administration Guide.

3. Migrate custom configurations, such as parameter values and server component definitions.

   For more information, see Migrating Custom Configurations.

4. Migrate database triggers.

   Siebel CRM does not migrate custom database triggers. If your Siebel base tables include custom database triggers, then you must disable them before you migrate the repository, and then recreate them on the target repository after the migration finishes.

5. Update database statistics.

Migrating Web Templates, Image Files, and Style Sheets

A Siebel Server installation includes the following files that determine how Siebel CRM displays the Siebel client in a Web browser:

• Siebel Web template files (SWT files)
• Image files (GIF, JPG, and PNG files)
• Cascading style sheet files (CSS files)

If you modify any of these files in the source environment, then you must copy them to the target environment. Note the following:

• You can use Siebel Application Deployment Manager (ADM) to automate this work. For more information, see Siebel Application Deployment Manager Guide.
• For information about specifying the Siebel Enterprise Security Token and how to migrate content from the Siebel Server to the Web server, see the Siebel Installation Guide for the operating system you are using and Siebel Security Guide.

To migrate web templates, image files, and style sheets

• Copy any new or modified files from the source Siebel Server to the target Siebel Server using values from the following table.

  File Type	File Location
  Web templates	SIEBSRVR_ROOT\WEBTEMPL
  Images	SIEBSRVR_ROOT\webmaster\images\language_code
  Cascading style sheets	SIEBSRVR_ROOT\webmaster\files\language_code

Migrating Custom Configurations

If you migrate a repository, then you must also migrate any custom environment configurations that exist in the source environment to the target environment. For example, custom server component definitions. Siebel CRM stores this information in the siebns.dat file on the Siebel Gateway Name Server. The Database Configuration Wizard does not migrate this information.

To migrate custom configurations

1. Recreate any custom environment configurations.

   Use the Server Manager command-line interface (srvrmgr) and scripts that provide input to srvrmgr that automate this work in the target environment. It is recommended that you use scripts because you can save them and reuse them for future migrations. If you reuse a script, then make sure you edit this script if the target environment is a new Siebel version. For example, a Siebel upgrade includes a new Siebel version. New parameters or srvrmgr commands might be available with this new version. For more information, see Siebel System Administration Guide.

   You can also use the Server Manager GUI or command-line interface (srvrmgr) to manually create these custom configurations in the target environment. For information, see Siebel System Administration Guide.

2. Recreate parameter values.

   For more information, see Siebel System Administration Guide.