1. Installation Guide
  2. Installing Multiple Instances of the Same Version of Siebel CRM

Installing Multiple Instances of the Same Version of Siebel CRM

This task is part of Planning to Install Multiple Instances of Siebel CRM.

By default, the Siebel CRM installer automatically installs Siebel CRM software in directories with unique names that will not conflict with other Siebel CRM modules that you install on the same computer or operating system instance. To install another instance of the same version of a module on a single computer or operating system instance (where applicable), specify a custom installation path.

However, installing multiple instances of some modules might cause problems. For example:

  • (Windows) You cannot install multiple instances of the same version (or any version) of Siebel Gateway on the same computer or operating system instance. The reason for this is that installing and configuring the Siebel Gateway creates a service which cannot coexist in multiple instances for different installations.

  • (UNIX) You cannot install multiple instances of the same version of Siebel Gateway on the same computer or operating system instance.

  • You must take care to avoid conflicts in port number usage whenever you install or configure multiple Siebel CRM modules or multiple instances on the same computer or operating system instance. You specify multiple port numbers for application containers when you install and configure Siebel CRM modules.

For important related considerations, see also About Installing Siebel CRM and Preparing the Hardware and Planning Topologies.

Note: In this context, same version refers to multiple installations of a given release, such as Siebel CRM 22.7.

All Siebel CRM server modules that you install together on the same computer or operating system instance are installed into the same root directory (such as C:\Siebel on Microsoft Windows or /Siebel on UNIX). Siebel Enterprise Components you install include Siebel Gateway, Siebel Server, Siebel Application Interface Database Configuration Utilities, and EAI Connector. Restrictions and guidelines apply to collocating Siebel CRM modules, as noted in About Installing Siebel CRM. See also File and Directory Naming Conventions.

If you have already installed Siebel CRM modules (Siebel Enterprise Server) for the current release, and you require additional Siebel CRM modules (for example, Siebel Gateway is already installed and you want to install a Siebel Server), then you can install a new instance of Siebel Enterprise Components. You must install the new instance in a different directory or on a different computer or operating system instance. For more information about options in this situation, see General Requirements for Installing and Configuring Siebel Enterprise Components and other relevant topics.

Each installed instance of Siebel CRM software, whether on the same or on a different computer or operating system instance, must be configured in order to operate it in your Siebel deployment. Configuration requirements are different for new installations and migration installations. A new installation must be configured using Siebel Management Console, by configuring and applying profiles for each module. Depending on your existing deployment, in a migration installation case involving multiple instances of a Siebel CRM module, you might have a choice about whether to install and configure each additional instance of a new module as a new installation or as a migration installation. Specific requirements vary by Siebel CRM module and by installation case.

If you install additional instances of Siebel Application Interface (when the primary instance is operational, whether a new or migration installation), then some additional steps might be necessary to deploy these instances. These steps involve editing the applicationinterface.properties file, which is located in SIEBEL_AI_ROOT/applicationcontainer_external/webapps. Copy the following parameters and their values from applicationinterface.properties on the primary instance of Siebel Application Interface into the [Application Interface] section of the corresponding file on the new instance: Password, UserName, and CGHostURI. For each new Siebel Application Interface instance, after you save the updated file, restart the application container. Then you can apply a profile to deploy this instance.