Upgrade Overview

PeopleSoft Upgrades
The Big Picture and the Little Details
Presented by: CedarCrestone Managed Services

Topics
‣ Upgrade Overview
Terminology
Initial Pass
Test Moves
Go-Live
‣ Infrastructure
Environments
Backups
Refreshes
‣ Additional Considerations
Development & Migration Strategy
PeopleSoft Apply to Release (Applications Fixes)
PeopleTools Freeze
‣ Q & A

Upgrade Overview – Terminology
‣ C2 – Chapter 2: Pre-Upgrade Functional Setup
‣ C6 – Chapter 6: Post-Upgrade Functional Setup
‣ IP – Initial Pass
‣ TM – Test Move
‣ GL – Go Live
‣ SRC DB – Source DB for upgraded tools definitions
‣ TGT DB – Target DB; the upgrade database

Upgrade Overview – Initial Pass
‣ Plan, Build, Execute
Plan the upgrade
Install the software
Pre-upgrade functional setup/audits (C2)
Technical upgrade – upgrade PeopleTools
Generate and review compare reports
Complete technical upgrade – Deliver TST
Post-upgrade functional setup (C6)
Patch/Fix
Deliver DEV environment
Create & maintain Go Live task list**
** Post-IP ongoing activity

Upgrade Overview – Test Moves
‣ Test the planned Go-Live processes
Subset of Initial Pass processes
Plan the Upgrade
Install the Software
Functional setup and data audits (subset)
Technical upgrade (subset)
Run and Review Compare Reports
Complete technical upgrade (subset)
Complete functional setup (subset)
Continue Testing
• Unit, System, Parallel
Continue to maintain Go-Live task list

Upgrade Overview – Go Live
‣ Final Move to Production
Back up production
Upgrade Production in place ** - OR -
Create copy of production on new release
production box **
Run same subset of processes as test moves
Apply go-live checklist tasks
Final user verification test
Communicate to user base
New Release Live in Production
** which method to use to be determined later

Initial Pass – A Picture (Part 1)
UPG DB
OldRel Demo DB
UPG DB
NewRel Uprader
DMU DB
1. Execute PreUpg Functional tasks
on UPG
2. Full DB Compare UPG to oldrel
DMO – creates UPGCUST Project
3. If UPG LastUpdOprID
PPLSOFT, assumes customization
4. Remove all non-custom objects
from UPGCUST project
5. UPGCUST Project Compare from UPG to
NewRel Upgrader DMU DB
6. Generate compare reports
7. Review compare reports; select ‘custom’
objects to bring forward into 9.2
8. Upgrader copies custom objects from UPG to
DMU
9. Export all newrel DMU tools objects + the
custom objects pushed from UPG to DMU;
then import those into UPG
10. Now, UPG is upgraded with 9.2 object
definitions
11. Complete technical upgrade on UPG (SQL
Builds, Data Conversion, etc)

Initial Pass – A Picture (Part 2)
NewRel Client
DEMO DB
UPG DB
NewRel TST DB
P/F team begins applying
MP’s and bundles to 9.2
DEM toward end of IP
12. DB Copy UPG to TST
13. Complete Post-Upgrade
Functional Tasks in TST
14. P/F applies MP’s & Bundles
in TST after Post-Upgrade
Functional Tasks
15. After P/F is complete, DB
Copy TST to DEV
NewRel DEV DB

Test Moves – A Picture
TST
Test Env
UPG
TST is
refreshed
from UPG
after each
TM
Test Moves
COP2-n
Export Upgraded
Tools Objects
from TST
MVPRD.dat
TST is SRC DB
for TM1 -
GoLive

Go-Live – A Picture
New Rlse
PRD
TM3
MVPRD.dat
1. Backup oldrel PRD & either copy to what will be
NewRel PRD or Upgrade in Place
2. Complete pre-upgrade functional tasks in PRD
3. Import tools objects to PRD
4. Complete Technical Upgrade on PRD
5. Complete post-upgrade functional tasks & final
testing/validation
6. Communication – System is live on 9.2

Infrastructure
‣ Environments
‣ Backups
‣ Refreshes

Infrastructure - Environments
‣ Old Release Environment (UPG)
Required to run pre-upgrade functional tasks
All services (app/batch/web) running on NT/Terminal Server
‣ New Release Environments
Demo (DEM), Development (DEV), Test (TST)
Each has its own codeline for migration testing
Unix-based App/Batch Server + NT Batch Server
Crystal and NVisions run on NT Batch Server; normally all
other code runs from UNIX (COBOL, AppEngine, SQR)
App Engines and SQR can run from either NT or UNIX
schedulers with UNIX being the preferred server. COBOL is
only executable on UNIX.
New Release Production codeline is created from
copy of Test

Infrastructure - Backups
‣ Cold Backups
Initial Pass
• After Pre-Upgrade functional setup
• After tools upgrade
• After UPGCUST Compare
• After Upgrade copy
• Before Data Conversion
• After Data Conversion
• After completing initial pass

Infrastructure - Backups
‣ Cold Backups
Test Moves
• After Pre-Upgrade functional setup
• Before Data Conversion
• After Data Conversion (eliminated by TM3)
• Before application fix scripts (eliminated by TM3)
• After completing test move
‣ Hot Backups
DEV & TST - weekly

Infrastructure – Refreshes
‣ Refresh UPG from CurRel PRD each pass
‣ Build DEV from TST after Initial Pass**
‣ Refresh TST from UPG after each TM pass
** To preserve ongoing development work, DEV is created from TST after IP and is
NOT refreshed thereafter

Additional Considerations
‣ Development and Migration Strategy
‣ PeopleSoft Apply to Release (Application)
Fixes
‣ PeopleTools Freeze

Additional Considerations
Development & Migration Strategy
‣ Reapply mods/new
development
• Online & Batch
‣ Unit Testing
• Pages work;
retrieve data
• SQR’s run
DEV
Development
By TM3: DEV = TST
capture all reapp in final test move
(all reapp, online & batch, complete by
TM3)
1-Project Compare & Copy
Move reapps to test env
UPG
NOTE: Migrations to TST
are frozen from the start
to the end of each TM pass
Refresh
TST
User Test
2 - MVPRD.dat
3-Run Test Move then
refresh Test DB
2 - As changes are signed off on
in TST – incorporate them into
the next test move cycle

Additional Considerations
Apply to Release (Application) Fixes
CMS will apply the most current maintenance pack and
all subsequently posted bundles for the new release
after the Initial Pass.
• CMS Patch Fix standards are to apply all available
fixes, both Maintenance Packs and Bundles.
CMS will keep the upgrade environments
(DEM/DEV/TST) in sync with any Regulatory updates
that are applied to the current production environment.
This includes tax updates and any pre/post requisites
only.

Additional Considerations
Apply to Release (Application) Fixes Cont’d
After the Initial Pass, fixes will be applied on an asneeded
basis and only fixes required to fix showstopper
issues will be applied.
No fixes should be applied after the final test move;
database objects should not change before Go-Live.

Additional Considerations
PeopleTools Freeze
PeopleTools must be ‘frozen’ – e.g. halt
peopletools object changes in production - as
soon as the first cut of production is taken
Any Tools change in current release production
after the Initial Pass copy of production will not
‘carry forward’ in future Test Moves
Dual development is required if Tools freeze is not
possible in current release production
• Changes made to production must also be made to
the new release DEV/TST environments

Additional Considerations
PeopleTools Freeze – Cont’d
Queries, Trees and Security
• Queries, Trees and Security are considered PeopleTools objects.
• Changes to these objects should be frozen after first COP is
taken for initial pass.
• Changes to these objects in production must be manually
updated to the new release database.
• Option to capture these objects:
• Queries & Trees – add’l fee-based service offering to capture these
as part of one or more test move passes
• Security – UpgLab offers a free (mini) or a fee-based service (more
robust) to capture security changes during one or more test move
passes
Query Access Group Trees
• Custom records will be dropped from PS delivered Query Access
Group Trees
• Recommendation: Place all custom records on a custom query
access group tree

Questions?

The End
Let the Upgrade Begin!