effective update manager application: lessons learned in peoplesoft 9.2 session #con6144 oct 2 nd,...
TRANSCRIPT
Effective Update Manager Application: Lessons Learned in
PeopleSoft 9.2
Session #CON6144Oct 2nd, 2014
1
Speaker Info
Daniel F. MonzonSenior Infrastructure Specialist, Adventist Health [email protected]
Sandeep R. Vemireddi Senior Consultant, Deloitte Consulting [email protected]
Peter A. Christiaans Specialist Leader, Deloitte Consulting [email protected]
2
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.
3
4
1973Adventist Health System was established
70,000Employees and physicians
4.5 million+Patients served annually
22 Home health and hospice agencies
16 Skilled nursing facilities
45Hospital campuses operated in 10 states
5
500+Physician Offices
7.4 billion+Total Operating Revenue
1.2 billion+Expenses
8,300Licensed Beds
817,000+Invoices
385,600+ Purchase Orders (1.6 Million Lines)
iSynergy Scope
WorkForceOBIEEHyperion
Financial Management
PeopleSoft 9.2 (Tools 8.53.13)
Taleo UPK
• Accounts Payable• Accounts Receivable• Asset Management• Billing• Cash Management• Contracts• eSettlements• Expenses• General Ledger• Maintenance Mgt.• Project Costing
Supply Chain Management
Human Capital Management
Interaction HUB 9.1 (Tools 8.53.13)
CRM
• 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
6
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
7
PUM & Maintenance in PeopleSoft
8
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
9
10
PUM vs Maintenance BundlesPUM Maintenance Bundles
PeopleSoft 9.2 or higher versions(People Tools 8.53.02 )
PeopleSoft 9.1 or lower versions
11
PUM vs Maintenance BundlesPUM Maintenance Bundles
PeopleSoft 9.2 or higher versions(People Tools 8.53.02 )
PeopleSoft 9.1 or lower versions
Available on MOS to download as a cumulative package
Available on MOS to download by Bundle (Update) number
12
PUM vs Maintenance BundlesPUM Maintenance Bundles
PeopleSoft 9.2 or higher versions (People Tools 8.53.02 )
PeopleSoft 9.1 or lower versions
Available on MOS to download as a cumulative package
Available on MOS to download by Bundle (Update) number
Only current PUM Image (PI) is available at any given time by Application. It contains all updates released till PI release date
All bundles released till date for a Application are available to download and are needed to become current
13
PUM vs Maintenance BundlesPUM Maintenance Bundles
PeopleSoft 9.2 or higher versions(People Tools 8.53.02 )
PeopleSoft 9.1 or lower versions
Available on MOS to download as a cumulative package
Available on MOS to download by Bundle (Update) number
Only current PUM Image (PI) is available at any given time by Application. It contains all updates released till PI release date
All bundles released till date for a Application are available to download and are needed to become current
Provides ability to selectively apply bug fixes
Cannot choose a fix from Bundle – All or Nothing
14
PUM vs Maintenance BundlesPUM Maintenance Bundles
PeopleSoft 9.2 or higher versions(People Tools 8.53.02 )
PeopleSoft 9.1 or lower versions
Available on MOS to download as a cumulative package
Available on MOS to download by Bundle (Update) number
Only current PUM Image (PI) is available at any given time by Application. It contains all updates released till PI release date
All bundles released till date for a Application are available to download and are needed to become current
Provides ability to selectively apply bug fixes
Cannot choose a fix from Bundle – All or Nothing
One change package for all selected list of fixes
Each Bundles need to be a separate change package
15
PUM vs Maintenance BundlesPUM Maintenance Bundles
PeopleSoft 9.2 or higher versions(People Tools 8.53.02 )
PeopleSoft 9.1 or lower versions
Available on MOS to download as a cumulative package
Available on MOS to download by Bundle (Update) number
Only current PUM Image (PI) is available at any given time by Application. It contains all updates released till PI release date
All bundles released till date for a Application are available to download and are needed to become current
Provides ability to selectively apply bug fixes
Cannot choose a fix from Bundle – All or Nothing
One change package for all selected list of fixes
Each Bundles need to be a separate change package
Automatically ensures pre and post requisites
Manual tracking is needed to ensure Pre and Post requisites
16
PUM vs Maintenance BundlesPUM Maintenance Bundles
PeopleSoft 9.2 or higher versions(People Tools 8.53.02 )
PeopleSoft 9.1 or lower versions
Available on MOS to download as a cumulative package
Available on MOS to download by Bundle (Update) number
Only current PUM Image (PI) is available at any given time by Application. It contains all updates released till PI release date
All bundles released till date for a Application are available to download and are needed to become current
Provides ability to selectively apply bug fixes
Cannot choose a fix from Bundle – All or Nothing
One change package for all selected list of fixes
Each Bundles need to be a separate change package
Automatically ensures pre and post requisites
Manual tracking is needed to ensure Pre and Post requisites
Lists objects impacted for a Bug Fix even before applying
List of objects impacted is not readily available
17
Installation & Usage of PUM
18
InstallationThe PeopleSoft Update Image is a virtual machine running on Oracle VM VirtualBox
No additional license requirements for a PeopleSoft Virtual Box Images used for non-production activities such as patches and updates or demonstrations.
19
Guest Operating System
Oracle 11gR2
People Tools
Steps to set up the PUM Virtual Machine
20
Install Virtual Box and import PeopleSoft Image
Steps to set up the PUM Virtual Machine
21
Start VM and configure network settings
Steps to set up the PUM Virtual Machine
22
Configure Source and Target DB connections
1 2 3 4
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)
Clear agent cache and launch PSEMAgents
Steps to set up the PUM Virtual Machine
23
24
Clearing PSEMAgent CacheSteps to set up the PUM Virtual Machine
Creating Change PackageLaunch PeopleSoft Change Assistant and select Update Manager
25
Creating Change PackageDefine a New Change Package
26
Creating Change PackageOpen Browser and Connect to the PI Database
27
Creating Change PackageDefine Change Package
28
Creating Change PackageChoose Package type
29
Creating Change PackageReview Bug Details
30
Applying Change PackageSelect Change Package from Drop Down, Click Apply Change Package
and Finish
31
Applying Change PackageCompleted PUM Package
32
Migration and Remediation
33
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
34
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
35
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
Assitant followed by migration of remediated objects
36
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.
37
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
38
Strategies, Non PUM Updates & Our Challenges
39
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.
40
StrategiesProactive 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
41
StrategiesProactive 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
42
StrategiesProactive Application
Reactive Application
Selective Application
All of these strategies are equally important and have to be included in the Project Plan
43
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.
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)
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
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
It is important to keep maintenance log consistent with the fixes applied to environments
46
Non PUM Updates
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.
Planning
Planning
DMO DEV TST QA
Lockstep migrations from DMODEVTSTQA
Lessons Learned and Takeaways
1. Maintain a “Gold” Demo instance that is at the same patch level as your Production
environment.
2. 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.
3. Use individual packages in the event that patches do not work.
4. Use the same naming convention for packages.
5. Maintain an archive of PUM images that have been applied.
Lessons Learned and Takeaways
6. Validate that the list we expected to apply is in the database’s maintenance log at the
end of each move. Periodically schedule an audit of the maintenance logs to validate
any selective patches that have been applied.
7. Plan ahead on how best to add the images to your infrastructure – (DHCP vs. static).
8. Make sure you select bridged adapter in the settings of your VM so you will be able
to communicate with it from outside of the host system.
9. Use the same migration method (PUM versus project migration)
10. Patches will need to move in lockstep and will need to be handled as a ‘mini-
upgrade’. For example, a defined window needs to be structured for a group of
patches to move from DMODEVTST—QA.
Q&A
52