Upgrade PPM - PostgreSQL (Beta)

You can use the sh kUpgrade.sh command to upgrade PPM with a PostgreSQL database. This topic provides detailed steps to upgrade PPM with a PostgreSQL database to the latest version.

Note: This feature is available in PPM 10.0.1 and later versions. It is a Beta feature, not field-tested enough. Do not use it in production environment.

To upgrade PPM with a PostgreSQL database:

  1. (Optional but highly recommended) Back up your database and license.conf file.

  2. Extract the ppm-<PPM version>-install-pg.zip package.

  3. Do either of the following to edit the required parameters.

    • Edit the parameter values directly in the ppm.env file in the ppm-<PPM version>-install-pg directory.

    • (For PPM 10.0.2 and later versions) Run the export command to set the value for each parameter. For example,

      export PPM_HOME=<PPM_home_before_upgrade>

      Note: The values set by the export command override the values set in the ppm.env file.

      • Required parameters:

      • PPM_Home
      • PGHOST
      • PGPORT
      • PPM_DB_NAME
      • PPM_DB_USER
      • PPM_DB_PASSWORD

      Make sure these parameter values are the same as what they were before you upgrade PPM with PostSQL datasource. For details about the parameters, see Required parameters.

  4. Stop the PPM server.

  5. Run the sh kUpgrade.sh command to upgrade the PPM file system and database.

    For 10.0.2 and later versions, if you want to upgrade the file system only, attach this parameter to the command: -f, or --filesystem.

    Tip: If you have multiple PPM nodes across multiple physical servers, you need to upgrade the file system on each server but need to upgrade the database only once.

    During the upgrade process, PPM generates the logs in the ppm-<PPM version>-install-pg/logs directory. If any problems occur during the upgrade, you can check the log file for troubleshooting.

  6. Start PPM in your upgraded <PPM_Home> folder.

  7. To make sure the attachments, report logs, and execution logs can still be accessed by the upgraded instance, set the paths of the following parameters to the corresponding folders under the upgraded <PPM_Home> directory:

    • com.kintana.core.server.ATTACHMENT_DIRNAME
    • com.kintana.core.server.BASE_LOG_DIR
    • com.kintana.core.server.DISTRIBUTION_LOG_DIR
    • com.kintana.core.server.PACKAGE_LOG_DIR
    • com.kintana.core.server.REPORT_DIR
    • com.kintana.core.server.REPORT_LOG_DIR
    • com.kintana.core.server.REQUEST_LOG_DIR
    • com.kintana.core.server.SCRIPT_DIR
    • com.kintana.core.server.TEMP_DIR
    • com.kintana.core.server.TRANSFER_PATH
    • com.kintana.core.server.VALIDATION_LOG_DIR
    • com.kintana.core.server.WEB_CACHE_DIR

See also: