Siebel Deployment Planning Guide > Application-Level Deployment Planning > Siebel Product Configurator Deployment Planning >

About Deployment Topology for Siebel Product Configurator

There are two major topology approaches to deploying Siebel Product Configurator:

• Running Siebel Product Configurator in an Application Object Manager component.
• Running Siebel Product Configurator on one or more dedicated Siebel Servers.

For details, see Siebel Product Configurator Deployment Topology Options.

This topic is part of Siebel Product Configurator Deployment Planning.

Running Siebel Product Configurator in an Application Object Manager Component

You can run Siebel Product Configurator in the Application Object Manager component, such as a language-specific Call Center Object Manager component.

If a small number of concurrent users require configuration sessions, or there is a small number of customizable product definitions, then this deployment option might yield reasonable performance and make the most effective use of your hardware resources.

Running Siebel Product Configurator on Dedicated Computers

You can run Siebel Product Configurator on one or more dedicated Siebel Server computers using a server component called the Siebel Product Configuration Object Manager (eProdCfgObjMgr).

Such server computers are sometimes referred to as remote servers, because they are remote to the computer on which the Application Object Manager is running. In general, this guide uses the term dedicated servers.

If a large number of concurrent users require configuration sessions, or there are a large number of customizable product definitions, then using one or more dedicated Siebel Product Configurator servers might yield the best performance and make the most effective use of your hardware resources.

Possible variations on this deployment strategy include:

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