Adding a Policy to Provision PUM Environments

Create an event-driven policy to automatically provision a PUM environment when a new PeopleSoft Update Image (PUM DPKs) is downloaded into the Repository, and migrate PUM metadata to keep the environment current. After you set up the policy, the event is triggered for each new downloaded update image. You can also set up additional optional actions.

To add a policy to provision PUM environments:

  1. Set up an Oracle Cloud Infrastructure vault and add secrets for the passwords required for a PUM environment.

    See the information on creating vault resources in the Cloud Manager Installation tutorials at https://docs.oracle.com/en/applications/peoplesoft/cloud-manager/index.html#InstallationTutorials

  2. Define a password group that includes the passwords required for a PUM environment.

    See Password Groups.

    Here are passwords typically required:

    • Database Administrator Password

    • Database Access Password

    • Database Connect Password

    • Database Operator Password

    • Gateway Administrator Password

    • Weblogic Administrator Password

    • Web Profile Password for user PTWEBSERVER

    • Windows Administrator Password

  3. Subscribe to the desired update image in the Repository.

    See Download Subscriptions Page

  4. Define a template for a PUM full-tier environment and associate the password group with it.

    Note: A PeopleSoft administrator must enable user access to the newly created PUM source environment template.

    See Creating a Template.

  5. Define an event policy with these selections:

    Field or Control

    Description

    Policy Object

    Repository Artifact

    Policy Type

    Event

    Event Name

    PUM DPK Download

    Policy Conditions

    Select the Product and Release for the PeopleSoft update image to download. For example, HCM and 9.2.

    Note: Only Linux images are supported for PUM environments, so it is not necessary to specify the platform.

    Policy Action

    Provision PUM

    Migrate PUM Metadata

    Define and upload target (optional)

    Delete the old PUM source (optional)

    See Configuring Self-Managed Update Images.

  6. Use Policy Monitor to review the environment name and process details.

    See Using Policy Monitor.