| Bookshelf Home | Contents | Index | Search | PDF | |
Performance Tuning Guide > Tuning Siebel eConfigurator for Performance > Best Practices for Siebel eConfigurator Tuning >
Tuning Siebel eConfigurator
How you configure your Siebel Server components for Siebel eConfigurator server deployments, for appropriate tuning, depends in part upon which deployment method you use, as described in Topology Considerations for Siebel eConfigurator.
- If you deploy Siebel eConfigurator on the AOM, then your eConfigurator tuning calculations must be made in combination with your AOM tuning calculations.
- If you deploy Siebel eConfigurator using the Product Configurator Object Manager (eProdCfgObjMgr) server component on a dedicated Siebel Server machine, then your eConfigurator tuning calculations will be only indirectly related to your AOM tuning calculations and will be determined primarily by configuration-related concurrent users and request loads.
In particular, note that, for a dedicated Siebel eConfigurator server, the MaxTasks parameter should generally be set much lower than for an AOM. By default, the ratio of MaxTasks to MaxMTServers is 20:1 for eProdCfgObjMgr.
In addition, depending on request load, MaxTasks should generally be set lower for an AOM running Siebel eConfigurator than for an AOM that is not running Siebel eConfigurator.
You can follow this general procedure to determine how to set these parameters:
- Determine what percentage of users for your Siebel application are also users of Siebel eConfigurator. For example, for every 100 users, 60 work with Quotes.
- Calculate what percentage of time these users spend using Siebel eConfigurator. For example, out of the 60 users mentioned above, only 30 are concurrently using Siebel eConfigurator.
- Maintain the default ratio of 20:1 for MaxTasks/MaxMTServers.
| Bookshelf Home | Contents | Index | Search | PDF | |
Performance Tuning Guide Published: 24 October 2003 |