1. Performance Tuning Guide
  2. Tuning Siebel Product Configurator

Tuning Siebel Product Configurator

This topic is part of Guidelines for Siebel Product Configurator Tuning.

How you configure your Siebel Server components for Siebel Product Configurator server deployments, for appropriate tuning, depends in part upon which deployment method you use, as described in Topology Considerations for Siebel Product Configurator.

  • If you deploy Siebel Product Configurator on the Siebel Application Object Manager, then your Siebel Product Configurator tuning calculations must be made in combination with your Siebel Application Object Manager tuning calculations.

  • If you deploy Siebel Product Configurator using the Siebel Product Configuration Object Manager (eProdCfgObjMgr) server component on a dedicated Siebel Server computer, then your Siebel Product Configurator tuning calculations will be only indirectly related to your Siebel Application Object Manager tuning calculations and will be determined primarily by configuration-related concurrent users and request loads.

In particular, note that, for a dedicated Siebel Product Configurator server, the MaxTasks parameter is generally set much lower than it is for a Siebel Application Object Manager. By default, the ratio of MaxTasks to MaxMTServers is 20:1 for eProdCfgObjMgr. In addition, depending on the request load, MaxTasks is generally set lower for a Siebel Application Object Manager running Siebel Product Configurator than it is for a Siebel Application Object Manager that is not running Siebel Product 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 Product Configurator. For example, for every 100 users, 60 work with Quotes.

  • Calculate what percentage of time these users spend using Siebel Product Configurator. For example, out of the 60 users mentioned previously, only 30 are concurrently using Siebel Product Configurator.

  • Maintain the default ratio of 20:1 for MaxTasks divided by MaxMTServers.

If you deploy Siebel Product Configurator using eProdCfgObjMgr on a dedicated Siebel Server computer and the database connection (login and logout) is slow, then 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 minus 1.

    This setting pools all user connections without sharing and avoids the creation and deletion of a new database connection for each eProdCfgObjMgr session. For more information about database connection pooling, see Configuring Database Connection Pooling for Siebel Application Object Managers.

  • 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 Siebel Security Guide.