Siebel Reports Administration Guide > Installing the Siebel Reports Server for UNIX > Postinstallation Tasks for the Siebel Reports Server >

Enabling the Siebel Reports Server with the Dedicated Web Client

This section describes how to modify Siebel Web Client files, such as siebel.cfg and uagent.cfg, on the Dedicated Web Client to run with Siebel Reports Server.

To configure the Siebel Application Object Manager files

  1. Navigate to the BIN\language subdirectory of your Siebel eBusiness Applications installation directory.

    2. Where:

    language = the Siebel code for the Language Pack you installed; for example, enu for U.S. English.

  2. Locate and open the appropriate configuration (CFG) file.
  3. Using your default text editor, edit the following parameters in the [Siebel] and [ActuateReports] sections.

    4. [SIEBEL]

    EnableFQDN = TRUE

    Where:

    EnableFQDN is the setting that enables the processing of requests to Web sites even if the user does not provide the fully qualified domain name.

    FQDN = name of local host followed by domain name

    Where:

    FQDN stands for Fully Qualified Domain Name. An example of a fully qualified domain name would be server1.siebel.com.

    The local host is the machine where the Dedicated Web Client is installed (example: localhost.Siebel.com).

    EnableFQDN and FQDN parameters are used in a Single Sign-On environment in which the Reports Server cookie, named ReportCookie, with a FQDN must be passed to different servers in the same domain. The Reports Server uses Single Sign-On to allow users access to reports without having to manually log in.

    [ActuateReports]

    EnableReportServer = TRUE

    ReportServerHost = name of the Reports Server machine followed by SOAP (Simple Object Access Protocol) server port number (example: server1:8000).

    ReportCastHost = name of the Actuate HTTP service followed by domain name and the Actuate HTTP service port number (example: server1.siebel.com:8700).

    ReportCastDomain = domain name for the Active Portal machine (example: siebel.com).

    ProtocolName = name of protocol to use for viewing reports (example: HTTP or HTTPS).

    RoxDir = /Siebel Reports/

    ConnectString = siebel.TCPIP.none.NONE://GatewayServerName:PortNumber/EnterpriseServerName/XXXOBJMGR_language/SiebelServerName

    Where:

    siebel.TCPIP = the networking protocol

    none (first instance) = the encryption type chosen

    NONE (second instance) = data compression method chosen

    GatewayServerName = the name of your Siebel Gateway Server

    PortNumber = the listening port number (default is 2320)

    EnterpriseServerName = the name of your Siebel Enterprise Server

    XXXOBJMGR_language = the type of Object Manager and language pack for the Siebel eBusiness application you are installing, for example:

    SCCOBJMGR_enu for U.S. English Siebel Call Center Object Manager

    SSEOBJMGR_enu for U.S. English Siebel Sales Object Manager

    SiebelServerName = the name of your Siebel Server

    When deploying the Reports Server with a load-balanced Siebel Server, the Reports Server should be installed separately on a machine that does not have a Siebel Server installed.

    However, if the Siebel Server is deployed with Resonate load-balancing, the Siebel Server name parameter should be excluded from the connect string. Reports will not generate if the Siebel Server name is included in the ConnectString parameter.


 Siebel Reports Administration Guide 
 Published: 18 July 2003