Pre-migration tasks
include backing up the source environment, preparing the new machine
for the migration (when applicable), and creating the migration package.
Follow these steps to prepare for the migration:
-
-
If you are migrating
to a different machine, use the appropriate pre-installation checklist
to prepare the machine. Preparation tasks include installing required
third-party software, creating required user accounts, and reviewing
port numbers. For details, see the following topics:
-
Create the migration
package. In this step, you use the SAS Migration Utility to analyze
the source environment. After correcting any detected issues, you
run the utility again to extract the source environment’s content
and configuration and create a migration package. Follow these steps:
-
Log on to the metadata
server host machine in the source environment, and navigate to the
directory that contains the SAS Migration Utility executables. By
default, the executables are located in the SAS Software Depot in
the path
utilities/smu
.
-
Open the utility template
file (smu.properties.template) in a text editor. Edit the file to
specify properties including the following:
-
fully qualified paths for the source
environment’s configuration directory (SMU.config.dir), the
SAS executable (SMU.SASROOT), the source environment’s SASHome
(SMU.SASHOME), and an output directory for the migration package (SMU.Output.Dir).
-
the metadata server host name (SMU.host.metadata),
administrative user ID (SMU.user), and administrative user password
(SMU.password) to access the source environment’s metadata
server; or the name of a connection profile (SMU.profile) that contains
this information. You must specify an unrestricted user (for example,
sasadm@saspw).
-
the user ID (SMU.webinfpltfm.dbms.userid)
and password (SMU.webinfpltfm.dbms.password) that can be used to open
a JBDC connection to the SAS Web Infrastructure Platform database
in the source environment. For JBoss Application Server, this information
is stored in
JBoss-Home/SASServer1/deploy/SharedServices-ds.xml
.
For WebLogic Server and WebSphere Application Server, see the server’s
administrative console.
-
Run the migration utility
in analyze mode, using the following command from an operating system
prompt or command line:
-
smu93_32 -analyze -properties absolute-pathname-to-properties-file -replace
-
smu93_64 -analyze -properties absolute-pathname-to-properties-file -replace
-
./smu93 -- -analyze -properties absolute-pathname-to-properties-file -replace
-
./smu93.zos -- -analyze -properties absolute-pathname-to-properties-file -replace
-
Check the migration
utility log file (migrate.log), which is located in your migration
package output directory. If the utility completed successfully, the
following messages should appear at the end of the log:
[INFO] SMU Product analyses completed
[INFO] SMU No packaging was performed due to the mode setting
-
Check the Migration
Analysis report (AnalysisReport.xml), which is located in the path
host-machine-name/Analysis
Report
within your migration package output directory.
Red Xs indicate error conditions that must be addressed before the
migration can be completed successfully. For an explanation of the
messages in this report, go to
http://support.sas.com/migration/utilitynotes
.
-
Correct any errors that
are reported in the migrate.log file or in AnalysisReport.xml, and
then rerun the migration utility in analyze mode. Repeat this process
until all error situations have been resolved.
-
Run the migration utility
using the same command that you used in step 4, but without the
-analyze
option.
The command creates the migration package. Check the migration utility
log file (migrate.log) and the Migration Analysis report (AnalysisReport.xml)
to verify that the migration package was created successfully.