E-DPK: Deployment with Customizations Does Not Install Component Software and/or PeopleSoft Homes in the Custom Locations Specified in psft_customizations.yaml (Doc ID 2916680.1)

Last updated on JANUARY 30, 2023

Applies to:

Symptoms

DPK deployments with customizations include these use cases.

Use Case 1:  New installation of component software and/or PeopleSoft Homes in custom locations specified in the  psft_customization.yaml file.

The custom locations can be either of these:
  ---New custom locations (the directories do not exist and will be created by the DPK setup script)
  ---Existing custom locations (the directories have been previously created and exist in an accessible location)

Use Case 2:  Skip new installation and use existing installation.

Perform the DPK deployment to use the already installed component software and/or PeopleSoft Homes in the custom locations specified in the  psft_customization.yaml file.

The issue is seen with these steps:

1. Deploy the PeopleTools DPKs and use psft_customizations.yaml to specify non-default locations for new installation.
   The customized installation locations could be for PS_HOME, PS_APP_HOME, Oracle WebLogic, Oracle Tuxedo and so on.

2. Specify an existing directory that is not empty for the customized installation location.

    Result: The deployment will not install if the directory is not empty.


Example for DPK deployment

1. Run the DPK setup script.
2. Enter the BASE_DIR at the prompt.
    Example for Linux/UNIX:  /usr/psft_base
    Example for Windows: C:\psft_base
 

3. Answer No to the question that asks whether you want to continue with the default initialization process.
4. Create a psft_customizations.yaml file with a customized location that is the same as the entered BASE_DIR.
   See these and other customization examples in PeopleSoft PeopleTools 8.60 Deployment Packages Installation, on Oracle Help Center.
   Preparing Customization Files for Component Software Locations
   Preparing the Customization Files for the PeopleSoft Homes.

   For example, this is a psft_customizations.yaml for a custom PS_HOME that is the same as the BASE_DIR:
---
ps_home:
     db_type: "%{hiera('db_platform')}"
     unicode_db: "%{hiera('unicode_db')}"
     location: "/usr/psft_base"

5. Run the puppet apply command given when the script exits.
6. Notice that the custom PS_HOME is not installed.

   The script sees that the custom PS_HOME location, /usr/psft_base in this example, is not empty, and skips that portion of the deployment.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.