Migration to SAS Enterprise Guide 4.2

Using the Migration Wizard

The Migration Wizard enables you to migrate multiple projects to the SAS Enterprise Guide 4.2 format at one time. If you have the SAS Add-In 4.2 for Microsoft Office installed, the wizard also migrates files that are used with the SAS Add-In 2.1 for Microsoft Office, such as Microsoft Word files or Microsoft Excel files. You can use the wizard to identify the projects and documents that you want to migrate and specify new locations for objects in the migrated files. The wizard converts the projects and documents to the correct format and makes global changes to the changed object references.

In addition, you can use mapping files and a migration record file to supply information to the wizard.

Using the Wizard

To run the Migration Wizard, follow these steps:

Create all required metadata objects in metadata. If you need to create new metadata definitions for objects such as servers or libraries, you should create these definitions before you run the migration wizard. The wizard does not create any metadata definitions. If you run the wizard before you create new definitions, you will receive an error whenever you open a project that refers to a metadata object that has not been defined.
Navigate to the SAS Enterprise Guide installation directory (the default location is C:\Program Files\SAS\EnterpriseGuide\4.2). Start the wizard by double-clicking on MigrationWizard.exe or issuing the command from the command line.

Note: You must close all Microsoft Office applications before you run the Migration Wizard.
Follow the procedure in the wizard:
1. Page 1 provides an introduction to the wizard.
2. On page 2, verify that the active connection is correct. Click Modify to display the Connections dialog box, where you can change the active profile or create a new profile.
  
  If the selected connection contains information about SAS folders that have been moved or renamed as part of the SAS installation and migration process, click Import. The information that is imported from your connection is used by the Migration Wizard to automatically remap the location of SAS folders.
3. On page 3, select the files that you want to migrate. You can select files from local directories, servers, and SAS folders. Use the arrow to move files (preserving the tree structure) to the Selected Files area. Selecting a node such as a folder or a server automatically selects all files under that node. Expand the Local, Server, or SAS Folders nodes to locate individual files or directories. Use the Show field to select the type of files that are displayed. To access files on a remote machine, click Add Location. The Windows Add Network Drive dialog box is displayed, which enables you to map a network drive to a remote location.
  
  The Migration Wizard processes these types of files:
  - SAS Enterprise Guide Projects (*.egp)
  - SAS Web Report Studio Reports
  - Microsoft Excel files (*.xls)
  - Microsoft Word documents (*.doc)
  - Microsoft PowerPoint presentations (*.ppt)
  The SAS Add-In for Microsoft Office must be installed in order to migrate Microsoft Excel files and Microsoft PowerPoint presentations.
4. Page 4 provides an overview of the process of identifying object references that might need to be changed. When you click Next, the parsing process begins. The status of the process is indicated by a progress bar.
5. If the wizard finds a mapping file, it will ask whether you want to use it. A mapping file is an XML document that specifies correlations between old locations and new locations for objects. A mapping file enables you to specify the object mappings once and then have those mappings automatically applied in the wizard. By default, mapping files are stored in \\My Documents\Application Data\SAS\BI Clients\4.2\Migration .
6. Page 5 lists all of the metadata objects that are referenced in the selected files, identifies their type, and provides the currently specified location of the object. To change the mapping for an object, click in the New Mapping column for the object, click the button in the field to open the Change Resource dialog box, and enter a new location or browse to the new location. You can also choose to automatically apply the new location to all objects in the migration list that use the current value. No changes are made until the wizard completes.
7. On page 6, you can specify the name of the migration record file, which contains all of the settings that are specified in the wizard. If you specify the migration record file as a parameter when you run the Migration Wizard from the command line, the wizard will be initialized with all of the settings that you used when the file was created. You can also specify the location of a log file and specify whether files will be backed up before conversion.By default, migrated files are backed up and the original files are overwritten.
  
  You can specify that the migration process attempts to verify that the new resources exist and note the status in the log. The changes are applied whether or not the resources are verified. In order to accurately verify the remappings, you must have Read permissions in metadata for objects such as servers and libraries and operating system Read permissions for file locations. Click Finish to migrate the selected files.

Mapping File Format

The following is the format of the mapping file that is used to identify correlations between old and new locations for metadata objects. This file must be named MappingInformation.xml and stored in \\My Documents\Application Data\SAS\BI Clients\4.2\Migration . Include as many <MappedItem> blocks as needed to change the mapping for all affected objects. The format of MappingInformation.xml is as follows:

<MappingInformation>
		<MappedItem>
			<ReferenceName>server name
			<ReferenceID>server ID
			<ReferenceType>Server
			<CurrentMapping>old server definition
			<NewMapping>new server definition
		
		<MappedItem>
			<ReferenceName>library name
			<ReferenceID>library ID
			<ReferenceType>LIBRARY
			<CurrentMapping>old library definition
			<NewMapping>new library definition
		
		<MappedItem>
			<ReferenceName>stored process name
			<ReferenceID>stored process ID
			<ReferenceType>SAS.EG.ProjectElements.StoredProcess
			<CurrentMapping>old stored process definition
			<NewMapping>new stored process definition
		
		<MappedItem>
			<ReferenceName>external file name
			<ReferenceID>external file ID
			<ReferenceType>SAS.EG.ProjectElements.ExternalFile
			<CurrentMapping>old external file definition
			<NewMapping>new extenal file definition
		
		<MappedItem>
			<ReferenceName>information map
			<ReferenceID>information map ID
			<ReferenceType>SAS.EG.ProjectElements.InformationMap
			<CurrentMapping>old information map definition
			<NewMapping>new information map definition
		
		<MappedItem>
			<ReferenceName>OLAP catalog name
			<ReferenceID>OLAP catalog ID
			<ReferenceType>OLAPCATALOG
			<CurrentMapping>old catalog definition
			<NewMapping>new catalog definition
			<OLAPCatalogName>old OLAP catalog name
			<OLAPServerName>old OLAP server name
			<OlapServerType>old OLAP server type
			<OlapProviderName>old OLAP provider
			<OlapLoginMode>old login mode
			<OlapExtProperties>extended properties for connecting to the OLAP server
			<OlapHostName>old host name
			<OlapPort>old port
			<NewOLAPCatalogName>new OLAP catalog name
			<NewOLAPServerName>new OLAP server name
			<NewOlapServerType>new OLAP server type
			<NewOlapProviderName>new OLAP provider
			<NewOlapLoginMode>new login mode
			<NewOlapExtProperties>new extended properties for connecting to
			the OLAP server
			<NewOlapHostName>new host name
			<NewOlapPort>new port
		
		<MappedItem>
			<ReferenceName>OLAP server name
			<ReferenceID>OLAP server ID
			<ReferenceType>OLAPSERVER
			<CurrentMapping>old server definition
			<NewMapping>new server definition
			<OLAPServerName>old OLAP server name
			<OlapServerType>old OLAP server type
			<OlapProviderName>old OLAP provider
			<OlapLoginMode>old login mode
			<OlapExtProperties>extended properties for connecting to the
			OLAP server
			<OlapHostName>old host name
			<OlapPort>old port
			<NewOLAPServerName>new OLAP server name
			<NewOlapServerType>new OLAP server type
			<NewOlapProviderName>new OLAP provider
			<NewOlapLoginMode>new login mode
			<NewOlapExtProperties>new extended properties for connecting to
			the OLAP server
			<NewOlapHostName>new host name
			<NewOlapPort>new port
		
		
(repeat as needed for all objects)
<MappingInformation>

Initializing the Wizard by Using a Migration Record File

You can create a migration record file when you run the Migration Wizard. This file contains a record of all of the information that is provided in the wizard. If you start the Migration Wizard from the command line and specify the migration record file as a parameter, the wizard will be initialized with the same settings that you used when the file was created.

To create a migration record file, specify a name for the file on the last page of the Migration Wizard.

To run the wizard and specify the migration record file, issue this command from a command line:

MigrationWizard <migration record file>

Top of Page