Data Servers Settings

The Data Servers folder in the Configuration tab contains settings to configure the Reporting Servers associated with WebFOCUS ReportCaster. Using the configuration settings in this folder, you can also configure multiple Reporting Servers with WebFOCUS ReportCaster.

Note: Data Server connection information is stored in the WebFOCUS Client, and not in WebFOCUS ReportCaster. WebFOCUS ReportCaster runs scheduled procedures through the WebFOCUS Client which is installed with the Distribution Server. When a WebFOCUS ReportCaster job is executed by the WebFOCUS Client, the alternate deferred server is used if an alternate deferred server is defined. For more information about configuring alternate deferred servers, see the ibi™ WebFOCUS® Security and Administration technical content.

The Data Servers folder contains the following configuration settings.

Setting

Optional or Required/Default Value

Descriptions and Possible Values

Settings for the Data Servers folder:

Graph Agents

The default value is 1.

Optimizes the processing of graphs. Due to performance considerations, we recommend configuring this setting to 1 Graph Agent for each concurrent graph report. However, your own internal testing should determine the Graph Agent value that best suits the business needs of your organization.

Graph Servlet URL

Optional.

There is no default.

Overrides the default graph server setting and configures graph image files to be created on the Application Server.

Type the following value

http://hostname/context_root/IBIGraphServlet

where:

hostname

Is the host name of the Application Server where the WebFOCUS Client is installed.

context_root

Is the site-customized context root for the WebFOCUS web application deployed on your Application Server. The default is ibi_apps.

This setting is available for WebFOCUS Reporting Server and WebFOCUS procedures.

This setting should not be used when web server security is enabled. This includes Basic authentication, IWA, SSL, and third-party security products (such as SiteMinder). In these cases, the web server security settings can prevent WebFOCUS from creating the graph.

Excel Servlet URL

Optional.

Specifies the application server to be used to zip the file components that comprise an EXCEL® 2007 file (.xlsx) as follows:

&URL_PROTOCOL://servername/alias/IBIEXCELSERVURL

where:

URL_Protocol

Is HTTP.

servername

Is the name of the application server where the WebFOCUS Client is installed.

alias

Is the context root of the WebFOCUS application. The default is ibi_apps.

This setting is available for the WebFOCUS Reporting Server and WebFOCUS procedures. This setting should not be used when web server security is enabled. This includes Basic authentication, IWA, SSL, and third-party security products (such as SiteMinder). In these cases, the web server security settings can prevent WebFOCUS from creating the Excel 2007/2010 file.

FOCEXURL/FOCHTMLURL

Default value is

http://localhost:8080

Specifies the fully-qualified URL, including host name and port of the FOCEXURL/FOCHTMLURL. If running with SSL security, update the URL to specify https.

Settings for an individual Data Server:

Name

Required.

Name of the selected Data Server.

Note: Data Server names are case-sensitive. Data Servers are defined in the WebFOCUS Client as uppercase so you should also define Data Servers as uppercase in WebFOCUS ReportCaster.

Default

Required.

This option is selected by default.

Set FOCEXURL/ FOCHTMLURL in the scheduled procedure

Required.

This setting is selected, by default. If this setting is not selected, the Distribution Server will not set the value of FOCEXURL or FOCHTMLURL for a scheduled procedure. Therefore, when cleared, if FOCEXURL or FOCHTMLURL is already set in the edasprof.prf file, this setting remains in effect, unless it is overridden in the scheduled procedure.

Security section

Security Type

By default, this option is set to User.

Static. A valid Execution Id and password is supplied in the User setting. When creating a schedule, you cannot specify an Execution Id and password.

User. A valid Execution Id and password must be specified when creating a schedule.

Shared. When creating a schedule, the user ID and password is internally assigned as the Execution Id and password.

Note: Since the actual password is not stored in the WebFOCUS repository, the Shared configuration can only be used when a password is not required to connect to the WebFOCUS Reporting Server.

Trusted. The Execution Id is the schedule owner and no password is sent to the WebFOCUS Reporting Server when schedules run.

Note: The Reporting Server must be a configured to accept a Trusted connection when the Trusted option is selected.

User

Required if Security Type is set to Static.

Default Execution Id and password.

To access the ID and password, select the icon to the right of the User field. The User dialog box opens, where you can type the user name and password.

Graph section

Graph Engine

Required. The value is GRAPH53.

Controls which graph engine to use for server-side graphics. By default, this specifies the GRAPH53 setting.

Headless

By default, this option is not selected.

Determines whether a graphics card exists on the WebFOCUS Reporting Server. When not selected (the default), a graphics card exists on the server. When selected, no graphics card exists on the server.

Maximum Connection/Threads

Required.

The default connection is 3.

Maximum number of connections available to the WebFOCUS Reporting Server. You can specify any maximum that can be supported by your hardware and memory.

Configuring Reporting Servers With ReportCaster

You can configure multiple Reporting Servers with ReportCaster through the Data Server folder in the ReportCaster Configuration tab. Although the installation program automatically populates values for the default EDASERVE server, all additional Reporting Servers must be added to the configuration manually.

Note: If the default WebFOCUS Reporting Server is changed on the Client, then the change will not be effective until the period specified by the IBFS Cache Cleaner service or until the Distribution Server is restarted. If the Distribution Server is installed on another machine with a separate copy of the Client, then a change to the default WebFOCUS Reporting Server will not be effective until the same change is made on the Client installed on the same machine as the Distribution Server.

Adding a Reporting Server

    Procedure
  1. In the left panel of the Configuration tab, select the Data Servers folder, then select New in the toolbar.
    Note: The default Data Server names are SERVER, SERVER 2, SERVER 3, and so on.
  2. From the Available Data Servers dialog box, select one or more Data Servers, and click OK. You can optionally select the Select All check box.
  3. Double-click the new server node in either the Data Servers folder in the left panel or the server list in the right panel.

    The right panel displays the default properties for the selected server .

  4. Provide values for the appropriate settings.

    In the Name field, verify the name of the server you want to add to the ReportCaster configuration is the same as the NODE setting for that server specified in the WebFOCUS Client Server Connections configuration. You can review the WebFOCUS Client Server Connections by accessing the Administration Console and selecting Reporting Servers within the Configuration tab.

    Optionally, provide values for the Security Type and Maximum Connections settings or leave the default values in place.

    You can also optionally set the Data Server being added to be the default Data Server when new schedules are created, specify not to have the FOCEXURL and FOCHTMLURL settings automatically added when scheduled jobs run, and specify that the Data Server does not have a graphics card, is Headless.

  5. To implement the changes in Report Broker, in the Configuration tab toolbar, select Save, then Restart.
Result
Caution: We recommend that you avoid changing the name of a WebFOCUS Reporting Server, since all existing jobs on that server will no longer run.