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

Configuring Siebel Applications for Pop-Up Blocker Compatibility

Pop-up blocking software may sometimes cause Siebel applications not to work, because such software may block required Siebel application functionality generated by ActiveX controls. Such blocking software typically blocks ActiveX-generated processes or pop-up windows that originate from particular machine host names or domain names.

See also ActiveX Requirements in High-Interactivity Deployments.

Siebel applications that you run over the local Intranet (Siebel Web Client) or that run on local client machines (Siebel Mobile Web Client) may be affected by pop-up blockers. Configuring the Siebel application to use a fully qualified domain name (FQDN) may prevent such problems and allow you to use pop-up blockers safely.

For example, the URL http://ebiz.oracle.com uses FQDN, while http://ebiz does not.

CAUTION:  If you have configured FQDN for your Siebel applications, but conflicts with pop-up blockers persist, it may be necessary to uninstall the pop-up blocking software or any applications in which such functionality is built in.

Parameters to configure fully qualified domain names are located in multiple places. How you set these parameters depends on the Siebel client you are using. Specified hostnames or domain names must meet all applicable requirements-for example, underscores may not be used.

• Siebel Web Client. To use FQDN for this client type, configure the following parameters in the eapps.cfg file on each SWSE that is applicable to Siebel Web Client deployments.

  [default]
  EnableFQDN = TRUE
  FQDN = hostname.primaryDNS.domainsuffix

  where:

  • hostname, an optional element, is the name of the Web server machine
  • primaryDNS is the primary part of the domain name (such as siebel)
  • domainsuffix is the domain type (such as com)

    For example, FQDN might be set to corp.oracle.com, or to server1.corp.oracle.com.

    EnableFQDN is set to FALSE by default for the SWSE.

• Siebel Mobile Web Client. To use FQDN for this client type, configure the following parameters in the Siebel application configuration file, such as uagent.cfg for Siebel Call Center, on each local client machine.

  [Siebel]
  EnableFQDN = TRUE

  EnableFQDN is set to TRUE by default for the Siebel Mobile Web Client.

  If you do not also specify the FQDN parameter, the system constructs the URL automatically. For example, the system might construct the FQDN for CCHENG as ccheng.corp.oracle.com. Optionally, you can explicitly provide similar information below, using the FQDN parameter.

  CAUTION:  When you explicitly configure an FQDN for use with the Siebel Mobile Web Client, you must specify the local machine name. The localhost string from the default Siebel Mobile Web Client URL (which is used when EnableFQDN = FALSE) cannot be used as an element in an FQDN. The localhost string is only functional when used by itself, with no additional qualifying elements.

  FQDN = hostname.primaryDNS.domainsuffix

  where:

  • hostname is the name of the local client machine
  • primaryDNS is the primary part of the domain name (such as siebel)
  • domainsuffix is the domain type (such as com)

    For example, you might set FQDN to ccheng.corp.oracle.com.