The following are upgrade considerations and product changes for ReportCaster:
As of Version 7 Release 7, the ReportCaster Web application (default context root, rcaster) has been integrated into the WebFOCUS Web application (default context root, ibi_apps).
Applications that use cgipath.js to obtain the value of the ReportCaster specific context root will not be affected by this change. Applications that contain a hardcoded reference to rcaster or a ReportCaster specific context root will be affected. This includes the functionally stabilized subroutines, such as DSTRUN, which make hard-coded calls to rcaster.
If you have developed applications with URLs that contain rcaster or a custom ReportCaster context root value specified during the WebFOCUS Client and ReportCaster installation, then see the following advisory for options to accommodate this change.
http://techsupport.informationbuilders.com/tech/wbf/wbf_rln_77_rcaster.html
In Version 7 Release 7, the ReportCaster web application is part of the WebFOCUS web Application and has the same context root. The functionally stabilized DSTRUN subroutine assumes a default ReportCaster context root of rcaster. Therefore, when using DSTRUN in Release 7.7 you must supply the actual Reportcaster context root as part of the hostname parameter.
For example, if you are using the default port 80 for your web server and the default WebFOCUS context root ibi_apps, the host name parameter can be coded, as follows:
hostname:ibi_apps
If you are using a different port, for example 8080, and the default WebFOCUS context root ibi_apps, the host name parameter can be coded as follows:
hostname:8080:ibi_apps
If you are using a customized WebFOCUS context root you must specify the customized context root twice (once for WebFOCUS and once for ReportCaster). For example, if you are using port 8080 and the context root ibi_apps77, the host name parameter can be coded as follows:
hostname:8080/ibi_apps77:ibi_apps77
As of Version 7 Release 7, the ReportCaster repository tables have the same structure as in Version 7 Release 6, but two tables (BOTSCIT and BOTCDATE) were added to support the custom scheduling interval feature. You can use an existing Version 7 Release 6.x ReportCaster repository with Version 7 Release 7 without the need to migrate data, as long as all of the required tables exist in the repository. If all of the required tables do not exist, then the Distribution Server will start in Console Mode and a message will be written to the scheduler.log file with information about the missing table(s).
To create the new Version 7 Release 7 Repository tables, access the table creation utility and select the Custom Scheduling Interval Tables option, as described in the WebFOCUS Installation and Configuration manual for your platform.
Depending on which 7.6.x release you are currently using, additional tables may need to be created to use this repository with a Version 7 Release 7 installation. Within Version 7 Release 6, tables were added at various releases, as follows:
Therefore, if you are currently using Release 7.6.1, you will need to create three additional tables, BOTSBDS, BOTWATCH and BOTSTATE. If you are currently using a release from 7.6.2 through 7.6.6, you will need to create two additional tables, BOTWATCH and BOTSTATE. If you are currently using Release 7.6.7, you will need to create one additional table, BOTSTATE. If you are using Release 7.6.8 or higher, no additional tables beyond the Custom Scheduling Interval tables need to be created.
When starting the Distribution Server or running the test utility, a message is written to the scheduler.log file specifying whether the repository tables have been validated at the Version 7 Release 7 level.
WebFOCUS |