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.
You set the value for EnableSIBusyCursor in the [InfraUIFramework] section of your application configuration file.