Would you like to make the Migration Utility easier to use for your users?
There is a MappingInformation.xml file which can assist by completing the maps from old to new items (libraries, file references, information map locations, stored processes, etc) on pg 5 of the MigrationWizard.exe.
In order to implement this mapping, there is a multi step process.
Step 1. Create a MappingInformation.xml file.
The inital layout of this document is described by SAS on page: http://support.sas.com/documentation/cdl/en/enclient/61192/HTML/default/a003233727.htm
Note ~ There are NO xml end tags on this page so error messages will occur. Be sure to close EACH xml tag.
<NewMapping>SASApp:Test Library (TESTLIB)</NewMapping>
Store this in a shared location.
Step 2. Create a Migration Record file.
Included in this file is the reference for where the MappingInformation.xml is located.
Save this as MigrationRecord.mig in a shared location.
Step 3. Create a Migration Wizard Execution step for end users to run.
Include the path for Enterprise Guide and then the path for the Migration Record file created in step 2.
cd "C:\Program Files\SAS\EnterpriseGuide\4.2\"
Save as a .bat file in a shared location and make available to your Enterprise Guide users.
NOTE: It's important that the EG 4.2 Migration Wizard runs from within the same location as Enterprise Guide. If the first two lines of code are excluded, but you are saving & sharing this .bat file in another location (such as E:) you will see a number of issues with missing .dll files within Migration Wizard logs or Enterprise Guide itself.
Couple extra notes about using the Migration Wizard.
a. If you'd like to rearrange or change locations &/or names your source files (excel, text, libnames, etc) this tool makes it really easy. Of course, you need to reorganize BEFORE running this.
b. Be sure to SELECT all files associated with the .egp file during the migration process. For instance, if you fail to select that .xls file that is imported into EG then any Import Data modifications you had made previously could be LOST.
c. It appears that you CAN run this Wizard on a 4.2 file, but always keep a backup. (The last step, by default, doesn't select the 'Do not create a backup' option. I'd continue down that default path.)
d. Also note, if you are ONLY changing the SASMain to SASApp server, you could run the Migration Utility on the entire directory of .egp files. OR??? Why not stick with the SASMain server in your BI Configuration?