Moving Entity Registry Data Between Databases
(Doc ID 1623119.1)
Last updated on JULY 10, 2020
Applies to:PeopleSoft Enterprise CS Student Records - Version 9 and later
PeopleSoft Enterprise CS Recruiting and Admissions - Version 9 and later
PeopleSoft Enterprise CS Campus Community - Version 9 and later
Information in this document applies to any platform.
PeopleSoft Campus Solutions leverages the Entity Registry to provide a secure and unified means to access data in features such as AAWS, Delegated Access, New User Registration Framework and the Rules Engine.
An Entity is an object that provides access (view, create, update) to data in a record. The properties on the Entity represent the fields in the actual records. By design, an Entity is the primary point of access to the underlying records. This avoids potential inconsistencies between multiple instances of the same logic, helps make relevant code reusable, and streamlines maintenance.
Although Entities are delivered and can be used without alteration, Entities can be extended to include other child entities as well as properties. Customers also have the ability to create their own (read-only) entities, entity views and entity profiles. As extension and setup is typically done in test environments, this setup may need to be migrated to other environments. Oracle delivers Entity Registry setup as System Data. This predefined system data is made available via DataMover scripts and data files (dat and dms files). It is expected that customers will create their own entities in a test environment before migrating to production. Because the setup is extensive, repeating it in each environment would be a daunting task. The following set of instructions is provided to assist with the migration of Entity Registry setup data between environments.
The process of migrating Entity Registry setup data includes two steps:
- Exporting Entity Data: Create an export DataMover script that will create a DataMover .dat file to export data from the source database
- Importing Importing Data: Create an import DataMover script to import the data in the .dat file to the target database.
After Entity Registry data is migrated, it is necessary to synchronize the entity properties. For instructions on running the synchronization processes for the Entity Registry, please see the following KM article: Maintaining Campus Solutions Entities [Doc ID 1546057.1]
This document is intended as a guide to assist customers who want to migrate Entity Registry data between databases. While great care was taken to ensure the accuracy of the information, it is possible misspellings and typographical errors occurred during code transposition into this document. Therefore, great care should be exercised before using any scripts created by this code. Oracle does not assume responsibility for issues caused by writing scripts based on the information in this document.
The Sample code provided in the next two sections are formatted as follows:
EXPORT STATEMENT: EXPORT FROM ps_table WHERE fieldname IN (‘value1’,’value2’,…);
IMPORT STATEMENT: DELETE FROM ps_table WHERE fieldname IN (‘value1’,’value2’,…);
This following is an explanation of the statement:
- ps_table – the name of the table where data will be exported
- fieldname – the name of the field used as the unique identifier, there may be more than 1 fieldname to comprise the unique key
- valuex – the value of the key field
Table and fieldnames are provided in the below statements and should not be changed. Each statement contains placeholders for a list of values (VALUE1, VALUE2). Insert your own list of valid value for export inside the parenthesis, surrounded by single quotes, and separated by a comma.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Exporting Entity Data|
|Importing Entity Data|