Siebel Performance Tuning Guide > Tuning Siebel Web Client for Performance > Best Practices for Siebel Web Client Tuning >

Configuring the Busy Cursor for Standard Interactivity Applications

When the parameter EnableSIBusyCursor is set to TRUE (default), the Siebel application cannot accept new requests until it has finished serving the current request. An example of a new request is a user's attempt to drill down on a record.

The default setting of this parameter helps prevent the occurrence of JavaScript errors as the user cannot click on another link while a page is loading. Setting EnableSIBusyCursor to FALSE may improve network bandwidth usage for Siebel applications that use standard interactivity mode. It disables the appearance of the hourglass icon and allows the user to click on other links before the current request has been served.

You set the value for EnableSIBusyCursor in the [InfraUIFramework] section of your application configuration file.

Siebel Performance Tuning Guide Copyright © 2006, Oracle. All rights reserved.