|Bookshelf Home | Contents | Index | PDF|
Some performance considerations for Siebel applications involve processing or tuning activities on servers only, and do not affect Siebel client performance. However, many other such factors either directly or indirectly affect Siebel client performance. This chapter highlights some of the factors most directly related to the performance of the Siebel Web Client.
The performance of the Siebel client depends on many factors, some of which are summarized below. For additional information on these topics, refer to applicable documents on the Siebel Bookshelf or Siebel SupportWeb.
All Siebel applications have many architectural elements in common. Multiple applications can use the same Siebel repository file (SRF). Each application uses its own AOM component. You may need to define, configure, and test multiple instances of each application to verify that your requirements are met in each usage scenario.
The performance of your Siebel applications will vary according to how you have configured the applications using Siebel Tools or custom browser scripts. See Following Configuration Guidelines.
Client performance will also vary according to which Siebel modules you deploy. The performance of the Siebel client is highly dependent on feature functionality. Therefore, performance characteristics of Siebel modules will differ.
Some modules add special processing requirements. For example, Siebel CTI uses the Communications Session Manager (CommSessionMgr) component, and supports the communications toolbar and displaying screen pops in the client. Server and local resources support this functionality.
The resources available on each user's local machine should meet or exceed the recommendations outlined in System Requirements and Supported Platforms on Siebel SupportWeb. Some performance enhancement measures depend directly on the available resources.
|Performance Tuning Guide|