Cross platform Migration of SAS BI Environment: Tips and Tricks Amol Deshmukh California ISO Corporation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Cross platform Migration of SAS BI Environment: Tips and Tricks
Amol Deshmukh California ISO Corporation
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
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
SAS BI Migration Lifecycle
INSTALLATION & CONFIGURATION
MIGRATION
VALIDATION
PLAN
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 Post installation configuration Hot Fix Installation Validation
User Metadata Migration Metadata Objects Migration Web Content Server Migration SAS Datasets & code Migration
Validation Training Cutover
SAS BI Migration Lifecycle
ASSESSBI 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
Metadata Objects assessment utility
options metaserver='your.hostname.com'metaport=8561metaprotocol='bridge'metauser='sasadm@saspw'metapass='encrypted(or not)-pw-here'metarepository='Foundation';
%mdsecgo (folder="/", includesubfolders=YES,membertypes="STOREDPROCESS,REPORT,INFORMATIONMAP,INFORMATIONMAP.RELATIONAL,INFORMATIONMAP.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;
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.
SAS BI Migration Lifecycle
PLANDecide Roles and ResponsibilitiesAcquire 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
SAS BI Migration Lifecycle
INSTALLATION & CONFIGURATIONInstallation of SAS Software using SAS Deployment Wizard
"So You Want to Install SAS®?" by Rafi Sheikh to perform installation and configuration.
Post installation configurationHot Fix Installation using “SAS Hot Fix Analysis, Download
and Deployment” Tool (SASHFADD) Validation
SAS BI Migration Lifecycle
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.
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 interactionTools ExportPackage.exe and ImportPackage.exe can be
found within the “commands” directory of your SAS Management Console install
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>\Lev1\Web\Utilities
Promotion process for entire Portal Application Tree Promote the Entire Portal Application Tree
Extr
act P
orta
l Ap
plic
atio
n Tr
eePr
epar
e So
urce
Sy
stem
Prep
are
Targ
et S
yste
mIm
port
Por
tal
Appl
icat
ion
Tree
Valid
atio
n
Migration
Backup Source system
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
Set environment variables for
SAS_HOME and JAVA_HOME
Extract Portal Application Tree using script
extractPortal version.sh
PortalApplicationTree_deployFile.xmlPortalApplicationTree_expand.xmlPortalApplicationTree_extract.xmlextract.log
Backup Target system
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
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
Remove any existing Portal Application Tree using script removePortal 92.sh
Set environment variables for
SAS_HOME and JAVA_HOME
import Portal Application Tree using script
importPortal 92.sh
Copy output Files to target System
Import.log
Apply the Portal ACT to the Portal
Application Tree
Validate portal contents
Portal Content Migration :
WebDAVDum p.sh
Zip file containing all the contents and W FSD ump.xml
WebDAVRestore.sh
Zip file containing all the contents and W FSD ump.xml coped from source system
Source SystemTarget 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
SAS Datasets & code MigrationPROC CPORT/CIMPORT : Catalog MigrationPROC Migrate : Datasets MigrationsCode : Copy entire program with modifications reflecting
changes in directory structure.
SAS BI Migration Lifecycle
VALIDATION & CUTOVER
Validation
Training
Cutover
Contact Information
Name : Amol V DeshmukhEnterprise: California ISO CorporationAddress : 250 , Outcropping WayCity, State ZIP: Folsom CA 95630E-mail : [email protected]
Related Documents
