In this section:
This section explains how to configure WebSphere Application Server with or without IBM HTTP Server for use with WebFOCUS and ReportCaster. It is assumed that WebSphere components are installed and configured. You should refer to the WebSphere documentation for additional information.
As of WebFOCUS 8, Java Version 6 is the minimum version required on the system that is hosting the application server where the WebFOCUS Reporting Server and ReportCaster Distribution Server are deployed.
Important: For IBM WebSphere Application Server Version 7.0, apply the IBM WebSphere Application Server feature pack for OSGI applications and Java persistence API 2.0.
To apply the IBM APAR:
The Custom Properties page opens.
The Messages dialog box opens.
Before deploying WebFOCUS web Applications, you should configure WebSphere for WebFOCUS graphs.
To generate graphs, WebFOCUS Servlets either need access to an X Windows Server (through the DISPLAY variable), or they can use the Java VM headless option.
DISPLAY. If an X Windows Server is available, you should set a DISPLAY environment variable.
DISPLAY must be set outside of the WebSphere Administrative Console before you start the application server. You can set this by declaring the variable when you launch the server. You can do this by editing the startup script for WebSphere or by editing the .profile for the user ID that starts WebSphere. For example:
DISPLAY=xserver_host:0.0 export DISPLAY TERM=xterm export TERM
Is the hostname or IP Address of a machine that is running an X Server.
Note: Graphs are not actually displayed on the machine you set to DISPLAY, but WebFOCUS Servlets must access this X Server to generate graphs. After finishing this chapter, be sure to review the tests to verify graphs in Verifying and Troubleshooting Server Side Graphics (PCHOLD).
Headless. If an X Windows Server is not available, you can set the headless Java option using the WebSphere Administrative Console. However, be aware that headless does not support GIF files or the older WebFOCUS GRAPH32 engine.
You will need to restart the server for the headless option to be used, but you can do that after performing the next procedures.
If you use ReportCaster, the CLASSPATH variable must include the JDBC driver of your repository. You can set CLASSPATH using the WebSphere Administrative Console.
Note: If you use InfoAssist, you may need to increase the default Java memory options as explained in Java Memory Issues. This can be done at a later time if needed, but it is done from the same area of the WebSphere Administrative Console as setting CLASSPATH.
Note: If you need to change the Java VM memory options discussed in Java Memory Issues, you can specify the options in the Generic JVM arguments field.
If you are using WebSphere Application Server Version 8.0 or 8.5, you must upgrade the version of jackson-all-1.9.11.jar that is included with WebSphere, then redeploy the WebFOCUS web application.
WebFOCUS 8 is packaged with a newer version of the jackson-all-1.9.11.jar file, which includes updated classes. To avoid conflicts with the current version of the jackson-all-1.9.11.jar that is included and used by WebSphere Application Server Version 8.0 and 8.5, perform the following steps. These steps describe how to define a container-wide shared library that can be used by deployed WebFOCUS applications.
The Shared Libraries pane opens, as shown in the following image.
The Shared Libraries > New pane opens, as shown in the following image.
This procedure describes how to define a container-wide shared library that can be used by deployed WebFOCUS applications.
Note: Only the webfocus.war file for the WebFOCUS web application requires this change. The ibi_help.war, approot.war, and ibi_html.war files do not require the changes described in this procedure.
The Enterprise Applications pane opens, as shown in the following image.
The Shared library references pane opens, as shown in the following image.
Note: The WebFOCUS Application being used in this example is called 15215webfocus_war and the Module is called WebFOCUS 8.1.
The Shared Library Mapping pane opens, as shown in the following image.
The IBI Jackson 1.9 shared library is now listed in the Selected area.
Ensure that the IBI Jackson 1.9 shared library for the Module is moved to the Selected area.
You are returned to the Shared library references pane, as shown in the following image.
Notice that the new shared library (IBI Jackson 1.9) is now listed in the Shared Libraries column for the Application and Module.
Note: Restarting only the WebFOCUS application will not be sufficient.
Use the WebSphere Administrative Console, to deploy (install) the WebFOCUS web application. Repeat this procedure for each web application you need to deploy.
The web applications are located in the following directory:
All web applications should be deployed.
Always deploy this web application.
Always deploy this web application.
Deploy this web application if you are using an application server only configuration.
You can use the default WebSphere instance or create a new instance using the WebSphere Administrative Console. See your IBM documentation if you wish to create new instances or virtual hosts.
Note: If you want to deploy new instances of WebFOCUS but keep your old version, you must install WebFOCUS with different ports and new context roots.
Note: In WebFOCUS 8, there is one web application in the WebFOCUS81/webappsdirectory, which contains the WebFOCUS Client and ReportCaster (ibi_apps).
When the application deployment is complete, click Save directly to the master configuration.
After configuring WebSphere components, verify operability.
You may wish to bookmark this page for future use. This page is also referred to as the WebFOCUS home page.
Be aware that you may need to increase your Java memory settings if you use InfoAssist. You can do this later, as explained in Java Memory Issues.