Preparing the Customization File for Session Cookie Names

Use the information in this section if you want to customize session cookie names. For example, you may need to set cookies when creating web server clusters.

See PeopleTools: Portal Technology, "Configuring Web Profiles."

See PeopleTools: System and Server Administration, "Working with Session Cookie Names."

Note:

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

Use these guidelines in creating the psft_customizations.yaml file:

  • This customization uses parameters that are not included in the YAML files generated by the deployment. Follow the samples given here in creating the psft_customizations.yaml file.

  • You are responsible for setting the correct values. There is no validation for the cookie names.

  • Follow the legal naming conventions for http cookies.

  • Set a unique name for each “setup of cluster of servers”.

    For example, if a set of web-servers are for an HCM production site and the cookie-name is used in persistence criteria, then all the web-servers of that HCM site must have the same Portal cookie-name.

  1. Locate the psft_configuration.yaml file 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 Notepad on Microsoft Windows or vi on Linux, and save it in the same location as the psft_deployment.yaml and psft_configuration.yaml files.

    Ensure that the file begins with three dashes (---).

  3. Copy the entire collection parameter section for pia_domain_list from the psft_configuration.yaml file into the psft_customizations.yaml file.

    Retain the indentation as given in the delivered YAML file.

  4. Add the parameters for portal_cookie_name and portlet_cookie_name below webserver_https_port, and ensure that the indentation is the same as that of webserver_https_port. 

    pia_domain_list:
  "%{lookup('pia_domain_name')}":
    os_user:               "%{lookup('domain_user')}"
    ps_cfg_home_dir:       "%{lookup('ps_config_home')}"
    gateway_user:          "%{lookup('pia_gateway_user')}"
    gateway_user_pwd:      "%{lookup('pia_gateway_user_pwd')}"
    auth_token_domain:     ".%{::domain}"

    webserver_settings:
      webserver_type:           "%{lookup('webserver_type')}"
      webserver_home:           "%{lookup('weblogic_location')}"
      webserver_admin_user:     system
      webserver_admin_user_pwd: ENC[PKCS7,xxxxxxxxxxxxxx.]
      webserver_admin_port:     "%{lookup('pia_http_port')}"
      webserver_http_port:      "%{lookup('pia_http_port')}"
      webserver_https_port:     "%{lookup('pia_https_port')}"
      portal_cookie_name:       FIN-PORTAL-PSJESSIONID
      portlet_cookie_name:      FIN-PORTLET-PSJESSIONID

    site_list:
      "%{lookup('pia_site_name')}":
        appserver_connections: "%{lookup('pia_psserver_list')}"
        domain_conn_pwd:       "%{lookup('domain_conn_pwd')}"

        webprofile_settings:
          profile_name:        "%{lookup('pia_webprofile_name')}"
          profile_user:        PTWEBSERVER
          profile_user_pwd:    ENC[PKCS7,xxxxxxxxxxxx]

        report_repository_dir: "%{lookup('report_repository_dir')}"

  5. Save the file.

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