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.

Please note that the statements in the Database object type SQL files must be delimited properly.

For Database objects : The SQL Databases supported by the parser are:

Oracle 10g+
- Using statement delimiter of ;
- PL/SQL blocks starting with DECLARE or BEGIN and finishing with END; /
MySql 5.1+
PostgreSql 9.0+
Derby 10.8.2.2+
SAP HANA
SQL Server 2008+
MariaDB 10.0+
Vertica 6.5+
H2 1.2.137+
solidDB 6.5+
SQL Azure
DB2 9.7+
AWS Redshift
Hsql 1.8+
Sybase ASE12.5+
SQLite 3.7.2+
DB2 z/OS 9.1+
EnterpriseDB 9.4+
Phoenix 4.2.2+
Greenplum 4.3+

No JDBC drivers are included in the plugin, so the path to one is required (FDPSOFT_JDBC_DRIVER_PATH).

This operation can only be used in peoplesoft package deployment projects of type PEOPLESOFT.

Target Properties

Property Name	Property Code	Required	Description
Database Type	`FDPSOFT_DATABASE_TYPE`	Yes	The type of source database to which to connect to. (e.g. ORACLE, SYBASE, etc.)
Database Name	`FDPSOFT_DATABASE_NAME`	Yes	The name of the source database to which you are connecting.
PeopleSoft User	`FDPSOFT_USER_ID`	Yes	The user ID to use to sign into the source database.
PeopleSoft Password	`FDPSOFT_PASSWORD`	Yes	The password for the specified user ID for the source database.
PeopleSoft Connect Id	`FDPSOFT_CONNECT_ID`	No	The ID that is used to connect to the database.
PeopleSoft Connect Password	`FDPSOFT_CONNECT_PASSWORD`	No	The password for the specified connect ID.
PeopleTools Executable Path	`FDPSOFT_PEOPLETOOLS_EXE`	Yes	The path to the PeopleTools executable. (pside.exe)
PeopleSoft JDBC Driver Path	`FDPSOFT_JDBC_DRIVER_PATH`	Yes	Classpath for locating the JDBC Driver ( For example, `/u01/app/oracle/product/12.1.0/dbhome_1/jdbc/lib/ojdbc6.jar`).
PeopleSoft JDBC URL	`FDPSOFT_JDBC_URL`	Yes	The JDBC URL of the database. Connecting to Oracle Autonomous Database You will need client credential zip file (wallet) to connect with Oracle Autonomous Database on Oracle cloud. You can download wallet zip file from Oracle Cloud, you will need admin userid and password to perform this download.See Download Client Credentials (Wallets) for more details on how to download wallet file. You must make sure that only authorized users have access to these wallet files. Unzip the client credentials zip file (wallet_databasename.zip) on endpoint where it will be used, which most likely will be FlexDeploy server as we generally use localhost endpoint for JDBC. For example, /home/flexdeploy/.wallets/<wallet_databasename> is folder where specific wallet file was unzipped. Make sure to secure this folder to FlexDeploy and/or Endpoint user, so that it is not readable by all users. Database URL Syntax : jdbc:oracle:thin:@service_high?TNS_ADMIN=/home/flexdeploy/.wallets/<wallet_databasename> service_high is one of the entries in the tnsnames.ora file where client credentials zip file was unzipped. See Predefined Database Service Names for Autonomous Database for details on services. TNS_ADMIN value in URL points to the location of the unzipped client credentials zip file. Database URL Long Connection String Format Syntax : jdbc:oracle:thin:@(description= (retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=<hostname>))(connect_data=(service_name=<serice_name>))(security=(ssl_server_cert_dn="CN=<hostname>,OU=Oracle BMCS US,O=Oracle Corporation,L=Redwood City,ST=California,C=US"))) Examples for the same can be found here
PeopleSoft JDBC User	`FDPSOFT_JDBC_USER`	No	The username that will be used to connect with.
PeopleSoft JDBC Password	`FDPSOFT_JDBC_PASSWORD`	No	The password for JDBC User.
Data Mover Executable Path	`FDPSOFT_DATAMOVER_EXE`	Yes	The path to the Data Mover executable.
Build Configuration File	`FDPSOFT_BUILD_CONFIG_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	`FDPSOFT_PROJECT_NAME`	Yes	The name of the PeopleSoft project.
PeopleSoft Object Types	`FDPSOFT_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	`FDPSOFT_SQL_EXTENSIONS`	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. Default value is: {{seq,tbl,idx,typ,tps,tpb,sql,pkh,plb,pks,pkb,pls,pck,fnc,trg,spc,bdy,prc}}
Database SQL Files Retry Count Default	`FDPSOFT_JDBC_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	`FDPSOFT_JDBC_IGNORE_FAILURE_EXT_DEF`	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	`FDPSOFT_JDBC_IGNORE_COM_ERR_EXT_DEF`	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	`FDPSOFT_JDBC_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	`FDPSOFT_JDBC_IGNORE_DROP_FAILURE`	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 Target Folder	`FDPSOFT_SQL_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.
Database SQL Ignore Drop Failures	`FDPSOFT_JDBC_IGNORE_DROP_FAILURE`	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.
Internal Files Retry Count Default	`FDPSOFT_INTERNALS_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 Property Replacement Default	`FDPSOFT_INTERNALS_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).
Customizations File Owner:Group Default	`FDPSOFT_CUSTOMIZATIONS_FILE_OWNER_GROUP_FILE_DEFAULT`	No	When populating or evaluating Files, default the Owner:Group value to this.
Customizations File Permissions Default	`FDPSOFT_CUSTOMIZATIONS_FILE_PERMISSION_FILE_DEFAULT`	No	When populating or evaluating Files, default the Permissions to this.
Customizations Files Property Replacement Default	`FDPSOFT_CUSTOMIZATIONS_FILE_PROPERTY_REPLACEMENT_DEFAULT`	No	When populating or evaluating Files, default the Property Replacement option to this. Defaults to true(checked ).
Customizations Home Folder	`CUSTOMIZATIONS_HOME`	No	Location where your customized PeopleSoft application files are installed.

Inputs

Input Name	Input Code	Required	Description
PeopleSoft Project Name	`FDPSOFT_INP_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	`FDPSOFT_INP_EXECUTE_SQL`	No	If true the generated SQL files will automatically be executed against the target database.
Additional Parameters	`FDPSOFT_INP_ADDITIONAL_PARAMETERS`	No	Additional parameters to be added to the PeopleTools command.
Run Destructive	`FDPSOFT_JDBC_INP_RUN_DESTRUCTIVE`	No	Destructive SQL statements are allowed to be run if checked.
Show DBMS Output	`FDPSOFT_JDBC_INP_SHOW_DBMS_OUT`	No	Print DBMS Output in log. Only supported for Oracle Database.
Show SQL	`FDPSOFT_JDBC_INP_PRINT_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.

packageDeploy (PeopleSoft)