In this section:
Troubleshooting WebFOCUS requires considering all the places where a problem can occur. These include the following:
Try some of these solutions when troubleshooting WebFOCUS problems:
This may be the problem if you receive a Resource not found message.
If you are planning to use WebFOCUS products, note that browsers released after the production date of a WebFOCUS version are subject to certification. Certification is done with the current release level of WebFOCUS, App Studio, and Developer Studio. For additional information, see Web Browser Support for WebFOCUS, which can be accessed by clicking on the following URL:
Note: Some browsers may function differently depending on the operating system. See the WebFOCUS Release Notes for detailed information on known issues related to browser version or configuration.
For information on supported Firefox browser versions, see Web Browser Support for WebFOCUS, which can be accessed by clicking on the following URL.
The following settings are required to use Firefox with Dashboard:
WebFOCUS 8 requires Java VM Version 6 or higher on the system that is hosting the application server where the WebFOCUS Client web application is displayed and the ReportCaster Distribution Server is installed.
There are two methods for verifying the Java VM version installed on the machine where the WebFOCUS client is deployed.
The version is listed under java.runtime.version.
The version is listed under java.vm.version.
In this section:
Ensure your web and application servers are configured as explained in Configuring Web and Application Servers.
Since WebFOCUS relies on processing by the Java VM, web server, and application server (or servlet container), their debugging tools and log files can help troubleshoot common WebFOCUS issues. Review the documentation for your web and application servers for information on their tracing and log files.
Setting some Java VM options can improve performance and correct problems with the application server. The most common settings 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.
If you run into performance problems or receive out of memory exceptions, you can adjust these sizes. The following are the most common Java VM options related to memory settings. Replace the ### with the size you wish to set:
Sets the Java thread stack size.
Sets the maximum Java heap size.
Sets the initial Java heap size. This should be at least 1024 MB (1 GB).
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.
File permissions, deployment of the WebFOCUS web application, or the Java plug-in browser are common causes of the following problems:
Directive not found in IBIMRcgi: ---COMMENT---START Directive not found in IBIMRcgi: ---COMMENT---END
Do the following to troubleshoot these errors.
WebFOCUS and ReportCaster expect an ISO8859-1 based character set. However, some systems may default to using Unicode (ISO 10646/UTF-8) instead. If this is the case, some characters, such as subscripts, may appear as a question mark (?) or other unexpected symbols in your reports. To correct this, set the LANG environment variable to specify the correct ISO8859-1 character set for your language. On Solaris systems, also set the LC_ALL environment variable to specify the correct ISO8859-1 character set. For example, English on Solaris is:
export LANG=en_US.ISO8859-1 export LC_ALL=en_US.ISO8859-1
Set the LANG and LC_ALL variables so they are available to the Java VM running your application server and Distribution Server. Where to set this varies depending on your application server, but you can normally export and set the variables in the application server startup script. For the Distribution Server, you can export and set this in schbkr script.
A jar utility is installed with the Java JDK. It lets you create, extract, and edit the contents of JAR, WAR, EAR, ZIP, RAR, and other archive files. If you deploy the WebFOCUS web application as a WAR file, the jar utility lets you change the webfocus.war file contents.
The WebFOCUS web application is provided as both an expanded directory and a WAR file:
The easiest way to edit the web application is the following:
jar cvf ../webfocus.war *
This creates a webfocus.war file containing all files and subdirectories in your current directory. The webfocus.war file will be located one directory above your current location because you prefaced it with "../".
You can edit the ReportCaster web application in the same fashion.
The options for using the jar commands are useful to know.
jar cvf FileToCreate.war FileToAdd1 FileToAdd2
You can add all files and subdirectories using an *:
jar cvf FileToCreate.war *
jar xvf ExistingFile.war FileToExtract1 FileToExtract2
Files are extracted to your current location.
You can extract all files and subdirectories by not specifying any files to extract:
jar xvf ExistingFile.war
jar uvf ExistingFile.war FileToAdd1
A path issue can generate an error during the silent installation of a distribution server.
When running the silent parameter file, you may see the following messages:
./install: var_asgn_file: not found.
To solve this problem, you must add . (dot) to your UNIX PATH statement.
This is an example of the syntax:
Verifying the setting should show new path as:
You should then be able to run the silent installation.