Bookshelf Home | Contents | Index | Search | PDF |
Siebel Wireless Administration Guide For Financial Services > Installing Siebel Wireless > Incremental Installation and Configuration >
Tuning Performance and Scalability
Several different parameters within the Siebel configuration files and within the Siebel application itself impact the performance and scalability achievable by Siebel Wireless applications.
The values of these parameters can be increased or decreased to support different numbers of concurrent users.
The first set of parameters that can be configured reside in the Siebel Web Engine's configuration file. These parameter settings can be viewed and updated by opening the eapps.cfg file located in the SWEApp/bin directory created during installation on the machine in which the Siebel Web Server Extension is installed.
Parameters to consider within the eapps.cfg file when tuning for scalability and performance include:
- AnonUserPool. Governs the maximum number of anonymous logins allowed at one time. For a typical configuration, this value is set to 10% to 15% of expected concurrent users to be supported. For additional information about the AnonUserPool parameter, see the Siebel Server Installation Guide for the operating system you are using.
- SessionTimeout. Governs the amount of time (in seconds) allowed before individual user sessions time out. The number of anonymous logins required typically increases as the duration of the Session Timeout parameter increases. The Session Timeout parameter could be set to 3600 (seconds, or 1 hour) for a typical configuration.
SessionTimeout parameters are defined in sections specific for each language under the following headings in the eapps.cfg file for each of the Siebel Wireless applications as follows:
- Under the /finswpsales_<language> heading, for Sales
- Under the /finswpserv_<language> heading, for Service
- Under the /wpbanking_<language> heading, for Banking
Once these parameters have been modified, the Siebel server should be stopped and started to force the new parameter values into effect.
Several parameters should also be configured from within the Siebel Web Client by a user with systems administrator access to support various Wireless concurrent usage levels. These parameters can be updated by navigating to Server Administration > Components > Component Parameters.
The parameters listed below are included for each of the following three Server Components, and must be updated for the particular server components representing the Siebel Wireless applications that are used. The three Server Components to consider are:
- Siebel FINS Sales Wireless (representing Siebel Wireless Sales)
- Siebel FINS Service Wireless (representing Siebel Wireless Service)
- Siebel Banking Wireless (representing Siebel Wireless Banking and Brokerage)
The following parameters must be set for the appropriate Server Components listed above for each of the Siebel Wireless applications that are used:
- Minimum MT Servers. Defines the default number of multithreaded server processes that are started for a component that has multithreading enabled. In a typical configuration to support 100 concurrent wireless users, this value is set to 5.
- Maximum MT Servers. Defines the maximum number of multithreaded server processes to be run concurrently for a component that has multi-threading enabled. In a typical configuration to support 100 concurrent wireless users, this value is set to 20.
- Maximum Tasks. Defines the maximum number of background mode, batch mode, or interactive mode processes or threads that can run concurrently for a component. In a typical configuration to support 100 concurrent wireless users, this value is set to 600.
NOTE: The value input for the Maximum Tasks parameter must be a multiple of the Minimum MT Servers parameter and the Maximum MT Servers parameter.
More general performance setting details can be found in the Siebel Server installation guide for your operating system.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Wireless Administration Guide For Financial Services Published: 18 April 2003 |