WebFOCUS Online Help > WebFOCUS Administration Console > Reporting Servers > Adding or Changing Server Settings for a Specific Reporting Server Node

Adding or Changing Server Settings for a Specific Reporting Server Node

How to:

Administrators can use the WebFOCUS Administration Console to add WebFOCUS Reporting Servers and HTTP Listeners to the WebFOCUS environment. Additionally, the console can be used to add WebFOCUS Client node profiles for each WebFOCUS Reporting Server. We recommend setting WebFOCUS Reporting Server security using the node profiles. The nodes are added to the ibi/WebFOCUS76/client/wfc/etc/odin.cfg file.

A node can enable access to one server or multiple servers. If it specifies multiple servers, it is called a cluster node. The WebFOCUS Administration Console lets you define a basic cluster node and specify the servers it can access.

Tip: You can configure more advanced cluster functionality using the Web Console of the server. For details, see Technical Memo 4641: Distributing Workload Across Clustered WebFOCUS Reporting Servers.

Top of page
Procedure: How to Add a Remote Server to the WebFOCUS Environment
  1. Click Reporting Servers and then Remote Services.
  2. Click New.
  3. In the NODE field, specify the name by which you will refer to the server. The name is your choice, but cannot be the same as any other node name. In addition, the name must begin with a letter and cannot be more than eight characters. When the WebFOCUS Client accesses this server, it will use this name.
  4. Specify the Node class (Client, Cluster, or CLM Processing).

    If you specify:

    • Client, this node will function as a stand-alone server. It can also be used as an alternate server within a cluster configuration.
    • Cluster, this is the primary node that will be used to distribute workload to alternate servers.
    • CLM Processing, the Cluster Manager node monitors server performance statistics and sends the request to the best available server for processing.
  5. Click Next.
    • If you selected Client in step 4, proceed to step 6.
    • If you selected Cluster in step 4, proceed to step 7.
    • If you selected CLM Processing in step 4, proceed to step 8.
  6. The New Node window opens. Enter the following required parameters:
    1. HOST. Host name or IP address of the server.
    2. PORT. Port number for the TCP listener. The default port is 8120.
    3. HTTP_PORT. Port number for the HTTP listener. This is normally the second consecutive port that the server uses. Type the same port number that was specified during installation. The default HTTP port is 8121.
    4. CLASS. If this is a z/OS server, you must include a qualifier.
    5. SECURITY. Determines how WebFOCUS connects to the WebFOCUS Reporting Server. The following are possible SECURITY values:

      Default. Is the initial value for new nodes and represents the traditional behavior, where the odin.cfg file does not contain a SECURITY keyword. In this case, WebFOCUS makes an explicit connection to the Reporting Server with whatever user ID and password it has available for the request. A user ID may come from IBI_REPORT_USER on the console Client Settings, Reporting Server pane, from a WebFOCUS Client Node Profile, or from the user WF_COOKIE if a Reporting Server sign-on has taken place. How the server processes explicit connections depends on its security setting (OFF, PTH, OPSYS, LDAP, DBMS).

      HTTP Basic. Configures WebFOCUS to extract the user ID and password from the Authorization header. These credentials are then used to make an explicit connection to the WebFOCUS Reporting Server. You should only select this option when your Web tier is performing Basic Authentication so that the user Base64 encoded ID and password will be available in the request header. For example:

      Authorization              Basic amx0XHdmdXNlcjp3ZnVzZXIx

      To verify that the Authorization header is available to WebFOCUS, click the Diagnostics menu on the WebFOCUS Administrative Console and select HTTP Request Info.

      Kerberos. Configures WebFOCUS to pass the Kerberos ticket for the user to the WebFOCUS Reporting Server. This option enables an end-to-end single sign-on solution from the desktop to WebFOCUS, from WebFOCUS to the Reporting Server, and from the Reporting Server to supported relational DBMS systems. When using this option, the WebFOCUS Reporting Server must run in security OPSYS mode. There are additional setup requirements for WebFOCUS and Microsoft Active Directory that are described in Technical Memo 4647: Configuring Single Sign-on to the WebFOCUS Reporting Server Using Kerberos.

      SAP Ticket. Enables customers using WebFOCUS Open Portal Services in SAP Enterprise Portal to achieve single sign-on through WebFOCUS to a Reporting Server configured with the Data Adapter for SAP. WebFOCUS passes along the MYSAPSSO cookie of the user, created on SAP Enterprise Portal, to the Reporting Server which validates it using the SAP security API.

      Service Account. Enables you to specify a user ID and password to be used for all connections to the Reporting Server, as shown in the following image.

      The service account credentials are encrypted and stored in the SECURITY keyword of the odin.cfg file. When defined, the service account overrides any other credentials that may be presented to WebFOCUS for this Reporting Server node.

      Trusted. Enables you to connect to the Reporting Server with only a user ID. This option is useful when no password is available for the user, and controls can be placed on the server to ensure that connections from unauthorized clients are rejected (for example, employing the server RESTRICT_TO_IP setting so that only a particular WebFOCUS client can connect to the server).

      If the server runs in security OPSYS mode, the connecting user ID must be valid on the server operating system and the Reporting Server cannot run on Windows. In this scenario, the connecting user appears in the server edaprint.log file and is returned by the server GETUSER and CNCTUSR subroutines. The report agent runs in the security context of the connecting user, which makes it possible to use operating system permissions and the trusted option for DBMS adapters in order to restrict file and data access.

      Trusted connections are also supported by servers running in security OFF, PTH, and LDAP modes provided that the server trust_ext setting is enabled.

      In this configuration the connecting user appears in the server edaprint.log file and is returned by the server CNCTUSR subroutine. The server GETUSER subroutine will always return the user ID that started the server. When the server runs in LDAP mode the connecting user must be found in the LDAP directory before the connection is accepted.

      If the server runs in the PTH or OFF security modes, then trusted connections will be accepted without authentication by Reporting Servers on any platform, including Windows. The server edaprint.log file and CNCTUSR subroutine will reflect the connecting user ID, and the server GETUSER subroutine shows the user ID that started the server.

      The following lines in a report request are useful to determine connection behavior.

      -SET &CONNECT_USER = CNCTUSR('A30');
-SET &AGENT_USER = GETUSER('A30'); 
-TYPE Connect User is: &CONNECT_USER
-TYPE Report Agent runs as: &AGENT_USER

      When you select Trusted, the WebFOCUS script variable and Web server HTTP variable settings are displayed, as shown in the following image.

      Select the option that will be used to retrieve the connected user.

      Note: Trusted connections are not supported by servers running in security DBMS mode.

      You can also specify the following optional parameters:

      Because you specified Client in Step 4, proceed to Step 8 (and skip Step 7, which is used when Cluster is specified).

  7. The New Cluster Node window opens. Enter the following required parameters:
    1. ALTERNATE. Select the servers to be included in the cluster.
    2. DESCRIPTION. Description for the cluster.
  8. The New CLM Processing Node window opens. Enter the following required parameters:
    1. HOST. The IP address of the Reporting Server where the Cluster Manager is configured.
    2. PORT. UDP Port number.
    3. DESCRIPTION. Optional description for the CLM Processing node.

      You can add multiple CLM hosts and ports by clicking Add. A check box is added next to each new host and port combination. To remove a host and port, select the associated check box and click Remove.

  9. Click Save.

Tip: More advanced cluster functionality can be configured using the Reporting Server Web Console. For details, see Technical Memo 4665: Distributing Workload Across Clustered WebFOCUS Reporting Servers.

Top of page
Procedure: How to Change a Remote Server Node
  1. Click Reporting Servers and then Remote Services.
  2. Select the node you want to change.
  3. Click one of the following buttons:
    • Modify. Displays the settings for the selected node, enabling you to make changes.

      You can select the Set as Default Server Node check box to specify that the node is the default WebFOCUS Reporting Server. The node will be written as the IBI_REPORT_SERVER parameter value in the cgivars.wfs file. Note that even if you check Set as Default Server Node, this can be overridden if an IBIC_server is set in site.wfs or a node profile.

      If the site.wfs file or request URL contains an IBIC_server setting, it will override the IBI_REPORT_SERVER parameter. In this case, the WebFOCUS Administration Console indicates that the IBI_REPORT_SERVER is the default node, even though it is no longer the default.

      You can also click Save As to save these settings for another specified node that will be added to the ibi\WebFOCUS76\client\wfc\etc\odin.cfg file.

    • Remove. Deletes the selected node. You will receive a message asking for you to confirm the deletion. This button only appears if you have more than one node defined.
    • Profile. Enables you to override WebFOCUS default settings for a specific WebFOCUS Reporting Server node. These settings are written to ibi\WebFOCUS76\client\wfc\etc\node.prf, where node is the node you selected in Step 2.
    • Server Console. Displays the WebFOCUS Reporting Server Console, which enables you to remotely manage your server environment. For more information, see the Server Administration for UNIX, Windows, OpenVMS, i5/OS, and z/OS manual.

    Note: You can select the Sort alphabetically check box to sort a list of multiple servers.

Top of page
Procedure: How to Configure 3DES Encrypted Communication to a WebFOCUS Reporting Server

This procedure assumes that you have already successfully installed and configured the WFServlet implementation of WebFOCUS.

  1. Download the Bouncy Castle .jar file from the following URL: http://www.bouncycastle.org/latest_releases.html .

    Depending on the JDK you installed on the machine where WebFOCUS resides, use the following.jar file:

    • For JDK1.5, use bcprov-jdk15-142.jar.
    • For JDK1.6, use bcprov-jdk16-142.jar.
  2. Add the Bouncy Castle .jar file in the \ibi\WebFOCUS76\webapps\webfocus76\WEB-INF\lib directory.
  3. Redeploy the webfocus.war file if it is necessary to point to the .war file. Otherwise, point to the Web application directory.
  4. In the WebFOCUS Administration Console, click Reporting Servers and then Remote Services.
  5. Select the WebFOCUS Reporting Server node (for example, EDASERVE) you want to configure for encryption, then click Modify.

    The Remote Services - Modify Settings window appears.

  6. Click Add Setting.

    The Remote Services - Modify Settings - EDASERVE window appears.

  7. Set the ENCRYPTION parameter to 3DES using the drop-down list.
  8. Click Set and then click Save.
WebFOCUS