General Guidelines for Installing Siebel CRM

Follow these general guidelines for your installations:

Before installing any Siebel CRM module, review all documented requirements, including those found in Installation Tasks for Siebel CRM and in Requirements for Installing and Configuring Siebel CRM. Also review the information in Siebel Deployment Planning Guide, Siebel Security Guide, other relevant guides on Siebel Bookshelf, and the Certifications tab on My Oracle Support.
You must plan for the installation and management of the Siebel CRM modules that you are installing. Review the installation instructions and the installer screens to help you understand the information that is requested by the installers. Such information includes installation locations, languages, application container port numbers, other port numbers, and authentication settings.
When you install Siebel CRM, as described in Installing Siebel CRM using the User Interface, the installer prompts you to specify valid keystore and truststore files, which are Java files containing certificates. These files are necessary for the application container to use secure two-way communications when connecting with other Siebel CRM modules, as occurs during Siebel Management Console configuration and in normal operation. These files must contain the server certificate chain and an imported CA certificate. Generate your files so that the keystore file references both the private key and the public key, while the truststore file references the public key only. Specify the password that was previously configured to open the certificate files. If you do not configure these files correctly, then you will not be able to configure Siebel CRM, as described in Configuring Siebel CRM Server Modules. See also Siebel Security Guide.
Siebel Gateway is installed with every installation of Siebel Enterprise Components. You can configure it to run in the same installation as a Siebel Server or configure it in a separate installation, depending on your requirements. You can optionally install and configure it on multiple nodes in order to support Siebel Gateway clustering. For more information, see Installation Tasks for Siebel CRM. See also Configuring the Siebel Gateway Cluster.
You install New Database Repository once, together with the first Siebel Server installed.
You install all of the Siebel CRM server modules that you will require to get started, and then you configure them.
Various requirements apply to the sequence in which you must perform configuration tasks. Security requirements such as for authentication affect many phases of your installation and configuration process, including the overall task sequence. For example, depending on your authentication method, you might need to install the Siebel database for a new deployment before you configure the Siebel CRM server modules using the Siebel Management Console.
The update installation, migration installation, and database upgrade cases differ in their requirements for installation sequence, Siebel database tasks, configuration of the Siebel environment, and other post-installation tasks.
For example, for migration installations, you must perform the migration installation of the Siebel Application Interface first (for your existing installation of SWSE). Then perform the migration installation of the Siebel Gateway and Siebel Server.
You can install additional instances of Siebel Server, Siebel Gateway, or Siebel Application Interface, as needed, for medium-sized or larger deployments.
You must activate license keys for Siebel CRM, using the License Key Activation utility, after you install a new database, run Incremental Repository Merge (for migration installations), or complete a full database upgrade.
During a migration installation from a release prior to Siebel CRM 17.0 or an update installation from Siebel CRM 17.0 through Siebel CRM 21.1, the original Siebel CRM installation directory is backed up.

This directory is renamed from OriginalName to OriginalName_pre22.x. For example, if the original installation directory name was ses, then this directory is renamed to ses_pre22.7.0.0.0, indicating a release prior to Siebel CRM 22.7. The new installation directory is named OriginalName, such as ses. Retain the original installation directory, in case you choose to restore your prior installation later. For more information, see Restoring a Prior Installation and Configuration.

Note: The installer stops all the associated services for the existing installation so that it can rename the original installation directory. If the installer is not able to rename the directory for some reason, then it displays an error message. You are prompted to review the possible reasons and resolve the problem before asking the installer to retry the step (renaming the directory). For example, your environment might have running processes (such as Java processes that can be reviewed through the task manager list) related to system environment variables such as JAVA_HOME or might have current file references within the existing installation directory. These processes or references must be terminated or resolved before the home directory renaming can complete.

Related Books

Siebel Deployment Planning Guide

Siebel Security Guide

Deploying Siebel Open UI

Siebel Performance Tuning Guide

Siebel System Administration Guide

Certifications tab on My Oracle Support

Install & Configure Advisor: Siebel CRM Installer 21.2 & Later, 2753807.2 (Article ID) on My Oracle Support

Siebel CRM Update Guide and Release Notes on My Oracle Support, 2382435.1 (Article ID) on My Oracle Support

Related Topics

Related Books