Siebel Performance Tuning Guide > Tuning Siebel Configurator for Performance > Best Practices for Siebel Configurator Tuning >

Tuning Siebel Configurator

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 Topology Considerations for Siebel Configurator.

  • If you deploy Siebel Configurator on the AOM, then your Siebel Configurator tuning calculations must be made in combination with your AOM tuning calculations.
  • If you deploy Siebel Configurator using the Product Configurator Object Manager (eProdCfgObjMgr) server component on a dedicated Siebel Server machine, then your Siebel Configurator 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 Configurator 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 Configurator than for an AOM that is not running Siebel Configurator.

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 Configurator. For example, for every 100 users, 60 work with Quotes.
  • Calculate what percentage of time these users spend using Siebel Configurator. For example, out of the 60 users mentioned previously, only 30 are concurrently using Siebel Configurator.
  • Maintain the default ratio of 20:1 for MaxTasks/MaxMTServers.

If you deploy Siebel Configurator using eProdCfgObjMgr on a dedicated Siebel Server machine and database connection (login and log out) is slow, it is recommended that you do the following:

  • Enable database connection pooling

    To enable connection pooling, set the parameters, MaxSharedDbConns and MinSharedDbConns, to positive integer values (at least 1) that are no higher than MaxTasks - 1.

    This pools all user connections without sharing and avoids the creation and deletion of a new database connection for each eProdCfgObjMgr session.

  • Use third-party user authentication

    Using third-party user authentication, such as LDAP, rather than database authentication avoids creating an additional database connection for authentication. For more information about authentication options, see the Siebel Security Guide.

For more information about database connection pooling, see Configuring Database Connection Pooling for AOMs.

Siebel Performance Tuning Guide Copyright © 2006, Oracle. All rights reserved.