Data Server Settings in the Applet

In this section:

The Data Server tab of the ReportCaster Server Configuration tool enables you to configure the WebFOCUS Reporting Server(s) associated with ReportCaster. Using the configuration settings in this tab, you can also configure multiple WebFOCUS Reporting Servers with ReportCaster and set up a cluster environment. Instruction for multiple and cluster servers appear later in this section.

Each WebFOCUS Reporting Server configured with ReportCaster contains the following folders (in bold) and settings, which are specific to each server:

Setting

Optional or Required/Default Value

Descriptions and Possible Values

Graph

Graph Engine

Default value is GRAPH53.

Controls which graph engine to use for server-side graphics. By default, this specifies the GRAPH53 setting. You can also specify the GRAPH32 setting used in Version 5 Release 2 and earlier.

Headless

Default value is NO.

Determines whether a graphics card exists on the WebFOCUS Reporting Server. When set to NO (the default), a graphics card exists on the server. When set to YES, no graphics card exists on the server.

Run Id

Type

Default value is USER.

USER - A valid Execution ID and password must be specified when creating a schedule.

STATIC - A valid Execution ID and password is supplied in the SRV User setting. When creating a schedule, you cannot specify an Execution ID and password.

User

Required if Type is set to STATIC.

Default Execution ID and password.

Server Config

>JDBC Driver

Class Name

Required.

Default value is ibi.jlink.EdaDriver.

Path and name of the Java class that is the driver for the WebFOCUS Reporting Server.

Note: ReportCaster only supports the JLINK Client. The WebFOCUS Client has a configuration setting to specify whether to use the NGx Java Client or the JLINK Client. NGx is the default value for the WebFOCUS Client.

URL

Required.

Default value is:

jdbc:eda:\\{host}:
{port};server=;

Used internally to establish the JDBC connection to the WebFOCUS Reporting Server for the execution of reports.

The default URL value enables ReportCaster to use the default service. If you want to use a service other than the default, then:

  • Create a service using the Reporting Server Web Console.
  • Append CLASS=CLIENT(servicename) to the URL value, where servicename is the non-default service name. For example, for ReportCaster to use a service named rcaster, set the URL value to: 
    jdbc:eda:\\{host}:{port};server=;
CLASS=CLIENT(rcaster)

    Optionally, you can set ENCRYPTION=1 to encrypt the communications link between the ReportCaster Distribution Server and the WebFOCUS Reporting Server using the Data Encryption Standard (DES). For example,

    jdbc:eda:\\localhost:12470;server=;
ENCRYPTION=1

    To connect to a CLM node, specify an odin.cfg file instead of the host and port on the JDBC URL. For example: 

    jdbc:eda:\\cfg=c:\ibi\
WebFOCUS77\client\wf\
etc\odin.cfg;server=nodename

>Server Config

Maximum Connections

Required.

Default value is 3.

Maximum number of connections available to the WebFOCUS Reporting Server. You can specify a maximum of 20 connections.

This setting works in conjunction with the optional Weight setting, enabling you to prioritize the alternate servers in a cluster queue.

Weight

Optional.

This setting may be from 10 (the highest) to 0 (the lowest). Default value is 4.

This setting is only available when you create alternate server(s) within a cluster. Used with the Maximum Connections setting.

This setting works in conjunction with the Maximum Connections setting, enabling you to prioritize the alternate servers in a cluster queue.

For example, if you have three servers (A, B, and C), you might want server A to be used as the primary server. You would specify a higher weight (10 is the highest) and Maximum Connection (20 is the highest) setting for server A. If you want server B to be used the least, you would specify the lowest weight of 1 and a Maximum Connection of 3.

Shared

NO is the default value.

Can only be enabled when Run Id is set to USER.

YES - When creating a schedule, the ReportCaster user ID and password is internally assigned as the Execution ID and password.

NO - When creating a schedule, the Execution ID and ReportCaster user IDs and passwords are independent sets of credentials.

Trusted

Default value is NO.

When set to PASSTHROUGH, Shared must also be set to YES.

YES - The Execution ID is the value set in REMOTE_USER at schedule time, and no password is required to connect to the WebFOCUS Reporting Server when schedules run. Trusted security is not supported when the WebFOCUS Reporting Server resides on a Windows platform.

No - Valid Execution credentials are required to connect to the WebFOCUS Reporting Server when schedules run.

PASSTHROUGH - The owner ID of the schedule is used as the Execution ID, and no password is required to connect to the WebFOCUS Reporting Server when schedules run. A password is required at schedule creation. PASSTHROUGH can only be enabled when Shared is set to YES. PASSTHROUGH is not supported when the WebFOCUS Reporting Server resides on a Windows platform.

Type

NODE is the default value.

NODE - This server provides a single connection point for data transmissions.

CLUSTER - This is the primary server among a group of servers that act as a single system. This feature is useful for enabling high availability, load balancing, and parallel processing.

For more information about cluster servers, see Configuring Cluster Servers in the Applet.
x
Configuring WebFOCUS Reporting Servers With ReportCaster in the Applet

How to:

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

x
Procedure: How to Add a WebFOCUS Reporting Server in the Applet
  1. In the Data Server tab of the ReportCaster Server Configuration tool, click the WebFOCUS Server List folder.
  2. Click the Create a new element icon, or right-click and select New from the drop-down menu. The Server Name dialog box opens.
  3. In the Name field, specify the name of the server you want to add to the ReportCaster configuration file. For Managed Reporting Standard Reports or My Reports, this name must match the NODE setting for that server specified in the /client77/wfc/etc/odin.cfg file.
  4. Click OK. The server is added to the list of available WebFOCUS Reporting Servers.
  5. Fill in the appropriate settings. For more information about these settings, see Data Server Settings in the Applet. If you are planning to configure a cluster server, see Configuring Cluster Servers in the Applet.
  6. Click the Save icon, or select Save from the Action menu. A message appears asking for confirmation that you want to save the changes to the configuration file.
  7. Click Yes to save the changes, click No to cancel the changes and exit the configuration tool, or click Cancel to cancel the changes and remain in the configuration tool.

Caution: Information Builders does not recommend changing the name of a WebFOCUS Reporting Server, since all existing jobs on that server will no longer run.

Top of page
x
Configuring Cluster Servers in the Applet

How to:

In the Data Server tab of the ReportCaster Server Configuration tool, you can configure cluster servers. This way, if ReportCaster attempts to connect to a primary WebFOCUS Reporting Server but is unsuccessful, it can connect to a secondary, or alternate server.

Note: DSTRUN only uses the default server. If the default server is clustered, then DSTRUN will not work.

The cluster functionality can be seen as a workload distributor because it distributes users and applications to different servers. This process is controlled through a single primary node that is defined in the Server Configuration tool.

The priority of the alternate servers are based on a combination of the Maximum Connections and Weight settings for each server. To obtain the priority value of each alternate server, multiply the values for these two settings. The higher the resultant value for the server, the higher the priority is for that server when allocating jobs to schedule. During run time, this priority is calculated dynamically based on the number of connections currently being used.
x
Procedure: How to Configure a Cluster Server in the Applet
  1. For the primary server within the cluster (for example, CLUST1), configure the Run Id and Type settings. Be sure to specify CLUSTER as the Type setting:

    RC-Server Configuration image

  2. Click the Cluster Servers folder.
  3. Right-click and select New from the drop-down menu.

    RC-Server Configuration image

    The Server Name dialog box opens.

  4. In the Name field, specify the name of the alternate server you want to add to the cluster.
  5. Type the URL setting for the server (for example, jdbc:eda:\\qaserver:8120;server=;).

    RC-Server Configuration image

  6. Specify Maximum Connections and Weight values for each server. Your priority total (Maximum Connections multiplied by Weight) decreases each time a connection is made. The ReportCaster Distribution Server then looks for the highest priority total for the next connection. Therefore, if you have multiple alternate servers with the same priority value, requests are dispatched according to the order of the server list.
  7. Repeat steps 2 through 6 for any additional alternate servers you want to add to the cluster. Once you have completed adding alternate servers to the primary cluster server, click the Save icon, or select Save from the Action menu. A message appears asking for confirmation that you want to save the changes to the configuration file.
  8. Click Yes to save the changes, click No to cancel the changes and exit the configuration tool, or click Cancel to cancel the changes and remain in the configuration tool.
WebFOCUS