Siebel Deployment Planning Guide > High Availability Deployment Planning > How Service Failures Affect the Siebel Deployment >

Components Involved in Service Failures

This topic identifies major architectural components in a Siebel deployment that might be affected when a service failure occurs.

This topic is part of How Service Failures Affect the Siebel Deployment.

Siebel Web Clients

Client hardware failure and browser failures are the most common causes of Siebel Web Client failure. Operating system failures can also cause this, but are rare.

When the Siebel Web Client fails, user sessions are lost even though the sessions might continue running on the Siebel Server for a time. The user session is lost because when the Web Client fails, the Siebel session cookie usually is also lost. Without the cookie, the user cannot be routed back to the existing user session on the Siebel Server. Therefore, the user usually has to log in again and start a new user session.

Web Servers

Web servers might fail because of hardware or software issues. Typically, when the Web server fails, Web Clients cannot access Siebel applications, since requests must go through the Web server first. Existing connections from the Web server to Siebel Servers are also lost.

If Web servers are set up for high availability, for example if there are multiple, load-balanced Web servers, then subsequent requests can be routed to another working Web server. Usually when this occurs, the function of affected Web Client user sessions is not noticeably affected.

Third-Party HTTP Load Balancer for Siebel Servers

Third-party HTTP load balancers handle communication between Web servers and Siebel Servers. Causes of failure differ significantly between hardware-based and software-based solutions. When the load balancer fails, Web Clients and Web servers going through the load balancer cannot communicate with Siebel Servers. Network connections in most cases would also be severed, and user sessions are lost.

If there are multiple, clustered load balancers, then the backup load balancer can take over. Some load balancers can failover TCP sessions to a backup load balancer. For more information, see the vendor's load balancer documentation.

When the backup load balancer takes over, user sessions continue without interruption. However, user sessions are lost if any of the following occurs:

• A Web Client makes a request while the load balancers are failing over.
• TCP sessions are not cleaned up properly on the Web servers.

Siebel Servers

Siebel Servers might fail because of hardware or software issues. If the hardware platform fails, or the Siebel Server software fails, then all of the Siebel Server components are lost.

In other cases, individual Siebel Server components might fail. In turn, component failure can cause related user sessions or user requests to fail. The major groups of Siebel Server components are as follows:

• Application Object Managers. When Application Object Manager processes terminate unexpectedly, user sessions hosted by the Application Object Manager are lost. Users must log in to the Siebel application again.

  If users return to the same Siebel Server, then SCBroker tries to route the user request to a running Application Object Manager process.

  If there is only one Application Object Manager process and it has failed, then the request is directed to a different Siebel Server, unless there is only one Siebel Server.

• Batch-mode server components going through SRBroker. Most batch-mode server components receive server requests through SRBroker. An example is Workflow Manager. When a batch-mode component fails, the current server request fails.
• Synchronous server requests. An error is returned to the requesting component.
• Asynchronous server requests. An error is logged but not returned to the requesting component.

  Subsequent requests for the failed batch-mode component are attempted against a different instance of the component on the same Siebel Server or on a different Siebel Server.

  If no instance of the batch-mode component is available, then the request is logged to the S_SRM_REQUEST table to be processed later.

• Direct Object Manager requests. Examples of direct Object Manager requests are those to Siebel Product Configuration Object Manager. Some components, such as Siebel Configurator, have a native failover mechanism.
• Other server components with location restrictions. There are specialized server components that do not communicate through SRBroker. Siebel Remote Server is an example. Typically, requests to these components can only be processed by a specific Siebel Server. Therefore, if the server fails, then requests to that server fail, until the server is restarted.

Siebel Database

Access to the Siebel database can fail due to a number of factors:

• Database server hardware failure
• Database server running out of resources
• Disk failure
• Network failure

The impact on the Siebel deployment is either temporary or long term. For example, a temporary networking interruption, or a quick database server reboot, would result in a temporary disruption in service. A long-term interruption might occur when there is database corruption or a major server malfunction.

In general, user sessions are lost when there is a Siebel database service interruption. Users must log in to the application again. Application Object Manager sessions continue to try to connect to the database. After the database is running (assuming the connection retry count has not been exceeded), the connection succeeds. Users might not notice that there was an outage, unless they were currently working at the time of the database failure. In this case, users get database error messages.

If the interruption is temporary, then the interactive server components and most of the batch-mode server components try to reconnect with the Siebel database. If the interruption is long-term, then the Siebel deployment must be shut down and restarted once the database service is restored.

NOTE:  It is strongly recommended not to collocate a Siebel Server or other components with the Siebel database on the same server hardware. Such a deployment can affect performance of either component, and might in some cases lead to Siebel Server failure or extend interruptions of availability. For example, where a Siebel Server and the Siebel database are collocated, if the server computer is rebooted, then the database instance might not be up by the time this Siebel Server is up, so a connection could not be made. Siebel Server failure could result. However, if the Siebel Server and the database are on separate servers, as recommended, then the database is unaffected by rebooting the server computer where Siebel Server is installed, and is available as soon as the Siebel Server was ready to connect.