If you have not modified
your service architecture configuration, the SAS Environment Manager
2.5 update process will update your service architecture without you
needing to make any changes. However, if you modified your original
service architecture, you must make these changes when updating:
-
If you stored content in the metadata
folders that were used by the report center, the update process exported
that content as a SAS package file, then deleted the folders. To recover
the content, use the metadata import wizard in SAS Management Console
to import SASEVProductsFolderBackup.spk,
which is in the SASPackages subdirectory
under the update backup directory. The update backup directory is
named \emi-framework_date_time,
where date and time correspond
to the date and time at which the update process began.
-
If you used the SAS Management
Console Configuration Manager plug-in to change the service architecture
configuration properties, those changes might have been overwritten.
Review the current configuration settings and make changes where needed.
-
If you used a method such as soft
link or NFS mounts to locate the data mart libraries at a location
other than the default, you must review the updated data mart to determine
whether the data was successfully moved. If it was not moved, re-establish
the redirection and run the ugipInit script to restructure the data.
-
If you modified any of the LIBNAME
statements in the service architecture autoexec files, those changes
were overwritten, so you will need to make the corresponding changes
in the new autoexec files. You can refer to the old files, which are
located in the backup directory, but you cannot replace the new files
with the old files. Doing so will cause the service architecture to
not work.