General Requirements for Installing and Configuring Siebel Enterprise Components

This topic is part of Requirements for Installing and Configuring Siebel Enterprise Components.

Review this topic before installing and configuring Siebel CRM server software. See also the topics about individual modules.

Before installing Siebel CRM software, you must review all of the relevant information in the Certifications tab on My Oracle Support. Also check for applicable alerts, bulletins, or other documents on My Oracle Support.
Review About Installing Siebel CRM and Planning Your Siebel Deployment.
All computers or operating system instances on which the Siebel Enterprise Components software is installed must meet the hardware and software requirements detailed in the Certifications tab on My Oracle Support or elsewhere. The Siebel CRM installer verifies that you have required software at the necessary version levels.
You must have created a Siebel CRM installation image that includes all of the modules and components that you require. Users who run the Siebel CRM installer or modify installer files must have the necessary permissions to the network directories where the Siebel image is located. For information about creating the Siebel installation image, see Creating the Siebel Installation Image on the Network.
Where you install Siebel Enterprise Components software on the same computer, then all modules are installed into a common root directory, as follows:
- (Windows) For example, the installation directory might be C:\Siebel. For more information, see About Installing Siebel CRM and About Installation Tasks for Siebel CRM.
- (UNIX) For example, the installation directory might be /Siebel. The environment variable SIEBEL_ROOT might be set differently in different locations, to reflect the full path to the installation location of a specific component, such as Siebel Server. For more information, see About Installing Siebel CRM and About Installation Tasks for Siebel CRM.
Installation directories must meet the requirements described in File and Directory Naming Conventions.
If you will be clustering the Siebel Gateway or Siebel Server, then plan your use of clustering or redundant disk arrays (RAID) to configure against a single point of failure. For information about the recommended native clustering feature for Siebel Gateway, see Configuring the Siebel Gateway Cluster. See also Siebel Deployment Planning Guide.
Each computer or operating system instance that supports Siebel CRM server software must have TCP/IP network connectivity to other computers that are part of or that work with the Siebel Enterprise Server. For example, the Siebel Gateway computer requires connectivity to all of the Siebel Server computers. Verify connectivity between all such computers, using the ping utility. For more information, see Verifying Network Connectivity for the Siebel Server Computer.
Before running any of the Siebel Management Console tasks in which you will specify a server computer’s host name or IP address, validate the host name or IP address that you will enter during configuration. You can use the ping utility for this purpose. The host name and IP address data that you specify when you run the Siebel Management Console must be correct in order for the configuration process to proceed correctly.
Verify that the network names of the servers that will support the Siebel Gateway and all of the Siebel Servers are recorded in Siebel Deployment Planning Worksheet. You need this information when configuring the Siebel Servers.
It is strongly recommended to review all applicable security information before you configure Siebel CRM, which uses Transport Layer Security (TLS).
When data encryption is enabled, make a backup copy of the key file before you start a migration installation for Siebel Enterprise Server. Copy back this file after the migration.
Caution: When data encryption is enabled, a migration installation for Siebel Enterprise Server creates a new key file (keyfile.bin), overwriting your existing key file. If this happens, the encrypted columns will be inaccessible. To prevent this result, you must make a backup copy of the key file before starting the migration installation. After the migration installation, copy back the original key file. For more information about data encryption, see Siebel Security Guide.
Review the issues described in Managing Temporary Disk Space Required by Siebel Installers and Wizards. For example, make sure that you have adequate disk space.
It is strongly recommended that you install and deploy, or at least install, all of the languages that you expect to require. For more information, see Installing and Deploying Siebel CRM with Multiple Languages.
For more information, see additional relevant topics, including:
- About Installing Siebel CRM
- Planning RDBMS Installation and Configuration
- About the Siebel Network Image
- About Configuring Siebel CRM and following topics
- Preparing to Run Siebel Server Components
You cannot install new Siebel Enterprise Server modules into an existing installation.
Note that the Siebel CRM installer user interface can run in the supported languages described in About the Language in Which Siebel Installers and Wizards Run.
Before you configure Siebel Enterprise Server modules, you must have created the Siebel File System. It must meet all of the criteria described in Creating the Siebel File System.
Before you install Siebel CRM, review documented information about the installation and configuration process and applicable requirements. Customers must manage the overall installation and configuration process carefully to ensure success.
For existing deployments, all Siebel Server component jobs must complete before:
- You perform any Siebel CRM installations in a migration installation case.
- You perform any upgrade tasks in a full database upgrade case.
  After you perform all installation and upgrade tasks, recreate any component job definitions that you require for your deployment.
Administrative rights are required for installation or uninstallation of Siebel CRM software. For information about setting administration rights, consult the operating system manuals applicable to your installations.
Antivirus software, firewalls, and other security software can interfere with installation and operation of software if they are not properly configured. In some cases, you might need to disable antivirus software while installing Siebel CRM software. It is also recommended to exclude certain types of files from virus scanning. In addition, you might need to disable the Windows feature User Account Control while installing Siebel CRM software. Follow these guidelines for using antivirus software:
- Run virus scans on Siebel Enterprise Servers during maintenance windows, if possible, not when they are online. Scans can then be performed on all files at that time.
- You can run regular virus scans for the Siebel File System. It is recommended to perform these scans during off-peak hours.
For a migration installation case, you must perform the migration installation for Siebel Application Interface before you perform the migration installations for any other Siebel CRM server modules. When you do the migration installations for other Siebel CRM modules, the installer prompts you to provide the host name and installation location for the migrated installation of Siebel Application Interface. Without this information, the migration installations of Siebel Gateway, Siebel Server, or other modules cannot complete successfully.
Additional requirements apply for migration installations of the current release. For more information, see Additional Tasks for Migration Installations.

Related Books

Siebel Security Guide

Siebel Deployment Planning Guide

Related Topics

Related Books