WebFOCUS Architecture

In this section:

This topic briefly explains the main WebFOCUS components and implementations. For a complete description of WebFOCUS, see the WebFOCUS documentation.

Top of page

WebFOCUS and Your Network

WebFOCUS unobtrusively integrates into your existing network by connecting your web server to your data. End users access WebFOCUS applications through a web browser, so they need only the following elements:

Top of page

WebFOCUS Components

There are two main WebFOCUS components.

Top of page

WebFOCUS Processing

The following steps accompany the figure and describe how WebFOCUS processes requests:

  1. A user requests a report and passes parameters by calling a WebFOCUS Servlet through links and forms on a webpage or through Developer Studio.
  2. The request and parameters come to the WebFOCUS Client on the web server, which processes the parameters and creates a request for the Reporting Server.
  3. The Reporting Server receives the request, processes it, and accesses any necessary data.
  4. Data is retrieved from data sources to process the request.
  5. The Reporting Server processes the user request using the retrieved data.
  6. The response is returned to the WebFOCUS Client on the web server.
  7. The response is returned to the user.

    Web Server

Top of page

WebFOCUS Configuration

WebFOCUS employs a distributed architecture, so the WebFOCUS Client, Reporting Server, and your data can be located on any platform in your network. You can easily connect to an Apacheā„¢ web server running on UNIX to SQL Server data on Windows or DB2 data on z/OS. There can be any number of Reporting Servers connected to the WebFOCUS Client. WebFOCUS can report on all of them. The requirements are the following:

For more information on WebFOCUS configuration options, see the WebFOCUS and ReportCaster installation manuals and the server configuration manuals.