Siebel Installation Guide for UNIX > Installing Siebel Enterprise Server and Related Components > Requirements for Siebel Enterprise Server Installation and Configuration >
General Requirements for Siebel Enterprise Server Installation and Configuration
This topic is part of Requirements for Siebel Enterprise Server Installation and Configuration.
Review the information in this topic before installing and configuring Siebel Enterprise Server components. See also the topics about individual components.
- Review Siebel System Requirements and Supported Platforms on Oracle Technology Network. Also check for applicable alerts and other articles on My Oracle Support.
- Review Preparing to Install Siebel Business Applications.
- All machines on which the Siebel Enterprise Server software will be installed must meet the hardware and software requirements detailed in Siebel System Requirements and Supported Platforms on Oracle Technology Network. The Siebel Enterprise Server installer verifies not only that you have the required software for installation of Siebel 8.x, but that the software is the necessary version level.
- In general, you must have installed all third-party products you will require for the Siebel Enterprise Server software you are installing. Some products can be installed after Siebel software. Such products are listed in Siebel System Requirements and Supported Platforms on Oracle Technology Network.
- You must have created a Siebel installation image that includes all products you require, and you must have appropriate 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.
- When multiple components of the Siebel Enterprise Server, such as Siebel Gateway Name Server and Siebel Server, are installed on the same machine, they are installed into a common root directory—for example, /export/home/sba80. The environment variable
SIEBEL_ROOT may be set differently in different locations, to reflect the full path to the installation location of a specific component, such as Siebel Server. Installation directories must meet the requirements described in the topic about file and directory naming in General Considerations in Planning Your Siebel Deployment.
- If you will be clustering the Siebel Gateway Name Server or Siebel Server, plan your use of clustering or redundant disk arrays (RAID) to configure against a single point of failure. For more information on this topic, see Siebel Deployment Planning Guide.
- Each machine that supports Siebel Enterprise Server software must have TCP/IP network connectivity to other machines that are part of or that work with the Siebel Enterprise Server. For example, the Siebel Gateway Name Server machine requires connectivity to all Siebel Server machines. Verify connectivity between all such machines, using the
ping utility. For more information, see Verifying Network Connectivity for the Siebel Server Machine.
- Verify that the network names of the servers that will support the Siebel Gateway Name Server and all Siebel Servers are recorded in Deployment Planning Worksheet. You will need this information when configuring the Siebel Servers.
- Verify that the network adapter is correctly configured to support full duplex Ethernet by verifying the following parameters:
- RJ45 Port Link Status: up
- Media Speed Selected: 100 Mbps Full Duplex
- Media Speed Running: 100 Mbps Full Duplex
- If you intend to use Secure Sockets Layers (SSL) with any Siebel products described in this guide, you must review all applicable information before you install and configure the software. For details, see Siebel Security Guide.
- If you are not yet ready to configure SSL for Siebel Enterprise Server (and Siebel Web Server Extension), you can either postpone installation or configuration until you are fully ready to configure SSL, or you can configure these components without SSL and reconfigure them to use SSL later.
- If you are not yet ready to configure SSL for Siebel Management Agent and Management Server, it is strongly recommended to postpone installation or configuration of these components until you are fully ready to configure SSL. See Installing Siebel Management Agent and Siebel Management Server and Configuring Siebel Management Agent and Siebel Management Server.
- Review the issues described in Managing Temporary Disk Space Required by Siebel Installers and Wizards. For example, make sure you have adequate disk space, and make sure the login ID running the installer has write permissions to this directory.
- Verify that you have created a Siebel installation image that includes all products you require, and that users who will run Siebel installers or modify siebel.ini files have the necessary permissions to the network directories where the Siebel image is located. For more information, see Preparing to Create a Siebel Installation Image.
- You cannot install additional products into a Siebel Enterprise Server root directory after applying a patch release.
- It is recommended to install and deploy all languages you expect to require. You can also add languages to an existing installation. Additional steps are required for deploying and implementing new languages in your Siebel deployment. See all relevant topics, including:
- If the set-group-id flag is used, make sure that the installer ID is a member of the group that owns the Siebel Enterprise Server root directory.
- Review documented information about the configuration process and applicable requirements.
The Siebel Configuration Wizard launches automatically after installation, although you can cancel the wizard and configure later. Release 8.x provides greater flexibility in the configuration framework for Siebel software than previous releases. However, customers must manage the configuration process carefully to ensure success.
For more information, see Configuring Siebel Enterprise Server and Related Components.
- Before you configure Siebel Enterprise Server components, you must have created the Siebel File System. It must meet all criteria described in Creating the Siebel File System.
- Installation can be performed either as root or as a nonroot user. In most cases, it is recommended that installation be performed by a nonroot user for simpler administration and maintenance.
If the Siebel Gateway Name Server or Siebel Server is installed by root, then only root can stop and start the server. To avoid this requirement, you can use an account other than root that has the correct authorizations to install.
All future patch releases must be installed as the same user who installed the base installation being patched.
Whether you install as root or as a nonroot user affects how you would configure autostart for Siebel Gateway Name Server or Siebel Server. For details, see Configuring the Siebel Gateway Name Server for Automatic Start and Configuring the Siebel Server for Automatic Start.
See also Setting Permissions and Ownership.
- (AIX only) Before installing, verify that the login ID performing installation has permission to run
slibclean by asking the administrator to change the permission as follows:
chmod 6555 /usr/sbin/slibclean
- (AIX only) Before you install Siebel Enterprise Server software on AIX, you must install X11 filesets, if they were not included as part of the base AIX installation.
- (HP-UX only) If the environment variable
LANG is set to a directory name that is a symbolic link, the Java installer for Siebel Server will fail. You must reset any existing
LANG variable to the actual directory that the symbolic link represents.
LANG variable cannot be set to
univ.utf8. Doing so causes the installer to fail.
- (Solaris only) Set the TCP ndd variable tcp_co_min to the MTU of the network interface card.