The following are upgrade considerations
and product changes for ReportCaster:
purgelib utility creates a purgelib.log file in the .../ibi/WebFOCUS8x/ReportCaster/log
Release 7.7, if the Reporting Server associated with a schedule
is configured to use Execution IDs and passwords, the Change Management
utility exports the encrypted password for an Execution ID with
an exported schedule and updates the Execution ID table during an
import. In Release 8.0 and higher, the Change Management export
utility does not include the password for an Execution ID with an
exported schedule and the Execution ID table is not updated during
the import of a schedule. If the Reporting Server associated with
a schedule is configured to use Execution IDs and passwords, and
an Execution ID does not already exist for that Reporting Server,
you must create the Execution ID and password separately in order
for a change managed schedule to work. This can be done before or
after the import using the ReportCaster Console.
When using DSTRUN in
WebFOCUS Release 8, as in earlier releases, you can supply either
the schedule description or the schedule ID.
of Release 8.1 Version 03, Data Server connection information is
stored only in the WebFOCUS Client and not in ReportCaster. ReportCaster
now runs scheduled procedures through the WebFOCUS Client which
is installed with the Distribution Server. When a ReportCaster job
is executed by the WebFOCUS Client, the alternate deferred server
is used if an alternate deferred server is defined. For more information
about configuring alternate deferred servers see the WebFOCUS
Security and Administration manual.
of Release 8.1 Version 03, the Distribution Server processing uses
the IBFS system to submit scheduled jobs to a Reporting Server so
that the processing for interactive and scheduled requests is consistent
(including support for WebFOCUS group security). This consistency
in processing includes the Distribution Server using the Reporting Server
(referred to as Data Server in the ReportCaster configuration),
host, and port definitions defined in the WebFOCUS Client configuration.
All other Data Server definitions required for Distribution Server
processing, including the Maximum Threads setting that defines the
number of scheduled jobs the Distribution Server can submit to a
Reporting Server, remain in the ReportCaster configuration. Select
the Data Server option in the tree of the
ReportCaster Console Configuration tab to create and maintain the
Data Servers defined in the ReportCaster configuration.
the integration of Reporting Server (Data Server) definitions, a
different host and port cannot be defined for a Data Server in the
ReportCaster Configuration tool. Instead, when ReportCaster submits
a report to the WebFOCUS Client for execution, the WebFOCUS Client
uses the alternate deferred server if an alternate deferred server
is configured. For more information, see the WebFOCUS Security
and Administration manual.
Due to the authentication requirements
of WebFOCUS 8 security implementation, the redirect solution for
the ReportCaster rcaster context root, which was provided with Release
7.7, is discontinued.
The redirect solution was provided in Release
7.7 as a result of the merging of the WebFOCUS and ReportCaster
web applications. For specific information on the ReportCaster redirect
solution, as presented in Release 7.7, see Redirecting Web
Applications with the RCASTER Context Root in the Release
7.7.03 version of the WebFOCUS and ReportCaster Installation
and Configuration manual. Additional information is also
available on the Tech Support website under the following topic: ReportCaster
and WebFOCUS Web Application combined into one Web Application in
Release 7.7. For more information, go to:
In Release 8, application
content that contains a hard-coded reference to rcaster or a ReportCaster-specific
context root must be modified to reference the WebFOCUS context
root. The default WebFOCUS context root value is ibi_apps. Application
content includes HTML pages, browser shortcuts, and procedures (FEX)
that reference the stabilized ReportCaster subroutines, such as
DSTRUN, that make hard-coded calls to rcaster. In addition, if you
have an application that uses ReportCaster Web Services, you must
re-consume the Web Services Description Language (WSDL) file in
order for this application to run in WebFOCUS 8. For more information,
see the Release 7.7.05 version of the WebFOCUS ReportCaster
Web Services manual, which is available at:
For assistance with upgrading and remediating
your legacy applications with ReportCaster rcaster contact root
references, as required in Release 8, contact Customer Support.
- In releases prior
to Release 8.1 Version 03, you had the ability to specify a parameter
(amper variable) in the Email Subject field in a schedule. The value
of this parameter was obtained from the values stored with the schedule
in the ReportCaster parameter table. As of Release 8.1 Version 03
and higher, you can specify amper variables in additional schedule
settings and have the run-time values of the amper variables substituted
by the distribution server at report distribution time. If you wish
to limit the use of amper variables to the Email subject field only
and use the parameter value stored in the schedule, select the Use
legacy behavior for parameterized schedule settings check
box in the General Preferences of the ReportCaster Configuration
of Release 8.1, the shared indicator icon does not display on the
Shared Content folder, which is a virtual folder that displays shared
content that was migrated from Release 7.x.
- The Google Library
Search has been desupported. The Magnify replacement is not yet
- Running a schedule
with traces is not yet implemented when selecting a schedule from
the tree in BI Portal, Dashboard, or the ReportCaster Explorer.
A schedule can be run with trace options from within the Basic or
Advanced Scheduling tools.
The following .jar
files have been removed from the ibi_html/javaassist directory:
If a Library report in HTML format was migrated from
an earlier release and it contains charts that are rendered through
applet tags that reference these files, the charts will no longer
display. Contact Customer Support Services to add these files back to
Release 8.1 Version 05M, reports distributed in a text format contain
trailing spaces. Users now have the option to remove trailing spaces
from these reports.
Your administrator needs to add the following
setting to the Administration Console Custom Settings text box:
IBIWF_trimreport=YES. You can also apply this setting to affect
only specific report formats, for example, IBIWF_trimreport=WP.
this setting makes reports display in a more compact format by reducing the
overall text width.