SAS® BI Lineage Scheduling Server
For any updates or hot fixes that are required before you can migrate, see the
baseline requirements topic.
Messages
Deployed Jobs to
be manually defined:
- This message is followed by a list of deployed jobs that are defined in metadata in the previous deployment.
For information about post-migration tasks, see
SAS
Intelligence Platform: Migration Guide.
There are no
BI Lineage Java batch servers found in the metadata repository. Configure a server using SASMC.
- For information about post-migration tasks, see
SAS
Intelligence Platform: Migration Guide.
Java batch servers
not being migrated because the command line property does not conform to the default configuration location:
- This message is followed by a list of Java batch servers that are defined in metadata in the previous deployment.
For information about post-migration tasks, see
SAS
Intelligence Platform: Migration Guide.
Java batch servers to be migrated:
- This message is followed by a list of Java batch servers that are defined in metadata in the previous deployment.
This is an informational message and no action is necessary.
SAS BI Lineage Scheduling Server
migration is complete.
- This is an informational message and no action is necessary.
User modified file to be migrated:
- This message is followed by a list of files. This is an informational message and no action is necessary.
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.