Canada Presentations

When we began creating Comm Gens in earnest we relied upon Data Mover Scripts to migrate the many records of Comm Gen config data through our dev to prd stream of environments. These were manually created, and required significant communication between functional and technical resources to make sure all data was captured, exported and imported correctly.

From there, I introduced Data Migration Workbench to our team with PeopleTools 8.55. This required the creation of custom Data Sets. This tool greatly increased the confidence that when a migration was completed it was comprehensive - no missing pieces! However, this did require manual execution of delivered Application Engine processes in each environment, including PRD. Still an improvement, but still restrictive.

A short time later Phire introduced support for Data Migration Workbench scripts. Now we can create a data migration project, copy it into our Phire repository, and migrate it in the same manner as all other migrations. This allows easy and rapid delivery of configuration or test data without needing elevated permissions or in depth technical knowledge.

We now use Data Migration Workbench and Phire for all new Comm Gen deployment. Additionally, we have had great initial success using it to manage and migrate the large volume of configuration changes required by our OUAC XML Admissions overhaul project. We are also experimenting with packaging and migrating synthetic test data.