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.
Tomcat can be used as both the web server and application server. If you choose this option, be aware that the default HTTP port for Tomcat is 8080, not 80. Therefore, when calling web server pages in a browser, you must use:
Manual configuration is described in Configuring Apache Tomcat.
Tomcat can be used as the application server while Microsoft IIS is used as the web server. This requires two servers and the configuration of their communications.
Manual configuration is described in Configuring Apache Tomcat, Configuring Microsoft IIS 6.0, and Configuring IIS to Use the Tomcat Connector (Plug-In).
For details, see Configuring IBM WebSphere.
Other web servers or application servers can be manually configured. Review your server documentation and perform steps that correspond to the information that follows.
If no web server is available, an application server can be used to handle all processing if the application server has robust HTTP capabilities.
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:
You can also use the web server to only pass requests to Tomcat through a firewall. In that case, you must deploy all three web applications on your application server.
If your web server and application server are located on different machines, see Configuring WebFOCUS in a Split Web-Tier and Application Server-Only Environment.
Application Server Only Configuration (all web applications). For application servers like IBM WebSphere, Oracle WebLogic, Oracle Application Server, SAP NetWeaver, and Oracle Java System Application Server, you can deploy all WebFOCUS content through web applications (WAR files). In this configuration, you deploy approot.war in addition to webfocus.war and ibi_help.war and you do not create web server aliases.
For important information on configuring approot.war, see Configuring WebFOCUS in a Split Web-Tier and Application Server-Only Environment.
If you do not have an application server, the WebFOCUS Client installation can install and configure Apache Tomcat for you.
For information on JDBC drivers, see Additional WebFOCUS Repository Topics and Tasks.
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:
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:
On some Windows Servers, you may need to grant Scripts only executable permissions as well.
Note: For information on manually configuring the ibi_html alias, see Removal of the ibi_html WebFOCUS Alias.
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.