Siebel Installation Guide for UNIX > Requirements for Installing and Configuring Siebel Business Applications > Requirements for Installing and Configuring Siebel Enterprise Server Components >

General Requirements for Installing and Configuring Siebel Enterprise Server Components


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

Review this topic before installing and configuring Siebel Enterprise Server components. See also the topics about individual components.

  • Before installing Siebel Business Applications 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 Business Applications and Planning Your Siebel Deployment.
  • All computers or operating system instances on which the Siebel Enterprise Server software is installed must meet the hardware and software requirements detailed in the Certifications tab on My Oracle Support or elsewhere. The Siebel Enterprise Server installer verifies that you have required software at the necessary version levels.
  • In general, you must have installed all of the third-party products that you will require for the Siebel Enterprise Server software that you are installing. Some products can be installed after Siebel Business Applications software. Such products are listed in the Certifications tab on My Oracle Support.
  • You must have created a Siebel Business Applications installation image that includes all of the modules and components that you require. Users who run Siebel installers 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.
  • If you install multiple components of the Siebel Enterprise Server, such as Siebel Gateway and Siebel Server, on the same computer, then they are installed into a common root directory, such as /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. Installing components in some combinations is not recommended. For more information, see About Installing Siebel Business Applications.
  • 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 more information about this topic, see Siebel Deployment Planning Guide.
  • Each computer or operating system instance that supports Siebel Enterprise 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 Business Applications, which use 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, and make sure that the login ID running the installer has write permissions to this directory.
  • 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 Business Applications with Multiple Languages.

    For more information, see additional relevant topics, including:

  • You cannot install new Siebel Enterprise Server components into an existing installation.
  • Note that the Siebel Enterprise Server 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 components, 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 Business Applications, 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.

  • 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.
  • Additional requirements apply for migration installations of the current release. For more information, see Additional Tasks for Migration Installations.
Related Topics

Overview of Installing Siebel Business Applications

Additional Tasks for Migration Installations

About Configuring Siebel Business Applications and following topics

Installation and Configuration Methods by Deployment Type

Requirements Specific to UNIX or Linux Operating Systems

Related Books

Siebel Security Guide

Siebel Deployment Planning Guide

Siebel Installation Guide for UNIX Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices.