smu Command Examples :: SAS(R) 9.3 Intelligence Platform: Migration Guide

Example 1: Basic, Two-Phase Migration Utility Invocation

In this example on Windows (64-bit), 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:

Migrating from SAS 9.1.3

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

Migrating from SAS 9.2 (64-bit)

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

Migrating from SAS 9.3 (64-bit)

smu93_x64 -profile md1234 -sasconfigdir C:\SAS\BIServer\Lev1 
-sasproductdir "C:\Program Files\SASHome"
-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 (32-bit), 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:

Migrating from SAS 9.1.3

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

Migrating from SAS 9.2 (32-bit)

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

Migrating from SAS 9.3 (32-bit)

smu93_32 -profile md1234 -sasconfigdir C:\SAS\BIServer\Lev1
-sasproductdir "C:\Program Files\SASHome"
-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. The migration utility writes the analysis report to SMU.Output.Dir/tier/AnalysisReport:

Migrating from SAS 9.1.3

./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

Migrating from SAS 9.2

./smu92 -- -sasconfigdir /opt/SAS/config/Lev1
-sasproductdir /opt/SAS -profile md1234
-outputdir "/home/sas/smu_packages" -tier server_tier
-replace -analyze

Migrating from SAS 9.3

./smu93 -- -sasconfigdir /opt/SAS/config/Lev1
-sasproductdir /opt/SASHome -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:

Migrating from SAS 9.1.3

./smu.sh --
-properties
/opt/sas_9.3/SAS_Software_Depot/utilities/smu/myhost.properties

-replace

Migrating from SAS 9.2

./smu92 --
-properties
/opt/sas_9.3/SAS_Software_Depot/utilities/smu2/myhost.properties

-replace

Migrating from SAS 9.3

./smu93 --
-properties
/opt/sas_9.3/SAS_Software_Depot/utilities/smu3/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 Running 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:

Migrating from SAS 9.1.3

./smu.sh --
-properties
/opt/sas_9.3/SAS_Software_Depot/utilities/smu/myhost.properties

-davtier -replace

Migrating from SAS 9.2

./smu92 --
-properties
/opt/sas_9.3/SAS_Software_Depot/utilities/smu2/myhost.properties

-replace

Migrating from SAS 9.3

./smu93 --
-properties
/opt/sas_9.3/SAS_Software_Depot/utilities/smu3/myhost.properties

-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.

-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 Running the Migration Utility Using a Properties File.