Bookshelf Home | Contents | Index | Search | PDF |
Performance Tuning Guide > Tuning Siebel eConfigurator for Performance > Topology Considerations for Siebel eConfigurator >
Running Siebel eConfigurator on Dedicated Servers
You can run Siebel eConfigurator on one or more dedicated Siebel Server machines using a server component other than the AOM. This component is Siebel Product Configurator Object Manager (eProdCfgObjMgr).
Possible variations on this general topology option 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
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 Snapshot Mode caching on each applicable AOM, and some on each applicable dedicated eConfigurator server. For details, see Using Siebel eConfigurator Caching.
Configuring AOM for Dedicated eConfigurator Deployments
When you designate one or more dedicated server machines to run the eProdCfgObjMgr 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 eConfigurator server with the fewest concurrent users.
Table 5 lists server parameters for managing dedicated Siebel eConfigurator deployments. Using Server Manager, set these parameters on each AOM (do not set them on the dedicated eConfigurator server machine).
Table 5. Server Parameters for Dedicated Siebel eConfigurator Server Deployment
Bookshelf Home | Contents | Index | Search | PDF |
Performance Tuning Guide Published: 24 October 2003 |