Location of the Application Namespace root directory on the Web server where WebFOCUS is installed. The default directory is installationdrive:\ibi\apps unless a different directory was specified during the installation of the WebFOCUS Client.

Location of the WebFOCUS installation directory.

Location of the temporary directory.

Location of the backup directory. By default, points to webfocus\backup. The conf subdirectory under backup contains a copy of cgivars.wfs with all of the default values. This is where the console retrieves the default values for cgivars.wfs when the Restore Default Values option is selected.

The administrator can change the backup directory to another location. However, the conf directory must be created under the new location.

Location of the root directory for HTML and Java language files.

Location of the directory containing WebFOCUS configuration files, including install.cfg, mrrealm.cfg, mradmin-config.xml, and approotConfig.xml.

Note: If you change this setting and you deploy the ibi_html76.war or approot76.war static content server Web applications, you may need to update their deployment descriptors with the new location of the approotConfig.xml file. For more information, please see Configuring WebFOCUS in a Split Web-Tier and Application Server-Only Environment in the WebFOCUS installation manual for your platform.

The time when reports generated by the WebFOCUS Reporting Server are to be re-executed. The expiration time is set in seconds, and the default setting is 300 seconds.

You can view a previously executed report on the browser without re-executing its request. If the request for a report you are running is the same as the one executed previously (within 300 seconds), then the browser displays the previously executed report stored in the cache when you use the browser's Back, Reload, or Refresh button.

You can set EXPIRE_REPORTS in the following ways:

• To ensure that the reports are re-executed, set EXPIRE_REPORTS to 1 second.
• To view the browser's cached output without using the browser's Back, Reload, or Refresh button, set EXPIRE_REPORTS to a large number, such as 4,000,000,000 seconds.

An HTTP Header field that is used to specify how a browser should handle the caching of data in a request. Possible values are:

PRIVATE - The data in the response message is intended for only one user and should not be cached by a shared cache. This is the default value.

NO-CACHE - Browser caching is disabled. No files will be created on disk in the user`s Temporary Internet Folder.

For internal use only. This setting is only for Japanese or Korean languages.

Number of minutes the WebFOCUS cookie remains in effect. A value of 0 means that there will be no expiration time applied to the cookie.

This expiration time is refreshed each time a WebFOCUS report is run. WF_COOKIE is deleted when the expiration time is reached. Once WF_COOKIE is deleted, user credentials must be reentered in order to continue using WebFOCUS.

The following syntax enables you to include code to be executed on the WebFOCUS Reporting Server.

_site_profile=command

where:

command is any valid WebFOCUS Reporting Server syntax. The WebFOCUS Site Profile is not processed during a reporting server sign-on. It is only processed when running a procedure. Therefore, you cannot use it to record sign-on events.

Deletes files from the temporary directory. Files are deleted if they are older than the number of seconds specified.

This setting is applicable only when using the WebFOCUS CGI on UNIX. In order to display NLS characters on a report with Server Side Graphics, you must set this parameter to the appropriate UNIX locale encoding (for example, en_us).

Prevents a redirected request that was run on one machine from being viewed from a browser on another machine. It uses a unique encrypted identifier to ensure that the person that sent the original request is the same person retrieving the output again.

Points to where the odin.cfg file resides.

Is a fully qualified Java class that does the transin/transout processing (processing of a request to/output returned by the WebFOCUS Reporting Server) for a plug-in for the Servlet version of the WebFOCUS Client. This class must implement the WFTransInOutInterface java class. For example, one use of this class can be to enable data that is passed between the WebFOCUS Reporting Server and the Servlet to be parsed for bi-directionality (left/right vs. right/left strings).

Alias used to locate WebFOCUS resources on the Web server.

Points to the HTML page that opens after a successful sign-on occurs.

Turns on the persistent && feature. By default, this is set to YES. To disable, set to NO. The persistent && feature allows you to persist && variables for the duration of the browser session.

Auto prompting of server credentials. Possible values are:

YES - Displays a dynamic server sign-on page after a failed connection to the WebFOCUS Reporting Server. YES is the default value.

NO - Disables the dynamic server sign-on page. Users will receive a message after a failed connection to the WebFOCUS Reporting Server.

PREPROMPT - Displays a dynamic server sign-on page before attempting to connect to the WebFOCUS Reporting Server for the first time.

The alias of the WebFOCUS Web application.

With the Dynamic Language Switch feature, the default user interface language for a session is based on the browser's language, or by setting the IBIWF_language=nn parameter in the URL (where nn is the ISO language abbreviation).

The WebFOCUS Client uses this default setting to control the display language when the user's browser language is not one of the available options from the Select Language drop-down list during logon, or if no parameter is set in the URL call.

For possible values for the ISO language abbreviations, see the WebFOCUS National Language Support for International Computing manual.

Overrides the CGI/ISAPI/WFServlet client path for every redirected request.

Defines the size of the buffer used for accumulating report content before moving it to the report cache (a temporary directory) or displaying it in the browser when using the Servlet implementation of the WebFOCUS Client. Possible values are:

blank, missing, or less than 1024 - Indicates that the WFServlet will use the current default size of 16384 bytes.

nn - Is the size in bytes of the buffer that will hold the report output.

Globally sets redirection on or off. Valid values are:

MIME - Respects the values set in the mime table. MIME is the default value.

ALWAYS - Always redirects. The report content is saved in the report cache (a temporary directory). Content is moved from memory to the report cache when it exceeds the value of IBIWF_sendbufsize. Then a second HTTP call is made from the browser to retrieve the report content for display.

NEVER - Never redirects. The report output displays in the browser immediately after the request is executed. The report content is streamed to the browser without writing anything to the report cache when the content exceeds the value stored in IBIWF_sendbufsize.

LEN - Does not redirect. If the size of the report content exceeds the value stored in IBIWF_sendbufsize, the report output is moved from memory to the report cache. Once the report output is completely accumulated in the report cache, it is sent to the browser without an additional HTTP call. This setting is useful for report formats such as PDF that require the CGI/WFServlet to accumulate the entire report on the middle tier in order to get the correct file size before sending it to the client.

Controls how many WebFOCUS Reporting Server messages will be accumulated before WFServlet stops processing the request and displays error message 32100: "Reporting Server messages exceeded IBIF_max_messages, report retrieval aborted." Messages include –TYPE commands, &ECHO=ALL variables, and errors or warnings from a data adapter. The setting protects against the situation where the Java VM executing WFServlet runs out of memory. 20000 is the default value. IBIF_max_messages can be passed with the request, in which case it overrides the value set in the console. When debug mode is enabled in Developer Studio, a value of 50000 is passed with each request. A value of 0 indicates that no limit exists.

Enables the display of Resource Governor advise messages for the servers you select. When enabled, this setting overrides all format redirection settings specified in mime.wfs. This is because redirection must be enabled for all report formats in order to process the messages returned from the WebFOCUS Reporting Server to determine if there are any Resource Governor advise messages to display.

Controls how Developer Studio loads the Projects tree and the Web Applications tree in the Project Development Environment. The default setting is NO to preserve legacy behavior. NO means that the project tree and Web application tree in the development environment are loaded with the set of applications found by WFServlet in the Web-tier application root directory. YES means that these trees are loaded with the set of applications found by the Project Development Reporting Server, except for APP MAP applications which are filtered out. Customers who wish that their developers see only their own projects/applications in a shared development environment may wish to change this setting to YES and also do one of the following: APPLOCK the project development server (for more information, see Technical Memo 4613: Creating Private Application Views With APPLOCK 7.1 and higher) or use file system permissions on the server’s application folders.

Specifies the fully qualified name of an SMTP server that can be used by WebFOCUS to send e-mail messages. It is used to send links to Dashboard Mobile Favorites pages for Mobile Favorites users. It is also used by Magnify to send Notification and Reply e-mails.

Used by the WebFOCUS Developer Studio Source Control feature to identify the development environment. It is required by certain Version Control Systems such as ClearCase, CVS, and Subversion. This variable is transparent to the developers.

A value for this string must be provided if the environment will be used to source control files. Here is an example using the machine’s host name:

SCC_NAME=dev-server-1

The value needs to be unique for every WebFOCUS environment accessing the same Source Control repository, and the name should not contain spaces or any of the following special characters:

. / \ " ` ? : * < > |

Note: Avoid changing the value after files have been added to the Source Control repository. If you need to change the value, either add all files to the repository again or change the repository to be consistent with the new value. For more information, see Managing a Project With Source Control in the Creating a Reporting Application chapter of the Developing Reporting Applications With Graphical Tools manual.

Determines the version number of the Google Maps API. Can be an integer or decimal value. An integer value represents a stable version. The default value is 2.

Setting this variable to Y (the default) enables server-side graphics. If set to N, WebFOCUS uses applets to display graphics. When set to APPLET, the graph displays in an applet in the browser window and the SET GRAPPLETONLY=ON command syntax is sent to the WebFOCUS Reporting Server.

Controls which graph engine to use for Server Side Graphics.

Configures graph image files on the Server. This is the default configuration option and is the required option on z/OS. In all other environments, JSCOM3 is the recommended configuration option.

The IBIF_graphservurl parameter has the following form:

&URL_PROTOCOL://machinename/alias/IBIGraphServlet

where:

URL_PROTOCOL is http.

machinename is the name of the Web server where the WebFOCUS Client is installed.

alias is the context root of the WebFOCUS application (usually ibi_apps).

IBIF_graphservurl should not be used when Web Server security is enabled. This includes Basic authentication, IWA, SSL, and third party Security products (such as SiteMinder, Clear Trust, Oblix, Web Seal). In these cases the Web Server security settings can prevent WebFOCUS from creating the graph. IBIF_graphservurl can be used with Basic authentication when the credentials are supplied as shown below:

http:// userid:password@host:port/ibi_apps/IBIGraphServlet

However, this is not recommended because the password is displayed as plain text in the Console and the Web server logs. If Web server security is enabled, JSCOM3 should be used.

For information about using JSCOM3, see the description of the IBI_USE_JSCOM3 variable.

Specifies the number of pre-started agents available for graph processing.

Enables Server Side Graphics when using the WFServlet. This setting is recommended for large graph requests since it spawns new JVM processes for each request.

This setting has been superseded by IBI_USE_ JSCOM3, which is the recommended graph configuration option for the CGI/ISAPI implementation of the WebFOCUS Client. It points to the location of the JRE/JDK installation directory. It is not used by WebFOCUS Servlet.

This setting has been superseded by IBI_USE_ JSCOM3, which is the recommended graph configuration option for the CGI/ISAPI implementation of the WebFOCUS Client. It points to where the Java Virtual Machine (JVM) is located in order to execute Java language-based programs such as Server Side Graphics.

When set to YES, enables the use of JSCOM3. This setting enables the use of Server Site Graphics when the Web Server has security enabled. The CGI/ISAPI implementations of the WebFOCUS Client must use JSCOM3 if amper auto prompting is desired. To use JSCOM3:

• You must blank out the IBIF_graphservurl value (as it takes precedence when it has a value).
• IBI_USE_JSCOM3 must be set to YES.
• A JSCOM3 node must be defined and properly configured in the WebFOCUS Reporting Server ODIN.CFG file (configured by default during installation). The WebFOCUS Reporting Server must also include the following jar file in either the IBI_CLASSPATH or classpath variable:

  ...\ibi\WebFOCUS71\ibi_html\javaassist\IBIGifGraphChart.jar

The IBI_CLASSPATH is configured automatically during installation. However the variable can be maintained either in the WebFOCUS Administration Console or in the Reporting Server Web Console. To set IBI_CLASSPATH in the WebFOCUS Administration Console, go to Special Services under Reporting Servers and modify the JSS node. To set it in the Reporting Server Web Console, Select Listeners & Special Services, then Special Services, then Configured, then JSCOM3.

Used to name each frame in a multi-frame report. The name of each frame will be this value followed by an index number. For example, for two frames with IBIF_mframename set to MYFRAME, the two frames will be named MYFRAME1 and MYFRAME2. MREPORT is the default value.

Specifies the maximum number of columns per page in multi-frame reports. 1 is the default value.

Specifies whether the report frames in a multi-frame report should appear in the order that the columns are specified in the request or the reverse order. Valid values are FORWARD and REVERSE. FORWARD is the default value.

Specifies whether to create an index report, a multi-frame report, or a standard report. Valid values are OFF, INDEX, and FRAME. OFF is the default value.

Specifies up to 50 characters of descriptive text that precedes a sequence number and identifies a report on a TOC. Used to create hyperlink names in index reports. For example, if the value is MyReport, the hyperlinks will be composed of the name MyReport followed by an index number starting with 1. Report is the default value. Do not use this variable if IBIWF_mreports=FRAME.

Is the number of vertically stacked reports when IBIWF_mreports is set to FRAME.

Controls whether a sequence number is appended to the end of the names on the TOC when IBIWF_mreports=INDEX. ON appends a sequence number of 1 (for the first report generated) to n (for the last report generated). This value is the default. OFF omits a sequence number. Only the text specified by IBIWF_mprefix applies.

The OLAP Control Panel is permanently displayed while running an OLAP report when set to YES. NO is the default value.

Location of the OLAP panel (top, bottom).

Enables administrators to preview and set a new color scheme for OLAP components, such as the OLAP Control Panel.

Controls display of On-Demand Paging (ODP) reports.

YES - Displays the report. Yes is the default value.

NO - Does not display the ODP report. Instead, a page with a message displays. You can specify the message text in variable IBIODP_disable_msg. If you do not, a blank line displays.

This variable contains a message, which will be displayed instead of the ODP report output when IBIF_odpenable is set to NO. A blank line is the default value.

Controls the back-button's action in the Web Viewer.

ON - The browser's Back button re-displays the first ODP page.

OFF - The browser's Back button returns the browser to the calling page of the ODP report.

Opening HTML tag for highlighting text found as a result of a search in an ODP report. <u> is the default value, to underline the text.

Closing HTML tag for highlighting text found as a result of a search in an ODP report. </u> is the default value, to underline the text.

Variable for amper auto prompting for self service reporting. Possible values are:

OFF - Turns auto prompting off. This is the default value.

XML - The XML document describing the amper variables is displayed in the browser. This setting is used internally by the WebFOCUS tools and is recommended for debugging purposes only.

XMLRUN - Only prompts for amper variables created with -DEFAULT when there is another amper variable that does not have a value assigned and, therefore, will be prompted for.

XMLPROMPT - Prompts for amper variables created with -DEFAULT and for any other amper variable that does not have a value.

Note: Managed Reporting uses a separate variable setting, which is IBIMR_prompting.

Specifies the location of the XSL document used to transform the XML document that describes the amper variables in the request. This variable replaces IBIF_external_xsl used in earlier releases. If the variable is blank, then the resulting document from the internal transformation is sent to the client.

Specifies the name of the XSL document used to transform the XML document that describes the amper variables in the request. A file extension is not required. This variable replaces IBIF_external_xsl used in earlier releases. If the variable is blank, then the resulting document from the internal transformation is sent to the client.

Specifies the location of the XSL document used to transform a resulting XML report. This variable replaces IBIF_external_xsl used in earlier releases. If the variable is blank, then the resulting document from the internal transformation is sent to the client. This setting is blank by default.

Specifies the name of the XSL document used to transform a resulting XML report. A file extension is not required. This variable replaces IBIF_xsl used in earlier releases. If the variable is blank, then the resulting document from the internal transformation is sent to the client. This setting is blank by default.

Overrides the client path for CGI, ISAPI, or WFServlet for WebFOCUS AUTOSIGNON feature.

Enhances request processing for the WebFOCUS Reporting Server.

Enables the WFServlet to send simple HTML reports to the WebFOCUS Client faster. If the request is being redirected, or if it is a complex ODP or OLAP report or a report with frames, this option should be turned off.

Sets the amount of data (in MBs) that is sent per request. For example, if the file is 6 MBs and the WF_DATATRANSFER_SIZE is 3, two requests are sent, each with half of the data.

If the variable is not specified or is equal or less than 0, no restrictions are enforced. This is used by Developer Studio when sending files to the approot directory.

ReportCaster's Agent Listener node.

ReportCaster's Agent Listener port.

FTP alias that is used to store ReportCaster files.

The type of logon that WebFOCUS Quick Data will use. Reporting Server is the default selection and requires no additional configuration.

If MR is selected and you click the drop-down menu for either the quick_data_domain_desc or quick_data_folder_desc setting, the Managed Reporting Logon opens. To select values for these settings, the Managed Reporting Logon must be validated with the User ID and Password of an MR Administrator who has the authority to see all of the Domains in the MR Repository. Both an MR Domain and Standard Reports folder must be selected in order to save these settings when MR is selected for the WebFOCUS Quick Data logon.

The drop-down menu for this setting enables you to select the MR Domain that contains the Standard Reports folder used for the quick_data_folder_desc setting.

The drop-down menu for this setting enables you to select the top level Standard Reports folder within the selected domain where WebFOCUS Quick Data SAFs (Structured Ad hoc Forms) can be stored. (An SAF contains a report procedure that is tied to a data source and enables users to select from a series of parameters to create a data set that can be analyzed using WebFOCUS Quick Data.)

The Use guided ad hoc forms only check box is enabled for this setting when you select MR for the quick_data_security setting and specify a Domain for the quick_data_domain_desc setting to specify the location of Quick Data SAFs (Structured Ad hoc Forms). Selecting the check box restricts users from creating SAFs with ad hoc reporting tools, for example, Report Assistant. The default value for this setting (in the cgivars.wfs file) is NO and is set to YES when the check box is selected.

Authorization              Basic amx0XHdmdXNlcjp3ZnVzZXIx

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

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's 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's operating system and the Reporting Server cannot run on Windows. In this scenario, the connecting user appears in the server's edaprint.log and is returned by the server's 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's trust_ext setting is enabled.

In this configuration the connecting user appears in the server's edaprint.log and is returned by the server's CNCTUSR subroutine. The server's 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.

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

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's edaprint.log and CNCTUSR subroutine will reflect the connecting user ID, and the server's GETUSER subroutine shows the user ID that started the server.

Trusted connections are not supported against servers running in security DBMS mode.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 following addtional settings are displayed:

Default WebFOCUS Reporting Server user ID. Only used when a user ID (IBIC_user) is not supplied.

Default WebFOCUS Reporting Server password. Only used when a user password (IBIC_pass) is not supplied.

Default WebFOCUS Reporting Server. Only used when a server (IBIC_server) is not supplied.

Controls whether to pass a DBA password to the WebFOCUS Reporting Server on each WebFOCUS request.

Is the user ID that the MR Realm Driver uses to connect to ReportCaster during Managed Reporting sign-on. This setting is used only when the MR Realm Driver is configured for external authorization and allows it to create (and update) the Managed Reporting user's privileges in the ReportCaster Repository. The ID specified must have rcadmin privileges. Typically, this value is set to the same ID stored in the ReportCaster Server Configuration Tool under General > User Info > Administrator. By default, the value is admin.

Reserved for future password expiration feedback support when using the MR Realm Driver. OFF is the default setting.

Servlet initialization parameter that controls which HTML parser Managed Reporting uses against the basedir directory. This setting was previously located in the \WEB-INF\web.xml file.

Information Builders recommends using the default value, as there is a 50% performance improvement.

Location where all Managed Reporting published pages will reside.

Location where all Managed Reporting templates will reside.

When enabled, this setting significantly improves Managed Reporting performance and scalability. However, this setting only applies to installations where the Authorization setting in the MR Security Settings - General window of the console is set to Internal.

REPOSITORY_CACHE=ON tells WebFOCUS to cache information about Managed Reporting users, groups, roles, and Domain content. Information is always read from cache unless WebFOCUS detects that the date-time stamp of the files that contain this data has changed. The date-time stamp feature supports scenarios where a cluster of application servers is sharing a single Managed Reporting Repository. User My Report information is also cached. This setting is turned ON by default.

When set to a numeric setting, WebFOCUS caches information about Managed Reporting Domain content. For example, a setting of 10 caches information about the last 10 domains the WebFOCUS processed. This setting is disabled (set to 0) by default. This setting only applies to installations where the Authorization setting in the MR Security Settings - General window of the console is set to Internal.

When set to a numeric setting, WebFOCUS caches information about Managed Reporting user resources such as information about My Reports and Deferred Receipt tickets. For example, a setting of 50 caches resource information for the last 50 users who have signed-on to WebFOCUS. This setting is disabled (set to 0) by default. This setting only applies to installations where the Authorization setting in the MR Security Settings - General window of the console is set to Internal.

In previous releases, when WebFOCUS was configured to use the CGI/ISAPI client, deferred output saved to a user's My Reports folder in the Managed Reporting Repository was written in a format that was incompatible with the WebFOCUS Servlet (WFServlet). This meant that if you upgraded to WebFOCUS Version 7 Release 1, which required the WFServlet configuration for Managed Reporting, you could not access your saved deferred output. The WFServlet now detects and reads the legacy output format, while continuing to read and write with the newer format.

The WF_CGI_ENDIANNESS setting is used by WFServlet to determine the byte order of the deferred output. If your legacy saved deferred output was created on a platform with a little-endian byte order, such as Intel x86, you should keep the default setting of LITTLE. If the output was created on a big-endian platform such as IBM S/390, z/Series, and some UNIX and Linux systems, you should change the setting to BIG. Some platforms can be configured either way so consult with your administrator or experiment if you are unsure of the proper setting for your environment.

Because WFServlet runs on Java technology, which is always big-endian, new deferred output will always be written in big-endian format. WF_CGI_ENDIANNESS is therefore used by WFServlet only to know which way to read legacy saved deferred output created by the WebFOCUS CGI/ISAPI Client.

Enables parameter prompting for all Managed Reporting requests. Possible values are:

Contains the URL of the .xsl file that styles the XML document returned from the Reporting Server when IBIMR_prompting is set to XMLRUN or XMLPROMPT.

Location of the Managed Reporting Repository.

This setting controls the security processing behavior of two different kinds of Managed Reporting requests:

• Launch pages created outside of Managed Reporting by the Managed Reporting Publish feature.
• Drill-down requests created by tools that reference a child report in a different Managed Reporting domain than the parent report.

When set to YES, a launch page can run a Managed Reporting report even though the user is not logged on to Managed Reporting. Additionally, a user who is logged on to Managed Reporting can run a drill-down request even when the child report is in a Managed Reporting domain that they do not have access to. If this behavior is a security concern, change the setting to NO.

When set to NO, Managed Reporting domain security is strictly enforced. The behavior for launch pages and drill-down requests is slightly different. If a user who is not logged on submits a Managed Reporting request from a launch page, they will receive an error message or be presented with the Managed Reporting logon page, depending on the value of MR_AUTOSIGNON. If a user who is logged on runs a drill-down request to a child report in a Managed Reporting domain that they do not have access to, they will receive an error message.

Note: This setting supersedes the <set> IBIMR_drill(protect) statement.The protect statement should no longer be used since it disables drill-down reporting, in addition to closing the publish security issue.

When set to YES, in conjunction with MR_ANONYMOUS_RUN_ACCESS=NO, when a user who is not logged on submits a request from a published launch page, they will be presented with the Managed Reporting logon page. After their credentials are successfully validated, the report will be run automatically and they will remain logged on to Managed Reporting. In scenarios where single sign-on is configured (for example SiteMinder integration) the user will be logged on to Managed Reporting transparently.

The setting is only valid for HTTP requests, which means it is not supported with Managed Reporting API and Web Service requests.