1. Cross platform Migration of SAS BI Environment: Tips and Tricks
Amol Deshmukh
California ISO Corporation

2. When do we need cross platform migration?
Server or storage technology replacement or upgrade
Server or storage consolidation
Relocation of the data center
Workload balancing or other performance-related
maintenance

3. Challenges to consider when migrating SAS BI
Server:
Performance
Primary volume/source data protection
Different storage medium
Different hardware platforms
Application downtime
Data corruption, missing data or data loss
Technical compatibility issues

4. SAS BI Migration Lifecycle
ASSES
•
•
BI Assesment
Existing Deployment Assesment
•
•
•
•
•
•
Roles and responsibilities
Obtain SID files , Deployment Plan , Checklists and Software Depot
Hardware requirement :Storage , RAM , CPU , IO considerations
Create all user IDs and groups
Ports
3rd party software : JDK , JBOSS , Database Clients
INSTALLATION &
CONFIGURATION
•
•
•
•
Installation
Post installation configuration
Hot Fix Installation
Validation
MIGRATION
•
•
•
•
User Metadata Migration
Metadata Objects Migration
Web Content Server Migration
SAS Datasets & code Migration
VALIDATION
•
•
•
Validation
Training
Cutover
PLAN

5. SAS BI Migration Lifecycle

6. ASSESS
BI Assessment
 Determine future needs
 Evaluate new features/products offered by SAS and see if they can
satisfy analytical requirements in future.
Existing deployment Assessment
 Identify issues associated with existing deployment
 Identify root causes for these issues/problems and find the solution for
them. ( If needed work with SAS Tech Support Team)
 Compile list of different application components as well as metadata
objects available in existing deployment

7. Metadata Objects assessment utility
options metaserver='your.hostname.com'
metaport=8561
metaprotocol='bridge'
metauser='sasadm@saspw'
metapass='encrypted(or not)-pw-here'
metarepository='Foundation'
;
Macro MDSECGO extracts information for a
specified set of objects. You specify one folder
and indicate whether to include subdirectories.
You can also provide a list of object types to
include and filter the data set by attribute
value.
%mdsecgo
(folder="/",
includesubfolders=YES,
membertypes="STOREDPROCESS,REPORT,INFORMATIONMAP,INFORMATIONMAP.RELATIONAL,INFORMATI
ONMAP.OLAP,DASHBOARD,CUBE,ACT",
memberfilter="",
objdata=M2_objects);
PROC FREQ DATA=m2_objects
ORDER=INTERNAL;
TABLES PublicType / SCORES=TABLE;
where publictype not in ("RootFolder", "Folder");
RUN;

8. SAS BI Migration Lifecycle

9. PLAN
Decide Roles and Responsibilities
Acquire Licenses and Software
If needed request for customized deployment plans which
will address organizations needs.

A deployment plan file is a Role wise/machine wise
election of the software which will be installed and configured
by the SAS installation wizard.
Fulfill Hardware requirement
Solve hardware related issues identified in assessment
phase.
Third party Software installation :JDK/JRE , JBOSS Server ,
Database Clients

10. SAS BI Migration Lifecycle

11. INSTALLATION & CONFIGURATION
Installation of SAS Software using SAS Deployment Wizard
"So You Want to Install SAS®?" by Rafi Sheikh to perform
installation and configuration.
Post installation configuration
Hot Fix Installation using “SAS Hot Fix Analysis, Download
and Deployment” Tool (SASHFADD)
Validation

12. SAS BI Migration Lifecycle

13. MIGRATION
 User identities & Group/Role metadata Migration
 MDUEXTR : Extract metadata identities & Groups in the
form of canonical tables from source Metadata Server &
Target Metadata Server.
 MDUCMP : Compare Metadat a identities and apply
exceptions
 MDUCHGV: Validate the changes you made to default
entries
 MDUCHG1 : Update the Metadata Identity.

14. MIGRATION
 Metadata Objects Migration using promotion
wizard
 Export SAS Package and Import SAS package wizard
available in Folders tab of SAS Management Console
 allows partial promotions using the filters which allows you
to promote metadata objects based on name, metadata
object type and change timestamps.
Batch Export/Import processes
 allows you to promote a collection of metadata objects
from one metadata to another without any user interaction
 Tools ExportPackage.exe and ImportPackage.exe can be
found within the “commands” directory of your SAS
Management Console install

15. MIGRATION
Portal content promotion
 Promote Entire Application Tree
 Migrate WebDAV Server contents
Migrate WebDAV Server contents such as directories,
contents and properties , we need to use WebDAVDump
and WebDAVRestore utilities.
These utilities are stored in below given directory
<SAS_CONFIG>Lev1WebUtilities

16. Promotion process for entire Portal Application
Tree
Promote the Entire Portal Application Tree
Prepare Source
System
Set environment
variables for
SAS_HOME and
JAVA_HOME
Validation
Import Portal
Application Tree
Prepare Target System
Backup Source
system
Extract Portal
Application Tree
Migration
Backup Target
system
Set environment
variables for
SAS_HOME and
JAVA_HOME
Apply the Portal ACT
to the Portal
Application Tree
Edit the source copy of the PortalPromotion
PortalApplicationTree.xml file so that it points to
the source metadata repository by changing
ReposId parameter to metadata repository 's ID
Extract Portal Application Tree
using script
extractPortal version
.sh
Edit the source copy of
the PortalPromotion
PortalApplicationTree.xml file so
that it points to the Target metadata
repository by changing
ReposId parameter to metadata
repository 's ID
import Portal Application Tree
using script
importPortal 92.sh
Validate portal
contents
PortalApplicationTree_deployFile.xml
PortalApplicationTree_expand.xml
PortalApplicationTree_extract.xml
extract.log
Edit the source of
the PortalApplicationTree_deployFile .xm
l file so that it points to the Target
metadata repository by changing
RepositoryBase Deploy _Id parameter
to metadata repository 's Idand target
system’s Metadata name as
Deploy _Name parameter
Import
.log
Copy output Files to
target System
Remove any existing Portal
Application Tree using script
removePortal 92.sh

17. Portal Content Migration :
WebDAVDump.sh
Zip file containing all the
contents and W FSD ump.xml
WebD AVRestore.sh
Zip file containing all the
contents and
W FSD ump.xml coped from
source system
Target System
Source System
If you are migrating any custom contents, you have to rebuild the
web applications and then redeploy them. Below given script would
be used to rebuild SAS Web Application :
SAS-installation-directory/SASDeploymentManager/9.2/config.sh

18. SAS Datasets & code Migration
PROC CPORT/CIMPORT : Catalog Migration
PROC Migrate : Datasets Migrations
Code : Copy entire program with modifications reflecting
changes in directory structure.

19. SAS BI Migration Lifecycle

20. VALIDATION & CUTOVER
Validation
Training
Cutover

21. Contact Information
Name
: Amol V Deshmukh
Enterprise: California ISO Corporation
Address : 250 , Outcropping Way
City, State ZIP: Folsom CA 95630
E-mail
: dav.amol@gmail.com