Understanding Silent Mode Installation

Use this section to perform a silent mode installation with the DPK setup script. In silent mode, you record the answers for the script prompts in a text file, called a response file. After you start the script and specify the response file location, no further interaction is required. Use these guidelines:

  • Include a customization file if necessary.

    You can also run the DPK setup script in silent mode and specify a customizations file in addition to the response file. Use the examples in the chapter “Completing the DPK Initialization with Customizations” to create a customization file. Follow the procedure in the section Running the DPK Setup Script in Silent Mode with Customizations.

  • Make a note of the required user IDs and passwords.

    The DPK setup process does not include any default passwords. You must supply the user IDs and passwords included in the samples.

  • Enter passwords in clear text.

    Note that some of the response file samples in this section include placeholders for passwords. When creating the response file for silent mode installation, enter the passwords in clear text. If you are running a customized deployment, enter the passwords in clear text in the psft_customizations.yaml file. Do not enter encrypted passwords.

  • Fulfill prerequisites if running as a non-root user.

    If you want to run as a non-root user on Linux, fulfill the requirements in the section Deploying as a Non-Root User on Linux. Before you run the silent mode installation as a non-root user, the root user must run the DPK setup prereq step.

    See "Installing the PeopleSoft Homes," Deploying as a Non-Root User on Linux.

Create your response file based on the samples in this section. The response file should include the values you would supply when running the DPK setup script interactively, and will vary depending upon the database platform and operating system.

The response files in this section include the following parameters:

  • env_type — Specify midtier as the type of DPK deployment.

  • install_type — Specify FRESH as the installation type for this task.

    See Reviewing the DPK Setup Script Options for information on the allowed installation types.

    This is required for mid-tier deployments if the DPK set includes App DPKs.

  • deploy_only — Specify true for one of the special deployment options, such as to deploy only PS_HOME.

  • deploy_type — Specify the type of deployment, as shown in the response file samples.

  • db_type — Specify whether you want to install a DEMO or SYS database.

  • db_is_unicode — Specify false if you want to install a non-Unicode database, or true to install a Unicode environment.

    The default setting is true. If you do not include the db_is_unicode parameter, the DPK setup script installs a Unicode environment.

  • psft_base_dir — Enter an accessible location for the base folder, which is used to extract the PeopleSoft DPKs and for deploying PeopleSoft components.

    The script creates the folder if it is not present.

    For installation on Microsoft Windows, use forward slashes (/) for the base folder. For example, C:/psft. Enter the full path, and enclose the path in double quotes. Do not use a name for the base folder that begins with a number.

    For installation on Linux, use forward slashes (/) for the base directory. For example, /cs1/psft. Enter the full path, and enclose the path in double quotes. Do not use a name for the base directory that begins with a number. Do not end the base directory name with a forward slash (for example, do not enter /ds1/psft/).

  • user_home_dir — On Linux, if you are performing the deployment as the root user, enter the full path to a writable directory for the home directory for the script-created users (psadm1, psadm2, psadm3, and oracle2).

  • db_platform — Specify the database platform.

    Enter ORACLE or MSSQL (Microsoft SQL Server).

  • db_name — Enter the PeopleSoft database name.

    If the database name includes non-alphanumeric characters such as periods, enclose the name in double quotes. For example, "HCM.92".

  • db_service_name — Enter the database service name.

    For the service name, enter the full name, including the domain, if the database was installed with the domain. Use forward slashes if necessary. If the service name includes non-alphanumeric characters such as periods, enclose the name in double quotes. For example, "HCM.92.example.com".

    This is required only for installations on Oracle RDBMS.

  • db_host — Enter the name of the host where the database is installed.

    Do not enter an IP address.

  • db_port — Enter the database port.

    This is required only for installations on Oracle RDBMS.

  • mss_odbc_name — Enter the ODBC driver name, for example, ODBC Driver 17 for SQL Server or ODBC Driver 18 for SQL Server.

    This is needed only for Microsoft SQL Server installations.

  • connect_id — Enter the PeopleSoft database Connect ID.

    The default is people.

  • connect_pwd — Enter the password for the Connect ID.

    Ensure the password meets the length and complexity requirements for your database platform.

    See E-DPK - PeopleTools 8.59 and later - DPK setup does not support some special characters for passwords (My Oracle Support, Article ID KB300834).

  • access_id — Enter the Access ID user.

  • opr_id — Enter the PeopleSoft operator ID, such as PS or VP1.

  • opr_pwd — Enter the password for the operator ID.

    Ensure that the password is between 1 and 32 characters in length. You may include these special characters !@#$%^&.

  • domain_conn_pwd — Enter the Application Server Domain Connection password.

    This is an optional password. If no password is entered, the connection between Web Server and Application Server will not be password protected.

  • weblogic_admin_pwd — Enter the Oracle WebLogic Server Admin password.

    The default Oracle WebLogic server administrator is system. Ensure that the password is between 8 and 30 characters in length with at least one lowercase letter, one uppercase letter and one number or one special character (!@#$%^&).

  • webprofile_user_id — Enter the web profile user name.

  • webprofile_user_pwd — Enter the password for the PTWEBSERVER web profile user.

    Ensure that the password is between 8 and 32 characters in length. You may include these special characters !@#$%^&.

  • pia_psserver_list — Enter <application_server_host>:<Jolt port>.

    List the application server domains that are used by the PIA domains, using the format <application_server_host>:<Jolt port>. If you enter more than one domain, separate the entries with a comma.

  • prcs_domain_id — Enter the name of the server with the Process Scheduler domain.

    The server name must begin with a letter and include a maximum of 8 characters.

    When you run the DPK setup script with default initialization, the name generated for the Process Scheduler Server is PRCSxxxx, where xxx is a random number. On a host where Process Scheduler has been deployed, you can find the Process Scheduler Server name (PrcsServerName) in the Process Scheduler configuration file. Locate it in <PS_CFG_HOME>/appserv/prcs/<Domain name>/psprcs.cfg, under General settings for the Process Scheduler. For example: 

    ;====================================================================
; General settings for the Process Scheduler
;====================================================================
PrcsServerName=PRCS8783

  • prcs_server_name — Enter the name of the server with the Process Scheduler domain, as described for prcs_domain_id.

    The server name must begin with a letter and include a maximum of 8 characters. When you run the DPK setup script with default initialization, Process Scheduler/PrcsServerName is an interpolation function based on prcs_domain_id.

  • gw_user_id — Enter the Integration Gateway user ID.

    The default is administrator.

  • gw_user_pwd — Enter the password for the Integration Gateway user.

    Ensure that the password is between 8 and 30 characters in length. You may include these special characters !@#$%^&.

  • gw_keystore_pwd — Enter the Integration Gateway keystore password.

    Ensure the password is between 8 and 30 characters in length. You may include these special characters !@#$%^&.

  • os_root_pwd — For the silent mode VirtualBox deployment, enter the root user password for the guest Linux operating system, in clear text.