• Print  |
  • Feedback  |

FOCUS AREAS

Resources for Intelligence Platform Migration

Quick Links

Analysis Report Messages

Migration

SAS® Forecast Server

For information about migration tasks, see the SAS Forecast Server 3.1 Administrator’s Guide to Upgrading from SAS Forecast Server 2.1 to SAS Forecast Server 3.1.

For any updates or hot fixes that are required before you can migrate, see the baseline requirements topic.

Messages

caution Stored process reports detection failed to complete. If any user reports are present, they should be manually migrated using the import/export capability of SAS Management Console. If present, user reports would exist under the metadata subtree /Forecast Studio/Stored Processes.
This message is very uncommon. It indicates that the analysis algorithm was unable to determine whether report objects exist in the repository. If report objects do exist, use the instructions below to migrate reports manually.

caution This system appears to contain stored process reports, which cannot be automatically migrated. User reports can be migrated manually using the import/export capability of SAS Management Console. If present, user reports would exist under the metadata subtree /Forecast Studio/Stored Processes.
The message can be triggered by sample reports; you only need to take notice if you had created custom reports that you want to use in the migrated system. To migrate manually, take the following steps:
  1. In the source system, export user reports to SPK files.
  2. In the target system, create or choose the environment in which to use some reports.
  3. Configure the reports' root location for the environment, if not done already, using the product plug-in for SAS Management Console.
  4. Import the SPK file contents into the chosen metadata location.
  5. Review report objects and make any necessary compatibility changes. The FS_REPORT keyword can be applied to all stored processes in the reports tree automatically using the product plug-in.

caution Environment settings will be automatically migrated but file system content must be manually copied to target system. In addition, migrated environment objects will be given default permissions.
Recursively copy the specified file system subtree specified to the same location on the new server. For in-place migration, the structure can be left as is.

Environments are automatically assigned generated names. If an administrator wants to rename the environment objects, use the product's plug-in for SAS Management Console.

Because OMR permissions are now checked for the environment and project objects, an administrator might want to alter those settings after migration. Use the SAS Management Console.

caution This configuration file has been deprecated and will not be migrated. Environment objects will be automatically created during migration for all active project locations, but may require additional manual configuration.
This message indicates that the user_locations.properties file is found in the installation area of the SAS Forecast Server component. The presence of the file does not necessarily imply that it is actively in use. Beyond the other general tasks related to environment migration (mentioned in the above item), this message implies no additional work. However, sites that used this file in the source system might want to customize the new environment objects in the target system, particularly the permissions, in order to configure the user spaces as desired.

Contributing to Migration

The migration team appreciates your feedback. Send e-mail to Migration.Feedback@sas.com with questions and comments for our developers, testers, and writers.