| Siebel CRM System Administration Guide Siebel 2018 E24823-01 |
|
 Previous |
 Next |
View PDF |
| Siebel CRM System Administration Guide Siebel 2018 E24823-01 |
|
Previous |
Next |
View PDF |
Siebel Server load balancing distributes the workload across multiple Siebel Servers. For background information and information about initially configuring your Siebel CRM server environment, see Siebel Deployment Planning Guide and the Siebel Installation Guide for the operating system you are using.
This topic includes the following information:
Server loads can become unevenly distributed for several reasons:
You have just added a new Siebel Server to the network. It will have a low workload compared to other Siebel Servers.
You have just enabled an Application Object Manager on a Siebel Server. It will have a lower workload than other Application Object Managers on different Siebel Servers.
There was a server configuration or request routing problem that prevented even distribution of workloads. When this problem is corrected, one or more Siebel Servers will have low workloads.
Siebel native load balancing distributes workloads based on logins. Users must terminate existing sessions and log in to the new sessions to cause workloads to be redistributed. For example, you have 1000 concurrent user sessions running on three Siebel Servers. You then add a fourth Siebel Server. Until all of the users end their sessions and log in again, the load is not evenly distributed between all four servers.
Whenever possible, let normal user login behavior rebalance Siebel Server workloads. Intervene only when absolutely necessary. To rebalance server workloads, you can optionally stop SCBroker on a Siebel Server. Doing so directs workload away from that server, but does not affect existing user sessions. However, session reconnect does not work for this server. If the connection times out, and user requests come through a Siebel Application Interface other than the one used for login, then the session is lost.
This topic provides guidelines for resolving problems with Siebel native load balancing. To resolve a problem, look for it in the list of symptoms or error messages in Table 3-2. Some problem solutions in the table require changing the function of server components.
Table 3-2 Resolving Siebel Native Load Balancing Problems
| Problem | Cause | Solution |
|---|---|---|
|
Users do not get a login page. The browser might display |
Verify TCP port access for Siebel Servers, Siebel Gateway, and Siebel Application Interface. |
See "Verifying Load Balancing Port Access on Siebel Servers". |
|
Increase the Siebel Application Interface logging level. |
To turn on detailed Siebel Application Interface logging, increase the log level for Siebel Application Interface. For more information, see the information about configuring the Siebel Application Interface in the Siebel Installation Guide for the operating system you are using. The logs for this module are located in |
|
|
Users can connect but loads are not balanced evenly between Siebel Servers |
Unequal loads might be caused by characteristics of users and jobs. |
Because jobs are distributed in a round-robin fashion, it is normal for a snapshot of the servers to show somewhat unequal loads. Unequal loads can be caused by several things, including the nature of the jobs and the rate at which users log in and log out on different servers. Over a longer period, the number of sessions handled by each server evens out. |
|
Siebel Servers do not have equal access to computing resources. |
Verify that all of the Siebel Servers have equal access to computing resources such as CPU and memory. |
|
|
A Siebel Server has recently added or has been restarted. |
Load balancing is based on user logins. During the process in which current sessions are terminated and new sessions are started, the new Siebel Server is included in the load sharing. |
|
|
A Siebel Application Interface cannot route requests to one or more Siebel Servers. |
Check for connectivity problems between the Siebel Application Interface and the Siebel Server with the low workload, as described earlier in this table. |
|
|
A Siebel Server is rejecting an unusual number of user requests. |
Check the Siebel Application Interface log files for
|
|
|
A Siebel Server has functional or configuration problems. |
Enable server diagnostics. Look for problems with components. Verify that the basic configuration is correct. For more information about monitoring and diagnosing server problems, see Siebel System Monitoring and Diagnostics Guide. |
This topic describes how to verify access to the load balancing port (that is, the port on which the SCBroker component listens) on your Siebel Servers.
To verify load balancing port access on your Siebel Servers
On the computer where Siebel Application Interface is running, telnet to the SCBroker port (such as 2321) on each Siebel Server.
For example, if a Siebel Server has the host name SiebSrvr1, then use the following command:
telnet SiebSrvr1 2321
If the connection succeeds, then there is load balancing port access. The connection times out after 500 ms.
If the connection fails, with the message Could not open connection to server, then complete the remaining steps that follow.
Verify that the Siebel CRM applications that you want are running on each Siebel Server.
On each Siebel Server, verify that SCBroker is running and is configured to listen on port 2321.
Verify that the operating system is not blocking access to the SCBroker port.
Check that no other networking device, such as a firewall, is blocking access to the SCBroker port.
