ibi WebFOCUS Variables

The internal variables that control the processing behavior of the WebFOCUS Client are loaded into a memory-resident table from several sources, including:

• WebFOCUS script and configuration files. The WebFOCUS Client has a set of script and configuration files (*.wfs, *.prf, *.cfg) containing information that defines its operation. For example, variables identify user IDs, host names, host ports, and directory locations.

  Configuration files (*.cfg) provide initialization parameters that define the environment of each request. Initialization parameters consist of name=value pairs.

  Script files (*.wfs, *.prf) define WebFOCUS variables that are used during processing. You can use the WebFOCUS scripting language to modify the variable values based on conditional logic.

• Template files and HTML pages. Template files describe page layouts for pages that display the status of core processing and some Managed Reporting processing, such as the deferred status page.
• HTTP headers. HTTP variables are passed between a web server and browser in the HTTP request/response header. HTTP variables typically define the environment of the web browser. For example, the HTTP_USER_AGENT header defines the browser manufacturer and version. The WebFOCUS Client can use any of the standard HTTP variables that are created and populated by the web server and the web browser.

ibi WebFOCUS Variable Table

The memory resident WebFOCUS variable table holds variables, allowing them to be used for local processing and in the communication between WebFOCUS components.

You can use the Administration Console to change the values of most WebFOCUS variables. For more information about the Administration Console, see Configuring the ibi WebFOCUS Client.