Processing behavior of the WebFOCUS Client is controlled by internal variables that may come from several sources and are loaded into a memory resident table. Sources for the variables include:

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

  Initialization parameters are collected from a configuration file (*.cfg) to define the environment of each request. These parameters consist of name=value pairs.

  WebFOCUS script files (*.wfs. *.prf) defines many of the WebFOCUS variables used during processing. In these files, you can set variable values based on conditional logic using the WebFOCUS scripting language.

• Template files. Other files used by WebFOCUS to process requests are template files and HTML files. Template files describe page layouts for certain Managed Reporting processing (such as the deferred status page) and core processing.
• WebFOCUS logon pages. User credentials are collected from a logon (or sign-on) page. To avoid repeated prompting, credentials can be stored in a cookie or an application server session variable. Managed Reporting logon pages set the variables required for Managed Reporting processing. There are Managed Reporting logon pages for several Managed Reporting authentication scenarios.
• HTTP header. Web servers support HTTP variables, which are passed between the Web server and the Web browser in the HTTP request/response header. These variables typically define the environment of the Web browser. For example, HTTP_USER_AGENT defines which browser manufacturer and version of the browser is being used. All standard HTTP variables that are created and populated by the Web server and the Web browser are available to the WebFOCUS Client.