Preparing psft_customizations.yaml and Completing the Deployment

Carry out these steps from the PeopleTools 8.63.<new> environment, installed in the previous section (for example, 8.63.11). Create or edit a psft_customizations.yaml file, and complete the initialization using the psft_puppet_apply script.

See "Completing the DPK Initialization with Customizations."

The documentation lists several types of customizations you can use for your environment. For this scenario, it is important that you include the following in the psft_customizations.yaml file:

• Location for an existing PS_APP_HOME (if you have one) to be associated with the PS_HOME.

• Existing installation locations for one or more of the components that you want to retain; that is, Oracle WebLogic, Oracle Tuxedo or Oracle Database client.

Here is a sample psft_customizations.yaml file that specifies the location for Oracle WebLogic and Oracle Tuxedo, so that these components will be retained and not redeployed. Since the Oracle Database client and JDK are not specified, they will be deployed fresh.

This customization also specifies an existing PS_APP_HOME location which will be associated to PS_HOME during the deployment process.

Note:

Be sure to retain the spacing and indentation as shown in this sample.

---
weblogic_location: C:/MyCurrentWeblogicLocation/weblogic
weblogic:
  location: C:/MyCurrentWeblogicLocation/weblogic

tuxedo_location: C:/MyCurrentTuxedoLocation/weblogic/tuxedo
tuxedo:
  location: C:/MyCurrentTuxedoLocation/weblogic/tuxedo

ps_apphome_location: c:/MyCurrentAppHomeLocation/fscm_app_home
ps_app_home:
  db_type: "%{lookup('db_platform')}"
  location: "%{lookup('ps_apphome_location')}"

Complete the initialization using the psft_puppet_apply script as described in the documentation.

See "Completing the DPK Initialization with Customizations."