Deployment Planning Guide > Siebel Architecture Overview >

About the Siebel Connection Broker

The Siebel Connection Broker (SCBroker) is a server component that provides intraserver load balancing. SCBroker distributes server requests across multiple instances of Application Object Managers (AOMs) running on a Siebel Server.

SCBroker listens on a configurable, static port for new requests. When a new request is received, it forwards the request to the AOM with the least number of running tasks. This creates a user session. Thereafter, SCBroker forwards requests that apply to this session directly to the AOM hosting the session.

SCBroker is enabled by default and has several parameters:

• PortNumber. Sets the port number on which SCBroker listens. The default is 2321, but you can change the port number.
• DfltTasks. Sets the default number of processes for SCBroker. The recommended value is 2.
• MaxTasks. Sets the maximum number of processes for SCBroker. The recommended value is 2. This value cannot be less than DfltTasks.
• AutoRestart. Default is On. If SCBroker terminates abnormally, this allows it to restart automatically. Setting this parameter to Off/False is not recommended.
• ConnForwardTimeout. The connection forward time-out determines how long SCBroker will wait for an Object Manager to accept a request. The default is 500 milliseconds. This time-out minimizes wait time when SCBroker forwards a connection request to an Application Object Manager, and the request cannot be accepted.

  If a time-out occurs, SCBroker reports an error back to the Web server. The SWSE then modifies the request by appending an RR to the Siebel URL. The SWSE then retries the request by forwarding it to the third-party HTTP load balancer. This causes the load balancer to use the round-robin routing rule to forward the request to the next available Siebel Server.

• ConnRequestTimeout. The connection request time-out determines how long SCBroker will wait for all the packets in an incoming new request. The default is 500 milliseconds. This time-out minimizes SCBroker wait-time when TCP/IP requests are incomplete.

  If a time-out occurs, the request is sent back to the Web server in the same fashion as a ConnForwardTimeout.