Tuesday, 13 August 2019

psft_customizations.yaml file for DPK installation but I want same folder structure what I had in past

---

ps_home_location:       "/oracle/peopletools/8.57.05"
ps_home:
  db_type:    "%{hiera('db_platform')}"
  unicode_db: "%{hiera('unicode_db')}"
  location:   "/oracle/peopletools/8.57.05"
  remove:  false

inventory_location:     "/oracle/oraInventory"
inventory:
  location: "/oracle/oraInventory"
  remove:  false

oracle_client_location: "/oracle1/app/oracle/product/12.1.0.2.0/fullclienthome1"
oracle_client:
  location: "/oracle1/app/oracle/product/12.1.0.2.0/fullclienthome1"
  remove:  false

jdk_location:           "/oracle/jdk/default"
jdk:
  location: "/oracle/jdk/default"
  remove:  false

weblogic_location:      "/oracle/middleware_12c"
weblogic:
  location: "/oracle/middleware_12c"
  remove:  false

tuxedo_location:        "/oracle/tuxedo"
tuxedo:
  location: "/oracle/tuxedo"
  remove:  false

ohs_location:           "/oracle/webserver"
ohs:
  location: "/oracle/webserver"
  remove:  false

Just note that You can do the customization however you want from your $/BASE/dpk/puppet/production/data

here you will have default files as 

defaults.yaml
psft_cm.yaml
psft_configuration.yaml
psft_deployment.yaml
psft_opa.yaml
psft_unix_system.yaml
psft_unix_system.yaml_20190806151800

after creating your customizations file you need to place here. Basically for location customizations you need to refer psft_deployment.yaml and for configurations related changes say you want 2 domains sites you need to refer psft_configuration.yaml and create psft_customizations file.


No comments:

Post a Comment

The purge process did not run because the Oprid configured to start the Process Scheduler did not have the required permissions to run the purge process.

  Purge process - Required permissions The PeopleSoft Oprid used to start the Process Scheduler, as defined in the Scheduler's psprcs.cf...