1 1100 H 4 MITs Migrations To Hana Enterprise Cloud

MIT'sHANAEnterpriseCloudMigration
KevinLyons,FrankQuern,GarryZacheiss
IS&T,MassachusettsInstituteofTechnology
Session:H4
1
2016MassachusettsInstituteofTechnology,IS&T
Agenda
Background:SAP@MIT
WhyHANA?
ProjectStructure&Milestones
MIT/HECArchitecture&Integration
Testing&GoLive
LessonsLearned
2
Background:SAP@MIT
September6,1996thejourneybeginson3.1with
corefinancials
April2007upgradetoECC6.0
December2015migrationofECC6.0,Ehp7toHANAin
theHANAEnterpriseCloud(HEC)
Eachandeveryyear,supportpacksandenhancement
packs
3
Background:SAP@MIT
Alongthewayweimplemented
Procurement,assetaccounting,project
systems,sales&distribution,funds
management,inventorymanagement,
plantmaintenance,EHS,HR/Benefits/Payroll
includingselfservice,training&events,enterpriselearning,
toomanytoincludeall
SAPweb,MITsfirstportal
integratedwithSAP
Atlas,MITslatestportalfor
communityfacingadministrativeapps
4
Didwementionthehardware?
StartedonTru64onUnix
MigratedtoSolarisaround2004
MigratedtoLinuxin2010
AspartofLinuxmigrationwevirtualizedourSAP
environment
5
SAPintegrateswithalot
6
SAPintegrateswithalot
SciQuest forprocurementcatalogs
Nimbusforbudgetadministration
Kuali Coeus forresearchadministration
Bannerandothersforstudentadministration
Adonisforgiftrecording
Kronos,Concur,OpenText,BSI,thedatawarehouse
SAP@MITalsosendsandreceivesmanyfeedsof
financialandnonfinancialdatato/fromexternal
partnersviaourcustommiddleware,theSAPDropbox
7
Background:Conclusion
AllofthismakesSAP@MITacomplexinterplay
ofprocesses,systems,andtools,somestandard
andsomehomegrown,allembeddedindayto
daylifeatMIT
Andwewantedto
moveittothecloud
8
WhyHANA?
9
HANADB Motivations
LayfoundationforfuturemigrationtoS/4.
LeverageHANADataServicestoimproveData
Warehousing&Reportingenvironment workin
progress.
EliminatecomplexETLprocess/batchextractfrom
ECC.
Improveperformanceforremainingbatchworkloads.
10
HANAEnterpriseCloud Motivations
Spaceiseverything.
Reduceonpremisesadministrativecomputingfootprint.
Prioritizelimiteddatacentercapacityforresearchcomputing
workloads.
Increasedresiliency:bicoastaldisasterrecoverystrategy.
Primarysite:Sterling,VA
Secondary:SantaClara,CA
TransferstandardizedandofftheshelfworkfromMITtovendorpartner:
rackandstack,hardwaremaintenance.
OSinstallation.
EnablestafftofocusonMITspecific,differentiatedneeds.
Integrationwithcampusidentitysystems(AuthN,AuthZ)
11
12
ProjectStructure
Planning
Workshops to define what it is we want to accomplish
Replace Oracle with HANA
Migrate our on premise data center to SAPs HEC service
Code
remediation
Cycles
Support Packs
Organization
Traditional PM
Scrum Framework
13
CodeRemediation
ABAP Custom Code Remediation for SAP HANA

Analysis ImpactedPrograms
Native SQL, Database Hints Critical Statements 2
Check assumptions regarding implicit sorting during access to 23
former pool and cluster tables
Check assumptions regarding implicit sorting during access to 45
transparent tables
14
TheProjectCycles
Cycle1 Proofof concept stagingenvironment
Cycle2 MigrateonpremisesdevelopmentenvironmenttoSAPsHANA
CloudEnterprise(HEC)
Cycle 3 Repeatmigrationofonpremises developmentenvironmentto
HECbutincludeyearendsupportpacksintheprocess
Cycle4 MigrateQA/Testenvironment toHEC
Cycle5 MockCutover executemigrationofproductionenvironment

toHEC
Cycle6 Dressrehearsal(Executedisasterrecoverytest)
Cycle7 Executeproductioncutover
15
WhereHANAintersectswithSupportPacks
Support Packs
We all know what they are, periodic releases of system changes and
corrections by SAP.
Rather than apply these support packs when released we collect the
Support Packs for a single installation at year end in an effort to
minimize business interruption.
The timing of our process is driven by SAPs release of its year end
support pack, typically in mid-October, which contains the base level
necessary for the successful execution of SAPs delivered year end tax
reporting functionality (AP and Payroll) and stages the system for
regulatory changes for the upcoming calendar year.
Can we leverage the Support Pack testing window to limit the projects
impact on business operations?
16
ProjectMilestones
Theproposedprojectschedulehadfourmajormilestones:
1. DecisionforDecember Go/NoGodecisionafterourPOC
(Cycle1).By9/8/2015makeadecisionifMITsSAP
landscapecanbemigratedtoHECby12/14/2015
2. SupportPackDecision Go/NoGodecisionby10/2/2015
(afterCycle2)whethertoapplySupportPacksinHECoron
premiseforproductionuseafterDecember
3. SuccessfulmockcutoverbeforetheThanksgivingbreak
4. GoLivedateof12/14/2015
17
Timeline
18
Whatsinaname?
Lettheteamdecide
Greekthemed
Scopas
Daedalus
Procrustes
Cloudthemed
Nimbus
Cumulus
Cirrus
Projectname:HANAtoOptimize(H2O)
19
ProjectCharter
PROJECT IDENTIFICATION
ProjectType
ProjectName (Implementation,Upgrade,Internal,other)
HANAtoOptimize(H2O)ECC
MIT TechnicalMigration
Migration
Vision
StandupafunctioningHANAERPenvironmentinHECfromwhichMITmaytestfunctionalityasit
appliestoMITslongtermvisionofproviding aplatformasaservice.
Mission
TheH2OECCMigrationProjectTeamisResponsibleandEmpoweredtoMigrateMITsdatato
SAPsHANAEnterpriseCloud(HEC).
GuidingPrinciples
Technicalmigrationonlywithnofunctionalityadded.
MigrateDevtoHECforGo/NoGodecisionforaDecemberGoLive.
EvaluateSupportPacks(SPs)forGo/NoGodecisiontodetermineifSPswillbeappliedtothe
migratedsysteminHEC.
MigrateMITsfour(4)tiersenvironmentto HEC.
20
ProjectStructure
Executive Sponsors
Steering Committee
Project Management
SAP Project Management MIT Project Management
Project Team
Project Team Members SAP Project Team Members MIT
Reporting to/Escalating to: Information:
21
ProjectStructure
MIT Team formed into 4 Scrum Teams

Infrastructure buildout and configuration management
Human Resources, Payroll, and E-Learning
Finance, Logistics, Plant Maintenance, and EHS
Atlas and other web applications
Assigned Scrum Roles
Product Owners
Scrum Masters
Scrum Team Members
Daily Meetings (15mins)
Scrum Teams
Product Owners
22
ProjectStructure
Scrum Team Charge:

Determine a comprehensive testing approach for all
cycles
Ensure the integrity of all critical applications and
integration methodologies in use across the SAP
landscape
Capture/resolve/escalate identified issues
23
Toolsofthetrade
Wiki
SAPJam
MSProject
Dropbox
Scrumboards
Burndowncharts
RT
24
MIT/HECArchitecture&Integration
25
Networking
Strategy:extendMITnet toHECdatacenters.
AssigneddedicatedIPv4addressblockstoHEC:
18.4.128.0/24,18.4.130.0/24.
Twophaseapproachtoconnectivity:
InitialconnectivityviaIPSec VPN:abletodeployrapidly.
Dedicatednetworkconnections/peeringtobothSterling
andSantaClara:2x10Gbps
InstalledroutingequipmentinHECdatacenters:MITnet
California
HECenvironmentsappearaspartofMITsinternalnetworkto
otherapplications.
26
DNS
Delegated.hec.mit.edudomaintoHEC.
4HECoperatedDNSservers,2persite.
.hec.mit.eduzonecontainsCNAMErecordspointedatcurrently
activedatacenter:
Sterling .stl.hec.mit.edu
SantaClara .sac.hec.mit.edu
DNSindirectionfacilitatesdisasterrecoveryprocess.
Regionspecificnamesneverexposedtoendusersorother
systems.
27
Authentication
MITauthenticatesSAPGUIusersusingKerberos/GSSAPIviaSNC.
HECapplicationserversprovisionedwithcredentialsfromATHENA.MIT.EDU
Kerberosrealm.
RequiredextensivecoordinationwithHECtechnicalstaff:
AdditionalOSpackagesinstalled.
ChangestoOSconfiguration(/etc/krb5.conf).
ChangestoSAPinstanceprofiles.
Keylearnings:
Beveryexplicitaboutyourrequirementsinthisarea.
Bepreparedtodotheheavylifting.
28
AncillarySystems
Outboundemail HECsystemssendviaMITsprimarySMTPrelay:outgoing.mit.edu
RequiredcoordinationwithHECteamsonPostfixconfiguration.
OpenText ArchiveServer migratedtoHECasIaaS.
HECmanagedHANADBinstancefordatabasebackend.
BSITaxFactory migratedtoHECasIaaS.
TransitionedfromOracletoSybaseASE.
ExploringuseofSAPApplicationManagementServices(AMS)forSybaseDBA
work.
SAPDropbox(custommiddleware) migratedtoHECasIaaS.
ProvidessharedstorageviaNFStoHECapplicationservers.
Requiredmostmodificationsforuseinnewenvironment.
AllotherMITmanagedsystems(customwebportal,centralauthorizationsDB,Data
Warehouse,etc.)remainonpremises.
ChangeswerelimitedtoconfigurationupdatesfornewenvironmentDNSnames
/ports.
29
Miscellany
SAPGUI modifiedinstallertodistributeconfigurationfilesvia
HTTPfromcentrallocation.
Backups IaaSsystemsarebackedupasthoughtheywereon
premise.
Allthatnetworkbandwidthcomesinhandy.
Monitoring SupplementHECmonitoringwithMITsexisting
enterprisemonitoring.
NoOS/shellaccesstoHECmanagedsystems.
Monitorsystemsatnetwork(ping/nping)andapplication
(HTTP/HTTPS)levels.
30
Testing&GoLive
31
TestingApproach
Testing will be managed by the 4 Scrum teams

Tectonics -Infrastructure buildout and configuration management
Spartans - Human Resources, Payroll, and E-Learning
Poseidon - Finance, Logistics, Plant Maintenance, and EHS
Globetrotters - Atlas and other web applications
Test Plans
Each team will determine a comprehensive approach, based on
past experience managing the SAP year-end support pack
process and similar large-scale application updates, to ensure the
integrity of all critical applications as well as testing all integration
methodologies in use across the MIT system.
32
TestingApproach
Specific areas of attention during the validation process will

include:
Integration with MIT Kerberos for GSSAPI authentication
Customized B2B solution enabling secure file transfers into and out of
SAP (SAP Dropbox)
Integration with MIT printing and network infrastructure
Porting of MIT-specific notification mechanisms to ensure seamless
e-mail and fax functionality
Implementing MIT ERP and SAP ancillary components in the cloud
while minimizing the need for ABAP code changes
Test Cases
Test cases from ALM/QC Repository will be leveraged where possible
Automated test cases will be used in Cycles 3 and 4 (HP QTP)
33
Testing Cycles1 4
Cycle 1: Proof of Concept Environment:

Test GUI, GUIXT, ITS, WDA and ATLAS, including integration with MIT authentication systems (Touchstone
and Kerberos).
Test data transfers / integration with MIT Data Warehouse.
Cycle 2: Development Environment (1st Pass):

GUI testing
Full integration testing
Dependent on completing testing of all integration solutions in PoC environment
Includes Concur, ATLAS JV, & SciQuest outbound which couldnt be tested in the PoC environment
Create cookbook/cutover plan version 1
==SPs============SPs============SPs============SPs==========
Cycle 3: Development Environment (2nd Pass):
Migration of Frozen environment
Application of Y/E Support Packs
Support Pack Unit Testing
Cycle 4: QA/Test Environment:
Collaborative Business and IS&T integration and regression testing of Support Packs on HANA
Testing includes GUI Transactions, GUIXT, ITS, WDA ,ATLAS, system feeds
Approximately 35% of test cases are automated
34
Testing WhereH2OintersectswithSupportPacks
(Cycles3&4)
35
TestingResults
QA environment: System Integration/User Acceptance Testing (Cycle 4)
36
TestingResults
Was it worth it?

Well, yes
PhasesIssueswereidentifiedin
(asof12/2/15)
Issuetype Unit SIT Total

RequiredanSAPfix 8 8 16
RequiredanMITfix 12 13 25
InfrastructureRelated 54 17 71
User/DataError 1 8 9
Duplicate 4 2 6
ProductionIssue
tobeaddressedafterSP 1 7 8
Totals 80 55 135
37
GoLiveDecision
Our criteria for recommending migrating the production environment to

HEC was based on:
Successful migration of MITs non-production SAP data to HEC-hosted
environments.
Validation of all critical SAP transactions / reports, including weekly and
monthly payroll processing, summary statement, etc.
Successful integration of HEC-hosted SAP environments with MITs
infrastructure: authentication (Kerberos, Touchstone) and authorization
(Roles).
Success integration of HEC-hosted SAP environments with ancillary
business systems: SAP Dropbox, CUPS printing, Data Warehouse, etc.
Disaster recovery for all existing SAP solutions (ECC, GRC, Solution
Manager) and ancillary systems (SAP Dropbox, OpenText) designed and
expected to be available by 11/2015.
38
Cutover
1. Preparation Work
2. System Isolation
3. Migration/Support Pack Application
i. Core cutover tasks
ii. HEC tasks
iii. High Availability tasks
iv. Disaster Recovery tasks
v. MIT web deployment tasks
4. Post Upgrade Processes (validations)
5. Go-live
39
HECCutoverPlan
Timing:
BeganuptimeprocessingonDecember8th inthemorning
Begansystemshutdownat4pmonFridayDecember11th
WehavecommunicatedwithsystemownersofBanner,CSAIL,iLab,andeShipGlobalthat
theirAPIconnectionstoSAPwillbeimpactedbythisdowntime
BeganexporttoHECat~6pmFridaynight
SAPhadthesystemuntilnoononSaturdaywhenweperformedsecurityandsystem
verifications
SAPthenhadthesystemagaintill8pmSaturdaynight
MITcompletedtransportsandPart1oftheactionlogfrom8pmto~2AM
MITandSAPtestedHighAvailabilityandDisasterrecoveryfailoverfrom2AMto11AM
MITthencompletedactionlogitemsandbegantheprocessofreconnectingSAPtoallits
ancillarysystems
IS&TBAsandDevelopersonsiteperformedtestsassystemscomeonlinefromnoonto2pm
Businessvalidationsbeganat2pmonSundayDecember13th
ThecalltoapproveGoLiveplannedfor5pm.
40
EndResult
Success!
MITisintheCloud
41
Howdiditgo?
Oh,HEC!
LessonsLearned
42
LessonsLearned
Doyourprojectplanningearly
Sponsors,steeringcommittee,stakeholders,
communicationsplans,recurringmeetings,all(and
wemeanall)projectmanagementprocesses
Doitearly,youllbetoobusytodoitonthefly
Engagethirdpartyrepresentationearly
Includeintegratedproductpartnersespecially
Weworkedextensivelywiththirdpartieslike
BSI,OpenText,BofA
43
LessonsLearned
Identifyandorganizeyourteams
Planforworktransitions,theyregoingtobebusy
Weorganizedaroundproductteams
HR/Benefits/Payroll(Spartans)
Finance/Logistics/EHS(Poseidon)
Atlasportalandotherwebapps(Globetrotters)
Systemsadministration(Tectonics)
Identifyotherpotentialparticipants
Usethemwhenandasneeded
Haveacommunicationsdepartment/team?Usethemto
youradvantage!
44
LessonsLearned
Identifyyoursystemstestlist,assignanowner,andtrackthem
45
LessonsLearned
Plantotestallcustomizations
Doanycoderemediationasearlyaspossible
Testexecution
Documentyourtestresultsforeachcycle
Itmakesstatusreportingmucheasier
FullintegrationtestingnolaterthanUAT
Wetestedsomeintegrationsasearlyasunittesting
Identifyexistingproductionissuesseparatelyfromprojectissues
Dontaddtothescopeofthemigrationinflight
Dotrueendtoendlandscapetesting
Scheduleenoughtimetoanalyzeandremediateintegrationissues
46
LessonsLearned
MPLS
Getitgoingearly,ittookus~70daysfromorderto
completion
DNS
Agreeonthemandconfigureasearlyaspossible
Email
AgreeearlyonHECvs.onpremisesSMTPrelay
IdentifycustomizationsorpotentialissuesaroundsystemIDs,
hardcodedservernames,URLs&IPaddresses
Firewallconfiguration
47
LessonsLearned
OSlevelchangeswillimpactyourabilitytoresolveissues
HANADBcanbehavedifferently
Indexes,sorts,orderinwhichdataisreturnedcanbe
differentthanyoureusedto
SAPadminswonthavethesameaccessasbefore
Systemmonitoring
Proactivemonitoringofsystemsasearlyaspossible
2unscheduledoutagesduringtesting
48
LessonsLearned
Golive
Theresalottodo,planinshiftsifnecessary
Communicateearlyandoftentoeveryone
HaveaSWATteam,escalationplans,theworks
Embedresourceswiththebusiness,theyreyoureyesandearsduring
golive
Makesureyoushutdownyouronpremisessystems completely
Finally,remember,stuffhappens
FedExlostthedisccopyofthedatabase,dobothbackups
WehadSAPGui issuesongoliveduetocentral*ini filechange,notSAP
systemissues,seekoutallreferencestolocalsaplogon.inifilesearly
49
Whatstartedlikethis
InJuly
50
Turnedintothis
byOctober
Anditwasonlyhalfdone
51
Bythenumbers
Thenumberofstandupmeetingsheldduringthecourseoftheprojectbythe42
coreteammembersacrossfourscrumteams:Globetrotters(whichhandled
400+ everythingonthefrontend),Tectonics(infrastructure),Poseidon(finance,
logistics,andplantmaintenance),and,yes,Spartans(HR,payroll,andelearning).
ThenumberofcyclesthattheSAPHANAprojectwasdividedinto.Thesevencycles(Sounds
mythical,saidSpartansteamlead)were:
Cycle1 ProofofConcept
Cycle2 MigrateonpremisedevelopmentenvironmenttoSAPsHANACloudEnterprise(HEC)
Cycle3 RepeatmigrationonpremisedevelopmentenvironmenttoHECbutincludeyearendsupportpacksintheprocess
7 Cycle4 MigrateQA/TestenvironmenttoHEC
Cycle5 ExecutemigrationofmockcutoverofproductionenvironmenttoHEC
Cycle6 Executedisasterrecoverytest
Cycle7 Executeproductioncutover
ThebusiesttimeoftheprojectwasCycle4,duringtestingandmockcutover.Thiswasthemost
brutaltimebecausewehadfivesystemsthathadtobeupgradedandtestedsimultaneously,IS&T
projectlead.
ThenumberofMITcommunitymembersusingSAPgui clientsoftwarewhichneededtobeupgraded
2,154 tov7.40beforetheywouldbeabletoconnecttoSAPHANA.Thisrequiredrepeatedremindersto
userstoupgradebeforethefinalcutoverwascompletedandtimeranout.
52
Bythenumberscontinued
ThenumberofstepsintheplanforthefinalcutovertoSAPHANA,whichincludedmore
84 than100subtasks.
ThefinalproductionmigrationcommencedlateintheafternoonofFriday,December
11thandwascompletedintimeforthestartofbusinessthefollowingMonday,
exactlyasplanned.
Thenumberofissuesthathadbeenidentifiedbygolive,thankstoexhaustivetestingduringearlier
cycles,including1,649testcasesrunduringCycle4alone.80oftheseissuessurfacedduringunit
135 testing,while55wereidentifiedduringsystemsintegrationtesting.Atthetimetheprojectwent
live,allbut5(lowpriority)issueshadbeenresolved,whichhelpedexplainthesmoothtransition
duringthefinalcutover.
Wedidatremendousamountofduediligencethatluckilycaught
1.7 everythingthatwassignificantbeforewewentintocutover,PMsaid.
Theamountofdata,interabytes(TB),(storedinMIT'sOracleSAPdatabase)
thatweremigrated.
AfterthemigrationtoHANA,thosesamedataonly tookup.95TB.
ThetotaldurationoftheH2Oprojectindays,fromkickoffonJuly13thtocompletionofproduction
155 cutoveronDecember14th.Thatdoesn'tincludepostprojectrecoverytimeforteammembers.
53
Thankyou
54

1 1100 H 4 MITs Migrations To Hana Enterprise Cloud

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

1 1100 H 4 MITs Migrations To Hana Enterprise Cloud

Transféré par

Droits d'auteur :

Formats disponibles

MIT'sHANAEnterpriseCloudMigration

ABAP Custom Code Remediation for SAP HANA

Cycle1 Proofof concept stagingenvironment

Cycle5 MockCutover executemigrationofproductionenvironment

SAP Project Management MIT Project Management

Project Team Members SAP Project Team Members MIT

Reporting to/Escalating to: Information:

MIT Team formed into 4 Scrum Teams

Scrum Team Charge:

Testing will be managed by the 4 Scrum teams

Specific areas of attention during the validation process will

Cycle 1: Proof of Concept Environment:

Cycle 2: Development Environment (1st Pass):

QA environment: System Integration/User Acceptance Testing (Cycle 4)

Was it worth it?

Issuetype Unit SIT Total

Our criteria for recommending migrating the production environment to

Vous aimerez peut-être aussi