Installing in interactive mode

You can install Cloud Pak System Software in interactive mode.

1. Download the installation package files.
   1. Log in to the Platform System Manager and create a temporary directory from a command line.
   2. Download the following files from Passport Advantage® to the temporary directory.
      Licensed customers with a Passport Advantage ID and password can download the necessary product repositories from the Passport Advantage site. Depending on your license, download the files from the Cloud Pak System Software product or the Cloud Pak System Software Suite product.

      • pure-app-software-version.tgz
      • pureappsw-power-content-version.tar

      or

      • pure-app-software-version.tgz
      • pureappsws-power-content-version.tar

      where: version is the version number to install.

2. Extract the pure-app-software-version.tgz file to the temporary directory.
   Avoid trouble:

   • Do not use the /tmp/ipas directory as your working installation directory.
   • Do not extract the pureappsw-power-content-version.tar or pureappsws-power-content-version.tar file. Make sure this file is in the root installation directory.
3. Log in Hosted VMware environments to as root user.
   1. Before you run the installation, complete these steps:
      1. Edit the install.sh script to change the flag from "yes" to "no" in the following content and save it:

         INSTALL_DEFAULT_DATA="yes"

      2. Start the installation process by running the install.sh script.
   2. Back up the ssl.conf file by running this command.

      $ sudo bash # cp /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.backup

   3. Edit the # vi /etc/httpd/conf.d/ssl.conf file.
      1. Comment the following lines by adding # at the beginning of these lines and save the file.
         Note: These lines are placed at the bottom of the ssl.conf file.

         RewriteEngine on
         RewriteCond %{HTTP_HOST} !^127\.0\.0\.1
         RewriteCond %{HTTP_HOST} !^localhost
         RewriteCond %{HTTP_HOST} !^\[::1\]
         RewriteCond %{HTTP_HOST},%{SERVER_ADDR} !^(.*),\1
         RewriteCond %{HTTP_HOST},%{SERVER_ADDR}:443 !^(.*),\1
         RewriteRule ^.*$ https://%{SERVER_ADDR}%{REQUEST_URI} [L,R]

      The commented lines are updated as follows:

      #RewriteEngine on
      #RewriteCond %{HTTP_HOST} !^127\.0\.0\.1
      #RewriteCond %{HTTP_HOST} !^localhost
      #RewriteCond %{HTTP_HOST} !^\[::1\]
      #RewriteCond %{HTTP_HOST},%{SERVER_ADDR} !^(.*),\1
      #RewriteCond %{HTTP_HOST},%{SERVER_ADDR}:443 !^(.*),\1
      #RewriteRule ^.*$ https://%{SERVER_ADDR}%{REQUEST_URI} [L,R]

   4. Restart httpd by running this command:

      service httpd restart

   5. After PSM installation completes, reedit the install.sh to revert the value from "no" to "yes".
   6. Rerun the install.sh script.
   7. When the installation completes, revert the changes in the ssl.conf file by restoring from the backup file.
   8. Restart httpd to re-enable the security fix. Run the following commands.

      # cp /etc/httpd/conf.d/ssl.conf.backup /etc/httpd/conf.d/ssl.conf 
      # service httpd restart

4. Run the following command.

   #touch /data/config/dd_pending_flag

5. Start the installation process by running the install.sh script.
   Use the -t option to specify the installation type. The valid value is "software_power".
6. If the firewall settings are different from the standard firewall setup, the installer asks you to select from the following options:
   • Overwrite firewall rules configuration with suggested one. (Recommended)
   • Proceed with the installation. I confirm that the firewall rules were set up according to the System Requirements documentation.
   • Exit installation so that I can manually correct firewall rules.
7. Enter a unique installation name.
   Note that the name cannot be changed later, and an existing host name on the network cannot be used.

   • The value must be between 2 and 24 characters in length.
   • The first character can be A-Z or a-z. The other characters can be alphanumeric or an en dash [ - ].
   • The value cannot end with the en dash character [ - ].
   • "localhost" is not a supported value.
8. Enter an administrative user name and password.
   These credentials are used to log in to the console and configure the Platform System Manager.

   • The user name must be greater than one character in length.
   • The first character of the user name can be a-z or an underscore [ _ ].
   • The user name can contain alphanumeric characters and any of the following special characters:

     _  - 

   • The password must be greater than seven characters in length.
   Tip: A default value is provided for the administrative user name. You can press Enter to use the suggested value.