Effective Update Manager Application: Lessons Learned in PeopleSoft 9.2

1. Effective Update Manager Application: Lessons Learned in PeopleSoft 9.2 Session #CON6144 Oct 2nd, 2014

2. Daniel F. Monzon Senior Infrastructure Specialist, Adventist Health System Dan.Monzon@ahss.org Sandeep R. Vemireddi Senior Consultant, Deloitte Consulting LLP sandereddy@deloitte.com Peter A. Christiaans Specialist Leader, Deloitte Consulting LLP PChristiaans@deloitte.com Speaker Info

3. Adventist Health System Adventist Health System is a faith-based health care organization headquartered in Altamonte Springs, Florida • Each facility operates independently in delivering care and services to best meet the needs of the local communities they serve. • While each entity is unique, all remain united in one mission of Extending the Healing Ministry of Christ.

4. 45 Hospital campuses operated in 10 states 1973 Adventist Health System was established 70,000 Employees and physicians 4.5 million+ Patients served annually 16 Skilled nursing facilities 22 Home health and hospice agencies

5. 8,300 Licensed Beds 500+ Physician Offices 7.4 billion+ Total Operating Revenue 1.2 billion+ Expenses 385,600+ Purchase Orders (1.6 Million Lines) 817,000+ Invoices

6. iSynergy Scope PeopleSoft 9.2 (Tools 8.53.13) Interaction HUB 9.1 (Tools 8.53.13) Financial Management Supply Chain Management Human Capital Management CRM • Accounts Payable • Accounts Receivable • Asset Management • Billing • Cash Management • Contracts • eSettlements • Expenses • General Ledger • Maintenance Mgt. • Project Costing • eProcurement • eSupplier Connection • Purchasing • Inventory • Mobile Inventory Management • Supplier Contract Management • Warehouse Management • Benefits Administration • Payroll • Human Resources • ePay • eProfile • eBenefits • Taleo On-Boarding • eCompensation • Workforce Communications • Helpdesk for Human Resources Hyperion OBIEE Taleo WorkForce UPK

7. Agenda • PUM & Maintenance in PeopleSoft • PUM Overview • PUM vs Maintenance Bundles • Installation & Usage of PUM • Installation • Creating and Applying Change Packages • Migration and Remediation • Strategies • Analysis and Rollback • Strategies, Non PUM Updates & Our Challenges • Q&A

8. PUM & Maintenance in PeopleSoft

9. PUM Overview • PeopleSoft Update Manager (PUM) is the new methodology by which Oracle delivers the maintenance packages • PUM is a flexible, streamlined patching process that enables project teams to identify, understand, and selectively apply maintenance updates aligned to requirements and schedule. • From PeopleSoft 9.2 all lifecycle management maintenance processes are delivered using only PUM, including the delivery of new features • PeopleTools patching is not included in the PeopleSoft Update Manager

11. PUM vs Maintenance Bundles

12. PUM vs Maintenance Bundles

13. PUM vs Maintenance Bundles

14. PUM vs Maintenance Bundles

15. PUM vs Maintenance Bundles

16. PUM vs Maintenance Bundles

17. PUM vs Maintenance Bundles

18. Installation & Usage of PUM

19. Installation The PeopleSoft Update Image is a virtual machine running on Oracle VM VirtualBox People Tools Oracle 11gR2 Guest Operating System No additional license requirements for a PeopleSoft Virtual Box Images used for non-production activities such as patches and updates or demonstrations.

20. Steps to set up the PUM Virtual Machine Install Virtual Box and import PeopleSoft Image

21. Steps to set up the PUM Virtual Machine Start VM and configure network settings

22. Steps to set up the PUM Virtual Machine Configure Source and Target DB connections

23. Steps to set up the PUM Virtual Machine Clear agent cache and launch PSEMAgents PeopleSoft Update Manager Agents PSEMAgent Web (Linux) $PS_HOME/PSEMAgent/StartAgent.sh Sending pulse from 'com.peoplesoft.emf.peer:id=1' PSEMAgent Application (Linux) $PS_HOME/PSEMAgent/StartAgent.sh Sending pulse from 'com.peoplesoft.emf.peer:id=2' PSEMAgent Batch (Windows File Server) %PS_HOME%\PSEMAgent\StartAgent.bat Sending pulse from 'com.peoplesoft.emf.peer:id=3' Workstation Change Assistant (Update Manager) 23

24. Steps to set up the PUM Virtual Machine Clearing PSEMAgent Cache

25. Creating Change Package • Launch PeopleSoft Change Assistant and select Update Manager

26. Creating Change Package • Define a New Change Package

27. Creating Change Package • Open Browser and Connect to the PI Database

28. Creating Change Package • Define Change Package

29. Creating Change Package • Choose Package type

30. Creating Change Package • Review Bug Details

31. Applying Change Package • Select Change Package from Drop Down, Click Apply Change Package and Finish

32. Applying Change Package • Completed PUM Package

33. Migration and Remediation

34. Migration Strategies • Option 1 - Creating a Change Package • Apply PUM to the development environment using Change Assistant • Remediate code line and scripts • Create a custom change package and apply it to higher environments for testing using Change Assistant

35. Migration Strategies • Option 1 - Creating a Change Package • Option 2 - Using a 3rd Party Migration Tool • Apply PUM to the demo environment • Create a project using the migration tool • Use the migration tool to migrate the project to Dev • Remediate and create a new migration set in Dev for testing in higher environments • Rollback option may be available

36. Migration Strategies • Option 1 - Change Package • Option 2 - Migration Tool • Option 3 - PUM followed by remediation • Apply PUM to the development environment using Change Assistant • Remediate code line and scripts • Apply PUM to higher environments using Change Assitantfollowed by migration of remediated objects

37. Migration Strategies • Option 1 - Change Package • Option 2 - Migration Tool • Option 3 - PUM followed by remediation • Based on the tools available, phase of the Project and team composition we opted with PUM followed by remediation strategy.

38. Analysis and Rollback • Create a list of Bug fixes that are part of technical or functional pre and post requisites • Perform High level Analysis of how a change package impacts PeopleSoft based of the objects impacted • Plan and Define retrofit windows appropriately as per project phase • Take backup of Project, Script target data and source file like SQRs and Cobols • Perform both technical and functional testing based of objects and code line impacted and business processes impacted • If Project team opts to not proceed or proceed with a subset of fixes rollback changes to the instances using backups and repeat the process

39. Strategies, Non PUM Updates & Our Challenges

40. Strategies • Proactive Application • Periodically download current PUM Image & apply using ‘All Updates Not Yet Installed’ • Introduces the most change, requires the most remediation and testing • Once every 9 to 12 months or when count of number of fixes in not applied state for the modules implemented is too high and creates risk for Reactive fix application.

41. Strategies • Proactive Application • Reactive Application • When an issue is identified and its fix is pointed to be available in PUM Image • Use search capabilities to find the fix, create a change Package and apply fix

42. Strategies • Proactive Application • Reactive Application • Selective Application • Review critical fixes and new features • Review the updates posted relevant to the Implemented modules for each PUM release • Apply once for every 3 to 6 months

43. Strategies • Proactive Application • Reactive Application • Selective Application All of these strategies are equally important and have to be included in the Project Plan

44. Non PUM Updates • Oracle delivers new PeopleSoft Update Manager (PUM) Images approximately every 10 weeks, however there are updates outside a PI also. • PeopleSoft Release Patchset (PRP) • Patches that are delivered between PI releases. • Should be applied to current PeopleSoft Update Image • Once applied select the fixes from PI and apply to target database.

45. Non PUM Updates • Oracle delivers new PeopleSoft Update Manager (PUM) Images approximately every 10 weeks, however there are updates outside a PI also. • PeopleSoft Release Patchset (PRP) • Proof of Concept (POC) Patches • Patches created for escalated critical reasons for a single customer • Apply directly to the DEV environment as a customization • Apply the patch from the subsequent PUM image as soon as it is available

46. Non PUM Updates • Oracle delivers new PeopleSoft Update Manager (PUM) Images approximately every 10 weeks, however there are updates outside a PI also. • PeopleSoft Release Patchset (PRP) • Proof of Concept (POC) Patches • It is important to keep maintenance log consistent with the fixes applied to environments

47. Planning Adventist Health will have successive rollouts of PeopleSoft to multiple hospitals/regions over the course of multiple years. A key challenge is not only when to plan PUM deployment windows within the existing rollout but also how these may impact concurrent deployments.

48. Planning

49. Planning Lockstep migrations from DMODEVTSTQA

50. Lessons Learned and Takeaways • Maintain a “Gold” Demo instance that is at the same patch level as your Production environment. • Proper planning is required when applying patches across PUM images. The latest version of the objects will be imported from the latest image. This may impact retrofits, regression testing and business processes. • Use individual packages in the event that patches do not work. • Use the same naming convention for packages. • Maintain an archive of PUM images that have been applied.