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

Example of Deployment Sizing with a Dedicated Siebel Configurator Server

Consider the sizing example for the deployment option of running the Siebel 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 Siebel Configurator running on a separate server.

This topic is part of Siebel Configurator Deployment Planning.

Assumptions

The requirement is to support 5000 concurrent Siebel Call Center users. Among them, at any time, 100 users use the Siebel Configurator. This means:

• The enterprise must support 5000 concurrent Call Center users.
• Of these 5000 Call Center users, 100 must be able to use the Siebel Configurator concurrently.
• There is only one customizable product in the product portfolio.

Sizing

Because all of the caching and services are specific to the Application Object Manager process on a Siebel Server, first you must estimate the size of the Call Center deployment. (The following numbers used are an example only and not indicative of Call Center sizing.)

• Assume that you are supporting the 5000 Call Center users on seven application servers (each being a Pentium 4 computer with 4 CPUs and 4 GB of memory), with each server handling 720 users.
• Each application server itself is run with 25 Application Object Managers, with each Application Object Manager supporting 25 users.
• Assume that one server has been configured to run the Siebel Configurator that supports the 100 users.
• The Siebel Configurator server is configured to run with four Application Object Managers, with each Application Object Manager supporting 25 users.

To support cached objects, factories, and workers for all 100 users, the following conclusions can be drawn:

• At least one factory must be cached for every Application Object Manager process. You must cache four factories for the Siebel Configurator server or one for each Application Object Manager.
• To support all 100 concurrent users to get a cached worker, you must cache, at a minimum, 100 workers across the Siebel Configurator server. This means that you must cache 25 workers for each Application Object Manager on the Siebel Configurator server.

In the preceding example, the cache size in this case for each Application Object Manager 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 Application Object Manager. Therefore, the Siebel Configurator cache requires a total of 4 times 630, which equals 2520 MB for each server.

The server parameters would be set as follows for the Siebel Servers running the Application Object Managers and the Siebel Configurator servers:

This type of deployment across an enterprise with eight servers, one a dedicated server to support Siebel 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 Siebel Configurator server is configured to allow only 25 connections to each Application Object Manager, 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 Siebel Configurator Server Deployment Mode

Table 10 shows server settings for dedicated (remote) Siebel Configurator server deployment mode. Except where noted, set these parameters on the Application Object Manager component.