1. Deployment Planning Guide
  2. Profile 2: Large Domestic Deployment

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.

This topic is part of Recommendations for High Availability Deployments.

  • Siebel Gateway. You can optionally configure clustering for Siebel Gateway using Siebel Management Console. For more information, see Defining High Availability Policies. Alternatively, you can use a dedicated, clustered server pair for this component, or include it with Siebel Servers in an existing cluster. Sharing the clustered servers has a 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 Application Interface. Application containers for Siebel Application Interface instances on multiple nodes can be load balanced using Apache HTTP Server (httpd) and Apache Tomcat Connector (mod_jk). For more information, see Components Involved in Service Failures.

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

  • Siebel Servers hosting other types of components. Same as Profile 1.

  • Siebel database. Deploy a clustering solution supported by your RDBMS vendor. To guarantee data availability and integrity, use data replication techniques such as mirroring and the disk arrays to keep the backup instance of the database in sync with the primary instance.