|
Siebel Deployment Planning Guide > Application-Level Deployment Planning > Siebel Configurator Deployment Planning >
Example of Deployment Sizing with a Dedicated Configurator Server
This topic is part of Siebel Configurator Deployment Planning. Consider the sizing example for the deployment option of running the Configurator on the same server as the application server (see Example of Sizing the Cache with SnapShot Mode). Size it instead for the deployment option of Configurator running on a separate server. Assumptions
The requirement is to support 5000 concurrent Siebel Call Center users. Among them, at any time, 100 users use the Configurator. This means:
- The enterprise needs to support 5000 concurrent Call Center users.
- Of these 5000 Call Center users, 100 are expected to use the Configurator concurrently.
- There is only one customizable product in the product portfolio.
Sizing
Because all caching and services are specific to the AOM process on a Siebel Server, first you must estimate the size of the Call Center deployment. (The numbers used below are an example only and not indicative of Call Center sizing.)
- Assume you are supporting the 5000 Call Center users on seven application servers (each being a Pentium 4 machine with four CPUs and 4 GB of memory), with each server handling 720 users.
- Each application server itself is run with 25 AOMs, with each AOM supporting 25 users.
- Assume that one server has been configured to run the Configurator that will support the 100 users.
- The Configurator server is configured to run with four AOMs, with each AOM supporting 25 users.
To support cached objects, factories, and workers for all 100 users, the following conclusions can be drawn:
- At least one factory needs to be cached for every AOM process. You must cache four factories for the Configurator server or one for each AOM.
- To support all 100 concurrent users to get a cached worker, you must cache, at a minimum, 100 workers across the Configurator server. This means you must cache 25 workers for each AOM on the Configurator server.
In the example above, the cache size in this case for each AOM equals the size of the factory cache plus the size of the worker cache. Expressed as a formula, it looks like this: (5 times 1) plus (25 times 25) equals 630 MB for each AOM. Therefore, the Configurator cache requires a total of 4 times 630, which equals 2520 MB for each server. The server parameters would be set as shown in Table 10 for the Siebel Servers running the AOMs and the Configurator servers:
Table 10. Example Parameter Settings for Siebel Configurator Server
|
|
|
eProdCfgServer |
Name of the Siebel Server running the Configurator. |
Set On: Each Siebel Server running the AOM (see Table 11) |
eProdCfgSnapshotFlg |
True |
Set On: Each Siebel Server running the AOM and each Configurator server |
eProdCfgNumOfCachedObjects |
1000 |
Set On: Configurator server |
eProdCfgNumbOfCachedFactories |
1 |
Set On: Configurator server |
eProdCfgNumbOfCachedWorkers |
25 |
Set On: Configurator server |
This type of deployment across an enterprise with eight servers, one a dedicated server to support Configurator, requires 2520 MB of cache. This figure is much lower than the 6000 MB required for the eight application server deployment option. Choosing this deployment option makes better use of the cache. Moreover, since the Configurator server is configured to allow only 25 connections to each AOM, there would never be a case where a user does not find a cached worker to work with. In a scenario with multiple customizable products, this deployment would be much more efficient in terms of memory usage. Server Settings for Dedicated Configurator Server Deployment Mode
Table 11 shows server settings for dedicated (remote) Configurator server deployment mode. Except where noted, set these parameters on the AOM component.
Table 11. Parameter Settings for Dedicated Configurator Deployments
|
|
|
|
|
eProdCfgRemote |
Product Configurator - Use Remote Service |
Boolean |
False |
Setting to determine if Configurator is running on a different server from the AOM. On the AOM: set it to TRUE when running a dedicated Configurator server. On the dedicated Configurator server: leave this set to FALSE. |
eProdCfgServer |
Product Configurator - Remote Server Name |
Text |
None |
Name of the Siebel Server on which you are running a dedicated Configurator server. If you are using multiple dedicated Configurator server, separate the entries with semi-colons (;). |
eProdCfgTimeOut |
Product Configurator - Time Out of Connection |
Integer |
20 |
Setting in seconds that determines for how long the Siebel Server would try to initiate a connection with the remote Configurator server before returning an error to the user. |
eProdCfgKeepAliveTime |
Product Configurator - Keep Alive Time of Idle Session |
Integer |
900 |
Setting in seconds to determine the maximum interval of inactivity during a configuration session. If the interval of inactivity reaches this value, the user session is ended and the worker returns to the pool. If this parameter is not set, an infinite interval is assumed. Set this parameter on the AOM only. It does not apply on the remote Configurator server. NOTE: On the remote Configurator server (eProdCfgObjMgr component), set the parameter ConnIdleTime to a value like eProdCfgKeepAliveTime plus 1 second.
|
| 
