Bookshelf v7.5: Considerations Based on Your Environment Profile

Siebel Server Installation Guide for UNIX > Preparing for the Installation > Planning Your Siebel Deployment >

Considerations Based on Your Environment Profile

Profile 1. Several thousand, or more, concurrent users with high availability requirements, or for one data center in a multi-data center deployment.

Siebel Gateway Name Server. Siebel Gateway Name Server should be hosted on a dedicated server or a non-load-balanced Siebel Server for this profile because the Siebel Gateway Name Server will not support high availability if it is located on a load-balanced Siebel Server. To achieve high availability for the Siebel Gateway Name Server, it is necessary to cluster the Siebel Gateway Name Server using cluster software such as VERITAS. Since clustering software is not compatible with a load balanced Siebel Server, the Siebel Gateway Name Server cannot reside on the same machine. The Siebel Gateway Name Server can reside on a dedicated server pair or pair of clustered Siebel Servers (non-load-balanced) without performance impact. Sharing the clustered server assumes that certain Siebel Server components have been identified as candidates that require clustering for high availability. This is because not all Siebel Server components support load balancing. For details on clustering, see Clustering Your Siebel Deployment for Failover.

Connection Broker. Typically requires multiple Siebel Servers, thereby requiring installation of Central Dispatch as well. The Connection Broker or Central Dispatch Primary Scheduler should run on dedicated servers. The Central Dispatch Secondary Scheduler can run on either a load-balanced Siebel Server or on a dedicated server without performance penalty during normal operations.

CAUTION: Sharing the Primary Scheduler with any Siebel Server or Name Server is not recommended for this type of setup.

Web Server. To remove a single point of failure, deploy multiple Web servers. When deploying multiple Web servers, installation of Central Dispatch with Connection Broker becomes a requirement. Web servers can be load-balanced with any standard load-balancing solutions, including Cisco CSS and F5 Big IP.

NOTE: Siebel eBusiness Applications only provide a Central Dispatch license for the load-balancing of Siebel Servers, but not of Web servers.

Dedicated Server for Siebel Gateway Name Server. 1-4 servers, 1 server for Siebel Gateway Name Server if you are not clustering and 2 if clustering, and additional 1 to 2 servers for Central Dispatch Primary and Secondary Scheduler. The Central Dispatch Backup Scheduler can be colocated with a load-balanced Siebel Server without significant performance impact. Figure 4 illustrates three options for deploying the Siebel Gateway Name Server with user Profile 1. Shaded boxes represent dedicated servers, while white boxes represent shared servers.

Figure 4. Siebel Gateway Name Server Deployment Profile 1 (Several Thousand Concurrent Users)

Profile 2. A few hundred to 1000+ concurrent users with moderate high-availability requirements.

Connection Broker. Multiple Siebel Servers may not be needed. Review Central Dispatch requirements carefully. (See Implementing Load-Balancing with Central Dispatch.) Multiple Web servers will require installation of Central Dispatch software on the Siebel Server.

For this type of deployment, the Central Dispatch Scheduler can reside on either a dedicated server to allow for future growth, or on a load-balanced Siebel Server, as long as the combined CPU utilization remains under 80%. The Secondary Scheduler is recommended as well and it can be set up on the other load-balanced Siebel Server.

Siebel Gateway Name Server. You can cluster the Name Server based on your high availability requirements. It is typically unnecessary to install the Name Server on a dedicated server for a deployment this size. Instead, consider sharing a pair of clustered Siebel Servers with the Name Server.

Web server. One Web server is generally enough to handle the load in this type of deployment. If multiple Web servers are needed for high availability, Central Dispatch/Connection Broker is required on the Siebel Server. However, if you colocate your Web server with your Siebel Server, you cannot install Central Dispatch on that particular server.

Figure 5 illustrates a recommended deployment for this user profile.

Figure 5. Siebel Gateway Name Server Deployment Profile 2 (Several Hundred to 1000 Con-current Users)

Profile 3. 100 to several hundred concurrent users with moderate high-availability requirements.

Connection Broker. Multiple Siebel Servers are not likely to be required. If only one Siebel Server is required, Central Dispatch may not be required, depending on whether your business plans to deploy multiple Web servers. To achieve high availability for Siebel Servers, you can either run all server components in a pair of clustered servers, or use Central Dispatch to provide failover between two Siebel Servers. In this type of deployment, the Central Dispatch Primary Scheduler can run on one of the load-balanced Siebel Servers, as long as it does not belong to a cluster. A dedicated Scheduler is not necessary here, but it can provide a higher level of availability and flexibility, if needed.

Siebel Gateway Name Server. A dedicated server for the Siebel Gateway Name Server is definitely not needed. If clustering is not required for the Siebel Gateway Name Server, consider colocating the Siebel Gateway Name Server with the Central Dispatch Scheduler (when a dedicated server is set up for it) in one of the Siebel Servers.

Dedicated server for Siebel Gateway Name Server. None.

Profile 4. Server components and Web servers are likely to exist on the same server. Therefore, Central Dispatch is not required. For high availability, consider clustering Siebel Server and Name Server components.

If multiple load-balanced Siebel Servers are used, review the recommendations for Profile 3.