Bookshelf Home | Contents | Index | PDF |
Siebel Deployment Planning Guide > Application-Level Deployment Planning > Siebel Configurator Deployment Planning > About Deployment Topology for Siebel ConfiguratorThere are two major topology approaches to deploying Siebel Configurator:
For details, see Siebel Configurator Deployment Topology Options. This topic is part of Siebel Configurator Deployment Planning. Running Siebel Configurator in an Application Object Manager ComponentYou can run Siebel 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 Configurator on Dedicated ComputersYou can run Siebel 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 Configurator servers might yield the best performance and make the most effective use of your hardware resources. Possible variations on this deployment strategy include:
|
Siebel Deployment Planning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |