Configuration Overview and Options

In this section:

WebFOCUS Client and ReportCaster web components run as part of web servers and application servers. Configuration steps vary depending on which web servers or application servers you use.

Top of page

Configuration Steps Overview

How to:

The following is an overview of the steps needed to configure web or application servers for WebFOCUS and ReportCaster. For Apache Tomcat, you can review this overview or proceed directly to Configuring Apache Tomcat.

Important: If you want to install WebFOCUS in a clustered or split-tier environment, see Configuring WebFOCUS in a Split Web-Tier and Application Server-Only Environment.

The steps vary depending on the type of configuration you use:

Procedure: How to Configure a Web Server and an Application Server for WebFOCUS
  1. Ensure application server and web server components are installed and properly functioning. Refer to third-party documentation, if necessary.

    If you do not have an application server, the WebFOCUS Client installation can install and configure Apache Tomcat for you.

  2. Add the WebFOCUS repository JDBC driver to your application server CLASSPATH.

    For information on JDBC drivers, see Additional WebFOCUS Repository Topics and Tasks.

  3. Deploy the WebFOCUS web application on the application server.

    WebFOCUS components are packaged as a J2EE web application. The web application is provided as the following WAR file:


    It is also provided as the following expanded directory:


    You can deploy either the WAR files or expanded directories, depending on your preference and the capabilities of your application server. For Tomcat stand-alone, using the expanded directories is recommended. Be aware that when applying a service pack, any changes made to the web applications must be in the expanded directories to be maintained.

    The default deployment parameters for WebFOCUS are:

    Context Root/Path

    Doc base or location


    If you are using a web server, you can create aliases for the static content. This maps directories containing WebFOCUS data to directories the web server can reference. The default settings are:

    Default Alias




    Read Only

    On some Windows Servers, you may need to grant Scripts only executable permissions as well.

  4. Ensure your web server routes requests for the web application context root (/ibi_apps, /ibi_help, and /approot) to the application server.

    Note: For information on manually configuring the ibi_html alias, see Removal of the ibi_html WebFOCUS Alias.

  5. Verify the configuration using the tools in the WebFOCUS Administration Console, as explained in WebFOCUS Client Post-Installation Tasks.

    Note: If you are installing multiple instances, completely install and configure a single instance, and then refer to Additional WebFOCUS Repository Topics and Tasks for instructions on configuring the second instance.