...
| Info |
|---|
This operation can only be used in peoplesoft package deployment projects of type PEOPLESOFT. |
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Database Type |
| Yes | The type of source database to which to connect to. (e.g. ORACLE, SYBASE, etc.) |
Database Name |
| Yes | The name of the source database to which you are connecting. |
PeopleSoft User |
| Yes | The user ID to use to sign into the source database. |
PeopleSoft Password |
| Yes | The password for the specified user ID for the source database. |
PeopleSoft Connect ID |
| No | The ID that is used to connect to the database. |
PeopleSoft Connect Password |
| No | The password for the specified connect ID. |
PeopleTools Executable Path |
| Yes | The path to the PeopleTools executable. (pside.exe) |
Customizations Home Folder |
| No | Location where your customized PeopleSoft application files are installed. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
PeopleSoft Project Name |
| Yes | The name of the PeopleSoft project. |
PeopleSoft Object Types |
| No | Comma separated list of object types as numbers to be included. If not provided all object types will be included. (e.g. 0,2,65,78) |
Database SQL Files Extension Order |
| No | SQL file extensions indesired order. Will be used for discover and sort. Files with these extensions will discover as type DATABASE Object. Specify the list of comma-separated extensions if you would like to change. |
Internal Files Root Source Directory |
| No | Where xml/INI file's package resides. Default is internals. |
Customization Files Root Source Directory |
| No | Where customization file's package resides. Default is customizations. |
Database Files Root Source Directory |
| No | Where SQL file's package resides. Default is sql. |
Datamover Files Root Source Directory |
| No | Where Datamover dms file's package resides. Default is dms. |
Project File Includes |
| No | Controls files included in Project Files during populate. Enter expressions separated by ##. Leave empty to select all files. Begin or end the expression with * for simple wildcards. Otherwise, regex is used (e.g. /java/*##*.java##*person*##/java/.*[tT]est.*\.java). |
Project File Excludes |
| No | Controls files excluded from Project Files during populate. Enter expressions separated by ##. Leave empty to select all files. Begin or end the expression with * for simple wildcards. Otherwise, regex is used (e.g. /java/*##*.java##*person*##/java/.*[tT]est.*\.java). |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Additional Parameters |
| No | Additional parameters to be added to the PeopleTools command. |
Artifacts
This operation builds a zip file artifact and saves it to the artifacts repository.
...
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
| Code Block |
|---|
-- 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
| Code Block |
|---|
-- 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;
|
If a package contains both EXPORT and IMPORT scripts,
During the packageBuild operation, the DMS EXPORT scripts are executed, generating an output DAT file.
This generated output is then saved to the artifact along with the EXPORT and IMPORT scripts.
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.