Configuration Requirements for Migration Installations

The migration installation case has particular requirements that relate to configurations. For your installed Siebel CRM software for a prior release (Siebel CRM 16.x or earlier), do the following, in the order shown. This topic is part of About Configuring Siebel CRM.

1. Review all relevant documentation. See Before You Install Siebel CRM and Installation Tasks for Siebel CRM.

2. Perform any necessary premigration tasks, as noted in Additional Tasks for Migration Installations.

   Caution: In particular, you must remove the existing Siebel Web Server Extension (SWSE) configuration on the Web server computer where you installed SWSE for the prior release. Do this before you perform the migration installation of Siebel Application Interface. Otherwise, the virtual directories cannot be cleaned up adequately. For more information, see Removing the Siebel Application Interface Configuration.

3. Install Siebel Application Interface as a migration installation for your existing installation of SWSE, as described in Installing Siebel CRM in a Migration Installation.

4. Install Siebel Enterprise Server as a migration installation, as described in Installing Siebel CRM in a Migration Installation.

   Note: For the Siebel Enterprise Server that includes the Siebel Gateway, when you perform the migration installation, you provide input that configures the Siebel Gateway and allows the existing configurations for the Siebel Enterprise and Siebel Servers to migrate to the new Siebel Gateway. This instance is considered the primary Siebel Gateway if you deploy Siebel Gateway clustering.

5. (Optional) Install Siebel Enterprise Server as a new installation, and install any other Siebel CRM modules that you require, as described in Installing Siebel CRM in a New Installation. For example, install Siebel Gateway (if you are using Siebel Gateway clustering on multiple nodes).

6. Perform any necessary postinstallation tasks, as noted in Additional Tasks for Migration Installations. For example, do the following:

   • Update the database client installation path in the defined environment variables.

   • Update files and directories on Siebel Enterprise Server and Siebel Application Interface (where necessary).

7. Run Incremental Repository Merge, as described in Siebel Database Upgrade Guide.

8. Run the Siebel Management Console, as described in Starting the Siebel Management Console. See also About Configuring Siebel CRM.

   • (Optional) Create a profile for the Siebel Gateway cluster, if you have installed Siebel Gateway on multiple nodes for this purpose, and then deploy this profile to deploy the cluster. For more information, see Configuring the Siebel Gateway Cluster.

   • Create a profile for Siebel Application Interface, and then deploy this profile to the installed Siebel Application Interface. For more information, see Configuring the Siebel Application Interface.

   • Configure any new Siebel CRM modules that you installed, including those noted in a prior step, or configure the Siebel Migration application.

Related Topics

Installation-Related Changes in Siebel CRM

Siebel CRM Download and Installation

Installation Tasks for Siebel CRM

Additional Tasks for Migration Installations

Running the Siebel Management Console

Installing the Siebel Database on the RDBMS

Additional Postinstallation and Configuration Tasks

Requirements for Installing and Configuring Siebel CRM

Process of Removing Configuration Data

Related Books

Siebel Database Upgrade Guide