Preparing the Customization File to Create PeopleSoft Domains Without Configuration

The default DPK initialization includes pre-boot and post-boot processes that use Automated Configuration Manager (ACM) plug-ins to configure and start the PeopleSoft domains. The ACM configuration, for example, sets up Integration Broker and the report repository for the Process Scheduler.

Use this customization if you want to install the necessary software for the PeopleSoft Application Server, PIA, and Process Scheduler servers without running the pre-boot and post-boot ACM processes. After you complete the DPK deployment with this customization, you can complete the configuration as needed.

Note:

Review the requirements in Understanding PeopleSoft Environment Customizations before preparing the customization file.

To prepare the customization file:

  1. Locate the psft_configuration.yaml file, which was installed by the deployment, in BASE_DIR/dpk/puppet/production/data.

  2. If necessary, create a psft_customizations.yaml using a standard editing tool, such as Notepad on Microsoft Windows or vi on Linux, and save it in the same location as the generated psft_configuration.yaml file.

    If this is the first entry in the psft_customizations.yaml file, ensure that there are three dashes (---) on the first line of the file. Do not indent the dashes.

  3. Copy the parameters below from the psft_configuration.yaml file and paste them into the psft_customizations.yaml file.

    Retain the indentation as given in the delivered YAML file.

    run_preboot_config_setup: true
    run_postboot_config_setup: true
  4. To specify that the deployment does not run the pre-boot and post-boot ACM processes, change the values to “false”; for example:

    run_preboot_config_setup: false
    run_postboot_config_setup: false
  5. Add the parameter prcs_domain_id and provide a name for the Process Scheduler domain server.

    The Process Scheduler domain server name must begin with a letter and include a maximum of 8 characters. For example, you might choose a name to indicate the operating system, such as PSNT for Microsoft Windows or PSUNX for Linux or UNIX.

    ---
    run_preboot_config_setup: false
    run_postboot_config_setup: false
    
    prcs_domain_id: PSNT
  6. Save the file.

  7. Continue with the steps in Completing the Customized Deployment.