PeopleSoft Tutorial

The PeopleSoft plugin for FlexDeploy simplifies the process of migrating PeopleSoft projects between different environments, creating SQL build files, and comparing project definitions on target locations.

Objective

Support for PeopleTools 8.40+
Allows sourcing customizations from SCM repositories or development PeopleSoft instances.
Explore PeopleSoft Package Object Types - FlexDeploy 8.0 - Confluence (atlassian.net) Reference for detailed information on supported types.
Benefit from automated change detection during deployment.
Enable Continuous Integration capabilities.
Utilize flexible build options tailored for PeopleSoft.
Seamlessly integrate with FlexDeploy Pipeline & Release features for enhanced project management.

Create a PeopleSoft Project using Blueprint

The assumption is that you have FlexDeploy installed and ready for use. When logged into the FlexDeploy, you will see the Home page. Click on the + icon top and click “Create Project” to create a new project.

The screen displays the list of blueprints supported by the FlexDeploy. Select the blueprint from the list or you can search for the blueprint in the search filter present at the top. In our case, we will select the PeopleSoft or PeopleSoft Package based on our needs.

Scroll through this guide to fill in the blueprint properties where the Source Control, Build, and Deploy options are auto-selected, enter Project Info first.

In the Source Control Option on the screen, enter the Source Repository and in the Sparse Checkout Folders Script enter the name of the folder from the repository in which you are looking for package files. If files are in the root folder of the repository, then leave this value empty.

Gather Build and Deployment Information

Enter values for any workflow properties that are required for the build and deployment. In the image below, the properties required for the build need to be filled. Select the target endpoint that the build and deployment should execute on. The below image shows the Build-Development Fields.

The image below shows the Deploy - Development fields.

Clicking on the confirm button will ask for confirmation to create the PeopleSoft Package-based Project.

General Configuration

After successful configuration, open the created project, click on "Configuration," and select "General Configuration."

Build and Deploy Workflows

Project Properties

Source Control

Click on the source repository dropdown. If you have already created a connection to your source code repository, select it from the list. Enter the sparse checkout folder, if any.

Otherwise, add one by clicking on “Create new Source Repository”. Enter the sparse checkout folders script, if any.

Enter the sparse checkout folder value, if any. The sparse checkout folder is a Folder in your repository where your PeopleSoft files are located. If files are in the root folder of the repository, then leave this value empty. For SCM configuration refer to the link SCM Instance - FlexDeploy 7.0 - Confluence (atlassian.net)

Branch Name

Change the branch name to the git repositories branch name. Click on Save.

Topology

Navigate to the Topology from the Menu. The Page with the Target Groups, Environments, and Endpoints sections will be displayed. Choose a Target Group on the left. You will see a list of Environments on the right with colored circles representing each Target.

Click on PeopleSoft Target Group and click on the Development Environment

Color coding represents:

RED - The Endpoint is not configured
YELLOW - some of the required properties are not set,
GREEN - all required properties are set and the Endpoint is configured.

Targets Properties

Clicking the environment row for Development allows modifying the Endpoint and properties. We can select the endpoint from the Map Endpoint option and Resource Types from the Resource Types option from the below screen.

Endpoint Properties

Populate the files

For the package-based project click on File Catalog under the Package screen. In the File Catalog, there is a discover files option which helps to fetch files from the SCM repository,

Click on “Show new Files” to see the list of files on the file catalog screen.

Create a Package

On the package screen, click on the create button to create a new package.

Enter the package name and select the package type. We select the “User Managed” in our use case.

To create new files, click on the Create button. The create file screen will expect the file path and object type. Here we have selected Object type as Customization. Enter the value and fields related to the object type selected will be displayed.

Click on Evaluate if any modifications are done. Click on the Save button to save the file.

To inactivate the file, click on the Active switch box.

The file is created in the below screen.

We can also Click on the Add Files icon to add the files that are populated from the SCM repository.

Click on the file name directly to add the file to the package.

We can see the file added to the package under the package file screen.

Building Package

Click on the Execution tab to submit the build request for that package. Click on Build.

The Build Request Form is displayed, select your package name and environment. Click on the “Submit” button for the build to execute.

The Deploy Request Form is displayed. Click on the “Submit” button for the deployment to execute.

Here you can make note of build execution and deploy execution details for version 1.0.1 of our Package package. To view more detail, click on the generated Execution Id

Notice the Initialize: Extract Project Files (Revisions) step. This is an implicit step that is injected into the build workflow when using partial deployment. This step extracts the source code for the package files from the configured SCM. These files are then available for the PeopleSoft Build step to assemble them into an artifact, which is versioned (1.0.1) in the artifact repository.

After the build completes, we can see the artifact on the Artifacts tab, and see details of the files within it on the Files tab.