Nature of Siebel Application Deployment

Which Siebel applications and other modules that you are using, how you have configured your Siebel applications, how you have deployed your applications, and other such factors also affect Siebel Application Object Manager performance and how many concurrent users that you can support. Some of these factors include:

• Will you support employee applications (such as Siebel Call Center), customer applications (such as Siebel eService), partner applications (such as Siebel PRM), or some combination of these?

• Will you deploy your Siebel software in a global environment using multiple languages?

• What degree and what kind of application configuration changes have you made, such as those that you do using Siebel Tools? For more information, see Tuning Customer Configurations for Performance.

  The number of concurrent tasks that you can support varies based on the level of customization or the use of process automation for the application the Siebel Application Object Manager supports. Recommendations in this guide generally assume that operations performed are fairly standard or typical. Depending on your deployment and the modules used, some operations initiated by a single user action can be relatively complex and demand more resources than most other operations.

• Will you use specialized functionality such as offered by Siebel Product Configurator (for product configuration) or Siebel CTI (computer telephony integration for call center agents)? How will you deploy such functionality? What percentage of your user base will use such functionality? These are only examples of such specialized functionality.