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:

• A Siebel Gateway Name Server must be installed and running to configure a Siebel Server.
• 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 Server 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 Within an Existing Siebel Enterprise Server.
• When you choose which component groups to enable on the first Siebel Server, subsequent Siebel Servers inherit the same ones. For this reason, you should enable all the component groups for your environment and then disable specific component groups on each individual Siebel Server that does not need that particular component group. If you forget to enable a component group during initial installation and configuration of the software, you must enable it manually later on using Server Manager.
• 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 (where $SIEBEL_ROOT is the environment variable for the installation root directory) to specify a unique $SIEBEL_ROOT for each Siebel Enterprise Server. For information on deploying multiple Siebel Enterprise Servers, see Deployment Planning Guide.

  NOTE:  Configuring multiple Siebel Enterprise Servers on a single machine is not supported for the production environment.

• Verify that you have all the required DVDs, for base and language. Or, verify that you have appropriate permissions to the network directories where the files reside in a network image.

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 Deployment Planning Guide.

Language 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 Global Deployment Guide.

NOTE:  Make sure the locale you are using matches the locale set at your operating system level. For details, see Locale Configuration on Your UNIX Operating System.

Guidelines for Installing Multiple Language Packs on the Siebel Server

If you will be installing multiple language versions of Siebel eBusiness Applications on your Siebel Servers, review the following configuration guidelines:

• You run the Siebel Enterprise Server Software Configuration Wizard only once for each Siebel Server. Do not use this wizard to reconfigure an existing server.
• When you configure a server, you have the option of creating Application Object Managers (AOMs) for every language that has been installed on that server.
• AOMs are created when you run the Configuration Wizard, based on the Language Packs you have installed. 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 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 Enabling Server Components. See also Siebel System Administration Guide.
• 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—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 your server up, you must change this language.

For deployment scenarios for installation of multiple languages on your Siebel Servers, see 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.

You also need to make sure that for any new Siebel Server you install the new installation is at the same patch level as the Gateway before starting the Siebel Server process.

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.

Hummingbird SearchServer

Any Siebel Server can also be configured to execute searching or can be pointed to another remote SearchServer to handle search execution tasks. If you want a server to function as a SearchServer, you must install Hummingbird SearchServer before installing the Siebel Server on that machine. For more information about Hummingbird SearchServer, see Siebel Search Administration Guide.

Database Requirements

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 Guidelines for 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 for both Siebel Servers and for Siebel Database Servers, refer to System Requirements and Supported Platforms on Siebel SupportWeb.

Third-Party Applications

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

The Siebel Server installer requires the following temporary disk space for the installation:

AIX: 200 MB (/tmp)

Solaris: 115 MB (/var/tmp)

HP-UX: 230 MB (/var/tmp)