Understanding the PeopleTools Middleware DPK Deployment with Existing Environments

You can use the PT-MW-DPKs to apply CPUs to the software components on an existing installation.

Follow these guidelines to use the PT-MW-DPKs with existing installations:

  • The PT-MW-DPKs, as well as the PeopleTools patch DPKs, PeopleSoft Client DPK, PeopleSoft Update Images, or the OSK DPK, must be based on PeopleSoft PeopleTools 8.63.

  • You have retained the DPKs used to install the existing environment.

    To use the PT-MW-DPKs to apply the CPUs, you use the DPK setup script from the original set of DPKs.

  • Use the PT-MW-DPKs for these environment types:

    • PeopleSoft Update Images, for performing PUM maintenance

    • PeopleSoft Update Images used for a PeopleSoft application environment

    • PeopleSoft PeopleTools patchsets for applying a PeopleTools patch or PeopleTools-only upgrade

    • PeopleTools Client DPK in standalone mode to install PeopleTools utilities such as Change Assistant and Application Designer.

    • PeopleTools Client DPK in update manager mode to set up Change Assistant and other software for applying PUM maintenance.

    • When performing an upgrade of the OpenSearch, OpenSearch Dashboards, and Logstash (OSK) DPK

  • You deployed the environment using the DPK setup script.

    The PT-MW-DPK depends upon information generated by the DPK deployment, based upon your input. If that information is not available, the PT-MW-DPK process may not give the desired results. This requirement applies to both default and customized deployments. For example, to deploy a mid-tier component to a non-default location, use the psft_customizations.yaml file. The PT-MW-DPK process will use that location to apply CPUs. If you install mid-tier components manually, (without using the DPK setup process), the PT-MW-DPK process will not be aware of that manual installation, and will not be able to apply the CPUs to those components.

  • You used the psft_customizations.yaml file.

    If you installed your environment using customizations to specify a non-default installation location for the supporting software components, the DPK setup script uses the information in the existing psft_customizations.yaml file to locate the software and apply the CPUs.

  • You want to apply CPUs for least one of the following supporting software components:

    • Oracle Tuxedo

    • Oracle WebLogic

    • Oracle Database Client

    • Oracle Java JDK

  • You can compare the included software component versions in the manifest delivered in the PT-MW-DPKs. Note that the PT-MW-DPKs are not delivered on the same schedule as the PeopleSoft product DPKs discussed here. The PT-MW-DPKs are delivered when security updates for one or more of the components are available or required.

  • Follow the instructions in the chapter “Using the PT-MW-DPKs with Existing Installations” to review the manifest and perform the deployment.

    To apply the CPUs, you will include the PT-MW-DPKs in the same installation directory as the PeopleSoft product DPKs discussed here, and run a specific command with the DPK setup script.

Briefly, when you use the PT-MW-DPKs on an existing environment, the DPK setup script:

  1. Validates the supporting software components in the existing deployed environment and determines if they qualify for applying CPUs from PT-MW-DPKs.

  2. Stops all or specific domains (Application Server, Process Scheduler, and PIA) based on the component that is being applied with the CPU.

  3. Takes the CPU archives from the PT-MW-DPKs and applies them to the already-installed supporting software components.

  4. After applying the CPUs, starts the domains that were stopped.

  5. If there is any failure in applying the CPU to Oracle WebLogic, Oracle Tuxedo, or Oracle Database Client, OPatch will roll back the CPU.

    This ensures that the original version of the component is retained as it was prior to applying the CPU through the PT-MW-DPK process.