Configuring WebFOCUS in a Split Web-Tier and Application Server-Only Environment

Using the Static Content Server Option

WebFOCUS installs a pair of web applications into the drive:\ibi\WebFOCUS82\webapps directory, which are designed to serve static content from the file system to the browser:

approot.war. Serves content from the drive:\ibi\apps directory.
ibi_html.war. Serves content from the drive:\ibi\WebFOCUS82\ibi_html directory.

Deploy one or both of these applications to address the following split web-tier and stand-alone application server configurations:

The web server is unable to access the static content because it is located on the application server machine.
There is no web server and you wish to use an application server by itself.
Note: Tomcat can be used by itself without these applications because it can map a directory on the file system to a context path. This configuration is referred to as the Tomcat Stand-alone option and can be configured during installation on Windows.

Each application includes a deployment descriptor (webconfig.xml) that is used to locate the directory containing its configuration file. The context parameter IBI_Configuration_Directory in webconfig.xml is updated during installation to point to drive:/ibi/WebFOCUS82/config, which contains the configuration file approotConfig.xml. The configuration file is shared by both content server applications even though its name suggests it would be used by only one. The configuration file is used to maintain MIME mappings, the physical path of the directories being served, and the logging level.

The applications also include a Log4J property file (log4j.xml), which contains the path to the log file used by each application. The installation updates each log4j.xml file with the path to its own log file, drive:/ibi/WebFOCUS82/logs/wfapproot.log and drive:/ibi/WebFOCUS82/logs/wfibihtml.log, respectively.

The content server applications roll the log files over daily by appending the date to the log file and creating a new one (for example, wfibihtml.log.2016-01-01). You can increase the log level by editing drive:/ibi/WebFOCUS82/config/approotConfig.xml and changing the log level setting to DEBUG, INFO, WARN, ERROR, or FATAL, where DEBUG is the most verbose.

There are special considerations for using the content server option in a clustered web-tier environment.

Top of page

Reference: Using the IBIARCFG and IBIARLOG –D Options With the Content Server Web Applications

Generally speaking, the approach of specifying a fully qualified path to the configuration file (approotConfig.xml) in webconfig.xml and of specifying a fully qualified path to the log files in log4j.xml is sufficient for most installations. These paths are properly set during installation.

However, there is an option to pass the content servers these paths from the Java VM command line. To do this, complete the following steps:

Edit the WebFOCUS webconfig.xml file found inside both the approot.war and ibi_html.war files. Replace the fully qualified path defined in the IBI_Configuration_Directory parameter with the notation shown below.
```
<context-param>
    <param-name>IBI_Configuration_Directory</param-name>
    <param-value>${IBIARCFG}</param-value>
</context-param>
```
Edit the WebFOCUS log4j.xml file located in the approot.war file and replace the fully qualified path specified by the File parameter, as follows:
```
<param name="File" value="${IBIARLOG}/wfapproot.log"/>
```
Use a forward slash, even on Windows systems.
Edit the WebFOCUS log4j.xml file located inside the ibi_html.war file and replace the fully qualified path specified by the File parameter, as follows:
```
<param name="File" value="${IBIARLOG}/wfibihtml.log"/>
```
Use a forward slash even on Windows systems.
Add the following –D options in the manner appropriate for the Java VM for your application server.
The settings below are slightly different in a clustered web-tier environment.
```
–DIBIARCFG=install_directory/ibi/WebFOCUS82/config 
–DIBIARLOG=install_directory/ibi/WebFOCUS82/logs
```