Running the Migration Utility Using a Properties File

Overview of Running the Migration Utility Using a Properties File

The following topics are contained in this section:

Run the Migration Utility Using a Properties File

An alternative to supplying SAS Software Migration Utility invocation options on the command line is to provide these options in the form of a properties file. You do this by creating a file containing values for the various migration utility properties you want to use and saving this file in the same directory where the migration utility batch or script file resides. For information about product-specific properties, see Review Product-Specific SAS Migration Utility Properties.

Note: SAS supplies a migration utility template file (smu.properties.template) that provides examples for how to use various properties. You can find this file in your SAS Software Depot in the smu subdirectory underneath utilities.

When you run the migration utility, you reference your properties file with the -properties command-line option. For example:

smu -s -a -properties "C:\SAS Software Depot\utilities\smu\mid_tier.properties" -replace

smu92_32 -properties "C:\SAS Software Depot\utilities\smu2\mid_tier.properties" -replace

smu92_x64 -properties "C:\SAS Software Depot\utilities\smu2\mid_tier.properties" -replace

smu93_32 -properties "C:\SAS Software Depot\utilities\smu3\mid_tier.properties" -replace

smu93_x64 -properties "C:\SAS Software Depot\utilities\smu3\mid_tier.properties" -replace

The migration utility enables you to use a combination of properties and command-line options. For example:

smu -s -a -analyze -profile myhost
-properties "C:\SAS Software Depot\utilities\smu\mid_tier.properties" -replace

smu92_32 -analyze -profile myhost
-properties "C:\SAS Software Depot\utilities\smu2\mid_tier.properties" -replace

smu92_x64 -analyze -profile myhost
-properties "C:\SAS Software Depot\utilities\smu2\mid_tier.properties" -replace

smu93_32 -analyze -profile myhost
-properties "C:\SAS Software Depot\utilities\smu3\mid_tier.properties" -replace

smu93_x64 -analyze -profile myhost
-properties "C:\SAS Software Depot\utilities\smu3\mid_tier.properties" -replace

In migration utility properties files, when specifying Windows paths or domains as a part of a user ID, you must escape any backslashes (\) with another backslash character. For example:

SMU.config.dir=C:\\SAS\\config\\913BIPlatform\\Lev1
SMU.user=mydomain\\sasadm

The migration utility recognizes the pound sign (#) as the comment character, when it is used as the first character in a line.

Sample Migration Utility Properties File

Below is the listing of a sample migration utility properties file with comments that describe each property:

Note: Migration utility properties are case-sensitive.

# Sample smu.properties file
#
# Specifies the absolute path of the current SAS configuration directory that
# the migration utility reads from.  This should usually be the "Lev" directory.
# It usually contains a SASMain, Data, and product directories.
#
SMU.config.dir=C:\\SAS\\MetadataServer\\Lev1
SMU.config.dir=/users/sas/SAS/913BIPlatform/Lev1


# Specifies the path to sas.exe that is used by the current SAS Metadata Server.
# Required if SMU.SASHOME is not used.
#
SMU.SASROOT=C:\\Program Files\\SAS\\SAS 9.1
SMU.SASROOT=/usr/local/SAS/SAS_9.1


# Specifies the pathname to the top-level directory where the current SAS 
# products are installed.
#
SMU.SASHOME=C:\\Program Files\\SAS
SMU.SASHOME=/usr/local/SAS


# Specifies the path of the current SAS configuration directory that the
# migration utility ignores. This property can be used for sites that have
# enormous amounts of data to migrate. The specified path can be absolute
# or relative to the SAS configuration directory. 

# levconfig.exclude.dir.12BYTE.1=AppData
# levconfig.exclude.dir.12BYTE.2=C:\\SAS\\Config93\Lev1\\SASApp
#  \\SASEnvironment\\test\\test1
# levconfig.exclude.dir.12BYTE.3=/opt/SAS/Config/Lev1/SASApp
#  /SASEnvironment/test/test1 


# The metadata server host.  This must be defined for the migration utility to
# run successfully.  The port defaults to 8561.  If a different metadata port
# was used, set SMU.port.metadata to the correct port.
#
SMU.host.metadata=metadata.example.com
#SMU.port.metadata=8561


# The metadata server administrative user and password.  This must be an 
# unrestricted user so all data can be read for metadata extraction.  The 
# password can be regular text or you can encode it using PROC PWENCODE with
# the {sas001} method (SAS 9.1.3) or with the {sas002} method (SAS 9.2 and 
# later).
#
#SMU.user=mydomain\\adminuser
SMU.user=adminuser
SMU.password={SAS002}FA0C32065CB6E9B3352EEF8431205759


# A workspace profile is acceptable as an alternative to providing the host,
# port, user and password (if the password is in the profile).  This can be just
# the profile name--which will look in the default location and the current 
# working directory--or a full path to the profile.
#
#SMU.profile=MyServer


# Specifies the absolute path to the directory where migration utility should
# write its output (package).  The migration utility creates this directory 
# when you run the utility on the metadata server tier.  When you run the utility
# on the metadata server tier without specifying an output directory, the utility 
# creates the directory for you in the current working directory with a name of 
# YYYYmmmDDHHmmss (for example, # 2011Dec30095705).
#
# When you run the migration utility on a SAS tier, the output directory should
# already contain the migration package from the metadata tier and packages from
# any other tiers on which you ran the utility. The packages from every tier in
# your SAS deployment should be included under the same output directory.
#
# SMU.Output.Dir=/home/sas/smu_packages/metadata_tier
# SMU.Output.Dir=C:\\SMU_packages\\metadata_tier


# Causes the migration utility to extract any WebDAV content that it locates.
# Use either the SMU.DAV.* properties or the SMU.WFS.XythosHome property.  If
# you want to re-use this properties file, we recommend that you not use 
# SMU.isdavtier but instead specify -davtier on the smu command line.
#
#SMU.isdavtier=true


# Specifies the absolute path where the Xythos Web File Server is installed.
# Specifying this property causes the WebDAV content to be extracted using a
# Xythos-specific mechanism that is more efficient than using standard DAV 
# extraction.
#
#SMU.WFS.XythosHome=C:\\Program Files\\SAS\\xythos\\2.2
#SMU.WFS.XythosHome=/usr/local/SAS/xythos/2.2


# The host where the Xythos server is running.  This is used to help migrate
# items in a Xythos DAV server to the SAS Content Server.  If this is omitted, the
# migration process uses a best guess as to which server represents the Xythos
# server.
#
#SMU.xythoshost=davnode.example.com


# The port on which the Xythos server is listening.  This was 8300 in SAS 9.1.3
# by default.  If your site uses a different port, specify it here.  This 
# property is used to help migrate items in a Xythos DAV server to the SAS 
# Content Server.  When you omit this property, the migration utilty uses the
# default port (8300).
#
#SMU.xythosport=8301


# If a non-Xythos WebDAV server is being used at a site, (such as Apache HTTP
# Server) and you want to migrate this content, use these properties.
#
# Specify user credentials with sufficient read permission with which the 
# migration utility can content to the WebDAV server to extract content.
#
#SMU.DAV.User=
#SMU.DAV.Password=


# The DAV URL for the root of the WebDAV data.
#
#SMU.DAV.URL=http://davnode.example.com:8300/sasdav


# Explicitly sets the machine host name on which the migration utility is
# running.  Use for machines that have multiple network interfaces or a dynamic
# name.  Specify a fully qualified host name for the machine.
#
# SMU.localhost=myserver.example.com


# Specify the user ID and password with which the migration utility can open a
# JDBC connection to the Shared Services database.  (In SAS 9.3, this is 
# referred to as the Web Infrastructure Platform database.) 
# 
# For sites using the JBoss Application server, the connection credentials are
# stored here:
# 
#   <JBoss-home>/SASServer1/deploy/SharedServices-ds.xml
# 
# For sites using WebLogic Server or Websphere Application Server, use the
# respective admin console to determine the correct JDBC connection credentials.
# 
# You can use regular text to specify the password or encode it using proc
# pwencode with the {sas002} method.
#
#SMU.webinfpltfm.dbms.userid=myDatabaseUserID
#SMU.webinfpltfm.dbms.password={SAS002}DBCC571245AD0B31433834F80BD2B99E16B3C969


# When migrating from SAS 9.2 only, in order for the SAS Content Server content 
# repository to be copied, the content server Web application has to be stopped.  
# This property pauses the migration utility and prompts the user to stop the 
# application.  After the copy is made, the migration utility pauses again and 
# prompts the user to restart the application.
#
# When this property is false, and a lock on the repository is detected in the
# analysis process, the migration utility writes an error message in the 
# analysis report and does not copy the repository content.
#
#SMU.scs.allow.sync=true


# These properties indicate SAS Content Servers whose repositories have been
# customized by the user. 
#
#scs.jndi.jndiName=
#scs.jndi.driver=
#scs.jndi.jdbcUrl=
#scs.jndi.user=
#scs.jndi.pwd=
#scs.jndi.jdbcdir=


# Set this property to true, when multiple SAS tiers are deployed on the same
# machine and require you to run the migration utility multiple times on this
# machine.
#SMU.isMultipleTierMachine=true


# Specifies non-standard locations for SAS application data sets and catalogs
# for the migration utility to move.
#
# The utility packages these directories in the levconfig output folder in the 
# "userdirs" subdirectory.
#
# List absolute paths or paths relative to the SAS configuration directory. 
# Separate multiple paths with a comma.
#
#levconfig.user.dirs=my_SAS_solution_data_sets,my_SAS_solution_catalogs,
# C:\my_data\my_SAS_solution_misc


# The Analytics Platform core install directory. The value provided
# here is the default installation path. If your AP was installed to
# a different location set this value to your path.
#
# If you are migrating Analytics Platform applications, youll also need
# to enable their migration by setting SMU.apcore.migration.is_enabled
# to true.
#
#SMU.apcore.dir=C:\\Program Files\\SAS\\SASAPCore
#SMU.apcore.migration.is_enabled=false


# This property is used by the SAS Deployment Wizard to verify the version of
# the migration utility that was used to create a migration package.
#
# DO NOT CHANGE THIS VALUE.
#
SMU.version=2.0
SMU.SAS.version=9.2