Bookshelf Home | Contents | Index | PDF |
Siebel Performance Tuning Guide > Tuning Siebel Configurator > Guidelines for Siebel Configurator Tuning > Tuning Siebel ConfiguratorThis topic is part of Guidelines for Siebel Configurator Tuning. How you configure your Siebel Server components for Siebel Configurator server deployments, for appropriate tuning, depends in part upon which deployment method you use, as described in Considerations for Defining Topology for Siebel Configurator.
In particular, note that, for a dedicated Siebel Configurator server, the MaxTasks parameter is generally set much lower than for a Siebel Application Object Manager. By default, the ratio of MaxTasks to MaxMTServers is 20:1 for eProdCfgObjMgr. In addition, depending on request load, MaxTasks is generally set lower for a Siebel Application Object Manager running Siebel Configurator than for a Siebel Application Object Manager that is not running Siebel Configurator. You can follow this general procedure to determine how to set these parameters:
If you deploy Siebel Configurator using eProdCfgObjMgr on a dedicated Siebel Server computer and database connection (login and log out) is slow, then it is recommended that you do the following:
For more information about database connection pooling, see Configuring Database Connection Pooling for Siebel Application Object Managers. |
Siebel Performance Tuning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |