PeopleSoft Object Types - Datamover
A PeopleSoft Data Mover script file is used to import or export data between PeopleSoft databases. These script are platform-independent and unique to PeopleSoft Data Mover.
FlexDeploy's PeopleSoft plugin facilitates the migration of data through data mover scripts, enabling both import and export operations. These scripts are stored in SCM as datamover type objects. Generally, two scripts are utilized for migration: one for export and one for import.
To streamline the process, a package containing both files must be created in FlexDeploy's Package based PeopleSoft's project. During the Build workflow execution, FlexDeploy's PeopleSoft plugin executes the export script on the source database, incorporating the exported data file into the artifacts. Subsequently, during the Deploy workflow execution, the import script is executed on the target database utilizing the data file retrieved from the artifacts.
Attributes
Name | Code | Description | Default Value |
|---|---|---|---|
Source |
| Object Source Location Type | SCM (**populating from SCM) |
Notes: DataMover Scripts(.dms)
Data Mover is the best way to export and import data between PeopleSoft databases.
PeopleSoft Data Mover requires two files to be available on the target before execution:
Control file (which ends with a .dms extension)
Data file (could be any file CSV, db, DAT)
Sample EXPORT script is
-- REF0001 DD/MM/YYYY Author
-- Brief explanation of what is being exported
SET LOG C:\REF0001_EXPORT.log;
SET OUTPUT C:\REF0001.dat;
EXPORT TABLE_NAME;sample IMPORT script is
-- REF0001 DD/MM/YYYY Author
-- Brief explanation of what is being exported
SET LOG C:\REF0001_EXPORT.log;
SET INPUT C:\REF0001.dat;
IMPORT TABLE_NAME;Â
SET LOG filename.log
The SET LOG command specifies the name of the log file where execution information is stored when running a PeopleSoft Data Mover script or command. This log file is automatically created during script execution and contains details such as errors, warnings, and status messages.
SET OUTPUT filename.DAT
The SET OUTPUT command specifies the output file where data is written when running a PeopleSoft Data Mover script. This command directs the script to save its output to a specific file for further analysis or processing.
SET INPUT filename.DAT
The SET INPUT command specifies the input file from which data is read when running a PeopleSoft Data Mover script. This command allows the script to access the necessary data for processing, such as importing data from the source file. These commands are essential for managing input and output files in PeopleSoft Data Mover scripts, ensuring that data is processed correctly and that detailed execution information is logged for monitoring and troubleshooting purposes.
Â
If a package contains both EXPORT and IMPORT scripts,
Build
During the packageBuild operation, the DMS EXPORT scripts are executed, generating an output DAT file.
The paths specified in the scripts for SET LOG and SET OUTPUT are replaced with the FlexDeploy current execution temp directory, while the file names remain the same,
ensuring that the DAT and LOG files are generated in the FlexDeploy temp directory upon completion of the execution.
The generated output, including the DAT file, is saved to the artifact along with the EXPORT and IMPORT scripts. Additionally, the LOG file is saved to the Report Directory during the packageBuild operation.
Deploy
During the packageDeploy operation, the IMPORT scripts read the input DAT file from the artifact (generated by the build operation) and execute the IMPORT scripts.
The paths specified in the scripts for SET LOG and SET INPUT are replaced with the FlexDeploy current execution temp directory, while the file names remain the same,
If the file is part of the artifact generated by the build operation, it is available in the current temp directory, and the execution will continue with the file. Upon completion, the log file will be saved to the Reports Directory.
after finishing log will save to Reports DIRectory
- style