Siebel Installation Guide for UNIX: Servers, Mobile Web Clients, Tools > Installing the Siebel Server >
Siebel Server Installation Requirements
Review the following requirements for Siebel Server installation:
CAUTION: Do not install Siebel Business Applications without first reviewing System Requirements and Supported Platforms on Siebel SupportWeb.
- A Siebel Gateway Name Server must be installed and running to configure a Siebel Server.
- When you install the first Siebel Server in your deployment, you automatically configure the Siebel Enterprise Server. All subsequent Siebel Servers installed in this Siebel Enterprise Server must connect to the same database.
- Be sure that all machines on which the Siebel Server will be installed meet the hardware and software requirements detailed in System Requirements and Supported Platforms on Siebel SupportWeb. The Siebel Enterprise Server installer verifies not only that you have the required software for installation of Siebel 7.x, but that the software is the necessary version level.
- Every Siebel Server supported by a given Siebel Database must belong to the same Siebel Enterprise Server, regardless of the platform on which the Siebel Servers are operating. When you install the first Siebel Server within a Siebel Enterprise Server, you will be automatically prompted to configure the Siebel Enterprise Server. Additional Siebel Servers installed in that Siebel Enterprise Server automatically inherit its parameters.
- The Siebel Server software needs to be installed only once on each machine. However, you may configure as many Siebel Servers as you want to operate from that single software installation by using the
config_server script. See Installing Additional Siebel Servers for an Existing Siebel Enterprise Server.
- When you choose which component groups to enable on the first Siebel Server in an Enterprise, subsequent Siebel Servers inherit the same ones. For this reason, it is recommended that you enable for your environment all component groups for which you have a license. If you do not enable component groups during initial installation and configuration of the software, you can enable them manually after installation, using Server Manager.
For each additional Siebel Server you install subsequently, you can manually disable any unneeded component group after installation, using Server Manager.
For more information about component groups and about using Server Manager, see the Siebel System Administration Guide.
- 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, you should 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 the Deployment Planning Guide.
- Verify that you have created a Siebel installation image that includes all products you require, and that you 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.
- (AIX only) Before you install a Siebel Server on AIX, you must install X11 filesets, if they were not included as part of the base AIX installation.
Clustering Requirements 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, you must install and configure the Siebel Gateway Name Server and the Siebel Server on separate resource groups. For information about clustering, see the Deployment Planning Guide.
Language and Locale Requirements
Make sure you have the appropriate locales 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 System Requirements and Supported Platforms on Siebel SupportWeb.
The language locale can affect how time is displayed. For more information, see the 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:
- You run the Siebel Software Configuration Wizard only once for each Siebel Server. Do not use this wizard to reconfigure an existing server.
- When you run the Configuration Wizard, Application Object Managers (AOMs) are created for every language that has been installed on that Siebel Server.
Because the AOMs are created from a file (omdefs.dat or omdefs_sia.dat) installed as part of the Siebel Language Packs, they are created only for languages for which a Language Pack has been installed. (The file omdefs_sia.dat is used for Siebel Industry Applications.) However, you can manually create AOMs for languages that have not been installed. To do this, use Server Manager in GUI or command-line mode, or create and import a modified omdefs.dat or omdefs_sia.dat file. For information about importing such a file, see the Global Deployment Guide.
- When new AOM components are created, they are automatically assigned to every server and they attempt to run on every server with the parent component group assigned and enabled. For information about server component groups and their member components, see the Siebel System Administration Guide. See also Preparing to Run Siebel Server Components After Installing.
- When you add a new server, it will inherit every component group and every AOM by default.
- If multiple languages are installed, you will be prompted for the primary (base) language. This is the primary (base) language for your Enterprise Server—the language in which you want your Siebel 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 language.
- For multilingual deployment scenarios, see also the Global Deployment Guide.
Adding a New Product to an Existing Installation
When you add a new product to an existing installation, it is vital that you install the same set of languages for the new product. For example, do this when adding a Siebel Server to the same directory in which you have installed a Siebel Gateway Name Server.
All Siebel Enterprise components must be at the same release and patch level.
Because both products share the same root directory, they are treated by the installer as one product in terms of patches and the addition of new languages.
After an installation directory is patched, a new product cannot be added to that directory. In that case, install the product in a new installation directory.
A Siebel Server can be configured to execute searching or can be pointed to another remote Siebel Search server to handle search execution tasks. If you want a server to function as a Siebel Search server, you must install the Siebel Search server (Hummingbird SearchServer) before installing Siebel Server on that machine. For more information about Siebel Search, see the Siebel Search Administration Guide.
Make sure your database administrator has installed the RDBMS your site will be using. During installation of the Siebel Server, you must have an established connection to that database for installation to be successful. For more information, see Configuring the RDBMS.
The RDBMS you are using must support the same languages and code pages that you will install on the Siebel Servers. To see the code pages and languages supported both for Siebel Servers and the RDBMS, refer to System Requirements and Supported Platforms on Siebel SupportWeb.
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 System Requirements and Supported Platforms on Siebel SupportWeb.
Temporary Disk Space
Review the issues described in Managing Temporary Disk Space Required by Installers. For example, make sure you have adequate disk space, and make sure the login ID running the installer has write permissions to this directory.