pum advisory and testing best practices...jsl psappsrv wsl wsh jsh ps messaging services application...

PUM Advisory and Testing

Best Practices How to stay current with your PeopleSoft Investment

Over 20 years consulting

experience focused predominantly

in PeopleSoft implementations and

upgrades covering all stages of the

Project Life Cycle.

System Business Process Analysis,

Requirements Study, Fit-Gap

Analysis, High Level Design,

ChartField and Codeblock Design,

Application Development, Testing,

Configuration, Training,

Deployment and Post-

Implementation Support

2

Randall Johnson

Managing Director

[email protected]

866-SPEARMC x812

www.SpearMC.com

About SpearMC

Founded in 2004, SpearMC is a technology and professional services firm specializing in

PeopleSoft FSCM, HCM, ESA

PeopleTools Development and System Administration

PeopleSoft Test Framework

Oracle Cloud ERP and HCM

Oracle Business Intelligence

PeopleSoft Training

Project Management

Oracle Public Cloud

QA & Test Automation

Host Analytics EPM

Our History

How to stay current with PeopleSoft

Available Tools in PeopleTools (8.54 and beyond)

PeopleSoft Upgrade Manager (‘PUM’)

PeopleSoft Test Framework (‘PTF’)

Which PeopleSoft products do you use?

CS / HCM / FSCM

What application version are you on?

What tools version are you on?

Do you plan to utilize selective adoption?

PUM Overview

PeopleSoft Update Manager (PUM) – New Lifecycle Management tool to apply application maintenance. Main Menu > PeopleTools > Lifecycle Tools

PeopleSoft Update Image (PI) – Application Maintenance is applied from the PI to a target environment. The images are released 4 to 5 times a year.

One Change Package - PUM defines one custom change package to apply all maintenance from the PI to the target environment. This significantly reduces the amount of time and effort since only one as opposed to many change packages need to be applied.

PUM Overview

PeopleSoft Update Image (PI) – A VirtualBox virtual machine that is posted to Oracle Support on a regular basis. The PI contains the latest maintenance for the application release.

PeopleSoft Release Patchset (PRP) – PRPs are sometimes needed between regularly released PIs. These are for critical fixes that cannot wait until the next image is posted. These fixes must be applied to a specific PI.

Proof of Concept (POC) - These rare patches are created only for escalated, critical reasons. A POC patch is posted and available only for a single customer in a password-protected patch. You apply this patch directly to the customer environment, bypassing the PI.

PUM Overview

Selective Adoption: the named process by which PeopleSoft customers are able to “selectively” determine how they will apply maintenance and new features as they are delivered approximately every 10 weeks by Oracle.

• Not the same bug deployment strategy of the past

• Provides for a SAAS like model

• Apply what you want/need

• Provides new functionality delivered more frequently

• Business solutions/functionality is agile

• Customizations are limited and scrutinized

• Creates a need for a different approach to staffing

• Eliminates large scale upgrades (if executed properly)

• Changes how organizations budget

PUM Architecture

File/Batch Server

Batch Server

App. Engine

Dist. Agent

COBOL

SQR

BBL

PSQCKSRV

PSQRYSRV

PSSAMSRV

JSL

PSAPPSRV

WSL WSH

JSH

PS Messaging services

Application Server

File Server

PSHOME1

PSHOME2

Application ServerDatabase Server

Database SQL

Web Server,

Report Repository

Web Server

http

server

Servlet

Engine

Gateway

Report

Repository

Secure Enterprise

Search Server

Oracle

Database

Web Server

http

server

Servlet

Engine

Gateway

Oracle Middleware

Oracle s Virtual Box

PeopleSoft Update Image

Oracle

Database

Oracle Middleware

httpsWeb Server

http

server

Servlet

Engine

Gateway

SQL

File Server

PSHOME1

Change Assistant

Environment HUB Agent

Oracle Database Client

PeopleSoft VBox Client

Environment HUBEnvironment HUB AgentEnvironment HUB Agent



PUM Deployment – Migration Path PUM Image Maintenance Steps

Te

chni

cal

Fu

nct

ion

al

Scope/Fit-Gap MTP / ProductionInitial Pass/Development MTP / Test MTP / SIT& Training

SNDSandbox

(Copy of DMO)

DMODemonstration

OVALatest Oracle

Virtual Appliance

DEVDevelopment(Copy of PRD)

Review Compare Reports Create

RICE spreadsheet

Retrofit RICE Reports, Interfaces,

Customizations, Enhancements.

Backup Database in order to restore a clean copy

before applying maintenance

Apply Image Maintenancefrom OVA or DMO

Run Compare Reports (Impacted Customizations)

TSTTest

(Copy of PRD)

Convert Custom Data

Apply Image Maintenancefrom OVA or DMO or DEV

Migrate Customizations from DEV

SITSystem int. Test(Copy of PRD)

Convert Custom Data

Apply Image Maintenancefrom OVA or DMO or TST

Migrate Customizations from TST

PRDProduction

(Copy of PRD)

Convert Custom Data

Apply Image Maintenancefrom OVA or DMO or SIT

Migrate Customizations from SIT


Develop Test Scripts TestingSystem Integration

Testing in SITGo Live

User Train in TRN

TRNTraining

Clone SIT to TRN

Address Security ChangesAnalysts evaluate and

determine if new features will be adopted. Self-train

and prototype configuration.

Perform an existing DMO to PRD compare report to

identify existing customizations

Review Image Release Notes

PTF Framework key features

©2014 Fred Hutchinson Cancer Research Center

12

• Record and Playback tool

• Automates Functional testing within PeopleSoft Application

• More tests - Greater Accuracy- Shorter time

• Stored in Database as App Designer Object

• Included in PT 8.51 & above

• PeopleSoft Images contain sample/demo PTF data starting with HCM PI

19 and FSCM PI 20 as a downloadable Application Designer project and

Data Mover files. Going forward, the PTF scripts and data mover files will

be shipped as part of the image.

Record and Playback


13

• PTF works by replicating the actions of a single user executing functional

tests against the PeopleSoft browser-based application

• Users can record manual test procedures and save them within the

framework

• Users can execute those tests against the application to verify whether

the application still behaves as expected

PeopleTools Metadata


14

• When PTF records a test, it recognizes the metadata, the actual name

of a field rather than the position of that field on a page

• If the field is moved in a subsequent revision, PTF is still able to locate it

when the test is executed

• If field is added/removed/modified, audit reports will identify

discrepancies between underlying objects and script metadata.

Interface with Other PeopleTools


15

• PTF tests can run processes and reports through Process Scheduler, as

well as queries and Data Mover programs

When to use PTF

2014 HEUG Midwest Regional

PeopleTools Metadata


18

• When PTF records a test, it recognizes the metadata, the actual name

of a field rather than the position of that field on a page

• If the field is moved in a subsequent revision, PTF is still able to locate it

when the test is executed

• If field is added/removed/modified, audit reports will identify

discrepancies between underlying objects and script metadata.

Common Issues with PUM

/ Testing

PUM Issues & Recommendations


Common Issues:

PeopleTools does not have PUM – only Application Images

Selective adoption is a blessing and a curse

There are still prerequisites when applying images, even with selective

adoption

Testing effort for frequent releases is more than planned / budgeted

Recommendations:

Pay particular attention to PeopleTools updates

Execute a maintenance ‘catch up’ at least annually

Use PTF to fast-track testing effort

Seek outside help for testing (hint – SpearMC…)

PTF Limitations and Gaps


Limitations:

PTF has matured since its first release on PeopleTools 8.49, it continues

to have limitations even on PeopleTools 8.55

PTF does not work outside PIA instance. For example, an interface

between PS FSCM and EDH will not work. It will only work inside PS

FSCM.

Test steps that involve any manual interventions such as File Scanning

transactions shall be excluded for automation scope

Continue to be on lookout for Oracle release enhancements on PTF

Gaps:

Doesn’t provide ability to parameterize and execute PTF test suites (

group of PTF tests)

No scorecards or dashboards to summarize and track test results from

multiple test scripts

Limited defect reporting across executed scripts

SpearMC Can Help


Randy Johnson

Managing Director

SpearMC

E-mail: [email protected]

Marcus Bode

Managing Director

SpearMC

E-mail: [email protected]

This presentation are

available for download from

the Conference site at

https://www.heug.org/page

/us-alliance-conference-files

Note: Sessions from previous HEUG

conferences are also available.

Appendix PUM Deployment Using the Change Assistant Wizard


PUM Deployment – Migration Path PUM Image Maintenance Steps

Te

chni

cal

Fu

nct

ion

al

Scope/Fit-Gap MTP / ProductionInitial Pass/Development MTP / Test MTP / SIT& Training

SNDSandbox

(Copy of DMO)

DMODemonstration

OVALatest Oracle

Virtual Appliance

DEVDevelopment(Copy of PRD)

Review Compare Reports Create

RICE spreadsheet

Retrofit RICE Reports, Interfaces,

Customizations, Enhancements.

Backup Database in order to restore a clean copy

before applying maintenance


Run Compare Reports (Impacted Customizations)

TSTTest

(Copy of PRD)

Convert Custom Data

Apply Image Maintenancefrom OVA or DMO or DEV

Migrate Customizations from DEV

SITSystem int. Test(Copy of PRD)

Convert Custom Data

Apply Image Maintenancefrom OVA or DMO or TST

Migrate Customizations from TST

PRDProduction

(Copy of PRD)

Convert Custom Data

Apply Image Maintenancefrom OVA or DMO or SIT

Migrate Customizations from SIT


Develop Test Scripts TestingSystem Integration

Testing in SITGo Live

User Train in TRN

TRNTraining

Clone SIT to TRN

Address Security ChangesAnalysts evaluate and

determine if new features will be adopted. Self-train

and prototype configuration.

Perform an existing DMO to PRD compare report to

identify existing customizations

Review Image Release Notes

PUM Deployment – Change Assistant

Configuration

Start the Agents

Crawl for Environments

Check Environment Viewer to confirm environments are found, Database, Batch Server, File Server, Web Server

PUM Deployment – Apply Maintenance

Start the Change Assistant

Select the Change Assistant Wizard

Select Action “Update Manager”


Configuration

General Options


Configuration

PUM Source


Configuration

PUM Source Configuration


Configuration

PUM Source Configuration

Note: Drives to Crawl must also contain the location for the database Query Tool


Configuration

Additional


Configuration

Select Task – Validate Change Assistant EMF Settings


Configuration

Select Task – Validate Change Assistant EMF Settings

Warning Message is expected. Insure EM Agent is running on the target server PS_HOME/PS_APP_HOME file directories to be updated

PUM Deployment – CA Define a New Change

Package

Define a New Change Package


Package

PUM Source Database = HR92U016 (Image 16 OVA)

Click Button to be transferred to PIA


Package

Login to PIA

PUM Deployment – Define Change Package

Select All Updates Not Applied


Complete List of Bug Fixes will be Displayed


Return to the Change Assistant for Packaging


Select the Change Package


Initial Pass

pum advisory and testing best practices...jsl psappsrv wsl wsh jsh ps messaging services application...

Documents