Siebel CRM Siebel Mobile Guide: Disconnected Siebel Innovation Pack 2017, Rev. A E52427-01 |
|
![]() Previous |
![]() Next |
View PDF |
Load balancing distributes the workload for multiple Siebel Servers. You can load-balance the synchronization of the Siebel Mobile disconnected application at the Siebel Server level to achieve better scalability and high availability. This capability removes the limitation of assigning users to a specific application Siebel Server at installation time.
The load balancers used for synchronization are the same as those for Siebel Business Applications. You can use either the native load balancer or a third-party HTTP load balancer.
For information about configuring native Siebel Server load balancing or third-party load balancing (which depends on the third-party product), see Siebel Installation Guide for the operating system you are using and Siebel Deployment Planning Guide.
The Siebel Server uses a location on the server to store users' extracted files and state information. Each user and mobile application combination has a unique synchronization directory. The Application Directory user parameter enables the administrator to define this location. For information about setting the Application Directory user parameter, see "Configuring the Application Directory Setting".
By defining a shared location for this parameter, synchronization services for Siebel Mobile disconnected applications can be load-balanced. When users request a synchronization session, their request is directed (by a load-balancer) to an available Siebel Server hosting the appropriate Application Object Manager for Siebel Mobile, which will be able to access the users' synchronization directory. For example, a Siebel Mobile disconnected application can be configured to point to a generic URL for synchronization.
If multiple servers are configured with load balancing for the Siebel Mobile disconnected application when synchronization is also configured for the application, then all requests are routed to only one server. To change this so that requests are routed to all load balanced servers, complete the steps in the following procedure.
To load balance when synchronization is configured for Siebel Mobile
Using Siebel Server Manager, set the MaxTasks and MaxMTServers parameters.
Set the following parameters:
MobileSync. Set the Disconnected Mobile Synchronization component group. (set componentgroup=MobileSync). For more information, see the first step in "Setting Up the Disconnected Mobile Synchronization Component Group".
MobileDbXtract. Set the Data Extraction component to whichever component is being used for the mobile data extraction (for example, set component= ServiceMobileDbXtract_enu). For more information, see the second step in "Setting Up the Disconnected Mobile Synchronization Component Group".
HonorMaxTasks. Set the HonorMaxTasks parameter to True.
To check the existing value of HonorMaxTasks from the command line:
list advanced param HonorMaxTasks for com <comp_name>
To set HonorMaxTasks from the command line:
change advanced param HonorMaxTasks=True for comp <comp_name>
To check (and if required reset) the existing value of HonorMaxTasks from the Siebel business application user interface:
Navigate to the Administration - Server Configuration screen, then the Servers, Components, Parameters view.
Click the Advanced button in the Parameters applet, and then query for the HonorMaxTasks parameter.
For more information about the MaxTasks, MaxMTServers, and HonorMaxTasks parameters and setting them, see Siebel System Administration Guide and Siebel Performance Tuning Guide.