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

About Deployment Topology for Siebel Configurator

This topic is part of Siebel Configurator Deployment Planning.

There are two major topology approaches to deploying Siebel Configurator:

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

For details, see Siebel Configurator Deployment Topology Options.

Running Siebel Configurator in an AOM Component

You can run Siebel Configurator in the AOM 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 may yield reasonable performance and make the most effective use of your hardware resources.

Running Siebel Configurator on Dedicated Servers

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

Such servers are sometimes referred to as remote servers, because they are remote to the machine on which the AOM 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 Configurator servers may 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 AOM component
• Running multiple eProdCfgObjMgr components with one AOM component
• Running one eProdCfgObjMgr component with multiple AOM components
• Running multiple eProdCfgObjMgr components with multiple AOM components