Siebel Deployment Planning Guide > High Availability Deployment Planning >

Best Practices for High Availability Deployments

Use the best practices below as a starting point for planning a high availability infrastructure.

Profile 1: Uninterrupted Global Deployment

This deployment has several hundred to tens of thousands of users worldwide requiring the Siebel application to be available 24 hours a day, seven days a week.

• Siebel Server load balancers. A dedicated third-party HTTP load balancer is recommended for this type of deployment. If using hardware load balancers, set up redundant load balancers. Verify that if a load balancer fails, the remaining load balancers can provide acceptable performance under high workloads.
• Siebel Gateway Name Server. This should reside on a dedicated, clustered server pair. It can also reside on Siebel Servers in an existing cluster. Sharing the clustered servers will have minimal performance impact.
• Siebel File System. Consider deploying fault-tolerant and resilient file systems to host the files. Clustering the server that hosts the Siebel File System is also an appropriate strategy. The File System is restricted to one for each Siebel Enterprise Server; therefore, you cannot use load balancing.
• Web servers. Set up load balancing using one of the standard HTTP load balancers certified by Oracle. Set up the Web server load balancer to allow user requests to failover to other Web servers. Verify that if a load balancer fails, the remaining load balancers can provide acceptable performance under high workloads.
• Siebel Servers hosting an AOM. Multiple Siebel Servers hosting an Application Object Manager (AOM) should be load-balanced. You can use either a third-party HTTP load balancer or Siebel native load balancing. Third-party HTTP load balancers typically offer more management capabilities, while Siebel native load balancing is less complex to set up and maintain.

  Consider AOM or server failure when doing capacity planning. For example, if each Siebel Server can handle 500 users, and you typically have 1500 concurrent users, consider providing four Siebel Servers to handle this load. If one server fails, the other three can still support user loads.

  The Siebel Product Configuration Object Manager is an exception to standard load-balancing configuration. It includes an internal load balancing mechanism.

• Siebel Servers hosting other types of components. Enable batch components on multiple Siebel Servers. Server Request Broker will route requests to these components, thus providing resilient processing for batch requests.

  Some components can be hosted on only one Siebel Server, for example Siebel Remote. If user loads permit, you set up high availability as follows:

  • For the AOM and related components, use load balancing.
  • For the components that can be installed on only one server, use server clustering.
• Siebel Database. Deploy high availability clustered services provided or supported by the vendor of your RDBMS. To guarantee data availability and integrity, use data replication techniques such as mirroring and disk arrays to keep the backup instance of the database in sync with the primary instance. Also consider fault-tolerant file systems to host database files.

Profile 2: Large Domestic Deployment

This deployment has several hundred to several thousand users in an Enterprise deployment that is operational during standard business hours only.

• Load balancers. If using hardware-based third-party HTTP load balancers, set up redundant load balancers. Verify that if a load balancer fails, the remaining load balancers can provide acceptable performance under high workloads.
• Web server. Set up at least two load-balanced Web servers for high availability.
• Siebel Servers hosting an AOM. Same as Profile 1.
• Siebel Servers hosting other types of components. Same as Profile 1.
• Siebel Gateway Name Server. This should reside on a dedicated, clustered server pair and can also reside on Siebel Servers in an existing cluster. Sharing the clustered servers will have minimal performance impact.
• Siebel File System. Deploy a clustering technology that has been certified by Oracle. At a minimum, use a RAID 5 disk array for your file system. In addition, make regular backups of your data.
• Siebel Database. Same as Profile 1.

Profile 3: Limited Resources Deployment

This deployment has 500 users or less and operates during standard business hours with limited hardware resources.

Consider collocating multiple Siebel Servers and Web servers on a single computer. Use load balancing for each server type to achieve high availability at minimal cost. Siebel native load balancing for the Siebel Servers will work well in this configuration.

To establish high availability, consider putting the Siebel deployment in a two-system cluster. At minimum, make sure that the Siebel Gateway Name Server, Siebel Database, and Siebel File System are clustered.

Profile 4: Application Integration Deployment

This deployment uses third-party application servers to access the Siebel application. There are multiple integration points between Siebel applications and other, third-party applications. This profile may use Siebel EAI extensively.

There are no unique high availability requirements for this profile. See the previous discussions of the other profiles.

Make sure that the third-party applications are highly available by reviewing the specifications published by those vendors.

If you use multiple load-balanced Siebel Servers, review the recommendations for Profile 2.