Bookshelf v7.5: Prerequisites for Siebel Web Server Extension Installation

Siebel Server Installation Guide for Microsoft Windows > Installing the Siebel Web Server Extension >

Prerequisites for Siebel Web Server Extension Installation

Before installing the Siebel Web Server Extension, you must have already installed the following components (for details on supported third-party products, see System Requirements and Supported Platforms):

A supported Web server with a supported browser.

If your browser is MS Internet Explorer, install any recommended patches.

If your browser is IE 5.5 and you will be using Siebel Call Center and Siebel Sales, install the Microsoft XML parser.

Siebel Gateway.

Siebel Enterprise Server and one Siebel Server, with the Application Object Managers enabled through Server Manager for the Siebel eBusiness Applications you purchased. For information, see Siebel Server Administration Guide.

NOTE: It is recommended that you wait to install additional Siebel Servers until after you have completed installation of the Siebel Web Server Extension and, if applicable, the Mobile Web Client software. This allows you to test that your connection is working from the Web server to the initial Siebel Server.

Before beginning the installation process, decide how you will distribute the server components.

Single-node. Installation of Siebel Enterprise Server components, Siebel eBusiness Application server components, and your Web server on a single machine or node.

Distributed. Distribution of the above-mentioned components across multiple Web servers connecting to multiple Application Object Managers whose load can be dynamically balanced across multiple Siebel Servers within an Enterprise Server.

NOTE: For the best performance, it is recommended that the Web server reside on a separate machine from the Siebel Enterprise Server.

Recommended Siebel Web Server Topology

Each deployment choice involves trade-off. However, in enterprise-size deployments, it is strongly recommended that you use a distributed node deployment for the following reasons:

Less resource contention. Distributing the Web server and the Siebel Server (with Application Object Manager) on different machines eliminates contention for CPU and other server resources. However, to take advantage of the performance improvement, you must have a high-speed network connection between the two machines.

Load-balancing. A single Web server can distribute the load of multiple user requests among multiple Application Object Manager instances.

Higher fault tolerance. Operating multiple instances of components on multiple machines reduces downtime and the impact of failure on any one machine.

Greater flexibility with firewalls. Putting the Web components of the Siebel eBusiness Applications on a different machine from the Siebel Server with Application Object Managers lets you deploy your Web server outside the firewall while keeping the Enterprise Server components behind the firewall.

High availability. A multi-node configuration is required for deployments that support large numbers of concurrent users or where high availability is an operating requirement.