Application Settings determine the configuration and behavior of the WebFOCUS web application.
The settings appear in the main configuration pane.
The Application Contexts Settings define the context root locations of various WebFOCUS components.
Specifies the context root for the local online Help web application.
The default value is /ibi_help. It is established during the WebFOCUS installation, and identifies the context root to which the local online Help web application is assigned, by default.
To assign the local online Help web application to the WebFOCUS context root, replace the default value with a new value that begins with the WebFOCUS Context, and is followed by the Help Context. For example, /ibi_apps/ibi_help.
To assign the online Help web application to any other context root, replace the default value with a new value that identifies the context root in use in your organization.
The context root defined in this setting only applies to the local host. If the Help Proxy Host and Port (IBI_HELP_PROXY_HOST) setting identifies an external sever name and port, you must also identify the context root for that external server in the Help Proxy Context (IBI_HELP_PROXY_CONTEXT) setting.
Specifies the name and port number of the external server where a remote online Help web application is installed.
If this setting is blank, no remote online Help web application is available. This is the default value.
If this setting contains a server name and port number, a remote online Help web application is available on the server name and port specified. The remote application does not need to be on the same server as the WebFOCUS web application.
When you specify a value in this setting, you must also specify a value in the Help Proxy Context (IBI_HELP_PROXY_CONTEXT) setting. It cannot remain blank.
When you identify a remote online Help web application by assigning values to these two settings, the Help Servlet acts as a proxy, and directs Help system calls to the host identified in this setting. The term Help Proxy indicates that the values in the settings that include it apply to a remote online Help web application.
Specifies the context root of the remote online Help web application in the target environment identified in the Help Proxy Host and Port (IBI_HELP_PROXY_HOST) setting.
This setting must remain blank if no remote online Help web application is identified in the Help Proxy Host and Port (IBI_HELP_PROXY_HOST) setting. When this setting is blank, no context root is identified for the remote online Help web application. This is the default value.
This setting must identify a context root if a remote online Help web application is identified in the Help Proxy Host and Port (IBI_HELP_PROXY_HOST) setting.
If selected, this check box activates the use of Secure Sockets Layer (SSL) security on all calls directed from the WebFOCUS client to the remote online Help web application located on the remote host identified in the Help Proxy Host and Port (IBI_HELP_PROXY_HOST) setting.
If cleared, calls to the remote online Help web application, do not use SSL security or encryption. This is the default value.
Note: This setting does not affect calls from WebFOCUS or any other Information Builders application to Help systems located on a local server. All customer-facing applications are SSL-enabled, by default, in compliance with the security policy of Information Builders. However, if the WebFOCUS Client is configured to access a Help system on a local intranet server, this setting should be selected if the Help system on that intranet server is also configured to use SSL.
Specifies the context root for ReportCaster content, previously /raster by default. The current default value is /ibi_apps.
Specifies the context root for the WebFOCUS servlet, previously /ibi_apps by default. The current default value is /ibi_apps/WFServlet.ibfs.
Specifies the context root for WebFOCUS web applications. The default value is /ibi_apps.
The Application Directories Settings define the directories in which various files are located.
Specifies the location of the Application Namespace root directory used by the WebFOCUS installation. The default location is drive D:/455/ibi/apps, unless a different directory was specified during installation.
Specifies the location of the directory from which the Change Management Import Package will imported. The default location is drive:/ibi/WebFOCUS82/cm/import, unless a different directory was specified during installation.
Specifies the location of the directory where the Change Management Export Package will be placed. The default location is drive:/ibi/WebFOCUS82/cm/export, unless a different directory was specified during installation.
Specifies the location of the directory where files will be transferred during source control operations, such as adding files to source control, checking files in, or checking files out of the source control repository. The default location is drive:/ibi/WebFOCUS82/scm.
This location can be customized. The directory path needs to be on the same machine where WebFOCUS is installed and a UNC path is currently not supported.
Specifies the location of temporary files when running a request. For example, redirected requests are written to this location. The default location is drive:/ibi/WebFOCUS82/temp, unless a different directory was specified during installation.
Specifies the number of days the files in the logs directory will be retained. The default value is 10 days.
Specifies the location of the directory used for client traces displayed in the Session Monitor and the Session Viewer. The default location is drive:/ibi/WebFOCUS82/traces, unless a different directory was specified during installation.
WebFOCUS directs all diagnostic output to the logs directory. The default location is drive:/ibi/WebFOCUS82/logs, specified with log4j.xml during installation.
Specifies the number of days the files in the traces directory will be retained. The default value is 10 days.
Specifies the names of a series of IBFS Nodes and the network locations of their corresponding file directories. ReportCaster can use these nodes and directories as destinations for report deliveries when using Repository Distribution.
In WebFOCUS, nodes defined in this setting appear as folders in the Resources tree when using the Full View mode. In ReportCaster, users who are authorized to use Repository Distribution can see these nodes in the Browse for Folder dialog box that opens from the Distribution dialog box of the Basic and Advanced Scheduling Tools.
Entries take the form:
Is the name of a File System Distribution node. When the Resources tree is displayed in Full View mode, this node appears as a folder on the Resources tree, under the WebFOCUS node, in the File folder. In ReportCaster, this node appears as a folder in the Browse for Folder dialog box that opens from the Distribution dialog box of the Basic and Advanced Scheduling Tools.
Is the path to the network location of the file directory that corresponds to the node that appears on the Resources tree in WebFOCUS and in the Browse for Folder dialog box in ReportCaster. The Distribution Server must be able to write files to the location defined by this path.
The format of a path assigned to this value must conform to the requirements of the operating system used by the Distribution Server or to the requirements of the Universal Naming Convention (UNC). For example, D:\455\ibi\apps, on a Microsoft Windows-based Distribution Server, /bigscm/455/ibi/apps on a Unix-based Distribution Server, or \\bigscm\455\ibi\apps if using the Universal Naming Convention.
If a path uses a format that is accessible to the Application Server as well, full details of the results of the file distribution will be available for review from the Application Server.
BI Portal Settings configure the display and behavior of the BI Portal.
Determines whether WebFOCUS supports basic portals.
Basic portals deliver the full range of reporting, charting, and other features, and are managed from the Portals node.
When this check box is selected (True), the Portals node appears under the Resources tree, and users can create, edit, and run basic portals. This is the default setting.
When this check box is cleared, (False), the Portals node does not appear under the Resources tree, and users are unable to create or edit basic portals. However, because data from previously-created basic portals remains in the repository, users can run a previously-created portal by typing the URL for it directly into the browser address bar. Users can also continue to import change management packages that contain basic portals.
Establishes the default layout for new pages in the BI Portal. This layout determines the way in which items, such as reports or charts, are organized on the page. Fluid Canvas, the default value, automatically arranges content evenly and redistributes space as you add more items. The other option, Single Area, does not establish a grid, and allows you to place items where necessary.
This setting is relevant only to basic portals. It is not relevant to collaborative portals.
Determines whether WebFOCUS supports collaborative portals, which are also identified as V4 portals.
Collaborative portals deliver the full range of features offered by a basic portal, such as reporting and charting. They also include responsive-design page templates, the ability to create and maintain independent pages, and the ability to create and maintain blogs, which are interactive messaging components that can be assigned to portals and pages.
When this check box is selected (True), Collaborative Portal, Page, and Blog commands appear in the domain folder shortcut menu. Users can create, edit, and run collaborative portals. Basic Portals remain available in their original format, but may not retain their full functionality. This is the default setting. To display the Portals node in the Resources tree, the Basic Portal (IBI_V3_PORTAL) check box must also be selected.
When this check box is cleared (False), Collaborative Portal, Page, and Blog commands do not appear in the domain folder shortcut menu. Users are no longer able to create, edit, or run collaborative portals, pages, or blogs. Previously-created collaborative portals, pages, and blogs no longer appear in the domain folder to which they were assigned. Data from previously-created collaborative portals, pages, and blogs remains in the repository, but users are unable to run a previously-created collaborative portal by typing the URL for it directly into the browser address bar. Users can also continue to import change management packages that contain collaborative portals, pages, and blogs, but they will not be visible in the folders to which they are assigned after the import.
Determines whether the first domain listed in the Resources tree opens automatically when you open the BI Portal. If this check box is selected (True), the first domain opens automatically when you open the BI Portal. If this check box is cleared (False), the first domain remains closed when you open the BI Portal. This check box is cleared, by default.
Specifies the type of files that you can upload to the BI Portal. Files that do not use one of the extensions listed in this setting cannot be uploaded to the BI Portal. The list includes the following file extensions, by default:
.png, .ppt, .pptx, .sty, .svg, .txt, .xls, .xlsx, .xml
Specifies whether confirmation will be requested when a user moves a folder by drag and drop. The default value is True (selected).
Determines when users receive simplified error messages. In simplified error messages, error details can be suppressed to avoid disclosing sensitive or technical information to end users. When a simplified error message is delivered to a user, the fully detailed error message appears in the event.log to support administrator troubleshooting. Error messages in the event.log are preceded by an identifier in the form IBFS-YYMMDD_hhmmss-n, where n is the sequence number for multiple messages generated during the same second.
The simplified error message displayed to the user contains the event.log entry identifier.
Each option in the Message Detail list specifies the highest error level for which end users will receive detailed messages. The options are:
Administrators can customize the styling of a simplified error message by creating and editing the custom template on which it is based. To create a custom error message template, copy the webfocus_ibfs_error.xml file from the prod directory to the custom directory. Both the prod and the custom directories are found in the drive:\ibi\WebFOCUS82\client\wfc\etc\ directory. Make all edits to the copy of the webfocus_ibfs_error.xml file found in the custom directory.
Note: Users with the Display Administration Console (opWFAdminConsole) or Desktop Connect (opDTConnect) privilege always receive the detailed error messages.
Specifies a custom message that displays in the Messages dialog box when a user signs in. You can enter plain text or HTML tags for text, links, and images, into this field. If you leave this field blank, the Messages dialog box does not display.
The following HTML tags may be used in the sign-in message: <l>, <br>, <b>, <u>, <a href>, </a>, <img>.
Enables the display of a custom sign-in page for users. The default value is False.
Specifies the default portal to appear when a user signs in, in the format /bip/portal/xyz, where xyz is the name of the portal.
Specifies the URL used to access Mobile Favorites. If left blank, the default Mobile Favorites is used.
Defines how deeply under the IBFS:/WFC/Repository subsystem WebFOCUS searches for session privileges during user sign in. If you wish to check for session privileges only on the domain folder, for example, IBFS:/WFC/Repository/Sales, use the default search depth, 1. To search for session privileges on subfolders directly beneath the domain folder, use a search depth of 2.
Note: Search depth may be set to any level, but increasing the depth may cause performance issues. It is strongly advised that you make the search depth value as low as possible.
Controls the session timeout value, which limits the amount of time users can remain idle before a session timeout takes place. This setting is defined in minutes, for example, IBI_Session_Timeout=120.
The Change Management Settings determine which files are exported during the change management process, the format of the exported file, and whether some legacy functionality is preserved.
Determines, by file extension, which files from the WebFOCUS Reporting Server or the web will be included in exports created by the change management feature. The values included by default are acx, bmp, css, fex, gif, htm, html, ico, jpe, jpeg, jpg, js, mas, mnt, png, sty, and svg.
When selected (True), the export package contains the original hrefs. The original hrefs are needed when using change management to move content that has been migrated from WebFOCUS 7, or ReportCaster schedules, from one WebFOCUS 8 environment to another WebFOCUS 8 environment. This setting ensures that the -INCLUDEs and drill downs in code migrated from WebFOCUS 7 continue to work, and ReportCaster schedules, which reference FOCEXECs by handle, continue to work. The default value is False (cleared).
When selected (True), the export package is compressed and delivered in a zip file.
Select an option from the drop-down menu to specify the name format of the zip file.
When selected (True), the export package is flagged for signature verification, which ensures both that the code has not been tampered with and that the signature was produced with the expected key.
The Client Settings configure miscellaneous Client options.
The following syntax enables you to include code to be executed on the WebFOCUS Reporting Server by the Client.
Is any valid Reporting Server syntax. The site profile is not processed during a Reporting Server sign in, or when a procedure scheduled in ReportCaster is run. It is only processed when procedures are run on the Reporting Server.
The site profile can also be added directly to the drive:\ibi\WebFOCUS82\client\wfc\etc\site.wfs file.
The following syntax enables you to include code to be executed by the Client and the ReportCaster Distribution Server. This differs from the _site_profile, which is only executed by a Client request.
Is any valid Reporting Server syntax.
A _universal_profile should not include any logic or constructs that will execute only on the Client. For example, http header variables should not be included, because they are available to the Client, but not to the ReportCaster Distribution Server.
The universal profile can also be added directly to the drive:\ibi\WebFOCUS82\client\wfc\etc\site.wfs file.
Deletes files from the temporary directory. Files are deleted if they are older than the number of seconds specified. The default value is 900 seconds.
This setting is only applicable 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).
Turns on the persistent ampersand (&&) feature. By default, this is set to Yes. To disable, set to No. The persistent ampersand feature allows you to persist && variables for the duration of the browser session.
With the Dynamic Language Switch feature, the default user interface language for a session is based on the language of the browser, or by setting the IBIWF_language=nn parameter in the URL (where nn is the ISO language abbreviation).
The client uses this default setting to control the display language when the browser language of the user is not one of the available options from the Select Language drop-down list during sign in, 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.
Globally sets redirection on or off. Possible values are:
Controls how many Reporting Server message lines 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. The default value is 20000 lines. The IBIF_max_messages setting can be passed with the request, in which case it overrides the value set in the Console. When debug mode is enabled in App Studio, a value of 50000 is passed with each request. A value of 0 indicates that no limit exists.
Defines the maximum size, in bytes, allowed for responses in the original window when using Internet Explorer.
Responses larger than the size identified in this setting will be launched in a new window, to ensure that it will open without errors. If this setting is blank, no maximum limit is applied. The default value is 400,000 bytes.
Identifies the location of the resource that WebFOCUS uses to render output in the Excel 2007 file (.xlsx) format.
The Excel Server URL drop-down list contains two options:
Determines the version number of the Google Maps™ API. Can be an integer or decimal value. An integer value represents a stable version. Currently, only Google Maps API v3 is supported.
Google API v3 does not require an API key. Therefore, this field must remain blank.
Determines the version number of the Bing Maps™ API. Can be an integer or decimal value. An integer value represents a stable version. Currently, only API Version 7 is supported.
Provides access to the Bing Maps API. The key is an 80+ character string that is copied from the Bing site and pasted into this field. The key enables Bing Maps to be embedded in customized HTML pages. To obtain a Bing Maps API key, go to:
Identifies the location of the resource that WebFOCUS uses to render output in graph image file format.
This option is required on z/OS. In all other environments, JSCOM3 is the recommended configuration option.
Note: If your WebFOCUS configuration must use a different resource, contact the Customer Support Service Team to obtain assistance.
Specifies the number of prestarted agents available for graph processing. The default value is 10 agents.
Controls whether to pass a DBA password to the Reporting Server on each request.
Permitted values are:
Is a fully qualified Java class that does the transin and transout processing (processing of a request to and output returned by the WebFOCUS Reporting Server) for a plug-in for the Servlet version of the 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 versus right/left strings).
Specifies the qualified name of a plug-in class to be invoked by the WebFOCUS Servlet. By default, this variable is set to ibi.webfoc.WFEXTDefault, which is the default plug-in supplied with WebFOCUS that contains several useful functions.
Determines if master files retrieved from the WebFOCUS Reporting Server include the master file title and suffix, or not. From the drop-down menu select:
Deferred Reporting Settings determine how deferred reports are processed.
When this check box is selected, the default setting, users are prompted to optionally customize the description for the deferred report, which defaults to the title of the report being run deferred. This occurs whenever the description defined in the parameter (IBIMR_defer_description) has not been submitted with the run deferred report request.
When this check box is clear, the title of the report being submitted to run deferred is assigned to the deferred report description automatically, and no prompt appears.
When this check box is selected, the default setting, the Deferred Request Submitted window displays to confirm a successful deferred request. The user clicks OK to close the window.
When this check box is clear, the Deferred Request Submitted window does not display.
Activates an automated message that prompts the user to confirm the deletion of a deferred report. When this check box is selected, which is the default, a message prompts the user to confirm the deletion, so a deletion requires two clicks. When this check box is clear, the user is not prompted to confirm the deletion, so a deletion requires only one click. Making a large number of deletions is faster when suppressing the confirmation message.
Encryption Settings determine the encryption provider and encryption and token key locations.
Specifies the encryption provider used. Supported options are:
ibi.webfoc.wfsecurity.encryption.wireaes.WFWireAES128. AES 128 Encryption with Internal Key. This is the default value.
ibi.webfoc.wfsecurity.encryption.wireaes.WFWireAES128KeyFile. AES 128 Encryption with External Key.
ibi.webfoc.wfsecurity.encryption.wireaes.WFWireAES192. AES 192 Encryption with Internal Key.
ibi.webfoc.wfsecurity.encryption.wireaes.WFWireAES192KeyFile. AES 192 Encryption with External Key.
ibi.webfoc.wfsecurity.encryption.wireaes.WFWireAES256. AES 256 Encryption with Internal Key.
ibi.webfoc.wfsecurity.encryption.wireaes.WFWireAES256KeyFile. AES 256 Encryption with External Key.
If the keyfile is specified, the IBI_Encryption_Key_Location setting must be set to the keyfile. Otherwise, WebFOCUS will use an internal key.
Specifies the value of the security token that allows trusted communication between the Client and other independent or third-party software. This token is a hexadecimal (HEX) string value that is used to perform 128-bit encryption.
The token must be specified in both WebFOCUS and the other software.
The ESRI Settings page defines the connection to the local application that supports Esri-based maps.
For more information about how to configure Esri On Premise for InfoAssist+, see the Configuring an Esri On Premise Environment topic in the WebFOCUS InfoAssist+ User’s Manual.
For more information about how to configure Esri On Premise for App Studio, see the Installing and Configuring Esri on Premise topic in the WebFOCUS App Studio User's Manual.
The Filters Settings enable protections against common web security vulnerabilities.
Requires all POST requests to provide a cross-site request forgery (CSRF) security token to be validated, except for legacy requests, if the exception is allowed by the IBI_CSRF_Allow_Legacy setting. The check box is cleared (False) by default.
Specifies the name of the cross-site request forgery (CSRF) security token. The default value is IBIWF_SES_AUTH_TOKEN.
When selected (True). the default setting, this check box allows legacy WFServlet requests to run without requiring or using a cross-site request forgery (CSRF) security token.
When selected (True), this check box specifies that RESTful Web Services functions which create, update, or delete can only be run with the HTTP POST method.
Note: If the IBI_CSRF_ENFORCE setting is set to True, then RESTful Web Services also require a CSRF token. The token name is specified with the IBI_CSRF_Token_Name setting.
When this check box is selected (True), the default value, this setting adds the cache-control response header and the expires response header to static files that use the *.htm, *.html, bindowsBundle.jsp, *.css, *.gif, *.png, *.jpeg, *.jpg, *.txt, *.htc, and CombineImageServlet format.
You can modify the cache-control response header with the Cache Control Header (IBI_HTTP_Response_Header_Cache_Control) setting. You can modify the expires response header with the Expires Header (IBI_HTTP_Response_Header_Expires) setting. However, you must consult Customer Support Services for assistance before altering this setting or either of these other settings.
Specifies the default cache control response for static content accessed by the web application. The default value is public, max-age=2592000 (30 days). Consult Customer Support Services for assistance before altering this setting.
Specifies the default expiration response header for static content served by the web application. The default value is 2592000 (30 days). Consult Customer Support Services for assistance before altering this setting.
Specifies whether the Microsoft Internet Explorer cross-site scripting (XSS) filter is enabled or disabled. Valid options are:
Enables the browser XSS filter by returning an HTTP response header of:
Disables the browser XSS filter by returning an HTTP response header of:
This is the default value.
Does not return an HTTP response header to the browser. The browser relies on its default XSS filter settings for the browser security zone.
The IBI_XSS_Protection setting works in conjunction with the IBI_XSS_Mode_Block setting.
Note: Because application development requires HTTP requests to use characters that can be misinterpreted as a cross-site scripting attack, this filter must be disabled in a development environment. You can set IBI_XSS_Protection to False (the default value) or Off. If IBI_XSS_Protection is off, the browser security settings will determine if Internet Explorer invokes its cross-site scripting protection. This is required only for development purposes. If you maintain a separate production environment, you may set IBI_XSS_Protection to True in that installation.
If the Microsoft Internet Explorer cross-site scripting filter is enabled in the IBI_XSS_Protection setting, this specifies the response the browser makes to a cross-site scripting attack. Permitted values are:
If the IBI_XSS_Mode_Block setting is False, the following is returned:
Internet Explorer will attempt to make minor corrections to the webpage if it detects a cross-site scripting attack.
If the IBI_XSS_Mode_Block setting is True, the following is returned:
X-XSS-Protection: 1; mode=block
Internet Explorer will not render the webpage at all if it detects a cross-site scripting attack.
Defines the maximum size for data files uploaded to the Repository or the EDA Server. Data files that are larger than the value in this setting cannot be uploaded. The default value is 2048 megabytes. The maximum allowable value is 10240 megabytes. A value of -1 deactivates this setting.
Defines the maximum amount of memory that data from files uploaded to the Repository or the EDA Server can occupy. During the upload process, data moves into memory until it reaches the limit defined in this setting. Any additional data is temporarily cached to disk. The default value is 256 megabytes. A value of -1 deactivates caching.
The Magnify Search Settings configure Magnify Search.
Specifies the full path to the directory where the configuration files are located.
Note: If your installation needs to make changes to the configuration directory, you should move this directory outside of the ibi directory. This ensures that future WebFOCUS upgrades do not overwrite your configuration information.
The default location is drive:/ibi/WebFOCUS82/config/magnify.
Specifies the full path to the directory where the default Lucene™ index resides. This is active only for the Lucene search engine.
The default location is drive:/ibi/WebFOCUS82/magnify/lucene4_index.
Additional search directories are configured in config/magnify/collections.xml.
Specifies the directory where Magnify Search stores records that are not yet loaded into the index. After all content is added to the Lucene index, the cached version is moved or deleted depending on the magnify_generate_deltas variable value of true or false. An index during a quiesce is loaded after the backup of the Lucene index is complete.
The default location is drive:/ibi/WebFOCUS82/magnify/feedcache.
Specifies the file name where the Lucene™ indexes and collections are defined. The default value is collections.xml. However, by default, this file does not exist. Instead, the Magnify Search installation provides a collections.xml template file in the drive:/ibi/WebFOCUS82/config/magnify directory, which defines default values for analyzers. This file can be renamed as collections.xml and modified to reflect the desired settings for your Magnify Search environment.
Specifies the maximum number of search results returned by a search request. Any results beyond this number are not displayed to the user. The default value is 300 results.
If an HTTP cookie name is specified, Magnify Search verifies that the cookie is set. If the required cookie does not exist, Magnify Search displays the webpage specified by the IBI_Magnify_Required_Cookie_Redirect setting. If the IBI_Magnify_Required_Cookie setting is blank (the default value), Magnify Search does not verify cookies.
Specifies the webpage that Magnify Search displays if the HTTP cookie specified by the IBI_Magnify_Required_Cookie setting does not exist in the browser session of the user.
The Multiple Reports Settings configure options for multi-frame reports.
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 IBWIF_mframename set to MYFRAME, the two frames will be named MYFRAME1 and MYFRAME2. The default value is MREPORT.
Specifies the maximum number of columns per page in multi-frame reports. The default value is 1 column.
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. Possible values are FORWARD and REVERSE. The default value is FORWARD.
Specifies whether to create an index report, a multi-frame report, or a standard report. Possible values are OFF, INDEX, and FRAME. The default value is Off.
Specifies up to 50 characters of descriptive text that precedes a sequence number and identifies a report in 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. The default value is Report.
Note: Do not use this setting if IBIWF_mreports is set to FRAME.
Is the number of vertically stacked reports when the IBIWF_mreports setting is 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). Off omits a sequence number. Only the text specified by the IBIWF_mprefix setting applies. The default value is On.
The On-Demand Paging Settings configure On-Demand Paging options.
Controls display of On-Demand Paging (ODP) reports.
Yes. Displays the report. This 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 the IBIODP_disable_msg setting. If you do not, a blank line displays.
This setting contains the message that will be displayed instead of the ODP report output when IBIF_odpenable is set to No. The default value is a blank line (\n).
Controls the action of the back button in the Web Viewer.
HTML tag for highlighting text found as a result of a search in an ODP report. The default value is <u>, to underline the text.
The OLAP settings configure OLAP options.
These settings are visible only if the Enable OLAP check box is selected. The Enable OLAP check box appears on the Other Settings page of the Administration Console Configuration tab.
When the check box is selected, the OLAP Control Panel is permanently displayed while running an OLAP report.
Specifies whether to display the OLAP Save the data in an Excel fie option. This check box is selected by default.
Specifies whether to display the OLAP Save the data in an Excel 2000 file option. This check box is selected by default.
Specifies whether to display the OLAP Save the data in an Excel 2000 file with formulas option. This check box is selected by default.
Specifies the location of the OLAP panel. Possible values are TOP and BOTTOM. The default value is BOTTOM.
Enables administrators to create a name to preview and set a new color scheme for OLAP components, such as the OLAP Control Panel. The default value is NEUTRAL.
Enables administrators to preview and set a new color scheme for OLAP components, such as the OLAP Control Panel. The default value is NEUTRAL.
The Other Settings determine miscellaneous configuration settings.
Specifies the email server used to email Mobile Favorites links.
For migrated environments, enables the Default Role tab in the Security Center. This check box is cleared, by default.
Enables OLAP settings and functionality. When this check box is selected, OLAP functionality appears in the following locations:
Note: In the Properties dialog boxes of Portals and Domains, this check box appears dimmed and is unavailable. In the Properties dialog boxes of reports, charts, and visualizations, this check box is fully visible and available.
This setting does not activate the use of OLAP within App Studio. To do so, open App Studio, and select the Enable OLAP check box on the Reporting tab of the App Studio Options dialog box. For more information, see the Setting User Preferences Using the Options Dialog Box topic in the WebFOCUS App Studio User's Manual.
This check box is cleared, by default.
Enables a page for testing HTTP requests and for testing RESTful web services. This check box is cleared, by default. You may wish to disable this page in a production environment.
The URLs for the HTTP request test page are:
Contains one or more FOCUS error message numbers separated by commas. If one of these FOCUS error numbers are encountered during schedule execution, ReportCaster will process it as a warning rather than an error. This means that if a report is produced, it will be distributed in spite of the FOCUS error number, and that this FOCUS error number will not trigger an error notification if the schedule is configured to notify on error.
Determines whether double-clicking a library item opens the latest version of the report (Last) or a list of report versions (Versions). The default value is Last. The value you specify here appears first in the shortcut menu when you right-click a library item and click View.
Uploads Repository images to the reporting server for embedding in reports and HTML pages. This check box is selected by default.
Activates automatic indexing of report and chart parameters. If this check box is selected (TRUE), when users save reports or charts, WebFOCUS automatically indexes the parameters on which they are based, making information about these parameters immediately searchable, and delivering more timely and comprehensive search results.
This check box is cleared (FALSE), by default.
Lists all procedures that run when users sign in to a portal or to web services. By default, this setting is blank, and no procedures run in response to user sign in. To configure a list of procedures, type the path name for each of them in this setting, and separate each path name with a comma, as shown in the following example.
The procedures you include in this setting can serve a variety of purposes. For example, you can use this setting to run a procedure that sends a message of the day to users upon sign in, using the syntax shown in the following example of the message of the day file, motd.fex.
-IF &FOCSECUSER EQ admin GOTO ADMINMSG; -TYPE <UserMsg>Hello normal user</UserMsg> -GOTO DONE; -ADMINMSG -TYPE <UserMsg>Hello admin</UserMsg> -DONE
You could also use this setting to run a procedure that initializes the environment and establishes a procedure within the repository that creates a single foccache ticket that can be used for all subsequent requests, as shown in the following example.
TABLE FILE IBISAMP/CAR PRINT COUNTRY IF RECORDLIMIT EQ 1 ON TABLE HOLD AS FOCCACHE/LATCH END
This procedure cannot produce any report output.
Establishes the default trace level for WebFOCUS Sessions. The session trace level assigned to this setting appears by default in the Tracing Level list fields on the main page of the Session Viewer. Trace levels identify the level of events captured in a trace file. They range from Basic, which only captures traces of high level events, to Server, which captures traces of all events. Administrators can override this default value for individual sessions. Definitions of each trace level appear in the topic Reviewing the Session Viewer Main Page. By default, this value is set to Off, meaning that no traces are captured.
Establishes the default level of echo traces and SQL Traces captured from the execution of FEX file commands. In a FEX file, the &ECHO variable displays command lines as they execute, in order to test and debug procedures. The level of traces captured from all SQL request and response events. This value is set to Echo On, SQL On, by default, activating both Echo and SQL tracing for an FEX file. Administrators can override this value with any of the other setting combinations identified in the list.
Activates the use of Custom Strings in global items such as menu bar options, error messages, or other features. When this check box is selected, WebFOCUS can access custom strings defined in the custom template file that is identified in the Custom Strings setting.
Note: Consult Customer Support Services before modifying this setting.
The name of the file that contains text strings used to customize labels for global items, such as menu bar options, error messages, and other features.
Note: Consult Customer Support Services before modifying this setting.
Displays detailed error messages in the SOAP xml response. This check box is selected, by default. If cleared, this setting suppresses details that administrators may not want to disclose to the end user.
Type WF_USER in this field to send this cookie back to the browser. This allows the WFSIGNON action when authenticating with the WebFOCUS Reporting Server.
Identifies the type of files that cannot be uploaded to the Reporting Server. Files types are identified by their extension. For example, .pdf. Files that use one of the extensions listed in this setting cannot be uploaded to the Reporting Server. This setting is blank, by default, enabling you to upload any type of file to the Reporting Server.
Identifies the name of the theme assigned to InfoAssist+ and Business Intelligence Portal designer tools. This value is blank, by default, meaning that the default theme behavior is in effect for these tools. The other value, BIPNeutral, sets the default theme for these designer tools to a more modern and neutral appearance.
The Parameter Prompting Settings determine parameter prompting behavior in the WebFOCUS Client.
Enables or disables parameter prompting for all Managed Reporting requests. Possible values are:
Enables or disables parameter prompting for Managed Reporting procedures (FEXes) when Managed Reporting (IBIMR_PROMPTING) is set to Always Prompt (XMLPROMPT) or Run with Default Values (XMLRUN), and the Prompt for Parameters check box is unselected in the FEX Properties dialog box. Possible values are:
Enables or disables amper auto prompting for self-service reporting. Possible values are:
Note: Managed Reporting uses a separate variable setting, which is IBIMR_PROMPTING.
Specifies the template that defines the layout of the autoprompt interface.
Specifies the value (_FOC_NULL or FOC_NONE) that the client assigns (in a -SET command) to the amper variable when the dynamic multi-select list No Selection value is selected. The default value is _FOC_NULL.
The Quick Data Settings determine how Quick Data performs authentication.
Specifies the type of sign in used by WebFOCUS Quick Data. Permitted values are Reporting Server and Managed Reporting. The default value is Reporting Server and requires no additional configuration.
Applies when MR authentication is selected for the IBI_Quick_Data_Security setting. Permitted values are
The Repository Settings specify the authentication credentials that the JDBC driver uses to access the WebFOCUS Repository.
Specifies the Java Database Connectivity API (JDBC) driver used to access the Repository.
The value in this setting is not available for updates. If you must change the default value assigned to this setting, contact the Customer Services Support team.
Specifies the URL used by the JDBC driver to access the Repository.
The value in this setting is not available for updates. If you must change the default value assigned to this setting, contact the Customer Services Support team.
Specifies the user ID used by the JDBC driver to access the Repository.
The value in this setting is not available for updates. If you must change the default value assigned to this setting, contact the Customer Services Support team.
Specifies the password used by the JDBC driver to access the Repository.
Specifies, in minutes, the interval at which other JVMs will synchronize security information with the WebFOCUS Repository, when multiple JVMs are using the same repository. For example, security information is not updated in the other application servers in a cluster or in the ReportCaster Distribution Server until this interval elapses. The default value is 5 minutes.
This information is not yet available.
Specifies the number of users for whom to retain the list of group memberships. The default value is 50 users and the maximum value is 1000 users.
Specifies the duration, in minutes, that WebFOCUS will retain the list of external groups for each user. The default value is 180 minutes and the maximum value is 720 minutes.
Specifies the number of minutes that WebFOCUS will retain user security information after sign out. The default value is 30 minutes.
Note: This setting may be useful for applications that run web services applications that sign in, perform a minor task, and sign out.
Specifies the maximum number of security policies retained for a single session. The default value is 50 policies and the maximum value is 500 policies.
Specifies the duration, in minutes, that a cached security policy is considered valid. The default value is 180 minutes and the maximum value is 720 minutes.
Specifies how many procedures (.fex files) are cached in memory to improve response time. The default value is 100 procedures (.fex files).
Specifies whether the Last Accessed On property is updated in the Properties dialog box when a resource is accessed. The default value is ON, which indicates that the property is updated.
Settings in this section activate the use of a third-party source control provider with App Studio. They also identify the location of the server and root project where the source control provider repository is stored.
When selected, this check box enables a source control provider to be integrated within WebFOCUS so it can be used for WebFOCUS code management while developing from App Studio.
The drop-down menu lists source control providers that are installed on your machine. Select the source control provider that you want to use within WebFOCUS.
In WebFOCUS Release 8.2 Version 01M, Team Foundation Server is the only source control provider available.
Type the version number of the source control provider you specified in the Provider field.
For example, when using Team Foundation Server 2013, type the value 2013.
Type the URL of the server hosting the Team Foundation Server, including the collection name that is used to host the projects.
For example, http://TFS_hostname:port/tfs/collection_name.
Type the path and folder name where the root source control project was installed.
For example, $/TeamProject1.
The Text Generation Server Settings define the connections to an independent server that provides narrative descriptions for chart headers, footers, and tooltips.
Identifies the URL of the external natural language generation (NLG) server that provides narrative descriptions for chart headers, footers and tooltips. If your product installation supports natural language generation for charts, type the URL of the text generation server in this setting. This setting is blank, by default.
This setting is not in use and must remain blank.
The Validation Settings specify the behavior of WebFOCUS when validation tests fail.
Specifies the action to take if a URI-parameter validation test fails. The validation test is performed as a precaution against SQL injection and cross-site scripting attacks. Permitted values are:
Specifies the HTTP response code to return to the browser when URI-parameter validation has failed and IBI_Validate.Action is set to ENFORCE. Permitted values are any valid HTTP status code (such as 400 or 403), a URI, or a fully qualified URL. If an HTTP status code is entered, WebFOCUS returns a response header with the status code. If a URL or URI is entered, WebFOCUS returns 200 (success) and redirects the browser to the specified address. The default value is 400.
For diagnostic purposes only. If True, returns an HTTP response header to the browser specifying the URLs that failed validation and the reason for their failure. The default value is False.