Preparing the Customization File for Existing Users and Groups

This user customization applies to Linux OS platforms only. If you choose the default initialization, the Puppet framework creates default local users and groups. However, your security policies may prohibit creating these OS users. In such a scenario, you can override these default users using the customizations file. The customizations file can refer to one or more existing users or existing groups and Puppet will use them instead of the default users.

See “Using and Maintaining the PeopleSoft Environment,” Using the PeopleSoft Installation, for a list of the default users and permissions.

Note:

Review the requirements in Understanding PeopleSoft Environment Customizations before preparing the customization file.

Ensure you fulfill these requirements:

  • The users, groups, and GIDs that you specify in the psft_customizations.yaml file are present before you begin the installation.

  • The user who installs the Oracle Database software must belong to the oinstall group (primary or secondary).

  • Do not include a password in psft_customizations.yaml.

    The customizations file does not specify new passwords, because it is assumed that the passwords associated with the existing users will be used.

  • When you run the DPK setup script, you must specify a user home directory in which the existing user resides.

  1. Locate the psft_unix_system.yaml file, which includes default users and groups.

    By default, the DPK setup script installs the YAML files in BASE_DIR/dpk/puppet/production/data.

    Note:

    The code examples in this topic are for illustrative purposes only. Remember to use the text from the YAML files you install with each new deployment as the basis for your psft_customizations.yaml file.

  2. If necessary, create a psft_customizations.yaml using a standard editing tool, such as vi on Linux, and save it in the same location as the psft_unix_system.yaml file.

    If this is the first entry in the psft_customizations.yaml file, ensure that there are three dashes (---) on the first line. Do not indent the dashes.

  3. Copy the entire section for the users and groups from the psft_unix_system.yaml file into the psft_customizations.yaml file and modify the values as needed.

    Note:

    Be sure that your final psft_customizations.yaml file includes the indentation from the generated YAML file. The indentation may be lost when you copy and paste.

    Note:

    In this example, the user oraclex3 belongs to the primary group orainstgrp and the secondary group oinstall.

    For example:

    ---
psft_install_user_name:     psadmx5
psft_runtime_user_name:     psadmx6
psft_app_install_user_name: psadmx7
oracle_user_name:           oraclex3

psft_runtime_group_name:     psftrungrp
psft_app_install_group_name: psftappgrp
oracle_install_group_name:   orainstgrp
oracle_runtime_group_name:   orarungrp

user_home_dir:   /data1/home
users:
  tools_install_user:
    name:     "%{lookup('psft_install_user_name')}"
    gid:      orainstgrp
    groups:   "%{lookup('psft_runtime_group_name')}"
    home_dir: "%{lookup('user_home_dir')}/%{lookup('psft_install_user_name')}"

  psft_runtime_user:
    name:     "%{lookup('psft_runtime_user_name')}"
    gid:      orainstgrp
    home_dir: "%{lookup('user_home_dir')}/%{lookup('psft_runtime_user_name')}"

  app_install_user:
    name:     "%{lookup('psft_app_install_user_name')}"
    gid:      psftappgrp
    home_dir: "%{lookup('user_home_dir')}/%{lookup('psft_app_install_user_name')}"

  oracle_user:
    name:     "%{lookup('oracle_user_name')}"
    gid:      orainstgrp
    groups:   oinstall
    home_dir: "%{lookup('user_home_dir')}/%{lookup('oracle_user_name')}"

  es_user:
    name:     esuserx3
    gid:      users
    home_dir: /data1/home/esuserx3

    The following table describes the parameters in the sample psft_customizations.yaml and the default values in psft_unix_system.yaml:

    Attribute and Sample Value in psft_customizations.yaml Default Value in psft_unix_system.yaml Description 
    psft_install_user_name:     psadmx5

    Replaces the default user psadm1.

    This is the PeopleSoft PeopleTools installation administrator, who owns PS_HOME, but cannot write into PS_CFG_HOME. 

    psft_runtime_user_name:     psadmx6

    Replaces the default user psadm2.

    This is the PeopleSoft PeopleTools domain user who creates and configures the Application Server domain, Process Scheduler (batch server) domain, and the web server domain. This user cannot write to PS_HOME, but has read/execute access. 

    psft_app_install_user_name: psadmx7

    Replaces the default user psadm3.

    This is the PeopleSoft application installation administrator who owns PS_APP_HOME. 

    oracle_user_name:           oraclex3

    Replaces the default user oracle2.

    This is the Oracle Database Server owner, who owns ORACLE_HOME. 

    psft_runtime_group_name:     psftrungrp

    Replaces the default group psft.

    Note: Do not use the same name for the four group name parameters. Ensure that the names that you specify for these parameters in psft_customizations.yaml are different. 

    psft_app_install_group_name:   psftappgrp

    Replaces the default group appinst.

    This group is the primary group for the app_install_user.

    Note: Do not use the same name for the four group name parameters. Ensure that the names that you specify for these parameters in psft_customizations.yaml are different. 

    oracle_install_group_name:  orainstgrp

    Replaces the default group name oinstall.

    This group is the primary group for the oracle_user, psft_runtime_user, and tools_install_user.

    Note: Do not use the same name for the four group name parameters. Ensure that the names that you specify for these parameters in psft_customizations.yaml are different. 

    oracle_runtime_group_name:   orarungrp

    Replaces the default group name dba.

    Note: Do not use the same name for the four group name parameters. Ensure that the names that you specify for these parameters in psft_customizations.yaml are different. 

    users:
   tools_install_user:
     name:     "%{lookup('psft_install_user_name')}"
     gid:      orainstgrp
     groups:   "%{lookup('psft_runtime_group_name')}"
     home_dir: "%{lookup('user_home_dir')}/%{lookup('psft_install_user_name')}"

    NA

    • The name for the tools_install_user is the same as the psft_install_user_name, as specified by an interpolation function.

    • The orainstgrp is the primary group for the tools_install_user.

    • The tools_install_user must belong to the psft runtime group as a secondary group.

      To satisfy this requirement, the value for users/tools_install_user/groups is set to the interpolation function "%{lookup('psft_runtime_group_name')}".

  4. Save the file.

  5. Continue with the steps in Completing the Customized Deployment.