Reviewing the Customization File for a PIA Domain on a Separate Host

If you want to set up an environment in which the PIA domain and web server are not on the same machine as the application server domain, you must use customizations to specify the machine where the application server is installed. This customization is required for the Integration Broker configuration. The sample includes annotations (marked by ###) for the purposes of this explanation.

1. Copy the entire component_postboot_setup_list collection type parameter section (comprised of several lines) from psft_configuration.yaml and paste it into psft_customizations.yaml.

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

2. Locate the env.ib_appserver_host parameter.

   This parameter sets the host for Integration Broker to the PIA host. The default value in the delivered psft_configuration.yaml file is the machine where the DPK setup script is run:

   env.ib_appserver_host:            "%{lookup('pia_host_name')}"

3. Change the value for env.ib_appserver_host to point to the host where the application server is set up, for example ps_app_server1.

   See "Deploying the PeopleSoft PeopleTools Deployment Packages," Running the DPK Setup Script to Deploy a PIA Domain.

4. In the section PTIBConfigureGatewayProperties, change the value for env.app_pia_same_host to “N” to specify that the application server and web server are on different hosts.

5. Add the scalar parameters for pia_http_port and pia_https_port at the top of the file.

   Interpolation functions that reference these scalar parameters will also use the non-default values. This applies to the interpolation function in psft_customizations.yaml as well as those used by the ACM plug-ins in psft_customizations.yaml and psft_configuration.yaml.

   The pia_http_port and pia_https_port scalar parameters replace the default port 8000 and 8443 with 8050 and 8943, respectively. This sets the value for env.gateway_port and env.gateway_ssl_port to the non–default port values.

Note:

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

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

---
### Custom port numbers in scalar parameters  ###
pia_http_port: 8050
pia_https_port: 8943

component_postboot_setup_list:
  integration_broker:
    run_control_id:                       intbroker
    os_user:                              "%{lookup('domain_user')}"

    db_settings:
      db_name:                            "%{lookup('db_name')}"
      db_type:                            "%{lookup('db_platform')}"
      db_opr_id:                          "%{lookup('db_user')}"
      db_opr_pwd:                         "%{lookup('db_user_pwd')}"
      db_connect_id:                      "%{lookup('db_connect_id')}"
      db_connect_pwd:                     "%{lookup('db_connect_pwd')}"

    acm_plugin_list:
      PTIBActivateDomain:
        domain.activate_retry_count:      10
        domain.activate_wait_time:        10

### Ports refer to scalar parameters ###
      PTIBConfigureGatewayNodes:
        env.gateway_host:                 "%{lookup('pia_host_name')}"
        env.gateway_port:                 "%{lookup('pia_http_port')}" 
        env.gateway_ssl_port:             "%{lookup('pia_https_port')}"
        env.use_ssl_gateway:              false
        env.default_local_node:           "%{lookup('gateway_node_name')}"
        env.gateway_user:                 "%{lookup('pia_gateway_user')}"
        env.gateway_password:             "%{lookup('pia_gateway_user_pwd')}"

       ### Custom application server name ###
        env.ib_appserver_host:            ps_app_server1      
        env.ib_jolt_port:                 "%{lookup('jolt_port')}"
        env.ib_node_proxy_userid:         "%{lookup('db_user')}"
        env.ib_node_proxy_password:       "%{lookup('db_user_pwd')}"
        env.tools_release:                "%ToolsRelease"
        env.ib_appserver_domain_password: "%{lookup('domain_conn_pwd')}"
        env.ib_set_as_default_node:       true

      PTIBConfigureGatewayProperties:
        env.gateway_keystore_password:    ENC[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]
        env.webserver_domain:             "%{lookup('pia_domain_name')}"

        ### Application server and web server on different hosts ###
        env.app_pia_same_host:             "N"
        
      PTWebServerConfigUpdate:
        env.domainname:                   "%{lookup('pia_domain_name')}"
        env.sitename:                     "%{lookup('pia_site_name')}"
        env.piahome:                      "%{lookup('ps_config_home')}"
        env.psserver:                     ""
        env.KeyStorePwd:                  ""

    acm_plugin_order:
      - PTIBActivateDomain
      - PTIBConfigureGatewayNodes
      - PTIBConfigureGatewayProperties
      - PTWebServerConfigUpdate