Siebel Installation Guide for UNIX > Requirements for Installing and Configuring Siebel CRM > Requirements for Installing and Configuring Siebel Enterprise Server Modules >

Requirements for Installing and Configuring the Siebel Server

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

Review this topic before installing and configuring the Siebel Server. See also General Requirements for Installing and Configuring Siebel Enterprise Server Modules.

• To configure a Siebel Server, a Siebel Gateway must be installed and running, and the Siebel Enterprise must be configured.
• After you install the Siebel Gateway, you run the Siebel Management Console to configure it, and then you configure the Siebel Enterprise. All Siebel Servers you install that are part of the same Siebel Enterprise, regardless of the operating system, must connect to the same Siebel database. For most deployments, all of the Siebel Servers connecting to this database will belong to the same Siebel Enterprise.

  Additional Siebel Servers that you install and configure inherit parameters from the Siebel Enterprise. You configure each Siebel Server using the Siebel Management Console.

• When you run the Siebel Management Console to configure each Siebel Server, all of the component groups are listed and you must enable the ones that you need for this server. If you do not enable component groups during Siebel Server configuration, then you can enable them manually after installation, using Siebel 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.
• Depending on your business requirements, you might deploy one or more Siebel Enterprise Servers. For information about 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 large deployments, a single Siebel database can support multiple Siebel Enterprises. Such a deployment must be planned carefully. For details, see 477829.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 544.

About Clustering the Siebel Gateway and Siebel Server

If you will operate certain servers as part of a cluster, then it is strongly recommended that you install and configure the Siebel Gateway and the Siebel Server on separate resource groups. For information about clustering, see Siebel Deployment Planning Guide.

For information about configuring Siebel Gateway clustering using Siebel Management Console, see Configuring the Siebel Gateway Cluster.

Language and Locale Requirements

Make sure that you have the appropriate locales installed on the computers 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, then proper viewing and editing requires a UTF-8 locale.

For more information about supported locales, see the Certifications tab on My Oracle Support.

The locale can affect how dates and times are displayed. For more information, see Siebel Global Deployment Guide.

NOTE:  Make sure that the locale that 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 install multiple language versions of Siebel applications on your Siebel Servers, then review the following configuration guidelines:

• You can include multiple languages when you install and configure a Siebel Server.
• For each installed language that you choose to deploy when you configure the Siebel Server, language-specific Application Object Manager components are created.

  For more information about scenarios for multilingual deployments, see Installing and Deploying Siebel CRM with Multiple Languages and related topics. See also Siebel Global Deployment Guide.

• If multiple languages are installed on a Siebel Gateway or Siebel Server, then 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, then you must change this setting.

Search Server

A Siebel Server computer 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 search-related installation guidelines and requirements, see Siebel Search Administration Guide.

Database Requirements

Make sure that your database administrator has installed the RDBMS that your site will use and created the Siebel database instance and that you meet all of the database connectivity requirements. For more information, see Configuring the RDBMS including Configuring Siebel Server Connectivity to the Siebel Database. See also Planning RDBMS Installation and Configuration.

The RDBMS that you are using must support the same languages and code pages that you install on the Siebel Servers. For Siebel CRM language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support.

NOTE:  After performing a migration installation of the current release, then you must run Incremental Repository Manager. For more information, see About Database Updates for Siebel CRM 18.12 Update.

Third-Party Software Requirements

Make sure that you have already installed the appropriate version of all of the third-party software products required. Otherwise, the Required Software Components prompt appears. For more information, see the Certifications tab on My Oracle Support.

Temporary Disk Space

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.