FOCUS AREAS

Resources for Intelligence Platform Migration

Quick Links

Analysis Report Messages

Migration

SAS Real-Time Decision Manager

See the "Migration" chapter of SAS Real-Time Decision Manager Administrator's Guide for important information before you begin migration.

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

Messages

error Migration of this SAS environment is not recommended. This version of the SAS Migration Utility does not support migration for SAS Real-Time Decision Manager Queues Configuration. See http://support.sas.com/migration/utilitynotes for more information.
The queues configuration is deleted in this release.

caution Migration is supported for this version. The custom SAS Activity code requires manual migration. You will need to execute the MigrateActivity script to migrate your custom sas code.
More information is available in the administration guide or in the instructions.html document that is created during deployment.

caution Migration is not supported for this version. The system resources that reference the queue manager and queues will be removed. Do not include the SAS connection type system resources in the exported .spk files that will be migrated manually.
The queues configuration is deleted in this release.

caution Migration is supported for this version. If the objectspawner is not needed then you will need to manually remove the object spawner that was configured for exclusive use by SAS Real-Time Decision Manager.
More information is available in the administration guide or in the instructions.html document that is created during deployment.

caution Migration is supported for this version. The metadata folder System\Applications\SAS Decision Services\Decision Services (version)\ is the new folder path for design and production repositories.
More information is available in the administration guide or in the instructions.html document that is created during deployment.

caution The migration of the design and production repositories is not complete. The design of the system resources has changed. Any artifacts must be added manually to the new design and production repositories after the SAS Deployment Wizard is complete.
More information is available in the administration guide or in the instructions.html document that is created during deployment.

caution The migration of the design and production repositories is not complete. The design of the system resources has changed. Any artifacts must be added manually to the new design and production repositories after the SAS Deployment Wizard is complete.
More information is available in the administration guide or in the instructions.html document that is created during deployment.

okay Migration is supported for this version. All sas activity xml in only the design and production repositories that were configured out of the box will be migrated to use the same system resource. You will need to manually migrate additional user repositories that you may have created. When manually migrating to 9.3, do not include the SAS connection type resources into your exported .spk files.
More information is available in the administration guide or in the instructions.html document that is created during deployment.

okay Migration is supported for this version. The message queue polling servers will be removed.
The queues configuration is deleted in this release.

okay Migration is supported for this version. The queue manager and queues metadata will be removed.
The queues configuration is deleted in this release.

okay Migration is not supported for this version. The dependency on a Websphere MQ Server has been removed.
The dependency on a Websphere MQ Server has been removed in the release.

okay The name of this product component has been changed to product-name.
This message is informational only. The component names have been changed.


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.