Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Performing the upgrade

This topic describes how to upgrade your installed version of BMC Release Process Management to the latest version. When you upgrade to version, the new installation does not replace the product files related to the older version. You can upgrade from an earlier version of the product to the new version BMC Release Process Management in one of the following ways:

  • By migrating the earlier version's database to new version.
  • By using a fresh database for the latest version.

Also, you have the option of running different versions of BMC Release Process Management concurrently.

Before you begin

  • Ensure that you have Administrator privileges (on Windows) or superuser privileges (on Linux or Solaris) to upgrade (or migrate) to the latest version and register the product as a service. You also need Administrator privileges to install the new version of the product in the Program Files directory (on Windows).
  • Verify that your environment meets the requirements listed in the System-requirements topic and verify that you have prepared your environment for upgrade.
  • If you are installing the BMC Release Process Management product on any Linux platform, ensure that there is no rvm environment in the path of the installation.
  • Download and unzip the BMC Release Process Management zip files in your preferred location to perform the upgrade.
  • If you plan to use BMC Release Process Management version 2.6 concurrently with version 2.5, see Running-version-2-5-00-and-2-6-00-concurrently.

Notes

  • With version 2.6.00 you can install the product as a normal user without Administrator privileges (on Windows) or superuser privileges (on Linux or Solaris). But without Administrator privileges or superuser privileges you cannot register the product as a service. Also, you cannot install the product in the Program Files directory (on Windows).
  • Save a backup of your database to safeguard against any issues with the product upgrade.
  • Before migrating the product database to the new version, ensure that your current database works properly and stop the BMC Release Process Management server.

To upgrade the product

  1. Start the installation program:
    • Windows:
      1. If you are installing the product with administrator privileges:
        1. Enter the setup.cmd (BRPM\Disk1) command.
        2. From the pop-up menu, right-click setup.cmd, and click Run as administrator.
      2. If you are installing the product as a normal user, double-click setup.cmd to start the installation.
    • Linux or Solaris:
      1. Log in as root and navigate to BRPM/Disk1.
      2. Enter the chmod -R +x. command.
      3. Enter the ./setup.sh command.
  2. When the BMC Release Process Management Installer screen is displayed, click Next.
  3. On the license agreement page, select I agree to the terms of the license agreement, and then click Next.
  4. On the Installation type screen, select your privileges for the installation (a root user or as a normal user) by selecting one of the following options and then clicking Next:
    • Installer is started with root privileges so perform full installation
       (Select this option to install the product as an administrator or root user)

    • Install solution files and configurations. Do not perform tasks that require special rights.
      (Select this option to install the product as a normal user)

      Notes

      • If you are a normal user without administrator or root privileges and if you still select the first option, then your installation might not complete successfully.
      • If you select the second option, you can install the product as a normal user without administrator or root privileges. But you cannot register the product as a service. This means the services related to the BMC Release Process Management (tomcat) server, Hornetq messaging server, and the PostgreSQL database server are not started automatically on restarting your computer.

  5. On the Directory Selection screen, complete the following steps as shown on the image below and then click Next:

    1. Select the Refer to configuration and data from following location check box.
    2. Click Browse and enter the directory path for the current BMC Release Process Management configuration files.
      The default directory paths are:
      • For version 2.5.x,brpm_home\BRPM\server\webapps\brpm.
      • For version 2.4.x, specify the director path with the brpm.war file.
    3. For Database migration, select one of the following options:
      • Use same database: select this option to migrate your current database to 2.6.00.
      • Use same database (reset data contents): select this option to delete your current database and create a new database for version 2.6.00.
    4. For Other settings, select one of the following options:
      • Copy configuration: Select this option to copy your existing email notification settings to version 2.6.00.

      • Discard: Select this option to not copy your existing email notification settings to version 2.6.00.

        Note

        The directory that you select for the installation of version 2.6.00 must be empty for the installation to complete successfully.

    Directory selection
     (Click the image to expand it) 
    Directory selection-migrate.jpg

  6. On the feature selection screen, select Install BMC Release Process Management 2.6.00, and then click Next. 
    Feature selection
     (Click the image to expand it)
    migration feature1.jpg

  7. On the JRE information panelscreen:

    • To use the Java Runtime Environment (JRE) bundled with this product, select the Use the bundled JRE (version 1.6.0_26) check box.
    • To use your any other JRE, click Browse to specify the path where the JRE is located.

    After selecting your option, click Next.
    JRE information
     (Click the image to expand it)
    JREInformationPanel.jpg

  8. On the Server HTTP/HTTPS Port Information screen:
    1. If you use HTTP connection, specify the port of your Tomcat server (default 8080), and then click Next.

    2. If you use HTTP with SSL connection, select the Enable SSL check box and specify the HTTPS port (default 8443), private key, certificate file, and passphrase.

      Note

      The passphrase is used to set up the Java keystore. For more information about obtaining private key, certificate file, and passphrase, see Obtaining-test-SSL-certificates.

      HTTP/HTTPS port information
       (Click the image to expand it)
      http information.jpg

  9. On the Super User Details screen:
    1. If on the Directory Selection screen, for Database migration,  you selected Use same database option, the click Next.
    2. If on the Directory Selection screen, for Database migration,  you selected Use same database (reset data contents) option, specify the BMC Process Management super user details, and then click Next.
      Super user information
       (Click the image to expand it)
      migrate-superuser details1.jpg
  10. On the Messaging system details screen,specify the following details for the messaging system server and then click Next:
    1. Port:(Default 1099) Represents the port of the messaging system server.
    2. User: Represents the user name of the messaging system server.

    3. Password: Represents the password of the messaging system server.

      Note

      The Host field is disabled. By default, the installation program detects the IP address of the host computer on which you are installing this product.

      Messaging system information
       (Click the image to expand it)
      messaging system.jpg

  11. If on the Directory Selection screen, for Other Settings, you selected Discard, then the Email Notifications Details screen displays. On this screen:
    • If you donot want to use email notifications, select No Email Notifications , and then click Next.
    • If you want to use email notifications, select Use SMTPand then specify the following Simple Mail Transfer Protocol (SMTP) server details and then click Next:
      • SMTP Server: Represents the fully qualified name of the SMTP server used for sending emails.
      • SMTP Port: (Default 25) Represents the SMTP server port.
      • SMTP Domain: Represents the part of the user name after "xyz@" in your email address. For example, if your username is redmine@example.net, then your domain name is example.net.
      • SMTP Authentication: Represents the authentication mechanism used for your SMTP service. You can select from one of the options in the list displayed.
      • SMTP User: Represents the user name used to connect to the SMTP server.  For example, redmine@example.net.
      • SMTP Password: Represents the password used to connect to the SMTP server.

      • TLS: Select this check box if your SMTP server requires a secure connection and is using TLS.

        Notes

        Email notification information
         (Click the image to expand it)
        email notification.jpg

  12. On the Installation Preview screen, verify the installation details before the installation actually begins. Click Next to begin the installation process.
  13. (Optional) During the installation process, to see the installation log, click View Log.

After the upgrade

After the successful upgrade to version 2.6.00, perform the following instructions depending on your operating system:

  • Windows: Ensure that the startup settings for your BMC Release Process Management server (earlier version) is set to Manual.
  • Linux or Solaris: Remove links from the etc\init.d location by running the following commands with a root login.
    • Linux commands:
      rm --rf /etc/rc0.d/K02bmcrpm
      rm --rf /etc/rc1.d/K02bmcrpm
      rm --rf /etc/rc3.d/S98bmcrpm
      rm --rf /etc/rc4.d/S98bmcrpm
      rm --rf /etc/rc5.d/S98bmcrpm
      rm --rf /etc/rc6.d/K02bmcrpm
    • Solaris commands:
      rm --rf /etc/rcS.d/K02bmcrpm
      rm --rf /etc/rc0.d/K02bmcrpm
      rm --rf /etc/rc1.d/K02bmcrpm
      rm --rf /etc/rc2.d/K02bmcrpm
      rm --rf /etc/rc3.d/S98bmcrpm

Start the BMC Release Process Management server.

To run several product versions concurrently

  1. Navigate to Start > Run and enter services.msc.
  2. Locate the BMC Release Process Management service for the previous BMC Release Process Management and stop it.
  3. Save a backup of your database for version your previous BMC Release Process Management version.
  4. Restore the data in a separate database by carrying out the following changes:
    1. In <BRPM_HOME>/server/webapps/brpm/WEB-INF/config, edit the database.yml file.
    2. Provide details regarding the user name, password, and a new name for the database (the same database name with which you saved the backup earlier) to point to the newly created database.
  5. Start the service for your previous BMC Release Process Management.
  6. Start the product to ensure that version your previous BMC Release Process Management version is working correctly.
  7. Stop the service for your previous BMC Release Process Management.

  8. Run the installation utility for the new BMC Release Process Management version upgrade.

    Note

    During the upgrade, provide ports that are not in use.

  9. Start the BMC Release Process Management services for the new version.
  10. Start version the new version of the product to ensure that the new version is working correctly.
  11. In <BRPM_HOME>/server/webapps/brpm/WEB-INF/config, edit the database.yml file and provide details such as the user name, password, and database name for the previous version of BMC Release Process Management.
  12. Start the service for the previous version of BMC Release Process Management.
  13. Start the previous version of BMC Release Process Management to ensure that it is working correctly.

Related topic

Preparing-for-upgrade

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*