Deployment Planning Guide > Managing Third-Party Load Balancing >

Monitoring Servers with Third-Party HTTP Load Balancers

Most third-party HTTP load balancers support server health monitoring. To set up Siebel Server monitoring, configure the load balancer to send an HTTP GET to the server URL. Here is an example URL:

//SiebSvr1:2321/siebel/SCBroker

• SiebSvr1. The Siebel Server host name or IP address
• 2321. The port number for the Siebel Connection Broker. The default is 2321.
• siebel. The Siebel Enterprise Server name
• SCBroker. The Siebel Connection Broker

If the Siebel Server and Siebel Connection Broker are running, the Siebel Connection Broker returns the string: SCBroker OK. For an overview of the Siebel Connection Broker, see About the Siebel Connection Broker.

This confirms that the Siebel Server is running on the specified platform and that SCBroker is listening at the specified port. This health check does not verify that specific Application Object Managers (AOMs) or other server components are running on the platform.

CAUTION:  Do not use TCP Health Check. It may connect to SCBroker and remain connected. This causes SCBroker to wait until the SCBroker component parameter ConnRequestTimeout expires. During this period, SCBroker cannot handle new user-session requests.

Best Practices for Setting Up Monitoring

Implement the following best practices when you set up server monitoring:

• On the Siebel Servers you want to monitor, set the Default Tasks and Maximum Tasks for SCBroker to 2. This provides two instances of SCBroker, which helps prevent monitoring requests from delaying handling of user requests.
• Use HTTP 1.0 to do health checks. It terminates connections to SCBroker quickly.