Bookshelf v7.5: Siebel Server Deployment Considerations

Siebel Server Installation Guide for UNIX > Installing the Siebel Server >

Siebel Server Deployment Considerations

Depending on the requirements of your business, you may deploy one or more Siebel Enterprise Servers. For information on multiple Siebel Enterprise Servers, see Siebel Enterprise Server Overview.

The Siebel Server installation process must be completed on each server that will operate a Siebel Server. Deployment Planning Worksheets provides guidance on determining the number and configuration of Siebel Servers. 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. The SES Installer verifies not only that you have the required software for installation of Siebel 7.x, but that the software is the version level necessary.

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 is 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 Creating Additional Servers Within an Existing Siebel Enterprise Server.

You only can choose which component groups to enable on the first Siebel Server, and the subsequent Siebel Servers will inherit the same component groups. For this reason, you should enable all the component groups that are planned 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 the Configuration Wizard, you will need to enable it manually later on using Server Administration.