Creating and Exporting Change Management Packages
This section outlines useful information that you should
be aware of before creating and exporting CM packages.
- CM packages should
be imported from lower to higher WebFOCUS 8 environments (for example,
DEV to QA to PROD).
- CM packages can be
exported by using the CM export utilities or by running WebFOCUS 8
CM batch utilities.
- As of WebFOCUS Release
8.1 Version 04, CM packages can be created and exported in WebFOCUS
Release 8.0.x for import to WebFOCUS Release 8.1.x. This document
will be updated to provide guidelines for Release 8.2.x when that
release is available.
- When a CM package
is exported, the contents of the export package is written to the file
system in a Raw format that provides a mechanism to customize the
exported content before importing into the higher WebFOCUS 8 environment.
For example, if you want to replace FORMAT EXCEL with FORMAT PDF
in procedures, you would ordinarily need to open each resource in
the tool that you used to create the resource and change the format.
Instead, you make the change to the Raw format of the exported files
on the file system, then import the resources into the target environment.
The WebFOCUS IBI_CM_Format_Raw configuration parameter controls
whether the export package is written to disk in Raw format.
- CM export scenarios
should be created with the Retain Handles option selected, if the content
you are exporting does not include either ReportCaster content or
WebFOCUS content migrated from WebFOCUS Release 7.x.
- CM Export and Import
utilities do not support ReportCaster content as follows:
- Report Library content.
The expectation is that Report Library content is generated in each
environment, negating the need for export and import of Report Library content.
- ReportCaster Blackout
Dates. ReportCaster Blackout Dates can be moved from a lower WebFOCUS
8 environment to a higher WebFOCUS 8 environment using separate
utilities as described in the ReportCaster manual.
- ReportCaster Execution
IDs. The expectation is that the Execution IDs exist in the higher
WebFOCUS 8 environment.