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

Configuring Siebel Business Applications for Pop-Up Blocker Compatibility

Pop-up blocking software can sometimes cause Siebel Business Applications not to work, because such software might block required Siebel application functionality. Such blocking software typically blocks processes or pop-up windows that originate from particular computer host names or domain names. This topic applies to all Siebel Business Applications. See also ActiveX Requirements for Using High Interactivity.

Siebel Business Applications that you run on a LAN (Siebel Web Client) or that run on local client computers (Siebel Mobile Web Client) might be affected by pop-up blockers. Configuring the Siebel application to use a fully qualified domain name (FQDN), as described in this topic, might prevent such problems and allow you to use pop-up blockers safely. See also the descriptions of the EnableFQDN and FQDN parameters in Parameter Descriptions of the eapps.cfg File.

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

CAUTION:  If you have configured FQDN for your Siebel Business Applications, and if conflicts with pop-up blockers persist, then it might 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 that you are using. Specified hostnames or domain names must meet all of the applicable requirements, for example, underscores cannot 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 computer
  • primaryDNS is the primary part of the domain name (such as example)
  • domainsuffix is the domain type (such as com)

    For example, you might set FQDN to corp.example.com or server1.corp.example.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 computer.

  [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, then the URL is constructed automatically. For example, the FQDN for CCHENG might be constructed as ccheng.corp.example.com. Optionally, you can explicitly provide similar information, by using the FQDN parameter, as follows:

  FQDN = hostname.primaryDNS.domainsuffix

  where:

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

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

    CAUTION:  When you explicitly configure an FQDN for use with the Siebel Mobile Web Client, you must specify the local computer name. The localhost string from the default Siebel Mobile Web Client URL (which is used when EnableFQDN is 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.