In this section:
This section explains how to set up IBM WebSphere Application Server for use with WebFOCUS and ReportCaster. It is assumed that WebSphere components are installed and configured. For additional information, see the WebSphere documentation. In WebFOCUS 8, you can easily use WebSphere Application Server without the external IBM HTTP Server by deploying the approot.war file.
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.
Depending on your IBM WebSphere Application Server default settings, you may need to adjust the Java VM memory options if you run into performance issues.
The most common Java VM options you need to set involve the size of the Java heap and stack, which determine memory availability for Java programs and the Java VM. Errors can occur if not enough memory is available, and the heap size impacts performance, since it determines how often garbage collection occurs.
The following are the most common Java VM options related to memory settings. Replace the #### with the size you wish to set:
Sets the maximum Java heap size. It is common to make this 1/4 of the system RAM, but it should be at least 1536 MB (1.5 GB).
Sets the initial Java heap size. It is common to make this 1/8 of the system RAM, but it should be at least 1536 MB (1.5 GB).
Sets the Java thread stack size. You do not need to set this unless you are fine tuning your environment.
The size is normally set in Megabytes. For example:
To view your current Java VM memory settings, access the WebFOCUS Administration Console. In the left pane of the console, expand the Diagnostics node and click JVM Property Info, as shown in the following image.
The Java VM memory settings for your environment are displayed in the right pane, as shown in the following image.
Optimum sizes vary depending on your total memory, the needs of your application, how many other processes require memory, the type of Java VM, and other considerations. A good starting place is to set the minimum to 1/8 of the total RAM and set the maximum to 1/4 of total RAM.
Where to set these and other Java VM options, depend on your application server.
For Tomcat, these are set automatically if the WebFOCUS installation configured Tomcat.
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.
To prepare WebSphere for ReportCaster, you should set the CLASSPATH variable to include your JDBC driver.
Note: If you are using 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.
If you are not using ReportCaster, proceed to Deploying Web Applications.
You must include the file in the path. Providing a directory is not sufficient. If multiple files are needed for the JDBC driver, provide the path to each file separating paths by semicolons. Spaces can occur in directory names, but not between the paths and the semicolons. For example:
drive:\Program Files\Microsoft SQL Server 2008 Driver for JDBC\ lib\sqljdbc4.jar
For more information about JDBC drivers, see JDBC Overview.
Use the WebSphere Administrative Console, to deploy (install) the WebFOCUS and ReportCaster web applications. The number of web applications you deploy depends on your configuration. Repeat this procedure for each web application you need to deploy.
The web applications are located in the following directory:
For WebSphere, you deploy the WAR files.
You can use the default WebSphere instance or create a new instance using the WebSphere Administrative Console. If you want to create new instances or virtual hosts, see the IBM documentation.
Caution: If previous instances of the WebFOCUS or ReportCaster applications have been installed, you must stop and uninstall them before installing the new applications. To determine if previous instances have been installed, click Enterprise Applications on the left. If applications appear, check their boxes and click Stop. After they are stopped, click Uninstall.
Note: In WebFOCUS 8, there is one web application in the WebFOCUS81\webapps directory, 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.
Is the host name of the Websphere Application Server and its associated HTTP port. For the default_host, the default HTTP port is 9060. For other hosts, look in the WebSphere Administrative console under Environment, Virtual Hosts, host_name, and Host Aliases.
A page should appear displaying information about the current build.
If you receive an error, try restarting WebSphere.
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.