packageBuild (PeopleSoft)
- Karl Henselin
- M L Mounika
- Victor Krieg
Creates a build artifact containing Internals, customizations, database and data mover files. For builds sourced from SCM, artifacts are generated for all object types. However, for builds originating from PEOPLESOFT, artifacts for customizations are produced from the peoplesoft server endpoint, while those for Internals are produced from the peoplesoft client endpoint. This artifact is then used by the packageDeploy (PeopleSoft) operation.
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 |
| No | The name of the PeopleSoft project. If not provided, defaults to FD_PROJECT_NAME. |
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. Â
Endpoint Selection
This operation will select all available endpoints associated to the Target.
Endpoint Execution
This operation will randomly execute on one of the endpoints identified during selection.
Supported Object Types
The PeopleSoft plugin package-based support allows for deploying Internals, Customizations, Database and Datamover type objects. These links explain the four types and their attributes.
Object Types
- style