-
The Save On Demand Schedules for Job Duration option, which is specified in the Distribution Servers folder in the Configuration tool of the ReportCaster Console, is not functional.
- In WebFOCUS Version
8, the legacy ReportCaster API uses the ReportCaster and Library
Content folders that are created by the migration process. If you
have not migrated content to WebFOCUS Version 8 from an earlier
release of WebFOCUS, then you must manually create the ReportCaster
folder in order to use the legacy ReportCaster API to create a schedule
(unless you specify the full IBFS path in the Schedule description).
The ReportCaster folder must be created with the Auto Create My
Content Folders property set. The Library Content folder or folders
created during migration are the default destinations for Library
output from scheduled Managed Reporting procedures and Reporting
Server procedures. These folders must exist unless a full IBFS path
is specified as the destination for Library output at schedule creation
time.
-
When
a Library schedule has the access option Shared (Appears under Shared
Content folder) and the Send Email after Report Saved to Library
check box selected simultaneously, ReportCaster will only send email
messages to the schedule owner.
-
As
of WebFOCUS Version 8.0.03, the DSTRUN subroutine is supported.
-
If
you select the Shared setting for ReportCaster Data Server Security,
it will not work with Reporting Server security that requires a
password.
-
In
WebFOCUS Version 8, an administrator can no longer globally update
the Owner ID of ReportCaster content because the content is integrated
with IBFS security in the WebFOCUS Repository.
-
The
ReportCaster configuration file (dserver.xml) is placed in a WebFOCUS
Repository table during installation. Changes to this file can be
made using the ReportCaster Configuration tool and the WebFOCUS
Administration Console. A customer can export dserver.xml from the
WebFOCUS Repository to the file system or import dserver.xml from
the file system to the WebFOCUS Repository.
To export dserver.xml
to disk, run the exportcfg utility located in the ibi\WebFOCUS80\ReportCaster\bin
directory. The dserver.xml file is exported to the ibi\WebFOCUS80\ReportCaster\cfg
directory.
To import dserver.xml from disk, copy
dserver.xml to the ibi\WebFOCUS80\ReportCaster\cfg directory and
run the importcfg utility located in the ibi\WebFOCUS80\ReportCaster\bin
directory.
-
To
generate a wsdl for the legacy Managed Reporting Web Services, use
the URL .../ibi_apps/ibi_html/workbnch/webservice.htm. To generate
a wsdl for the legacy ReportCaster Web Services, use the URL .../ibi_apps/services/listServices.
-
When
the ReportCaster API is called to retrieve Category information,
the Category Name returned is the name of a folder. The Category
ID returned is the full IBFS path to that folder. In earlier releases,
if the Category name was the name of an MR Domain, the Category
ID was the href to that Domain. Otherwise, the Category ID was blank.
-
Charts
scheduled in HTML format generate embedded images instead of references
to applets. Therefore, charts can be distributed by any distribution
method and are not limited to Library distribution.
-
ReportCaster
is fully integrated with the Version 8 WebFOCUS Client security authorization
implementation. Users, Groups, Schedules, Distribution Lists, Access Lists,
and Library Reports are stored in the WebFOCUS Repository. Any custom applications
that reported directly against the ReportCaster User and Group tables
will need remediation to report against the Version 8 WebFOCUS Repository
tables.
- The Library Management
tool has been removed and replaced with equivalent functionality
available in the ReportCaster Explorer in Manager mode.
- You must be at a
WebFOCUS Version 7.6.x or 7.7.x level to migrate your ReportCaster
repository to WebFOCUS Version 8. If you are using an earlier release
of WebFOCUS, contact Customer Support Services for assistance.
-
The
Schedule option selected from an HTML Composer Page invokes the
WebFOCUS Version 8 Basic Scheduling tool. In prior releases, the
Single Page Scheduling Tool was invoked. This has been discontinued
in WebFOCUS Version 8 due to the ReportCaster Scheduling tools consolidation,
which replaces all prior scheduling tools with an intuitive ribbon-based
implementation.
When the template for the HTML Composer Page Schedule
button contains multiple distribution options, the user is prompted
to select one of the options before accessing the Schedule tool,
as shown in the following images:
In prior releases, the Single Page Scheduling
tool was invoked directly and the Distribute report by field listed
the distribution options available to the user to select.
- The Public flag in
Public Distribution lists has been removed. Users can now share Distribution
Lists with other users.
- The Google Library
Search has been desupported. The Magnify replacement is not yet
available.
- The Legacy ReportCaster
API supports the management of Distribution and Access Lists, the
scheduling of WebFOCUS Server procedures and WebFOCUS Repository procedures
migrated from an earlier release, Library distribution and retrieval,
Log management, and Console functionality.
- In WebFOCUS Version
8, the ReportCaster legacy API requires that the system property
IBI_DOCUMENT_ROOT be set. It does not need to be an environment
variable. ReportCaster uses IBI_DOCUMENT_ROOT to request that the IBFS
security system provide the information needed to connect to the
WebFOCUS Repository and obtain configuration information for initialization.
In previous releases, this was accomplished by using
the CasterManagedConnectionFactory methods setServerName and setPortNumber
to connect to the Distribution server. This connection to the Distribution
server for initialization has been replaced by the connection to
the IBFS security system using the system property IBI_DOCUMENT_ROOT.
The CasterManagedConnectionFactory methods setServerName
and setPortNumber have been deprecated. Use of these methods has
no effect in WebFOCUS Version 8.
For an example
of setting the system property IBI_DOCUMENT_ROOT, see the setenv
script (setenv.bat file on Windows), located in the ibi/WebFOCUS80/ReportCaster/Samples/Tools
directory.
- The Servlet API will
be supported in a future release of WebFOCUS Version 8.
-
Library
Access Lists utilize the WebFOCUS Client Security sharing functionality
to authorize groups and users access to Library reports in WebFOCUS
Version 8. As of Version 8.0.01, Access List support of subgroups
is available.
Users must be authorized to share Library reports
with the groups and users specified in the Access List for the library
report to be shared with them when distributed to the WebFOCUS Repository.
Changes to the Access Lists are applied at the next schedule execution.
If the Library report access changes are required before the next schedule
execution, they can be manually applied by accessing the Library
report from the resource tree in the Business Intelligence Portal
(BI Portal), Dashboard, or ReportCaster Explorer and selecting the Share or Share
Advanced options. The resource tree sharing options
are available to users who have been authorized to share library
reports.
- The Library Access
option Public has been replaced with Share to Everyone. Share to
Everyone means the report is available to all users who are authorized
to List and View Library content in the folder where the Library
item resides.
- The Library Access
option Access List has been replaced with Share Advanced. Share
Advanced means the report is shared at distribution time to the
users and groups that are on the Access List. If users or groups
are added or removed from the Access List, the change is not effective
until the next time the schedule is executed.
- Library Reports are
now stored in folders in the WebFOCUS repository. The Category field
is still available and can be used to sort reports displayed in
the ReportCaster Explorer. The folder that a Library report is stored
in must exist at the time a schedule is created. A Library item
is added to the selected folder when the schedule executes for the
first time. Subsequent versions are added to this item. The name
of the item is the name of the schedule or, in the case of a burst
report, the burst value.
- 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.
- In WebFOCUS Version
8, in order to retrieve a dynamic multi-select list using the Schedule
tool, you must click the Value button. In
Version 7.7.x, a Value button did not exist.
- In a schedule, there
are two new properties: Name and Title. Description, which is no
longer a property, has been replaced by Name. Title displays in
the BIP tree by default, however, this can be changed to display
the name. WebFOCUS Version 8 allows duplicate Titles, but not duplicate
Names.
Using the legacy ReportCaster API, you can create schedules
with duplicate Titles, but the Names must be unique. The legacy
ReportCaster API must be passed the unique Name when running a schedule
to ensure that the correct schedule is run.