buildProject
- Keith Ecker (Unlicensed)
- Rama Rimmalapudi
An operation to generate SQL scrip to migrate a PeopleSoft project. Provides option to execute the generated SQL file. This operation can be used in Deploy workflow after copying the project definitions from file to target environment.Â
In your PeopleSoft Application Designer, you create several kinds of definitions that represent database components. For instance, field definitions represent table columns, and record definitions represent tables and views. From these field and record definitions, you can create tables, views, and indexes. The important concept to remember is that the definitions are just the blueprints for the actual, physical database components with which they are associated. In the context of the entire application development cycle, use this operation (BuildProject) to build the underlying SQL tables that house the application data.  It generates the SQL file with following as needed for the project :
Tables.
Indexes.
Views.
Triggers.
You can also use the Build feature to alter existing tables if you change the record definition after the table already exists. Altering a table is useful, because it enables you to make changes without losing the application data that is already housed in the table. In general, the results of the build operation are written to a script file and can easily run with "Execute SQL" input.Â
Environment/Instance 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 in to 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) |
| 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. |
Project Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| PeopleSoft Project Name | FDPSOFT_PROJECT_NAME | Yes | The name of the PeopleSoft project. |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| Output Directory | FDPSOFT_INP_OUTPUT_DIR | No | Directory to output generated SQL file to. If no value is provided the temp directory will be used. |
| 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. |
Outputs
| Output Name | Description |
|---|---|
| FDPSOFT_OUT_SQL_FILES | A comma separated string of all the generated SQL files. |
| FDPSOFT_OUT_EXECUTE_SQL | Whether or not the SQL files were automatically executed. |
Artifacts
This operation doesn’t consume or produce any artifacts.
Endpoint SelectionÂ
This operation will select all available endpoints associated to the environment/instance.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Special Considerations
This operation will generate SQL files and store them in the output directory. The directories provided in the configuration file will be used. If no configuration file is provided the temp directory will be used.
- style