ReportCaster Troubleshooting Tips

If ReportCaster fails to perform properly, confirm that all components are installed, started, and listening on their expected ports. All components can run on one machine or components can be distributed across different machines running different operating systems. If components are distributed, ensure all machines are running and can communicate using the expected protocols.

The ReportCaster Distribution Server starts in Console mode if it cannot connect to the repository. The ReportCaster Distribution Server will also start in Console mode if it can connect to the repository but the tables are not created. The Scheduler log file indicates why the Distribution Server started in Console mode. If you need to change repository parameters, refer to WebFOCUS Repository Post-Installation Tasks.

Note: The ReportCaster web components, WebFOCUS Reporting Server, and ReportCaster Distribution Server must all be the same release number.

Troubleshooting ReportCaster Servlet Errors

Review the installation and configuration instructions in WebFOCUS Client and ReportCaster Installation and Configuring Web and Application Servers.

Ensure your web and application servers are running.
Ensure the WebFOCUS web application is installed and configured. The ReportCaster components are part of the WebFOCUS web application installed with the WebFOCUS Client.
```
/install_directory/ibi/WebFOCUS80/webapps/webfocus
```

Troubleshooting ReportCaster Distribution Server Errors

Review the installation and configuration instructions in WebFOCUS Client and ReportCaster Installation and WebFOCUS Repository Post-Installation Tasks.

Ensure the ReportCaster Distribution Server is running.
Ensure the WebFOCUS web application knows where the Distribution Server is. The AGENT_NODE and AGENT_PORT parameters specify the hostname and TCP Port for the Distribution Server in files installed with WebFOCUS Client:
```
/install_directory/ibi/WebFOCUS80/client/wfc/etc/cgivars.wfs
```
Ensure Java JDK 1.6 is properly installed and configured.
Check the settings in the following file:
```
/install_directory/ibi/WebFOCUS80/ReportCaster/install.cfg
```
This file records the information provided when you installed the Distribution Server. To change this information, use the ReportCaster Server Configuration interface or the scripts described in WebFOCUS Repository Post-Installation Tasks.

Troubleshooting ReportCaster Context Root

In this section:

Redirecting Web Applications With the ReportCaster Context Root

Applications containing a hardcoded reference to rcaster or a ReportCaster specific context root will encounter an error. There is a new war file for customers that will redirect to the new ibi_apps without having to change their code.

Top of page

Redirecting Web Applications With the ReportCaster Context Root

In WebFOCUS 8, the WebFOCUS and ReportCaster web applications have been combined into one web application. In prior releases, the two applications were deployed separately with unique context roots whose default values were ibi_apps and rcaster. In WebFOCUS 8 there is only one context root for WebFOCUS and ReportCaster with a default value of ibi_apps.

However, customers who have web applications that contain hardcoded references to rcaster in the URL or a ReportCaster specific context root will be affected. To resolve this, deploy the redirect.war file to redirect URLs that reference rcaster or a ReportCaster specific context root to the single context root.

Troubleshooting Reporting or Delivery Errors

Review the WebFOCUS and ReportCaster documentation and the documentation for your Mail or FTP server.

Ensure the WebFOCUS Reporting Server is running.
Ensure the report, file, or URL is valid.
Ensure the Mail or FTP server is running.
Check the settings in the ReportCaster Server Configuration interface.