Siebel System Administration Guide > Configuring the Browser for Siebel Web Clients >

Using the Browser Health Check

The browser health check is an optional feature that provides a mechanism to help administrators make sure that end users' browsers and client environments are configured appropriately for running Siebel high-interactivity applications.

When the browser health check is enabled, a dialog box may appear when a user starts the Siebel application, indicating required or recommended browser settings or other configuration changes for the local client machine.

The browser health check lists all settings for which required or recommended settings are not currently in effect. For many such settings, the user can fix the settings from this dialog box and proceed to running the application.

Although the default browser health check settings are intended to meet most customers' needs, they may not apply for all deployments. For configurable browser health check settings, customers can determine which settings should be set to Required and which settings may be set to Recommended. Customers should determine user policies for working within the browser and interacting with the browser health check based on their environment.

The browser health check runs in the current language for the Microsoft Internet Explorer browser.

NOTE:  The browser health check runs as an ActiveX control. In order for the browser health check to appear, each user's browser must already have minimum settings for enabling ActiveX controls. For more information, see ActiveX Requirements in High-Interactivity Deployments.

Running the Browser Health Check

As noted, the browser health check lists each setting that does not match the required or recommended setting, as currently configured. When the Siebel Browser Check window appears, required or recommended settings required to run Siebel high-interactivity applications appear. Click Auto Fix to enable all required and recommended settings. After clicking Auto Fix, the button changes to Run. Click Run to exit the browser health check and run the application.

For settings displayed as Recommended, you can manually uncheck the setting, should you wish to retain the setting. (For a recommended setting, the check is enclosed by a box.) If no checked settings are displayed, the Auto Fix button changes to Run. Click Run to exit the browser health check and run the application. To exit both the browser health check and the Siebel application, click Exit.

Some required settings cannot be auto-fixed. For such a setting, for which no check box is displayed, click to display more information about the requirement, then address the requirement as described.

About Settings

If you decide not to change settings currently shown as Recommended, and you have addressed all Required settings, you can check the box labeled Please do not warn me again about recommended settings. The browser health check no longer appears the next time you start the Siebel application. If, however, any settings are still Required, the browser health check continues to appear when you start the application; all Required and Recommended settings are listed. This behavior applies for each Siebel application.

Administering the Browser Health Check

In general, it is recommended that you enable the browser health check when you are deploying new or upgraded Siebel applications, or deploying applications to large numbers of new users or users whose browsers are newly installed. You should also enable the browser health check in environments that are configured with high security levels, or where installed Java software may not meet requirements for your Siebel high-interactivity applications.

The browser health check applies to deployments of the Siebel Web Client and Siebel Mobile Web Client (for high-interactivity applications).

After browser settings and other client environment settings for your users have been corrected and validated, you can optionally disable the browser health check to reduce login time for users.

To configure the browser health check, you set a series of parameter values, which are described later in this section. Where you configure the parameters depends on the type of client deployments:

• For Siebel Web Client deployments, you configure the browser health check parameters in the parameters view of the Application Object Manager component, such as SCCObjMgr_enu for the Siebel Call Center application in a U.S. English environment. After you modify the parameter, you must restart the Application Object Manager component in order for the changes to take effect for subsequent user logins.
• For Siebel Mobile Web Client deployments, you configure the browser health check parameters in the application configuration file, such as uagent.cfg for Siebel Call Center, on each client machine. After you modify the parameter, you must restart the Siebel Mobile Web Client in order for the changes to take effect for subsequent user logins.

Parameters for the Browser Health Check

Parameters applicable to the browser health check are described below.

To enable the browser health check, set the parameter EnableClientHealthCheck to TRUE (the default). Set this parameter to FALSE to disable the browser health check. Where you set a value for this parameter depends on the type of deployment in which you want to enable the browser health check:

• For a Siebel Web Client deployment, configure EnableClientHealthCheck in the Siebel Server Component Parameters view for the applicable Application Object Manager component.
• For a Siebel Mobile Web Client deployment, configure EnableClientHealthCheck in the [InfraUIFramework] section of the application configuration file, such as uagent.cfg for the Siebel Call Center application.

When EnableClientHealthCheck is TRUE, the browser health check reads the values of the following parameters to determine which settings it should check. The parameters may be set to Required, Recommended, or Ignore. The behavior associated with parameters set to Required or Recommended is described earlier in this section. Any parameter that is set to Ignore is not displayed in the browser health check-the same as if the parameter were not defined. You set the following parameters in the [ClientHealthCheck] section of the application configuration file for a Siebel Mobile Web Client deployment. For a Siebel Web Client deployment, you set the values of these parameters in the Siebel Server Component Parameters view for the applicable Application Object Manager component.

AppletScripting = Required
DisableScriptDebug = Recommended
FileDownload = Required
PasteViaScript = Recommended
PrintBGColors = Recommended
ReuseWindow = Recommended
SUNJREVersion = Recommended

NOTE:  Additional parameters may also be included in your released Siebel product. For example, parameters that start with QFE represent specific Microsoft Internet Explorer QFE patches that may be required.

Some of the browser health check parameters are described below:

• AppletScripting. Corresponds to the Internet Explorer security setting Scripting, Scripting of Java applets. For more information, see Manually Enabling Settings for Scripting.
• DisableScriptDebug. Corresponds to the Internet Explorer advanced setting Browsing Disable script debugging. For more information, see Disabling Script Debugging.
• FileDownload. Corresponds to the Internet Explorer security setting Downloads, File download. For more information, see Manually Enabling Settings for Downloads.
• PasteViaScript. Corresponds to the Internet Explorer security setting Scripting. Allow paste operations via script. For more information, see Manually Enabling Settings for Scripting.
• PrintBGColors. Corresponds to the Internet Explorer advanced setting Printing, Print background colors and images. For more information, see ActiveX Requirements in High-Interactivity Deployments.
• ReuseWindow. Allows the reuse of windows to launch shortcuts. This is an optional parameter but is recommended.
• SUNJREVersion. Corresponds to the version of Sun JRE software you must have installed. For more information, see Deploying Siebel Business Applications in High-Interactivity Mode Using JRE and Java Applets.