PeopleSoft Lifecycle Tools Data Migration Workbench

A new way to manage your application data

Dave.Alexander@ChildrensColorado.org March 2015

Overview

• About Children’s Hospital Colorado

• What is Data Migration Workbench? • Live Product Demo

• Dive into the product features

• Application Data Sets • Data Set Definition Tool • Data Migration Workbench Tool

• Implementation considerations • Recommendations

• Questions & Answers

2

3

About Children’s Hospital Colorado

4

About Children’s Hospital Colorado

5

resources for you

• ChildrensMD Symptom Checker Mobile App

• Abundant Parent Resources online @ www.ChildrensColorado.org

/wellness-safety

/parent-resources

6

What is Data Migration Workbench?

• Allows packaging of structured data • Application Data Sets (ADS) built in Data Set Designer tool

• Migration of ADS uses Data Migration Workbench tool • Compare

• Uses Upgrade compare philosophy

• Change*, Absent, etc.

• Validation & Transformation Framework

7

What is Data Migration Workbench?

• Security options available • Who can Copy To File from source

• Who can Compare data in target from source file

• Who can Copy From File into target environment

• Scheduling and Approvals • Uses Workflow Approvals (AWE) to allow supervisor approval

before loading into target

• Allows scheduling of Copy From File

8

Data Migration Workbench Features

• Simplicity • More convenient and easier than custom DataMovers • Empowered analysts / developers can move configuration data

around between environments • Based on your security requirements, of course

• Saves effort over hand-keying into each environment

• Integrity • Improves accuracy of moving configuration • Can transform and validate data automatically • Can compare data between environments

• Compliance • Allows configuration data to be a managed object • Meets change control / ITIL needs • Workflow Approvals before migration can occur

9

Demo – Let’s see it!

• Let’s take a look at a quick demo • Set up an ADS using Dataset Definition Tool

• Create a ADS Project using Workbench Tool

• Migrate data to File

• Compare in target environment

• Copy into target environment

10

Application Data Sets

• Uses Dataset Designer tool • >PeopleTools >Lifecycle Tools >Migrate Data >Dataset Designer

• Two ways to build ADS

• Generate • You provide the component name, it figures out the rest • Really easy • You’ll probably use this 95% of the time? • Dropped in 8.54

• Manual • You enter the base record • Enter other dependent records in hierarchical fashion

• Some ADS are delivered, more on the way

• Beginning with PeopleTools 8.54, Related Content, Pivot Grids, Activity Guides, Work Centers, and SES, will be managed using ADS in order to take advantage of the new merge and relationship frameworks

11

ADS Validation Framework

• Basic Validations

• Static prompts, translates, Y/N values and require fields validation

• Run for entire project before Copy or Compare actions

• If validations fail, Copy/Compare will not occur

• No PeopleCode required – these always fire

• Application Class Extensions

• Used to validate or transform data

• Extends PTADSDEFN:AdsValidationBase class

• Implement methods

• PreCopyCompare

• OnPreUpate

• OnPostCopy

12

When ADS validation class methods called?

Method When Called

Basic Validations Compare from File First pass of copy from file

OnPreCopyCompare Compare from File First pass of copy from file, prior to copy

OnPreUpdate Compare from File Second pass of copy from file, immediately before copying to database

OnPostCopy After Copy from File

• Details of exactly how to implement these methods in PeopleBooks • https://docs.oracle.com/cd/E38689_01/pt853pbr0/eng/pt/tads/task_

DefiningValidation-a28000.html

13

Important things to know about ADS

• Managed objects in Application Designer • Called Data Set Definitions

• Must be in target environment before usage

• Must be the same “shape” in both source and target • This is relaxed starting in 8.54

• Will not work with derived records or views

• Record keys • Children must match parent record

• Order of keys must be the same

• ADS only shows parent records’ keys -- View Keys button

14

Data Migration Workbench Security

• Page Security • Permission List: PTPT3500 • Role: ADS Designer

• Record-level security • Much like Query, uses Query Access Trees • Permission List based • NOTE: If you upgraded your Query Trees they are not likely current version,

you may want to consider pulling delivered Query Access Trees from PUM/Demo to include all new records

• Workbench Actions • Who can Compare and Copy • Permission List based

• Change Assistant uses upgrade override security to ensure full access during updates & upgrades

15

Data Migration Security

• Navigation: >PeopleTools >Security >Permission Lists

• New tab: Data Migration • Access Group Permissions

• Copy Compare Permissions

16

Access Group Permissions

• Choose needed Query Tree(s) and Access Group(s)

• Read checkbox required for: • Copy to File

• Compare

• Write checkbox required for: • Copy from File

17

Copy Compare Permissions

What can the user do in the Workbench?

• Allow Setting Copy Compare Attributes on Dataset Definitions checkbox • This privilege should only be given to architects with a thorough knowledge of the data set

definition and its associated data content who would certify data set definitions to be copyable and comparable. A flawed data set definition could corrupt a data base…

Copy Compare Access

Copy to File

Copy from File

Compare from File

No Access No No No

Read-Only Access

Yes No Yes

Full Access Yes Yes Yes

18

ADS Workflow

• Useful if you want a supervisor to approve before request can be scheduled

• Approval Workflow Engine • MigrateData

• Security Roles utilized • EOMW_REVIEWER

• EOMW_APPROVER

• Can review workflow status in Workbench

19

ADS Technical Configuration

• File Repository • ADS migrates using XML Files

• XML files are in plain text and are thus unsecured

• Must be on same server as Application Server and Process

Scheduler

• Depending on your migration policies, you may need a shared file system

• >PeopleTools >Lifecycle Tools >Migrate Data >Manage File

Locations • Path on server to shared folder • “Areas” are sub-folder name(s)

• Use environment names

20

Data Migration Workbench

• Navigation: >PeopleTools >Lifecycle Tools >Migrate Data >Data Migration Workbench

• Either add, search or load from file a Application Data Set project • Have your Architect(s) create these

• Others can use them to export data sets

• Project’s content of Data Sets are always organized alphabetically • If you need to load multiple dependent items, make sure their

names are chronological alphabetically

21

Adding Data Sets to your Project

• Type it in, Prompt View or Data Set Tree Search

• Tree Search • Look for *

22

Adding Data Set Content

• Use drop down to select which Data Set (if more than one was added) • This page can be slow

23

Insert Content Tips

• Use filters to improve performance of the page

24

Copy To File

• As simple as pressing the button • Need at least Read-only security for Copy Compare

25

Copy to File window

• Choose location (server) and area (folder) • Defined in >PT >LCT >Migrate Data >Manage File Locations

• Choose Run and submit the process • Ensure you are running on the appropriate server

• Then press OK to exit modal window • A bit confusing…

26

Compare and Load

• Requires that the Data Set Definition is • Already migrated into target

• The same structure (“shape”) in both environments

• Done in target’s Data Migration Workbench • Load Project From File

27

Compare

• Again modal window is a bit confusing • Choose languages (all)

• Always Run on correct server first

• Then click OK to return to DMW

• Use refresh button until process is complete • Progress will update in DMW window

• Compare Report tab takes a little getting used to • Play with it

• What is your experience with the Compare tool? Oracle is looking for some feedback and suggestions

28

Compare Report

• Click on record for details to show up in Compare Report grid or choose filters

29

Compare Report

• Very wide, scroll left/right

• Use grid’s Push to Excel functionality

Push To Excel

Highlight level of interest

30

Compare Report

• Data Set Instance, Record Field

• Source / Target Upgrade

• Source / Target Values

• Action / Upgrade / Done flags

31

Validation Report

• Most important column is Message Text

• Often highlights that other ADS should be loaded first?

32

Copy From File

• Validations must have all passed • Security dictates who can Copy From File • Load can be scheduled • Must go through approval successfully before load is

scheduled • No approvals required?

• Inactivate MigrateData AWE • or assign role to no-one (no approvals required) • or assign role to just yourself (self-approved)

• Modal window works a little differently on Copy • Does not request server like Copy To and Compare • PTADSAEPRCS Process Definition must have default server set to

where your file repository exists

• Review Approvals link at bottom of Workbench

33

Ready to Implement?

• Configure Environment • Created shared folder that Application Server and Process

Scheduler both have access to • Create “areas”, likely environment names (sub-folders)

• Configure Security • Who will be migrating data? • Who will be creating ADS? • Who can Compare? • Who can Copy? • Who can access what Records?

• Build Application Data Sets • Migrate ADS to source and target environments with

Application Designer • Start using the Data Migration Workbench!

34

Simple Security Model DMW=Data Migration Workbench Tool DSD=Dataset Designer Tool

• Production / Q&A environments (no approvals) • Administrative Role

• DMW: Can Copy From File

• DMW: Everything else

• DSD: No access

• Analyst Role

• DMW: No Copy From File

• DMW: Everything else

• DSD: No Access

• Non-production environments • DMW: Analysts have Administrative Role

• DSD: Architects can build Application Data Sets

35

A few initial standards

• Naming • Don’t use COMP_ for ADS that are auto-generated

• Use two-character module prefix

• PY_, GL_, BN_

• For multiple ADS in one project, use numbers

• For example…

• BN_PGM_03_DeductionCodes

• BN_PGM_05_EventIDs

• BN_PGM_10_BenefitProgram

• Projects

• Analyst initials as prefix

• Change Order Tickets use Ticket ID: ex. COxxxxxx_

36

ADS Limitations

• ADS Projects do not have a sequence number, ran in alphabetical order • Know dependencies?

• Do some prompt values have to be loaded first? • Use a numbering scheme in the Data Set Definition

• Adding ADS Project content can be painfully slow • For example, Benefits Event Rules configuration have many values, all with many

effective dates • Use the filters!!

• Some components will not work • Perhaps a creative workaround?

• PeopleBooks says: “Data set projects are meant for relatively small data sets of static data” • Vague, not sure what this means ???

37

Contact me at: Dave.Alexander@ChildrensColorado.org

38