Stat 5 4 Pre-Sales Demo Master

Copyright © 2006 Quest Software

Change Management and Version Control for PeopleSoft: Stat® ACM

Tim Steward, Senior Systems Consultant ServiceQuest Consulting

Visualizing a TypicalPeopleSoft Development Lifestyle

ProductionDevelopment Testing

10% Files (SQR, COBOL, SQC, Crystal, Scripts, etc)On Both Unix & Windows Servers

90% Proprietary Database Objects (Record, Page, Index, PeopleCode, Activity, Component, etc)

WindowsUnix

WindowsUnix

WindowsUnix

DB DBDB

PeopleSoft Development Lifestyle

Most Version Control Tools Only Version Files


Files (SQR, COBOL, SQC, Crystal, Scripts, etc)On Both Unix & Windows Servers

WindowsUnix

WindowsUnix

WindowsUnix


PVCS, SourceSafe, Harvest, etc., version & manage flat files, however, they only offer a

partial solution10%

DB DB DB

Which Are Only 10% of the Object TypesNo No No

Objects Objects Objects


10% Files (SQR, COBOL, SQC, Crystal, Scripts, etc)On Both Unix & Windows Servers

90% Proprietary Database Objects (Record, Page, Index, PeopleCode, Activity, Component, etc)

WindowsUnix

WindowsUnix

WindowsUnix

DB DBDB


= Full Object Support100%

Only Stat Versions & Migrates Both PeopleSoft Objects & Flat Files Natively

Change Management without Quest

File-based Version Control

Custom Database

Documents

Spreadsheets

Project Plans

Email

PeopleSoftEnvironment

Change ManagementNeedsVersion control

PeopleSoft ObjectsFlat Files

Change ControlPatchingObject/File LockingMigration ManagementImpact Analysis Audit TrailsDocumentation

Project Management Enforced WorkflowProject ManagementTask assignment,Tracking, Time Reporting

Native App Tools

Paper Forms

Change Management without Quest


Change ManagementNeedsVersion control

PeopleSoft ObjectsFlat Files

Change ControlPatchingObject/File LockingMigration ManagementImpact Analysis Audit TrailsDocumentation

Project Management Enforced WorkflowProject ManagementTask assignment,Tracking, Time Reporting

File-based Version Control

Custom Database

Documents

Spreadsheets

Project Plans

Email

Native App Tools

Paper Forms

With Stat® ACM

Version controlPeopleSoft ObjectsFlat Files

Change ControlPatchingImpact AnalysisObject/File LockingMigration ManagementAudit TrailsDocumentation

Project Management Enforced WorkflowProject ManagementTask assignment, tracking, time reporting

Single Solution

Stat® ACMRepository


Change ManagementNeeds

Common Change Management Goals

Establishing Controls •Can we enforce our policy and procedures•Do our controls match way of doing business?

Providing an Audit Trail

•Can we track migrations & changes?•Can we track approvals?

Supporting Compliance

•Can we satisfy the demands of our auditors?•Can we satisfy the needs of management?

Increasing Efficiency •Can we improve our methods with technology?•Can we do more with less risk?

Enhancing Visibility • Can we predict the impact of change?• Can we provide clear reporting to better see what we need to see?

Reducing Risk & Downtime

• Can we recover when things fail in production?•Can we rollback if something does not work?

Enabling Communication

•Can we streamline communication with automation?•Can we require communication through controls?

Change Management

& Version Control graphic.


Providing an Audit TrailDo I know who changed what?

Establishing ControlsCan I enforce my policy and procedures today?

Supporting ComplianceCan I satisfy the auditors

and management?

Enhancing Visibility

What impact is change having and

can I report on those changes?


Are we all on the same page and being

proactively notified?

Reducing Downtime & RiskCan I rollback? Can I fix production?

Increasing EfficiencyAre we leveragingtechnology & automation?

Here is Outline of What we will be covering

Change Management


Let’s Start With Establishing Controls


Establishing Controls:

Physically lock down tools using object security in PeopleSoft

Prevent changes without a proper change request ticket

Require task completion before advancing in workflow

Ensure read-only access to developers without obtaining a lock in Stat

Require an approval before a change or migration can occur

1

2

3

4

5

1

Stat uniquely able to… (if required)

2

3

5

4

6

6

Use role based security to enforce separation of duties

Dev

Read only access to

tools

Physical Locking

Ticket

Approvals

Security

Tasks

Because Stat Can Physically Lock PeopleSoft

• Any Change made to PeopleSoft such as an– Enhancement– Migrations– Emergency Fix– Or Patch

• …will be captured and recorded in the Stat Master Repository

Stat® ACMRepository

Workflow Enables Control of Policy & Procedures

Workflow allows you to assign/configure business steps ensure that…

Proper person has the change request at the proper time

Approvals have been met before migrations or transfers are made to the next person

Tasks have been accomplished

Issues and Documentation have been logged

Migrations and post migrations have been performed (Build, DMS, COBOL, Custom)

Workflow Enables Control of Policies & Procedures

DatabasesPeople

Status RuleTransfer Rule

Require Tasks & Approvals

Approvals & Notifications via Email

Can be applied to:• Workflow Status Transfer• Migration

Change Management





Providing An Audit Trail Through CSR’s


WindowsUnix

WindowsUnix

WindowsUnix

DB DBDB

Electronic change request (CSR) tracks all changes made from development to productionCSR

EnhancementsCustomizations

Patches

CSR Audit Trail

Migrations(objects & files)

ApprovalsDocumentationTasks & Issues

CSR Audit Trail

Final Version

Manager Review

Notifications

Sign-Off

CSR Audit TrailOpen Ticket

Close Ticket

CSR Audit Trail

The Change/Service Request (CSR)

File Links

CustomTemplates

Attachments

Automatic & Enforced Audit Trail

ChangeFrom Value

To ValueLast Update

Update By

Change Management






Can I Rollback My Changes?

PeopleSoft Projects PeopleSoft Flat Files

RecordsPages

IndexesComponentsPeopleCode

Etc.

SQRCOBOL

SQREnvision

Crystal ReportsEtc.

CSRBaseline, Interim, Final

(archive sets)Stat Repository

Separated by

Tools Version inside

ProdDev Test

Quick Rollback for Files & Objects

Via Drag& Drop

Rollback Examples

PeopleSoft Projects PeopleSoft Flat Files

RecordsPages

IndexesComponentsPeopleCode

Etc.

SQRCOBOL

SQREnvision

Crystal ReportsEtc.

Stat Repository

ProdDev Test

Quick Rollback for Files & Objects

Drag& Drop

Something Fails in Production

Emergency Fix Migrates Over Developer

Database Refresh to Test

1

2

3

Change Management







What Types of Automation Does Stat Provide?

STAT Automation Manual Process

Automatic email notifications Reactive manual communicationor paper forms

Drag & drop migrations &rollback of files & objects

Manual project copy & FTP to all source life locations - manual recreation

Scheduled reports providingSeamless visibility of all changes

Manually compiling documentation fromseveral report unfriendly sources

PeopleSoft centric wizards for impact analysis, mass migration,customization history, recovery,and release management

Manual time consuming impact analysis,one-off migrations, stacks of compare reports, object recreation, non-migration or object based release management

Independent repository providingcentral location for audit trail ofdocumentation and forms

Paper forms or multiple disparate applications difficult to audit and/orreport against

How an Independent Repository Helps with Automation

Drag and Drop Migrations

(Objects & Files)

Version Control

WindowsUnix

DB

STAT Example #1: Automated Migrations

Example #2 Mass Migrations & Release Management

MultipleChange Requests(CSRs)

MultiplePeopleSoft

Projects

MultipleFile Types & Locations

Mass Migration

By Release

8.42 8.44 8.45 8.47 8.49

Dev Test Stage Prod Demo

By Ready for Environment

Change Management










Difficult Scenarios Which Require Communication

"What we've got here is failure to communicate."

Reserved

Environment Wide Object & File Locking

By Environment

“waiting for lock”“environment specific”

Prod Dev Test

Lock Lock Reservation

Locked

“exclusive rights”

Object Compare Wizard

• Compare Multiple Objects at a time

Locks & Reservations

If Someone already has a lock on your objectYou will get a reservation and can see informationabout who has the lock and what stage they are in.

Example #1: An Emergency Fix

Prod Dev

TestDeveloper has a page locked that will soon be needed for an emergency fix that without Stat might overwrite the developer’s work

Emergency fix must communicate with developer and cannot migrate over developer’s lock without proper permission

Developer can back up their work in Stat and unlock objects allowing fix to go through with the option to later restore their copy if they had done more work than the fix

1

2

3

CSR #101

Page A (dev)

CSR #102

Page A (fix)

DeveloperEmergencyFix

lock

Stat

Page A (dev)

Page A (fix)

Page A (fix)

Example #2: Automated Email Notifications

Due Date

CSR Assignment

Approval Pending

Email Trigger

Change Management













Increasing Visibility through Impact Analysis

Prod

Dev

Test

Patches, fixes, and enhancement often impact existing customizations

Visibility is needed to determine what objects or files will be potentially impacted and what customizations will be impacted as well?

Because Stat tracks object history and customization history we can warn you of any objects and/or files that may be impacted by introducing new change

1

2

3

Patches, Fixes & Enhancements

Stat

Customization History in Database

Existing Customizations



Causing Overwrites

What objects/fileswill be impacted?

What customizationswill be impacted?

Increasing Visibility Through Reports

Central Repository

Version Objects

Version Files

Track ApprovalsDocumentat

ionWorkflow & Notifications

Because of STAT’s central repository auditors and managers have deeper visibility into…

Object & File History

Migration History

Approval History

Documentation

Providing quick access to critical reports and informationthat otherwise may take days to produce manually

Reports

Web: Generate PDF Reports on demand

Change Management





Supporting ComplianceCan I satisfy the auditors

and management?









Supporting Compliance: Already Established Points

41

Establishing Controls

•We physically lock down tools•We can require an approval before any key step like migrating to prod

•Role Base Security

Providing an Audit

Trail

•We track all object & file changes and can audit tools for changes outside Stat•CSR tracks approvals, tasks, documentation and update history


• Central repository for reporting• 180+ reports•Version History and Customization Tracking with baseline restore capability

We provide what mostauditors &managersare looking for

Supporting Compliance & Best Business Practices

Compliance& Best

Business Practices

SOX

ITILCOBIT

CMDB

Separation of Duties

Approvals

Workflow

Role Based Security

Stat Repository

Common Requirements STAT Solution

5.4 Architecture

Some of our Stat Customers

http://www.citigroup.com/citigroup/homepage/index.htm


http://www.accenture.com/xd/xd.asp?it=enweb&xd=index.xml


http://www.ing.com/

http://www.intel.com/index.htm?iid=HPAGE+header_intellogo&

http://www.lockheedmartin.com/wms

http://www.pfizer.com/main.html

http://www.capitalone.com/

http://www.standardchartered.com/

http://www.hilton.com/en/hi/index.jhtml

http://www.avis.com/AvisWeb/home/AvisHome;jsessionid=AN53CwNu3WMwyegDkrRM2eN2Pa1ePOyJwAFMyNqPJ2OFg5E1RUlS!558896041

Thank You

• For More Information Please Visit• http://www.quest.com/application-change-manageme

nt/

http://www.quest.com/application-change-management/

http://www.quest.com/application-change-management/