Bookshelf Home | Contents | Index | Search | PDF

Siebel Server Installation Guide for UNIX > Installing Siebel Web Server Extension >

Planning Siebel Web Server Deployment

---

Before installing the Siebel Web Server Extension, you must have already installed the following components:

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

NOTE:  Install any Siebel Servers additional to the initial Siebel Server after you have installed the Siebel Web Server Extension and, if applicable, the Mobile Web Client software. This allows you to verify that you have a working connection between the Web server and the initial Siebel Server.

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

Single-node. Installation of the Siebel Enterprise Server component and your Web server on a single machine or node (recommended only for Siebel MidMarket customers).
Distributed. Distribution of the above-mentioned components across multiple Web servers connecting to multiple Siebel Object Managers whose load can be dynamically balanced across multiple Siebel Servers within a Siebel Enterprise Server.

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

Deployment Limitations When Using Reverse Proxy Servers

You can only deploy Siebel applications that support the standard interactivity client on a Web server instance that is placed behind a reverse proxy server. You cannot deploy Siebel Employee applications, such as Siebel Call Center, or other Siebel applications that support the high interactivity client, on a Web server instance placed behind a reverse proxy server.

Special Deployment Cases

In either a single-node or distributed configuration, the database server resides on a separate node; its installation is independent from the servers listed above.

If you install Central Dispatch on any of your Siebel Servers, you cannot also install it on your Web servers and configure it on the same VIP or Central Dispatch site as the Siebel Server. This is because the Central Dispatch software on the Web server cannot send requests to the same VIP on the Siebel Server from which it receives requests.

Recommended Siebel Web Server Topology

Each deployment choice involves trade-offs. 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 Siebel Object Managers) 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 Siebel Object Manager instances, using the connection brokering capabilities of Central Dispatch.
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 Siebel Web Server Extension on a different machine from the Siebel Server and Siebel Object Managers lets you deploy your Web server outside the firewall while keeping the Siebel 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.

Bookshelf Home | Contents | Index | Search | PDF