Deploys a group of internals, customizations, database, and datamover files to specified destinations from a package created by the packageBuild (PeopleSoft)operation. See the appendix for information about the package file attributes.
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) |
PeopleSoft JDBC Driver Path |
| Yes | Classpath for locating the JDBC Driver ( For example, |
PeopleSoft JDBC URL |
| Yes | The JDBC URL of the database.
|
PeopleSoft JDBC User |
| No | The username that will be used to connect with. |
PeopleSoft JDBC Password |
| No | The password for JDBC User. |
Data Mover Executable Path |
| Yes | The path to the Data Mover executable. |
Build Configuration File |
| No | The path to the RDM Build Config File. The build operation will use the settings defined in this file when generating SQL files. If provided the output directory will be ignored. You can see an example RDM Build Config File in our Special Considerations below. |
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. |
Database SQL Files Retry Count Default |
| No | When populating or evaluating files, default the Retry Count to the specified value (0-5). This property sets the default attribute value for populated project files, and does not impact the deployment behavior of existing project files (unless explicitly re-evaluated to pick up the default). |
Database SQL Files Ignore Failure Extensions |
| No | When populating or evaluating files, set the Ignore SQL Compilation Errors attribute to true for files with these extensions (e.g. .tbl,.idx). This property sets the default attribute value for populated project files, and does not impact the deployment behavior of existing project files (unless explicitly re-evaluated to pick up the default). |
Database SQL Files Ignore Compile Error Extensions |
| No | When populating or evaluating files, set Ignore Failure to true for files with these extensions (.pks, .pkb). This property sets the default attribute value for populated project files, and does not impact the deployment behavior of existing project files (unless explicitly re-evaluated to pick up the default). |
Database SQL Files Property Replacement Default |
| No | When populating or evaluating files, default Property Replacement to this. This property sets the default attribute value for populated project files, and does not impact the deployment behavior of existing project files (unless explicitly re-evaluated to pick up the default). |
Database SQL Ignore Drop Failures |
| No | When executing drop SQL statements ignore errors. Useful if SQL files consistently have DROP statements but dropped entity does not always exist. Defaults to false. |
Database SQL Files Root Target Folder |
| No | The path to store the delivered Sql files. Sql files will be run from here. Leave blank to run them from the FD_TEMP_DIR. |
Internal Files Retry Count Default |
| No | When populating or evaluating files, default the Retry Count to the specified value (0-5). This property sets the default attribute value for populated project files, and does not impact the deployment behavior of existing project files (unless explicitly re-evaluated to pick up the default) |
Internal Files Ignore Failure Extensions |
| No | When discovering or evaluating files, set Ignore Failure to true for files with these internals type file extensions. |
Internal Files Property Replacement Default |
| No | When populating or evaluating files, default Property Replacement to this. This property sets the default attribute value for populated project files, and does not impact the deployment behavior of existing project files (unless explicitly re-evaluated to pick up the default). |
Internal Files Root Target Folder |
| No | The path to store the delivered Internal files. Leave blank to run them from the FD_TEMP_DIR. |
Customizations File Owner:Group Default |
| No | When populating or evaluating Files, default the Owner:Group value to this. |
Customizations File Permissions Default |
| No | When populating or evaluating Files, default the Permissions to this. |
Customizations File Execute Default |
| No | When populating or evaluating Files, default the execute option to this. Defaults to false (unchecked ). |
Customizations Files Ignore Failure Extensions |
| No | When discovering or evaluating files, set Ignore Failure to true for files with these extensions. |
Customizations Files Property Replacement Default |
| No | When populating or evaluating Files, default the Property Replacement option to this. Defaults to true(checked ). |
Customizations Files Root Target Folder |
| No | The path to store the delivered customization files. Leave blank to run them from the FD_TEMP_DIR. |
Customizations Files Use Source Path Default |
| No | When populating or evaluating Files, default the Use Source Path option to this. Defaults to true(checked ). |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
PeopleSoft Project Name |
| No | Used on Build. The name of the PeopleSoft project. Overrides the project property with the same name. Deployments will use the project name from the build. If multiple operations are used on the package build, they must have the same value. |
Execute SQL |
| No | If true the generated SQL files will automatically be executed against the target database. |
Additional Parameters |
| No | Additional parameters to be added to the PeopleTools command. |
Run Destructive |
| No | Destructive SQL statements are allowed to be run if checked. |
Show DBMS Output |
| No | Print DBMS Output in log. Only supported for Oracle Database. |
Show SQL |
| No | Print SQL statement in log. |
Artifacts
This operation consumes packages of files created by the packageBuild (PeopleSoft) operation.
Endpoint Selection
This operation delegates the selection to the workflow developer to determine.
Endpoint Execution
This operation will randomly execute on one of the endpoints identified during selection.
Special Considerations
See below for information about the project file attributes.
Supported Object Types
The PeopleSoft plugin partial deploy support allows for deploying Internals, Customizations, Database and Datamover type objects. These links explain the four types and their attributes.