Siebel Performance Tuning Guide > Tuning Siebel Web Client >

Performance Factors for Siebel Web Clients

Some performance considerations for Siebel Business 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, see applicable documents on the Siebel Bookshelf.

About Supporting Multiple Siebel Modules

Employee applications and customer applications have different requirements and characteristics and might use different browsers and other related technologies.

• Employee applications, such as Siebel Call Center, use high interactivity mode and run in supported Microsoft Internet Explorer browsers only.
• Customer applications, such as Siebel eService or Siebel eSales, use standard interactivity mode and can run in a wider range of browsers and browser versions.

All Siebel applications have many architectural elements in common. Multiple applications can use the same Siebel repository file (SRF). Each application uses its own Siebel Application Object Manager component. You might 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.

Supporting users who are dispersed in offices around the country or around the world introduces special deployment factors that can affect performance.

About Local Computer Resources

The resources available on each user's local computer must meet or exceed the recommendations outlined in Siebel System Requirements and Supported Platforms on Oracle Technology Network. Some performance enhancement measures depend directly on the available resources.