In this section:
ReportCaster relies on communications between the following components:
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 ReportCaster Configuration.
Note: The ReportCaster web components, WebFOCUS Reporting Server, and ReportCaster Distribution Server must all be the same release number.
Normally, you should turn the Distribution Server traces on and off using the ReportCaster Server Configuration interface. However, if the interface is not available, you can execute the following utility:
The trace files appear in /install_directory/ibi/WebFOCUS81/ReportCaster/trc. In addition, check the log files in /install_directory/ibi/WebFOCUS81/ReportCaster/log for more information.
Remember to turn traces off after solving problems.
To use the ReportCaster Development and Administration interface, end users must have Java 6 or higher installed on their machines. The web browser of the user must be configured to use this Java VM to process applets.
Be aware that when end users schedule reports, the default time they see is in part determined by the system time and Java VM on the end user machines. If this is incorrect, try updating the end-user Java VM plug-ins to Java 1.8.0_45. Earlier Java releases might not adjust for the recent changes in U.S. daylight savings time.
If the parameters are incorrect in these files, correct them. If you deployed the expanded webfocus directory, redeploy the directory. If you deployed the webfocus.war file, use the jar command to place this web.xml file into the WEB-INF directory inside the webfocus.war file, and then redeploy the webfocus.war file. See Using the jar Utility for more information.
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 ReportCaster Configuration.
If you deployed the expanded directory, redeploy it. If you deployed the webfocus.war file, use the jar command to insert the driver files or create a new web application as explained in Using the jar Utility. Then redeploy the WAR file.
In this section:
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.
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.
Review the WebFOCUS and ReportCaster documentation and the documentation for your Mail or FTP server.