Siebel Server Administration Guide > Siebel Enterprise Server Architecture > Siebel Gateway >

Connection Brokering

Connection Brokering directs client connection requests to the least-laden Siebel Server operating the desired component, which provides greater scalability and higher availability. Connection Brokering is an optional service of the Siebel Gateway that uses the Resonate Central Dispatch product to distribute client connection requests across multiple Siebel Servers. Only Web client requests to the Siebel Application Object Manager (such as the Call Center Object Manager) and Interactive Assignment Manager can be load-balanced by Resonate Central Dispatch.

NOTE:  Mobile Web client connections will not be distributed by Resonate Central Dispatch.

Impact of Failure

When the Resonate Scheduler fails, current user connections making use of the Scheduler will be interrupted immediately. No new user sessions can be established to Siebel Servers. Although no immediate interruptions will occur to the Siebel Enterprise itself, no users will be able to access the Siebel Enterprise using Resonate.

High-Availability Solution

Central Dispatch specifies two servers for use as the Scheduler—one acts as a Primary Scheduler, while the other acts as the Secondary Scheduler. The Primary Scheduler always listens on the Virtual IP (VIP) address and distributes traffic unless it at some point becomes unavailable, at which point the Secondary Scheduler takes over listening on the VIP and distributes traffic.

Resource Requirement

The Connection Broker/Resonate Scheduler does not generally require many resources even when there is a heavy user load. Routing modules reside in the kernel layer or network driver layer.

For more information about Connection Brokering, see the Siebel Server Installation Guide for the operating system you are using.


 Siebel Server Administration Guide, Version 7.5, Rev. C 
 Published: 18 April 2003