«

»

Jul 25

Print this Post

Data Migration Workbench

Till PeopleTools 8.52, application version 9.1, to migrate the configuration data from one PeopleSoft environment to another, there were different custom methods customers had to try, DMS scripts, SQL scripts etc. With the release of PeopleTools 8.53 and application 9.2, Oracle has come up with a new tool and methodology, “Data Migration Workbench”, which will help customers to do this task without applying any of the custom methods.


This tool provides a method of migrating configuration data between environments as managed objects, rather than using DMS, SQL scripts. With Data Migration Workbench, one can migrate application configuration data. This tool will copy all/selective data from the source database configuration tables to a flat file base and later the flat File can be loaded to target database and before copying the data to target data base one can compare the data too and then load it. This tool has permission and approval process also in between.

Data Migration Workbench facilitates the Configuration Management process using Application Data Sets. The Data Migration Workbench is designed to manage the complexity of migrating configuration data across multiple PeopleSoft systems. The Data Migration Workbench provides the ability for any authorized developer to easily define application data sets and to compare and copy the data similar to the way managed objects have been copied and compared.

Application Data Sets:

•Enable developers to use PeopleSoft Pure Internet Architecture (PIA) to define data set definitions as a hierarchy of records with some collective properties. A data set definition defines the shape of data set instances. It consists of a hierarchy of one or more record definitions and some properties. Each child record has all the keys of its parent record and optional additional keys. A data set instance has a single root row defined by the unique keys of the root record.

Data set definitions are like record definitions: record definitions define a group of fields that constitute a record; data set definitions define a group of records that constitute a data set. Both record definitions and data set definitions are metadata that define the shape of data.

•Enable developers using PIA to insert data sets instances ( data content) into projects to represent a unit of work as a data migration project. Data migration projects are like managed object projects: a collection of data set instances having various data set definitions.

•Enable developers using PIA or Change Assistant to copy and compare projects containing data sets.

•Enable PIA-based copy and compare to use powerful servers rather that the Windows workstations required for PeopleSoft Integrated Development Environment (PSIDE)-based copy and compare. (Copy and Compare can also be run from Change Assistant using Application Engine)

•Integrate with the Enterprise Components Approval Framework to provide administrative control of the project copy from file process.

•Provide enhanced security to assure that the data set definitions are suitable for copying data, that the user has access to the PIA data set pages, and that user has the right to copy and compare the data.

•Provide an alternative to Data Mover that offers greater visibility and control for managed changes of a customer’s environment.

The two main components in data sets are the Data Set Designer used to define the structure of the data set and the Data Migration Workbench, used to define the data migration project content and to orchestrate copy and compare. Data Migration Workbench shows the current status of a project and prevents inconsistent actions. Once you have defined the data migration project, you can copy the data to a file that can later be compared or copied from file on another PeopleSoft database.

The Data Migration Workbench uses a Project Repository as a place in the file system where project files can be copied to and from. The Project Repository is defined in the data base as a repository name, an associated file path, and one or more areas (sub folders) that can contain project files. The purpose of Project Repository is to avoid manually copying project files from one system to another by promoting common definition of shared file locations and providing better security for administrative control of the places that project files can be copied to.

 

Data Set Component  

 

Flow for creating and copying Data Set Migration projects

 

 

 

 

 

Steps:


1. Create Data Set Definition.
2. Create or select then populate Data Migration Project.
3. Copy to file.
4. Compare Data Migration Project from file.
5. Review compare and validation reports.
6. Copy Data Migration Project from file.


Data Migration Workbench Limitations and Recommendations:


Limitations

•The Application Server and Process Scheduler used must both be able to access the project files using the same path. This will require that both are running on Operating Systems that use compatible file access conventions. For example, Microsoft Windows and UNIX-derived operating systems do not have compatible native file access conventions.

•The Application Data Set framework is not sufficiently secure in 8.53 to use for sensitive data.

•The data set definition must exist on the target database before you load a data set project to the target database.

•The data set definition must have the same shape on both the source and target database. Shape is defined by the records and fields included in the data set. Shape equality can usually be achieved most easily by copying a managed object project containing the data set definitions from source to target prior to copying the Data Migration Project. But if the constituent records and fields are different between source and target matching shape may involve executing database CREATE or ALTER steps to attain equivalence.

•Application Data Set definitions containing views or derived records are not copy-able or comparable.

•In 8.53, the language selections available in Copy from File do not include COMMON, thus COMMON cannot be excluded during copy. For traditional managed objects COMMON can be excluded, making it possible to copy only the language specific data, leaving the language-independent data (COMMON) unchanged if the object exists on the target.


Recommendations

•Data set projects are meant for relatively small data sets of static data.and not recommended for large data sets.

•Do not change the source Data Migration Project file after the compare been performed.

•Setting up the Project Repositories and areas is a one time activity. The directories should first be created by a system administrator with read/write access permissions for the users who will start the application and process schedule servers.

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2013/07/25/data-migration-workbench/

2 comments

  1. Peoplesoft Community

    Well it is very informative and useful for every one. keep it up.

  2. Anonymous

    Outstanding post however , I was wanting to know if you could write a litte more on
    this subject? I’d be very thankful if you could elaborate a
    little bit more. Bless you!

    Have a look at my web site home staging and redesign

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>