SAS Migration Utility Reference

smu Command Examples

Example 1: Basic, Two-Phase Migration Utility Invocation

In this example on Windows, the migration utility executes both its phases--creating a migration analysis report and a migration package. The migration utility uses information in the connection profile named md1234.swa to communicate with the SAS Metadata Server:

smu -s -a -profile md1234 -sasconfigdir C:\SAS\BIServer\Lev1 
-sasproductdir "C:\Program Files\SAS" 
-outputdir C:\SMU_packages\host1234 -replace

-replace is specified to make sure that any output from a previous migration utility session--that might have specified the same output directory and tier name--is overwritten.

Example 2: Two-Phase Migration Utility Invocation With Output Preferences

In this example on Windows, the migration utility executes both its phases and creates a migration analysis report and a migration package in an output directory named server_tier@host1234.example.com that is a child of a parent directory named C:\SMU_packages. The migration utility uses information in the connection profile named md1234.swa to communicate with the SAS Metadata Server:

smu -s -a -profile md1234 -sasconfigdir C:\SAS\BIServer\Lev1 
-sasproductdir "C:\Program Files\SAS" 
-outputdir "C:\SMU_packages" -tier server_tier -replace

-replace is specified to make sure that any output from a previous migration utility session--that might have specified the same output directory and tier name--is overwritten.

Example 3: Report-Only Migration Utility Invocation

In this example on UNIX, the migration utility executes its analyze phase only, and creates a migration analysis report in an output directory named server_tier@host1234.example.com that is a child of a parent directory named /home/sas/smu_packages. The migration utility uses information in the connection profile named md1234.swa to communicate with the SAS Metadata Server:

./smu.sh -- -sasconfigdir /users/sas/SAS/sas_913/config/Lev1 
-sasproductdir /usr/local/SAS/SAS_9.1 -profile md1234 
-outputdir "/home/sas/smu_packages" -tier server_tier 
-replace -analyze

-replace is specified to make sure that any output from a previous migration utility session--that might have specified the same output directory and tier name--is overwritten.

Example 4: Migration Utility Invocation Using a Properties File

In this example on UNIX, the migration utility executes both its phases and creates a migration analysis report and a migration package. All of the required inputs are supplied to the migration utility in the form of properties contained in a text file named myhost.properties:

./smu.sh  -- 
-properties /opt/sas_9.2/SAS_Software_Depot/utilities/smu/myhost.properties 
-replace

-replace is specified to make sure that any output from a previous migration utility session--that might have used the same properties file--is overwritten. For more information, see Run the Migration Utility Using a Properties File.

Example 5: Migration Utility Invocation Using a Properties File on the WebDAV Tier

In this example on UNIX, the migration utility executes both its phases and creates a migration analysis report and a migration package on the machine that contains WebDAV content. All of the required inputs are supplied to the migration utility in the form of properties contained in a text file named myhost.properties:

./smu.sh  -- 
-properties /opt/sas_9.2/SAS_Software_Depot/utilities/smu/myhost.properties 
-davtier -replace

The properties file contains either the SMU.DAV.* properties or the SMU.WFS.XythosHome property. The SMU.WFS.XythosHome property causes the migration utility to extract DAV content using a Xythos-specific mechanism that is more efficient than using standard DAV extraction with the SMU.DAV.* properties.

Top of Page