session 34694 march 16, 2015. it makes migrating both transaction content and application components...

50
Expanding the Data Migration Workbench Session 34694 March 16, 2015

Upload: stephany-dana-townsend

Post on 06-Jan-2018

220 views

Category:

Documents


0 download

DESCRIPTION

SaNSSaNS Default Data Migration WorkbenchDefault Data Migration Workbench Extended Data Migration WorkbenchExtended Data Migration Workbench Problems, what – ifProblems, what – if Work-aroundsWork-arounds Questions ?Questions ? Agenda

TRANSCRIPT

Page 1: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Expanding the Data Migration Workbench

Session 34694March 16, 2015

Page 2: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

It makes migrating both transaction content and application components much easier. But not all migrations we want to do are supported - complex components, - components containing sibling records, - workcenters and dashboardsIn this presentation we will show you how you can expand the functionality of DMW and how you can overcome some of its shortcomings.

Data Migration Workbench DMW

Page 3: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

• SaNS• Default Data Migration Workbench• Extended Data Migration Workbench• Problems, what – if • Work-arounds• Questions ?

Agenda

Page 4: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

• Functional Developer at SaNS Expertise Center, since 2010• Background:

• Teacher Product Information at community college• Technical Developer

• Educational contracts NLD• Internship contracts NLD• Authorisation structure SaNS

Who is Henk Hebbink

Page 5: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

What is SaNS• SaNS: ‘Collaboration for a New SIS’ • 4 Universities in the Netherlands:

University of Amsterdam (Research Un.) Hogeschool van Amsterdam (Un. Appl. R.) Leiden University (Research Un.) Tilburg University (Research Un.)

• 120.000 students• 10.000 faculty users• 1000 administrative users• ‘Vanilla SaNS-CS’• Joint maintenance and development

(Expertise Center)

Page 6: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Expertise CenterExpertise Center• Joint effort of the 4 Universities• Responsible for:

Hosting of the InfrastructureTechnical MaintenanceApplication MaintenanceApplication Development and CustomizationServicedesk, support, testing, set up

• Delivers SaNS-CS as a SaaS-Solution• 13 FTE employees; 2 FTE external• (support, technical and functional)• Hosting is outsourced

Page 7: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

SaNS: Situation on Oracle• PeopleSoft Campus Solutions 9• Bundle #33• Modules in use:

Campus CommunityStudent RecordsAcademic Advisement(Recruitment and) Admission(Student Finance)

• Student Self Service• Heavily customized application• PeopleTools 8.53.04• Infrastructure and Database• Oracle 11g• 29 CS-environments (each institute 5 / 9 DEV)• 50 Physical servers, no VM

Page 8: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

PeopleTools>Lifecycle Tools>Migrate Data>Dataset Designer

Data Migration Workbench

Page 9: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Oracle delivered datasets, examples are:DATASET TYPE DESCRSCC_RE_RULE_DEFINITIONS Generated Rules Engine Rule DefinitionsSCC_RE_RULE_GROUPS Generated Rules Engine Rule GroupsSCC_RE_STATEMENTS Generated Rules Engine Statements

MSG Manual Message Catalog Entries

ACTIVITY_GUIDE_ITEM Manual Activity Guide ItemACTIVITY_GUIDE_LIST Manual Activity Guide ListPTPPB_PAGELET Manual Pagelet Wizard PageletsPTPPB_PAGELET_USER_DATA Manual Pagelet Wizard User DataSCC_ENTITY_PROFILE Manual Entity Registry ProfilesSCC_ENTITY_REGISTRY Manual Entity Registry DefinitionsSCC_ENTITY_VIEWS Manual Entity Registry ViewsWL_GENERIC_TEMPLATES_DEFN Manual Workflow Generic TemplatesWL_NOTIFICATION_TEMPLATES_DEFN Manual Workflow Notification TemplateWL_TEMPLATE_VAR_DEFN Manual Workflow Template Variables

Dataset Designer

Page 10: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Dataset MSG

Page 11: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Contains parent, child and related language records:PSMSGSETDEFN - parentPSMSGSETLANG - language record

PSMSGCATDEFN - childPSMSGCATLANG - language record

Dataset MSG

Page 12: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

The records are related to each other by key: MESSAGE_SET_NBR

Dataset MSG

Page 13: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

You should be able to use every component to create your own dataset,but there are restrictions;

- The Component does not have any physical records.- Adding / Changing / Saving / Deleting data trigger PeopleCode

events, which has effect on other records.- The data migrated contains database specific strings / paths.

Creating your own dataset

Page 14: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

The Component does not have any physical records.

Generating dataset

Page 15: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Dataset for USERMAINT

Page 16: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Dataset for USERMAINT• Records on a Component can be detected by using the

querytool.

Page 17: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Record Type Parent Rec Rellang Rec. Rec DescrRUN_CNTLLDAP 0 Run Control for PT UtilitiesPSUSEROTHER_VW 1PSROLEUSER_VW1 PSROLEDEFN User RolesPSROLEXLATOPRVW 1 Role User ViewPSOPRALIASFIELD 0 Operator Alias FieldnamesPSOPRALIASTYPE0 PSOPRALSTYPLANG Peoplesoft ID TypesPSUSERATTR 0 User Security AttributesPSOPRALIAS 0 Peoplesoft ID ValuesPSOPRDEFN 0 Operator DefinitionPSROLEDEFN 0 PSROLEDEFNLANG Role Definition

Records USERMAINT

Page 18: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Record Type Parent Rec Rellang Rec. Rec DescrPSUSEROTHER_VW 1PSROLEUSER_VW1 PSROLEDEFN User RolesPSROLEXLATOPRVW 1 Role User View

Views can contain other views or records.

Again we can use the query tool to find out what additional records exist on the component.

Views on USERMAINT

Page 19: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Views on USERMAINT

Page 20: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

VIEW SQL STATEMENTPSROLEUSER_VW SELECT ROLEUSER , ROLENAME , DYNAMIC_SW

FROM PSROLEUSERPSROLEXLATOPRVW

SELECT OPRID , ROLEUSER , DESCR , EMAILID , FORMID , WORKLIST_USER_SW EMAIL_USER_SW , FORMS_USER_SW , EMPLID , ROLEUSER_ALT , ROLEUSER_SUPR , EFFDT_FROM , EFFDT_TO FROM PS_ROLEXLATOPR

PSUSEROTHER_VW

SELECT MENUNAME , BARNAME , BARITEMNAME , ITEMNAME , DESCR100 , ACTIVE_FLAG FROM PSUSEROTHER WHERE ACTIVE_FLAG = 'Y'

Views on USERMAINT

Page 21: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

USERMAINT records

Page 22: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

USERMAINT records

Page 23: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

USERMAINT component

Page 24: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

USERMAINT component

Page 25: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Create dataset manualThe record names begin with USER or OPRID. This suggests the key field is also USER or OPRID.You can check this with the querytool or in Application Designer.

Page 26: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Dataset USERMAINT_OPRID

Page 27: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

KEY USERMAINT_OPRID

Page 28: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Dataset USERMAINT_USER

Page 29: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Project Data Migration Workbench

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

• The easiest way to migrate the user information is to make a project containing both datasets.

• Oracle will do some checks by importing the project to make sure all items are present.

Page 30: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Project Data Migration Workbench

Page 31: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Project Data Migration Workbench

Page 32: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Project Data Migration Workbench

Page 33: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Project Data Migration Workbench

• You can use filters to select data for migration on Tab Data Set Content.

• The filter you can use is based upon the key within the dataset.

• Using the button Copy to File starts the Application Engine process for building the xml project.(similar to copy to file using the Application Designer tool)

• The directory where the files are placed is stored by Manage File Locations

Page 34: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

DMW Manage File Locations

Page 35: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

DMW Processing

Page 36: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Check before import

Page 37: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Check datasets

Page 38: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Create datasets

Page 39: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Load DMW Project

Page 40: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

• Import project file using an Application Engine

DMW Processing import

Page 41: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

DMW Processing logging

Page 42: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

• Everything is okay until the project is imported. PreCopy had one or more validation errors, please see validation report for details. (257,353)End Application Engine Process (257,402)

• The validation report shows:ROLEXLATOPR - Static Prompt Validation –

VALUE: HEUG_copy_student specified for the FIELD: OPRID on the RECORD: ROLEXLATOPR is not found in the PROMPT TABLE: OPERATOR_VW (257,501)While performing a prompt validation, the provided value does not seem to be available on the prompt table.  Please address this issue and perform the validations again.

• The Keys do not match; what to do ?

DMW Problems !!

Page 43: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

DMW Solutions• The 2 datasets contain a set of data that’s connected to

each other.• The validation is done before all items are stored in the

database.• Splitting the datasets makes it possible to do the migration

in different steps.

Page 44: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

DMW Work-aroundExport a project for each dataset

Page 45: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

DMW Work-aroundImport a project for each dataset.

Page 46: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

DMW Result• The target database contains after the import action a user /

oprid: HEUG_copy_student who is able to sign in with his original password.

Page 47: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Final result

Page 48: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Questions?

Page 49: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

• Henk Hebbink• Functional Development• SaNS-Expertise Centrum for

• Tilburg University• Hogeschool van Amsterdam• University of Amsterdam• Leiden University

• E-mail: [email protected]

Contact

Page 50: Session 34694 March 16, 2015. It makes migrating both transaction content and application components much easier. But not all migrations we want to do

Presentations from previous meetings are also available

This presentation and all Alliance 2015 presentations are available for download from the Conference site atwww.alliance-conference.com