Siebel Installation Guide for UNIX > Installing Siebel Enterprise Server and Related Components > Requirements for Siebel Enterprise Server Installation and Configuration >
Requirements for Siebel 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 the Siebel Server.
- A Siebel Gateway Name Server must be installed and running and the Siebel Enterprise must be configured in order to configure a Siebel Server in live mode.
- After you install the Siebel Gateway Name Server, you are prompted to configure the Siebel Enterprise. All Siebel Servers you install that are part of the same Siebel Enterprise, regardless of operating system platform, must connect to the same Siebel Database. For most deployments, all Siebel Servers connecting to this database will belong to the same Siebel Enterprise.
Additional Siebel Servers you install and configure inherit parameters from the Siebel Enterprise. You configure each Siebel Server using the Siebel Server Configuration Wizard.
- When you run the Siebel Server Configuration Wizard for each Siebel Server, all component groups are listed and you must enable the ones you need for this server. If you do not enable component groups during Siebel Server configuration, you can enable them manually after installation, using Server Manager.
For more information about component groups and about using Server Manager, see Siebel System Administration Guide. See also Preparing to Run Siebel Server Components After Installing.
- The Siebel Server software needs to be installed only once on each machine. For test or development purposes only, you can configure multiple Siebel Servers based on a single installed Siebel Server. For more information, see Installing Additional Siebel Servers for an Existing Siebel Enterprise Server.
- Depending on the requirements of your business, you may deploy one or more Siebel Enterprise Servers. If you intend to configure multiple Siebel Enterprise Servers on a single machine in your development or test environment, issue a command similar to
unsetenv SIEBEL_ROOT to specify a unique value for each Siebel Enterprise Server. (
SIEBEL_ROOT is the environment variable for the installation root directory.) The command
unsetenv is a C shell command; use the appropriate command for your shell. For information on deploying multiple Siebel Enterprise Servers, see Siebel Deployment Planning Guide. See also 477770.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 531.
NOTE: In special cases such as for some very large deployments, a single Siebel Database may support multiple Siebel Enterprises. Such a deployment must be planned very carefully. For details, see 477829.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 544.
Clustering for the Siebel Server
The Siebel installer allows you to install all servers at once for which you have a license. If you will be operating certain servers as part of a cluster, it is strongly recommended to install and configure the Siebel Gateway Name Server and the Siebel Server on separate resource groups. For information about clustering, see Siebel Deployment Planning Guide.
Language and Locale Requirements
Make sure you have the appropriate locales installed on the machines on which you intend to deploy Siebel Server. Siebel log and configuration files use UTF-8 with Byte Order Mark as the default encoding. If these files contain any non-ASCII characters, proper viewing and editing requires a UTF-8 locale.
For more information on supported locales, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.
The locale can affect how dates and times are displayed. For more information, see Siebel Global Deployment Guide.
NOTE: Make sure the locale you are using matches the locale set at your operating system level. For details, see Specifying the Locale for Your UNIX Operating System.
Guidelines for Installing Multiple Language Packs on the Siebel Server
If you will be installing multiple language versions of Siebel Business Applications on your Siebel Servers, review the following configuration guidelines:
- For multilingual deployment scenarios, see About Installing and Deploying with Multiple Languages. See also Siebel Global Deployment Guide.
- When you run the Siebel Server Configuration Wizard to configure a Siebel Server, Application Object Manager (AOM) components are created for every language that has been installed on that Siebel Server. For information about enabling and disabling language-specific AOMs, see Preparing to Run Siebel Server Components After Installing.
- If multiple languages are installed on a Siebel Gateway Name Server or Siebel Server, you will be prompted for the primary (base) language. The primary (base) language is the language in which you want your server to run and in which you normally want to read messages. If you want to change the language in which you bring up your server, you must change this setting.
Adding a New Siebel Enterprise Component to an Existing Installation
When you add a new Siebel Enterprise Server product to an existing installation, you do not need to specify which languages to install. The new product is installed with the same languages you installed previously.
Because all Siebel Enterprise Server components share the same root directory (for example, the directory /export/home/sba80), they are treated by the installer as one product in terms of subsequent installations for patch releases and new languages you are adding to the installation.
After an installation directory is patched, a new product cannot be added to that directory. In that case, either uninstall the Siebel Enterprise Server software and reinstall with the products you require, or install a new instance of the Siebel Enterprise Server software on a different machine. Then install the applicable patch releases.
NOTE: All Siebel Enterprise Server components must be at the same release and patch level.
A Siebel Server machine can be configured to execute searching using a locally installed search server or can be pointed to a remote search server to handle search execution tasks.
NOTE: For specific guidelines and requirements about installing search products, see Siebel Search Administration Guide.
Make sure your database administrator has installed the RDBMS your site will be using and created the Siebel Database instance and that you meet all database connectivity requirements. For more information, see Configuring the RDBMS. See also Configuring Connectivity to the Siebel Database.
The RDBMS you are using must support the same languages and code pages that you will install on the Siebel Servers. For code pages and languages supported both for Siebel Servers and the RDBMS, refer to Siebel System Requirements and Supported Platforms on Oracle Technology Network.
Third-Party Software Requirements
Make sure that you have already installed the appropriate version of all third-party software products required. Otherwise, the Required Software Components prompt appears. For more information, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.
Temporary Disk Space
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.