Siebel System Administration Guide > Configuring the Browser for Siebel Web Clients > Requirements for Deploying Siebel Applications Using High Interactivity >

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 applications that are deployed using high interactivity.

When the browser health check is enabled, a dialog box might appear when a user starts the Siebel application, indicating required or recommended browser settings or other configuration changes for the local client computer. Requirements for client computers are also identified in the Certifications application on My Oracle Support. The browser health check lists all of the 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 might not apply for all deployments. For configurable browser health check settings, customers can determine which settings must be set to Required and which settings can be set to Recommended. You must determine the user policies for working within the browser and for interacting with the browser health check based on the environment for your users.

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 for Using High Interactivity.

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 for using high interactivity appear. Click Auto Fix to enable all of the 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 if you want to retain the existing setting. (For a recommended setting, the check is enclosed by a box.) If no checked settings are displayed, then 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 fixed automatically by using the Auto Fix button. For such a setting, for which no check box is displayed, click to display more information about the requirement, then address the requirement.

If you decide not to change the settings currently shown as Recommended, and if you have already addressed the settings shown as Required, then 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 that you start the Siebel application. If, however, any settings are still required, then the browser health check continues to appear when you start the application. All of the 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 Business Applications, or deploying applications to large numbers of new users or users whose browsers are newly installed. Also enable the browser health check in environments that are configured with high security levels, or where installed Java software might not meet requirements for high interactivity.

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 topic. Where you configure the parameters depends on the type of client deployed:

• 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 any applicable parameters, 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 [InfraUIFramework] section of the application configuration file, such as uagent.cfg for Siebel Call Center, on each client computer. After you modify any applicable parameters, 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

The parameters applicable to the browser health check are described in the following information.

To enable the browser health check, set the parameter EnableClientHealthCheck to True (the default). When EnableClientHealthCheck is True, the browser health check reads the values of the following parameters to determine which settings to check:

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

The parameters can be set to Required, Recommended, or Ignore. The behavior associated with parameters set to Required or Recommended is described earlier in this topic. Any parameter that is set to Ignore is not displayed in the browser health check, the same as if the parameter were not defined.

NOTE:  Additional parameters might also be included in your released Siebel product. For example, parameters that start with QFE represent specific Microsoft Internet Explorer QFE patches that might be required for applications that are deployed using high interactivity.

The following are some of the browser health check parameters:

• 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 for Using High Interactivity.
• ReuseWindow. Allows the reuse of browser windows to launch shortcuts. Using this parameter is optional, but recommended.
• SUNJREVersion. Corresponds to the minimum version of Java Runtime Environment (JRE) software that you must have installed for a high interactivity client. For more information, see Java Requirements for Using High Interactivity.