In this section:
You have several configuration options for WebFOCUS. This section addresses web server and application server deployment.
Important: For a split-tier environment, see Configuring WebFOCUS in a Split Web-Tier and Application Server-Only Environment.
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.
For important information on configuring approot.war, see Configuring WebFOCUS in a Split Web-Tier and Application Server-Only Environment.
The following is an overview of the steps needed to configure the web or application server for WebFOCUS.
If you do not have an application server, the WebFOCUS Client installation can install and configure Apache Tomcat for you.
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. 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
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.
The following configurations are explained in this chapter:
For other web and/or application servers, review the information for the servers above and consult your third party documentation for the corresponding steps.
Note: If you changed the default names for the WebFOCUS context root (/ibi_apps), substitute accordingly.