ReportCaster

In this section:

 


Top of page

x
Documentation Enhancements

The following are documentation enhancements for ReportCaster:


Top of page

x
Email Distribution Fix for Service Pack Upgrade to WebFOCUS 7.7.03 on Windows

How to:

Note: This problem was corrected in the installation packaging on July 1, 2011. If you downloaded WebFOCUS Release 7.7.03 for Windows prior to July 1, 2011, see the following information.

On Windows only, after installing WebFOCUS 7.7.03 as a Service Pack upgrade to an earlier version of WebFOCUS 7.7.x, if the Distribution Server is run as a Windows Service, ReportCaster generates an IO Exception error:

Unable to distribute to <email id>
IO Exception while sending message

The problem occurs because of renamed jar files, which require that the Windows ReportCaster Distribution Server service (and only the service) to be re-installed. The new jar files are activation-1.1.1.jar and mail-1.4.2.jar.



x
Procedure: How to Fix Email Distribution for Service Pack Upgrade to WebFOCUS 7.7.03 on Windows

If you have installed WebFOCUS 7.7.03 as a Service Pack upgrade on Windows, complete the following manual steps to correct the problem.

  1. Stop the WebFOCUS ReportCaster Distribution Server Windows service.
  2. Locate the correct ReportCaster service.bat file that is available after an upgrade installation and is located in the directory: \ibi\WebFOCUS77\7703_update\ReportCaster\bin. Verify the JAVA_HOME setting in the new service.bat file by doing the following:
    1. Open service.bat located in \ibi\WebFOCUS77\7703_update\ReportCaster\bin with a text editor.
    2. Update the line beginning with SET JAVA_HOME by changing the value of JAVA_HOME to the value found in service.bat located in \ibi\WebFOCUS77\ReportCaster\bin.
  3. Copy service.bat from \ibi\WebFOCUS77\7703_update\ReportCaster\bin to \ibi\WebFOCUS77\ReportCaster\bin.
  4. Verify the name of the existing WebFOCUS ReportCaster Distribution Server service.
    1. Open Control Panel, select Administrative Tools, and then Services.
    2. Right-click WebFOCUS ReportCaster WF77, and select Properties.
    3. Service Name: WF77 (WF77 is the service name by default).
  5. Reinstall the existing WebFOCUS ReportCaster Distribution Server service.
    1. Click Start, All Programs, Accessories.
    2. Right-click Command Prompt and select Run as administrator.
    3. Navigate to the \ibi\WebFOCUS77\ReportCaster\bin directory.
    4. Enter the command service.bat remove 'the name of your service' (for example, service.bat remove WF77).
    5. Enter the command service.bat install 'the name of your service' (for example, service.bat install WF77).
  6. Update the new WebFOCUS ReportCaster Distribution Server service from Manual to Automatic.
    1. Open Control Panel, select Administrative Tools, and then Services.
    2. Right-click WebFOCUS ReportCaster WF77, and select Properties.
    3. Change Startup type from Manual to Automatic.
  7. Start the WebFOCUS ReportCaster Distribution Server Windows service.

Note: Contact Customer Support Services if you have additional questions regarding this issue.


Top of page

x
Dynamic Language Options

As of Version 7 Release 7.02, Dynamic Language settings for ReportCaster are configured in the WebFOCUS Administration Console and no longer configured in the ReportCaster Configuration tool.


Top of page

x
EXL2K TEMPLATE

As of Version 7 Release 7, when EXL2K TEMPLATE is selected as an output format for distribution, the file type should be xls. The Save As value in ReportCaster defaults to xlt.

This issue has been addressed in Version 7 Release 7.02.


Top of page

x
ReportCaster API Javadoc

As of Version 7 Release 7, the ReportCaster API Javadoc is no longer accessible from the WebFOCUS Online Help. It is accessible using the following URL:

http://servername:port/webserver_alias/javadoc/rcaster/index.html


Top of page

x
ReportCaster Applet Interface JVM Issue

The toolbar icons on the ReportCaster Developer and Administrator (applet) interface are incorrectly spaced when the user browser is configured to use Sun Microsystems JVM Versions 1.5_08 and higher on Windows 2000 and Windows 2000 Server, and with JVM Versions 1.5_07 and higher on Windows 2003 Server. This is a documented problem in the Sun Microsystems release notes, which are found at:

http://www.oracle.com/technetwork/java/javase/releasenotes-142123.html

Sun Microsystems is tracking a number of related reported problems in this area. The main bug ID number is 6349010. The bug ID number that specifically references JVM 1.5_08 is 6234686. Although the description information on these problems states that it is for Windows XP, the problem within the ReportCaster applet interface is only occurring on Windows 2000 and 2003. This is not a problem if the user browser is running on Windows XP.

Evaluation has been performed with the Sun Microsystems JVM 1.6 version and this ReportCaster applet toolbar button issue has been confirmed not to occur with Windows XP, 2000, and 2003. This is a cosmetic issue and does not impact ReportCaster functionality.


Top of page

x
Opening Excel Files Using Outlook Web Access Mail Client

There is a known issue opening Excel files distributed by e-mail to an Outlook Web Access mail client due to Outlook attachment blocking. For more information about Outlook Web Access attachment blocking, go to the following URL:

http://support.microsoft.com/kb/555001.

The alternative for this issue is to zip the Excel file(s) before distribution. For information on zipping scheduled output, see the ReportCaster End User's Manual.


Top of page

x
Opening Excel and PDF Files Distributed by ReportCaster to Managed Reporting for WebSphere 6.1

You cannot open Excel and PDF reports in Internet Explorer if the reports were distributed to Managed Reporting on a WebSphere 6.1 application server configured with Java 1.5.

This problem does not occur:


Top of page

x
Distributing Scheduled Output Using SFTP

When distributing scheduled output using SFTP, you must specify the fully-qualified domain name.


Top of page

x
Issues When Using Informix

When ReportCaster is configured with Informix, the error java.net.UnknownHostException occurs when a schedule is run and the mail server specified is invalid.


Top of page

x
Accessing the Password and Advanced Buttons Using the Keyboard

When creating or editing a task and accessing the Password and Advanced buttons using the keyboard, the Enter key does not select the option. An alternative is to use the space bar to select the Password and Advanced buttons.


Top of page

x
Web Browser Issues

The following are Web Browser issues when using ReportCaster:


Top of page

x
Help Option in Email Address Search Dialog

The Help option from the Email Address Search dialog does not display online help. The alternative is to use the online help Index and enter Address Search in the keyword entry field to locate and view the online help information for Address Search.


Top of page

x
Opening ODP Reports in the Library

Under certain conditions, you may receive a Siteminder authentication prompt when you attempt to open an On Demand Paging (ODP) report in the Report Library by clicking the report in the left pane of the Library interface. (This prompt does not appear when you open the report in a separate window, that is, when you select the report and click the Open icon.)

If you receive the Siteminder authentication prompt, enter the requested information, then the report will open in the right pane of the Library interface.


Top of page

x
WIN Itanium and AMD64 Platforms

ReportCaster cannot be started as a service on WIN Itanium or AMD64.


Top of page

x
Secondary Run Interval Ignored When Schedule Updated

When a schedule is updated, the next run time is recalculated based only on the primary run interval. This means that if a schedule that includes a secondary run interval is updated before the secondary schedule is able to run, then the secondary run interval is ignored and the NEXTRUNTIME is calculated based on the primary interval.

For example, a schedule exists that is set to run daily at 2:00 PM with a secondary run interval of every 10 minutes from 2:00 PM to 3:00 PM. When the schedule runs at 2:00 PM, the NEXTRUNTIME is reset to run at 2:10, which honors the secondary run interval. If this schedule is updated at 2:03 PM, the NEXTRUNTIME is recalculated to be 2:00 PM the next day, rather than 2:10 PM on the current day.


WebFOCUS