Bookshelf Home | Contents | Index | PDF |
Performance Tuning Guide > Tuning Siebel Configurator for Performance > Topology Considerations for Siebel Configurator > Running Siebel Configurator on Dedicated ServersYou can run Siebel Configurator on one or more dedicated Siebel Server machines using a server component other than the AOM. This component is Siebel Product Configuration Object Manager (alias eProdCfgObjMgr_enu in a U.S. English environment). Possible variations on this general topology option include:
If a large number of concurrent users require configuration sessions, or there are a large number of customizable product models, then this deployment option (using one or more dedicated servers) may yield the best performance and make the most effective use of your hardware resources. With this option, you set some parameters for managing Siebel Configurator caching on each applicable AOM, and some on each applicable dedicated Siebel Configurator server. For details, see Administering Siebel Configurator Caching. Configuring AOM for Dedicated Siebel Configurator DeploymentsWhen you designate one or more dedicated server machines to run the Siebel Product Configuration Object Manager (alias eProdCfgObjMgr_enu in a U.S. English environment) component, then you must configure any AOM components from which users will initiate configuration sessions to route configuration requests to these machines. The AOM forwards each configuration session request to the dedicated Siebel Configurator server with the fewest concurrent users. Table 3 lists server parameters for managing dedicated Siebel Configurator deployments. Using Server Manager, set these parameters on each AOM (do not set them on the dedicated Siebel Configurator server machine).
|
Performance Tuning Guide |