Using Application Data Sets
The Application Data Set functionality includes the Data Set Designer component (PTADSMMGR) and the Data Migration Workbench component (PTADSDMW):
Data Set Designer
Authorized administrators use the Data Set Designer to create data set definitions (ADS definitions) as a hierarchical structure of records and their collective properties.
A data set definition, with its group of records, constitutes a data set. Both record definitions and data set definitions are metadata that define the shape of the migration data. The same data set definition must exist in any PeopleSoft database that participates in a data set copy or compare.
For more information about Data Set Designer, see PeopleTools: Lifecycle Management Guide, “Using Data Set Designer”.
Data Migration Workbench
Authorized administrators can then use the Data Migration Workbench to insert data set instances (data content) into projects that represent a unit of work as a data migration project. Data migration projects are like managed object projects: a collection of data set instances with various data set definitions. The Data Migration Workbench enables administrators to copy and compare projects containing data sets as well as view compare reports and validation reports.
You can also integrate the Enterprise Components Approval Framework to provide administrative control of the Project Copy from File process. Employ enhanced security to ensure that the Data Set definitions are suitable for copying data, to enable user security for the data set pages, and assign access to copy and compare the data. PeopleSoft delivers the MigrateData process ID for enabling data migration Approval Framework.
For more information about security, see PeopleTools: Lifecycle Management Guide, ”Implementing Data Set Security”.
Following is an example of steps for migrating application data sets using the Data Migration Workbench:
Create a Project for your migration using the Add New Project page, by entering a Project Name and Description.
Select PeopleTools, Lifecycle Tools, Migrate Data, Data Migration Workbench. From the Project Search page, click the Add a New Value link.
On the Data Migration Workbench page, select the Data Set Name look-up icon.
On the Look Up Data Set Name, select the Data Set Name referenced for the application data set.
On the Insert Data Set Content page, select values (or content) for specific fields that are used for that data set and you want to migrate to another database.
For example, for the SETID field name, select SHARE in the Values column. Additional field names are available depending on the data set.
Click the Search button.
Review all values in the Search Results section of the Insert Data Set Content page to verify that all desired content is selected.
If you want to narrow your results:
Repeat steps four through five until you get your desired results.
Select only the content you want to include.
Select the Insert Content or the Insert and Return button:
The Insert Content button to insert selected content into your project, but remain on the Insert Data Set Content page to perform another search.
The Insert and Return button inserts the selected content and returns you to the Data Set Content page
Repeat steps two through seven for all application data sets for the project.
On the Data Set Content page, select the desired content for the data set and select the Insert Content button.
The system returns to the Data Migration Workbench page with selected content in the Project Content section.
Click Save on the Data Migration Workbench page.
When saving , the Project Status changes from New Project to Created. You cannot save the project if you have not included data set content for each data set in your project.
Click the Copy to File button on the Data Migration Workbench page.
You must have a valid file location defined on the Manage File Locations page before you can perform this step. See PeopleTools: Lifecycle Management Guide,.
Click the Run button from the Copy to File page.
Access the process monitor to check progress. When the process completes, the Project Status in the Data Migration Workbench becomes Copy to file succeeded.
Verify that project files are copied to the file location as specified on the Manage File Locations page.
Log in to the target database to import the project file.
Access the Data Migration Workbench, Project Search page, and click the Load Project From File link.
Select the copied location and the project to import from the Load Project From File page and click the Load button.
On the Data Migration Workbench, Project Search page, find your migrated project and select it to access the Data Migration Workbench page.
Click the Compare button to launch the Copy and Compare process (PTADSAEPRCS) and click Run.
Access the process monitor to check progress. When the process completes, the Project Status in the Data Migration Workbench for the project becomes Compare from file succeeded.
Upon completion, a compare summary is displayed on the project definition page. Statistics are displayed for each data set definition in the project indicating the count of data set instances based on type (additions, deletion, differences, same or message). When you click on a count the compare report is displayed.
If all looks as expected, return to the Data Migration Workbench page for your project, click the Submit for Copy button and then click Run.
Upon successful completion of the Copy and Compare process (PTADSAEPRCS), you can navigate within your target database and find the migrated Allocation Steps and Allocation Groups.