How to: |
If you have configured a WebFOCUS Reporting Server elsewhere in your enterprise to access your data, and you wish to make that remote server visible in and accessible from the WebFOCUS Environments, Data Servers folder as a distinct, named entity, you must add the remote server to your WebFOCUS Client configuration. Except for the default server (for example, EDASERVE), which is visible under Data Servers, the listing of servers in this location is controlled by the WebFOCUS Client and implemented through the WebFOCUS Administration Console, which updates the WebFOCUS Client communication file (odin.cfg).
Once you add the remote server to your WebFOCUS Environment, you can access data and perform development directly against the named remote server. That is, you can use a variety of Developer Studio tools to access your application files, in their respective virtual folders, for development purposes. For example, you can open synonyms in the Synonym Editor, procedures in Report Painter, and HTML files in HTML Composer, and edit those files as if you were working on your local machine. These Reporting Servers can also be used by Managing Reporting if that environment is deployed in your organization.
Proceed as described in How to Add a Remote Server to the Environment.
The name cannot be the same as any other node name. It must begin with a letter and cannot be more than eight characters. When the client accesses this server, it will use this name.
Class options are:
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 the user ID and password it has available for the request.
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 Reporting Server. You should only select this option when your web tier is performing Basic Authentication.
To verify that the Authorization header is available to WebFOCUS, expand the Diagnostics node in the Administrative Console and select HTTP Request Info.
Kerberos. Configures WebFOCUS to pass the Kerberos ticket for the user to the 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 Reporting Server must run in security OPSYS mode. Kerberos must be specified in the odin.cfg file.
SAP Ticket. Enables customers using 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. The Reporting Server validates it using the SAP security API.
Service Account. Allows you to specify a user ID and password to be used for all connections to the Reporting Server.
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, and all users connect to the Reporting Server using the same credentials. This approach does not make it possible to identify which user is running a given request on the Reporting Server in Managed Reporting deployments, and therefore, is not recommended for them.
Trusted. Allows 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 Reporting Server RESTRICT_TO_IP setting or configuring a network firewall so that only a particular client can connect to the server.
Note: To complete the configuration of a trusted connection, you must enable the Reporting Server to accept trusted connections. Step 10 instructs you on how to configure the Reporting Server once you have completed configuring the WebFOCUS Client.
When you select Trusted, the Pass WebFOCUS User ID and their Groups and Advanced options become available, as shown in the following image.
If you select Advanced, you can enter the script variable and web server HTTP variable settings for User ID and User’s Groups.
You can also specify the following optional parameters:
cookie_name1, cookie_name2
header_name1, header_name2
Note: HTTP cookie and header names must not contain commas (,) or colons (:), since these are reserved delimiters.
REMOTE_USER is not a valid value in the HEADER input box, since it is a special type of HTTP header variable and its contents will not be sent to the Reporting Server. Instead, specify the WF_REMOTE_USER variable.
If you are using a self-signed certificate to enable HTTPS communication with a Reporting Server, the certificate must be configured in the Java environment in which the WebFOCUS Client is installed. This enables HTTPS communication between the Reporting Server and the following WebFOCUS Client tools:
Select one of the following options from the drop-down list:
CIPHER(x)(-MODE)
where:
Is AES128, AES192, AES256.
Is optional and defines an RSA key length of 1024 bits.
Is optional and is either Electronic Code Book (ECB) or Cipher Block Chaining (CBC).
For example, AES256x-CBC is the AES cipher, with 1024-bit RSA keys, and CBC mode. If the RSA or mode is not specified, then the default values are used. The RSA default value is 512 bits. The mode default value is ECB.
Because you specified Client in step 4, proceed to step 9 (and skip step 7, which is used when Cluster is specified).
Proceed to step 9.
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 the user ID and password it has available for the request.
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 Reporting Server. You should only select this option when your web tier is performing Basic Authentication.
To verify that the Authorization header is available to WebFOCUS, expand the Diagnostics node in the Administrative Console and select HTTP Request Info.
Kerberos. Configures WebFOCUS to pass the Kerberos ticket for the user to the 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 Reporting Server must run in security OPSYS mode. Kerberos must be specified in the odin.cfg file.
SAP Ticket. Enables customers using 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. The Reporting Server validates it using the SAP security API.
Service Account. Allows you to specify a user ID and password to be used for all connections to the Reporting Server.
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, and all users connect to the Reporting Server using the same credentials. This approach does not make it possible to identify which user is running a given request on the Reporting Server in Managed Reporting deployments, and therefore, is not recommended for them.
Trusted. Allows 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 Reporting Server RESTRICT_TO_IP setting or configuring a network firewall so that only a particular client can connect to the server.
Note: To complete the configuration of a trusted connection, you must enable the Reporting Server to accept trusted connections. Step 10 instructs you on how to configure the Reporting Server once you have completed configuring the WebFOCUS Client.
When you select Trusted, the Pass WebFOCUS User ID and their Groups and Advanced options become available, as shown in the following image.
If you select Advanced, you can enter the script variable and web server HTTP variable settings for User ID and User’s Groups.
You can also specify the following optional parameters:
cookie_name1, cookie_name2
header_name1, header_name2
Note: HTTP cookie and header names must not contain commas (,) or colons (:), since these are reserved delimiters.
REMOTE_USER is not a valid value in the HEADER input box, since it is a special type of HTTP header variable and its contents will not be sent to the Reporting Server. Instead, specify the WF_REMOTE_USER variable.
If you are using a self-signed certificate to enable HTTPS communication with a Reporting Server, the certificate must be configured in the Java environment in which the WebFOCUS Client is installed. This enables HTTPS communication between the Reporting Server and the following WebFOCUS Client tools:
Select one of the following options from the drop-down list:
CIPHER(x)(-MODE)
where:
Is AES128, AES192, AES256.
Is optional and defines an RSA key length of 1024 bits.
Is optional and is either Electronic Code Book (ECB) or Cipher Block Chaining (CBC).
For example, AES256x-CBC is the AES cipher, with 1024-bit RSA keys, and CBC mode. If the RSA or mode is not specified, then the default values are used. The RSA default value is 512 bits. The mode default value is ECB.
Because you specified Client in step 4, proceed to step 9 (and skip step 7, which is used when Cluster is specified).
Note: The node name provided in the Administration Console for CLM configurations must match the Cluster name of the Cluster Manager Server.
To access the user ID in a report request, use the protected Reporting Server variable &FOCSECUSER. This variable contains the connecting user ID, except when Reporting Server security is OFF. &FOCSECUSER is recommended over previous approaches, such as the GETUSER and CNCTUSR subroutines.
Note:
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.
You can also click Save As to save these settings for another specified node that will be added to the ibi/WebFOCUS80/client/wfc/etc/odin.cfg file.
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 Administration Console still indicates that the IBI_REPORT_SERVER is the default node, even though it is no longer the default.
WebFOCUS |