These packages contain all of the current SAS content—data and configuration—
residing on a machine. Later in the migration process, the SAS Deployment Wizard uses these migration packages to populate your SAS 9.4 deployment.
In addition to creating migration analysis reports, the SAS Migration Utility creates migration packages. A migration package contains all of the current SAS content from your deployment. Migration utility output (see Figure 2.1 on page 22) consists of data and configuration that resides on each machine in your deployment. In a multi-machine environment, each time you run the migration utility, the utility adds the local machine’s SAS content to build one, multi-machine migration package. Later in the migration process, the SAS Deployment Wizard uses the migration package to populate your SAS 9.4 deployment.
Note: If you downloaded the SAS Migration Utility before receiving your SAS 9.4 order, you should now use the migration utility that is provided in your order. The version of the SAS Migration Utility that is included with your SAS 9.4 order is
guaranteed to be compatible with the versions of the SAS products that you have ordered.
To create a migration package, follow these steps:
CAUTION:
The migration utility pauses the metadata server when it creates a migration package, so any attempts to use your current SAS system during this period will be unsuccessful. Therefore, you should plan accordingly.
1. Review the migration utility requirements. (See “SAS Migration Utility Requirements” on page 21.)
2. Make sure that you have backed up your current SAS Metadata Repository.
For more information, see “Back Up Your Current SAS System” on page 38.
3. If you have not already, complete a migration utility checklist. (See “Complete a Migration Utility Checklist” on page 18.)
4. Make sure that you have prepared your metadata repositories before you create a migration package on the metadata tier. (See “Prepare Your Metadata Repositories”
on page 20.)
5. Verify that the current SAS Metadata Server is running.
6. If you have multiple machines in your SAS deployment, then you have to run the migration utility once on each machine. (Always run the migration utility on the metadata server first.)
7. If you are creating a migration package on a middle tier machine, verify that the following applications are running:
SAS Middle-Tier Machine Applications That Must Be Running
SAS 9.2 SAS Shared Services database
By default, this database is the SAS Table Server.
However, this database can also be a third-party database.
On JBoss Application Server systems, either all web applications are running or all are shut down.
However, in order for the migration utility to copy the SAS Content Server content, the SAS Content Server must be stopped. To solve this dilemma, set the SMU.scs.allow.sync property to TRUE.
This pauses the migration utility and gives you an opportunity to stop the JBoss Application Server and then restart it after the utility has copied the repository. On systems that use WebSphere and WebLogic web application servers, you can shut down the SAS Content Server only. For more information, see “Sample Migration Utility Properties File” on page 151.
SAS 9.3 SAS Web Infrastructure Platform database
In SAS 9.3, the SAS Infrastructure Platform and SAS Shared Services has been combined.
SAS Middle-Tier Machine Applications That Must Be Running
SAS 9.4 All data servers in your SAS environment, including the SAS Web Infrastructure Platform database
8. Log on to the current SAS machine (the source machine) whose SAS content you want to migrate.
Note: On SAS multiple machine deployments, run the migration utility first on the machine hosting the SAS Metadata Server.
9. If the version of the migration utility that you are using has changed from one that you have used previously, then be sure to delete the migration utility's output directory.
10. Change to the SAS Migration Utility executable directory. By default, this is the smu-version subdirectory under the utilities directory in your SAS Software Depot.
11. Review the section, “smu Command Notes” on page 145.
12. Use the common migration utility properties file and the common connection profile that you have developed, unless the source machine requires any special
modifications.
(For example, SAS is installed on a nonstandard path.)
For more information, see “Develop a Common SAS Migration Utility Properties File” on page 23.
13. Add any necessary product-specific migration utility properties to your properties file. (See “Review Product-Specific SAS Migration Utility Properties” on page 25.) 14. If you have migration packages from any earlier migration utility invocations, delete
or move these packages before rerunning the migration utility.
15. Invoke the migration utility on the machine with the metadata server, using the following command from an operating system prompt or command line that is appropriate for your version of SAS and your operating system.
Note: On UNIX and z/OS, if you have not already, remember to assign file Execute permissions to smu.sh and smu.zos before attempting to run the migration utility.
For more information, refer to your UNIX or z/OS documentation.
If you have a multi-tier SAS deployment, you will need to run the migration utility once on each machine. (Do not run the migration utility on middle-tier cluster machines and machines that only contain SAS clients.) There are specific migration utility options, depending on the tier. For more information, see “SAS Migration Utility Overview” on page 139.
Note: You cannot run the migration utility on more than one machine
simultaneously, because the migration schema might be updated by more than one process at the same time.
Use the -replace option if the migration utility writes to the output directory used in earlier invocations:
SAS 9.2 on Windows 32-bit
smu92_32 properties absolute pathname to property file -replace
SAS 9.2 on Windows 64-bit
smu92_x64 -properties absolute pathname to property file -replace
SAS 9.3 on Windows 32-bit
smu93_32 properties absolute pathname to property file -replace
SAS 9.3 on Windows 64-bit
smu93_x64 -properties absolute pathname to property file -replace
SAS 9.4 on Windows 32-bit
smu94_32 properties absolute pathname to property file -replace
SAS 9.4 on Windows 64-bit
smu94_x64 -properties absolute pathname to property file -replace
SAS 9.2 on UNIX
./smu92 -- -properties absolute pathname to property file -replace
SAS 9.3 on UNIX
./smu93 -- -properties absolute pathname to property file -replace
SAS 9.4 on UNIX
./smu94 -- -properties absolute pathname to property file -replace
SAS 9.2 on z/OS
./smu92.zos -- -properties absolute pathname to property file -replace
SAS 9.3 on z/OS
./smu93.zos -- -properties absolute pathname to property file -replace
SAS 9.4 on z/OS
./smu94.zos -- -properties absolute pathname to property file -replace
• For more information about migration utility commands, see “SAS Migration Utility Overview” on page 139.
For more information about migration utility properties files, see “Develop a Common SAS Migration Utility Properties File” on page 23.
16. Review the migration analysis report to ensure that the migration package was properly created. Point a web browser to FullReport.html in the AnalysisReport subdirectory underneath the output directory that you specified in the migration utility properties file.
Note: Address any issues identified in your analysis report. Any errors or warnings might mean that your SAS deployment is unsuitable for migration. Consult http://support.sas.com/notes/index.html for SAS Notes pertaining to any specific warnings.
17. After you have created the migration package, make a backup of the package.
Backups are especially recommended in multi-tier deployments. If the package
creation fails for one tier, you can restore the package to the last successful version, without having to rerun the migration utility on every tier again.
18. If you have a multi-tier SAS deployment, you will need to run the migration utility on each machine. (Do not run the migration utility on middle tier cluster machines and machines that contain only SAS clients.) There are specific migration utility options, depending on the tier. For more information, see “SAS Migration Utility Overview” on page 139.
Note: You cannot run the migration utility on more than one machine
simultaneously, because the migration schema might be updated by more than one process at the same time.
Note: Later, the user ID under which the SAS Deployment Wizard runs must have Write permission for the SAS Content Server directories in the migration package on UNIX. For more information, see “Installer Permissions on the Content Server Migration Package on UNIX or Linux” on page 77.