1. Installation Guide
  2. Requirements for Installing and Configuring the Siebel Server

Requirements for Installing and Configuring the Siebel Server

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

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

  • 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. 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.

This topic includes the following information: