Bookshelf Home | Contents | Index | PDF |
Siebel Deployment Planning Guide > Application-Level Deployment Planning > Siebel Product Configurator Deployment Planning > Siebel Product Configurator Deployment Topology OptionsSiebel Product Configurator offers the flexibility of different deployment topology options. This topic is part of Siebel Product Configurator Deployment Planning. Siebel Product Configurator deployment topology options are as follows:
In many cases, the option of deploying Siebel Product Configurator on a different application server computer might result in a much better use of resources due to pooling effects. Considering the example examined and sized from the preceding topic, the result was a sizing of one factory and one worker to be cached for each Application Object Manager on each server. The implications of this approach across the whole enterprise are as follows:
Because the requirement is to support 100 concurrent users, many of these factories and at least 100 of these workers are idling at any time. The large amount of cache in this case is because there is no way to know in advance which Application Object Manager process the user who is configuring is connected to. For this reason, caching must be done across all of the Application Object Managers. There are other problems with this scenario. For instance, what happens when two users are connected to the same Application Object Manager process and both want to configure? In this case, the second user has to create a worker, causing performance issues for that user. Also, if there are multiple users configuring on the same computer, then the computer might run out of memory. Consider another scenario. Assume that the enterprise has customizable products that these users might be configuring, with 50 concurrent users configuring each customizable product. However, because there is no way to know in advance which Application Object Manager process these users might be connected to, you would have to cache two factories and two workers for each Application Object Manager, which would be a less-than-satisfactory solution. |
Siebel Deployment Planning Guide | Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |