Tuesday 12 July 2016

PeopleSoft Customization yaml file


After deployment of DPK, I was trying to execute the psft_customizations.yaml using the non-root user i.e, the specific user which we normally use for installing the PeopleSoft Stack components. I was using user_name and group_name twice in the psft_customizations.yaml which was causing it to fail. That is for oracle_group and psft_group, I was using the same group profile and similarly for psft_user and oracle_user, I was using the same userid. Puppet don't allow you to give same group name(profile) and same user_name twice in the customization file. As a workaround for this issue, I have removed the user section from psft_customizations.yaml and ran it with default users i.e, psadm1, psadm2, psadm3 and Oracle. You can then give the permission to these users to execute as per your setup requirement or alternatively you can change the ownership of the installation done by these default users. You can only get these default users created on your system, if you have the super user access to the box where you are attempting to install DPK and PeopleSoft components.
As a solution to this,if you are intending to use one user name and user group for both PeopleSoft and Oracle installation then you can give that username and group name once at the top of the file psft_customizations.yaml and that should not be repeated for PeopleSoft and Oracle separately in the file.
For example: The section below should be in the top of the file with other content

psft_user_name: hr92ut

psft_group_name: psadmin_prd

Hope this will help you to resolve the user profile issue in psft_customizations.yaml file where you are intending to use the signle user to use for the entire installation using DPK, however if you face any issue, pls leave a comment or email me and I will respond at the earliest possible.

9 comments:

  1. Hi Rimpal

    Can you post a complete example of your working psft_customizations.yaml file? I can't seem to get this working.

    ReplyDelete
  2. Hi,

    Here is the psft_customizations.yaml file. Don't forgot to keep three dashes in the top.

    ---
    peoplesoft_base: /home/fs92dev

    dpk_location: /home/fs92dev/dpk
    archive_location: "%{hiera('dpk_location')}/archives"
    pt_location: "%{hiera('peoplesoft_base')}/pt"
    db_location: "%{hiera('peoplesoft_base')}/db"
    db_platform: ORACLE
    setup_ohs: false

    unicode_db: false

    ps_home_location: "/home/fs92dev/ps_home8.55.05"
    inventory_location: "/opt/oracle/oraInventory"
    oracle_client_location: "/opt/oracle/oracle/12.1.0.2"
    jdk_location: "/opt/jdk1.7.0_95"
    weblogic_location: "/opt/bea"
    tuxedo_location: "/opt/bea/tuxedo"
    ohs_location: "/opt/bea/ohs"

    ps_home:
    db_type: "%{hiera('db_platform')}"
    unicode_db: "%{hiera('unicode_db')}"
    location: "%{hiera('ps_home_location')}"

    inventory:
    location: "%{hiera('inventory_location')}"

    oracle_client:
    location: "%{hiera('oracle_client_location')}"

    jdk:
    location: "%{hiera('jdk_location')}"

    weblogic:
    location: "%{hiera('weblogic_location')}"

    tuxedo:
    location: "%{hiera('tuxedo_location')}"

    ohs:
    location: "%{hiera('ohs_location')}"


    psft_db_location: "%{hiera('db_location')}/oradata/%{hiera('db_name')}"
    psft_db:
    type: fsdmo
    location: "%{hiera('psft_db_location')}"


    Let me know if you have any issue in it.

    Thanks
    Rimpal Johal

    ReplyDelete
  3. here is the YAML parser

    http://yaml-online-parser.appspot.com/

    Which help me

    ReplyDelete
  4. Can you please provide the customized script for user/groups in psft_cutomizations.yaml file

    ReplyDelete
  5. This comment has been removed by the author.

    ReplyDelete
  6. Hi Rimpal,
    Request you to share your customized working single user/ group yaml file to use a single user/group for the entire midtier installation using DPK. Thanks in advance.

    ReplyDelete
  7. ---
    ensure: present
    unicode_db: false
    install_type: FRESH

    ps_home_location: /PSOFT/PSHOME/
    ps_apphome_location: /PSOFT/APPHOME/
    ps_config_home: /PSOFT/CFGHOME/
    inventory_location: /PSOFT/oraInventory/
    oracle_client_location: /PSOFT/oracle/12.1.0.2/
    jdk_location: /PSOFT/jdk1.8.0_144/
    weblogic_location: /PSOFT/wlserver/
    tuxedo_location: /PSOFT/tuxedo/
    ohs_location: /PSOFT/ohs/


    psft_runtime_user_name: psft

    groups:
    psft_group:
    name: psft
    remove: false

    users:
    psft_user:
    name: psft
    gid: psft
    groups: psft
    home_dir: /home/psft

    change user/group as per your requirement

    ReplyDelete
  8. Hi Manish, Did you get the DPK Customization working ? Can you share your psft_customizations.yaml. I was kind of stuck at passing custom users, ps_cfg_home etc

    ReplyDelete
  9. Hi, I have a question. I tried to create psft_customizations.yaml file and it failed with the error
    2019-06-22 00:51:59 -0500 Puppet (err): Evaluation Error: Error while evaluating a Function Call, Lookup of key 'archive_location' failed: Unable to parse (C:\pt85707\dpk\puppet\production\data/psft_customizations.yaml): found unknown escape character while parsing a quoted scalar at line 4 column 15 (file: C:/pt85707/dpk/puppet/production/modules/pt_profile/manifests/pt_tools_deployment.pp, line: 33, column: 34) on node
    C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/pops/loader/../../../puppet/functions/eyaml_lookup_key.rb:59:in `rescue in block in load_data_hash'.
    Aim is to create ps_home on pt857 non-unicode db. Given below is the psft_customizations file.
    ---
    ps_home:
    db_type: "%{hiera('db_platform')}"
    unicode_db: false
    location: "C:\ps_home\pt85707"

    ReplyDelete