Reviewing the Customization File for Multiple Web Sites in a Single Web Domain

Use these guidelines to create the psft_customizations.yaml file for a single PIA (web server) domain with two or more web sites. Be sure to also fulfill the guidelines in the section Preparing the psft_customizations.yaml File.

Be sure to retain the indentation as given in the delivered YAML file when you copy the sections into the psft_customizations.yaml file.

This sample shows the psft_customizations.yaml file for a single PIA domain, called PIAHR2, with two web sites, hr92dev and hr92site.

• Copy the scalar parameter pia_site_name from psft_configuration.yaml and change the value to the name for the first web site, hr92dev in this example.

  This web site will be used for configuring the report node and Integration Broker.

• Copy the entire pia_domain_list collection type parameter (comprised of several lines) from psft_configuration.yaml and change the value "%{lookup('pia_domain_name')}" to the desired name for the PIA domain, PIAHR2 in this example.

  Note:

  Do not use the reserved names PIA, PIA1, PIA2, or weblogic for the PIA (web server) domain.

• In the pia_domain_list collection type parameter, to add a second web site, copy the portion defining the web site, and paste it below the first, default, web site definition.

  Copy and paste the web site portion for as many web sites as you need, and specify different names for the each site. The web site names in this example are hr92dev and hr92site. The name of the first web site that you use here is the same as the name you enter for pia_site_name.

• Replace the password sample here with encrypted text from the generated psft_configuration.yaml file.

  Note:

  Use clear text passwords for silent mode installation.

• The parameters webserver_admin_port, webserver_http_port, and webserver_https_port are interpolation functions. To specify non-default port numbers for these parameters, include the scalar parameters that the interpolation functions are based on at the top of the file. This sample replaces the default values 8000 and 8443 for pia_http_port and pia_https_port with 50000. This ensures that interpolation functions that are based on pia_http_port and pia_https_port use the custom values.

Here is a sample psft_customizations.yaml file, with annotations added (marked by ###) for the purposes of this explanation.

---
### Custom port numbers for first domain in scalar parameters ###
pia_http_port: 50000
pia_https_port: 50000

### First domain with custom name in scalar parameter ###
pia_domain_name: PIAHR2

### First site with custom name in scalar parameter ###
pia_site_name:              hr92dev

### First PIA domain refers to scalar parameter ###
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_install_type: "%{lookup('webserver_install_type')}"

    webserver_settings:
      webserver_type:           "%{lookup('webserver_type')}"
      webserver_home:           "%{lookup('weblogic_location')}"
      webserver_admin_user:     system
      webserver_admin_user_pwd: ENC[xxxxxxxxxxxxxxxxxxxxxxxxxxxx]
      webserver_admin_port:     "%{lookup('pia_http_port')}"
      webserver_http_port:      "%{lookup('pia_http_port')}"
      webserver_https_port:     "%{lookup('pia_https_port')}"

    site_list:
      ### First web site with custom name ###
      "hr92dev":                   
        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[xxxxxxxxxxxxxxxxxxxxxxxx]

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

      ### Second web site with custom name ###
      "hr92site":                   
        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[xxxxxxxxxxxxxxxxxxxxx]

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