1. Deployment Planning Guide
  2. Profile 1: Uninterrupted Global Deployment

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.

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. 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.

  • 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.

    The Siebel Product Configuration Object Manager is an exception, because it includes an internal load balancing mechanism.

  • Siebel Servers hosting other types of components. Enable batch components on multiple Siebel Servers. Server Request Broker routes 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, then you set up high availability as follows:

    • For the Application Object Manager and related components, use load balancing.

    • For the components that can be installed on only one server, use server clustering.

  • Siebel database. Deploy the 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.