Running Siebel Product Configurator on Dedicated Servers

This topic is part of Topology Considerations for Siebel Product Configurator.

You can run Siebel Product Configurator on one or more dedicated Siebel Server computers using a server component other than the Siebel Application Object Manager. This component is Siebel Product Configuration Object Manager (alias eProdCfgObjMgr_jpn in a Japanese locale, for example).

Possible variations on this general topology option include:

• Running one eProdCfgObjMgr component with one Siebel Application Object Manager component

• Running multiple eProdCfgObjMgr components with one Siebel Application Object Manager component

• Running one eProdCfgObjMgr component with multiple Siebel Application Object Manager components

• Running multiple eProdCfgObjMgr components with multiple Siebel Application Object Manager components

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) can yield the best performance and make the most effective use of your hardware resources.

With this option, you set some parameters for managing Siebel Product Configurator caching on each applicable Siebel Application Object Manager, and some on each applicable dedicated Siebel Product Configurator server. For more information, see Configuring Siebel Application Object Manager for Dedicated Siebel Product Configurator Deployments and About Siebel Product Configurator Caching.

Administrators can configure session pooling for Siebel Product Configurator. This feature is intended to provide better performance when users or agents work with customizable products that are routed to remote (dedicated) instances of the Siebel Product Configurator Object Manager. For more information, see Configuring Session Pooling for Siebel Product Configurator.