Upgrading from pre-4.3.00 versions

This topic explains how to upgrade (or migrate) the BMC Release Lifecycle Management solution products from a pre-4.3.00 version to version 4.3.00 (previously known as version 2.6.00).  

Note

This upgrade is supported for only one of the component products, BMC Release Process Management. When you run the installation program, you can choose to upgrade (or migrate) to version 2.6.00 of BMC Release Process Management and perform a fresh installation of BMC VaraLogix Q Deployment Automation (by using the same installation program). You can also choose to install only a single component product by selecting the appropriate features, as described in step 6 in the following procedure.

When you upgrade (or migrate), the new installation does not replace the product files related to the older version. You can upgrade from an earlier version of BMC Release Process Management to version 4.3.00 of BMC Release Lifecycle Management in one of the following ways:

  • By migrating the earlier version's database to version 4.3.00
  • By migrating the earlier version's database but resetting its contents

To perform a silent upgrade of the BMC Release Lifecycle Management solution, follow the steps described in Installing-silently. To learn more about options that you can specify in a silent upgrade options file, see Silent-installation-properties.

Before you begin

  • If you plan to run multiple versions of BMC Release Process Management side-by-side, perform the preparatory steps described in Running-multiple-versions-of-BMC-Release-Process-Management-concurrently.
  • To register the component products as services and to install the solution in the Program Files directory (on Windows), ensure that you have Administrator privileges (on Windows) or superuser privileges (on Linux).
  • Verify that your environment meets the system requirements and verify that you have prepared the installation environment.
  • If you are installing the BMC Release Lifecycle Management solution on any Linux platform, ensure that there is no rvm environment in the path of the installation.
  • Download and unzip the BMC Release Lifecycle Management zip files in your preferred location.
  • Back up your database to safeguard against any issues with the upgrade.
  • Ensure that your BMC Release Process Management server is stopped and the database is up and running.

To upgrade (or migrate) to the latest version of BMC Release Process Management

  1. Start the installation program:
    • Windows:
      • If you are installing the product with administrator privileges:
        1. Enter the setup.cmd (BRLM\Disk1) command.
        2. From the menu, right-click setup.cmd, and click Run as administrator.
      • If you are installing the product as a normal user, double-click setup.cmd to start the installation.
    • Linux:
      1. Log on as root and navigate to BRLM/Disk1.
      2. Enter the chmod -R +x . command.
      3. Enter the ./setup.sh command.
  2. On the first page of the BMC Release Lifecycle Management Installer wizard, click Next.
  3. On the license agreement page, select I agree to the terms of the license agreement, and then click Next.
    The Directory Selection page is displayed as shown in the following image:

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

  4. Provide the directory path for installing this solution (and upgrading to the latest version of BMC Release Process Management) by clicking Browse, and then click Next. 

    Note

    The directory that you select for the product installation must be empty for the installation to complete successfully.

    Default paths:

    • Windows: C:\Program Files\BMC Software\RLM
    • Linux: /opt/bmc/RLM
  5. On the Installation Type page, select the appropriate option for installing as either a root user or a normal user, and then click Next.
    • Installer is started with root privileges so perform full installation: Installs the solution as an administrator or root user

    • Install solution files and configurations. Do not perform tasks that require special rights: Install the solution as a normal user

      Note

      • If you are a normal user without administrator or root privileges and you still select the first option, then your installation might not complete successfully.
      • If you select the second option, you can install the solution as a normal user without administrator or root privileges, but you cannot register the component products as services. This means that the services related to the deployment engine, dispatcher, Apache server, tomcat server, Hornetq messaging server, and PostgreSQL database server are not started automatically when restarting your computer.
  6. Select the products and components that you want to upgrade, and then click Next: 
    • Install Process Modeling Server: Installs version 2.6.00 of the BMC Release Process Management product
    • Install VaraLogix Q Deployment Automation UI: Installs version 4.3.00 of the BMC VaraLogix Q Deployment Automation product

    • Install Deployment Engine: Installs the deployment engine for the BMC VaraLogix Q Deployment Automation product

      Note

      Do not select Install PostgreSQL, as you are migrating from an existing database

      Feature selection
       (Click the image to expand it)

      6.jpg

  7. If you are installing the Deployment Engine, the Deployment Action Packs page displays a list of action packs for the various types of middleware objects. Select the action packs according to the middleware type that you want to manage, and then click Next.

    Deployment action packs information
    (Click the image to expand it)

    7.jpg
  8. Specify details for upgrading or migrating your database to version 4.3.00 of BMC Release Lifecycle Management (which upgrades or migrates only BMC Release Process Management), and then click Next:   
    1. Select the Refer to configuration and data from following location check box.
    2. Select one of the following options as appropriate in the list displayed for Earlier version:
      • No migration required: Does not perform an upgrade or migration
      • BMC Release Process Management 2.5.x: Migrates from version 2.5.x of the BMC Release Process Management product to version 4.3.00 of the BMC Release Lifecycle Management solution (and upgrade to version 2.6.00 of BMC Release Process Management).
      • BMC Release Process Management 2.6.00: Migrates existing version 2.6.00 BMC Release Process Management database and installs version 4.3.00 of BMC VaraLogix Q Deployment Automation
    3. Click Browse and provide the directory location of the product from which you want to migrate:
      • If you are migrating from version 2.5.x, your product might be installed at brpm_home\BRPM\server\webapps\brpm.
        Example: C:\Program Files\BMC Software\BRPM\server\webapps\brpm 
      • If you are migrating from version 2.6.00, your product might be installed at brpm_home\BRPM\Releases\2.6.0
        Example: C:\Program Files\BMC Software\BRPM\Releases\2.6.0.
    4. Database migration: Select one of the following options:
      • Use same database: Migrates your database to version 2.6.00
      • Use same database (reset data contents): Deletes your database and creates a new database for version 2.6.00
    5. Other settings: Select one of the following options:
      • Copy configuration: Copies your email notification settings to version 4.3.00
      • Discard: Does not copy your existing email notification settings to version 4.3.00

        Migration information
         (Click the image to expand it)

        8.jpg

  9. On the JRE Information page, specify the the path where the JRE is located.
    This step relates specifically to the BMC Release Process Management component product installation. 

    • To use the Java Runtime Environment (JRE) bundled with this product, select the Use the bundled JRE (version 1.7.0_09) check box. 
    • To use any other JRE, click Browse to specify the path where the JRE is located on your computer, and then click Next.

    JRE information
    (Click the image to expand it)
    9.jpg

  10. On the Server HTTP/HTTPS Port Information page, specify details about the HTTP port, and then click Next.
    The HTTP port is the Tomcat server port for BMC Release Process Management (default port: 8080) and the Apache server port for BMC VaraLogix Q Deployment Automation (default port: 80). If you are already using the default port, specify an alternate port. 
    You can also choose to enable SSL settings for your Tomcat server or the Apache server by selecting the Enable SSL check box for the appropriate component product. If you enable your SSL settings, then you must specify the HTTPS port (default: 8443 for BMC Release Process Management and 443 for BMC VaraLogix Q Deployment Automation) and the private key, certificate file, and passphrase.
     

    Note

    The passphrase is used to set up the Java keystore. For more information, see Obtaining-test-SSL-certificates.


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

    11.jpg

  11. On the Super User Details page, provide super user details. The super user is the first user who has administrator access permissions to use the BMC Release Process Management and BMC VaraLogix Q Deployment Automation component products. You can choose to use the default details, provide the password, and then click Next. You can also choose to add your own details. The last three fields (Login, Password, and Confirm Password) are specific to the installation of BMC VaraLogix Q Deployment Automation.

    Super user information
    (Click the image to expand it)

    sudouser.png

  12. If you are installing BMC Release Process Management, on the Messaging System Details page specify the following details to connect to the messaging system server, and then click Next. 

    • Port: Port of the messaging system server (default: 1099)
    • User: User name of the messaging system server
    • Password: Password that corresponds to the user name 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)
    13.jpg

  13. On the Database Details page, specify the following details for the database that you want to use for the BMC VaraLogix Q Deployment Automation component product and then click Next.

    • If you are using the PostgreSQL or the SQL Server database, specify different SID names.
    • If you are using the Oracle database, you can use the same SID name, but you must specify a different user name.
    • In the case of an upgrade, the following database fields, which are related to BMC Release Process Management, are disabled.
      • Database
      • Host
      • Port
      • RPM Database/SID Name
      • RPM Database User
      • RPM Database Password
    • Q Database/SID Name: If you selected POSTGRESQL or SQL_SERVER on the list displayed for the Database field, then specify the name of the database instance that you used while creating it at the time of the database installation. If you selected ORACLE on the list displayed for the Database field, then specify the SID details.
    • Q Database User: Specify the user name of the database instance that you used while creating it at the time of the database installation.
    • Q Database Password: Specify the password of the database instance that you used while creating it at the time of the database installation.

      Database information
      (Click the image to expand it)
      dbDetails.png
  14. On the Email Notifications Details page, specify whether to configure email notification settings for the solution or not, and then click Next. Select the No Email Notifications option if you do not want to configure email notification settings. Alternatively, select the Use SMTP option and then specify the following Simple Mail Transfer Protocol (SMTP) server details for the configuration of email notification settings.On the Email Notifications Details page page, specify whether you want to configure email notification settings for the solution or not and then click Next.
    • SMTP Server: The fully qualified name of the SMTP server used for sending emails.
    • SMTP Port: (Default 25) The SMTP server port.
    • SMTP Domain: 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: The authentication mechanism used for your SMTP service. You can select from one of the options in the list displayed.
    • SMTP User: The user name used to connect to the SMTP server.  For example, redmine@example.net.
    • SMTP Password: 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.

      Note

      You can specify your email notification on this page for both BMC Release Process Management and BMC VaraLogix Q Deployment Automation. If on the migration page in step 8, you selected Copy configuration, then the settings you specify on this page are applied to BMC VaraLogix Q Deployment Automation only. But if you selected Discard in step 8, then the settings you specify are applied to both component products.

      The option of using Sendmail available in version 2.5.00 of BMC Release Process Management is not available in this release.

      To learn more about email notifications and how to change notification configurations manually, see Changing-email-notification-configuration-manually.

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

  15. The Installation Preview page is displayed. This page displays the various details of your installation before the installation starts, including installation location, features selected, and total disk space that will be used. Click Next to start the installation.
  16. (Optional) To see the installation log, click View Log.
  17. After a successful upgrade, perform the following action 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: Remove links from the etc\init.d location by running the following commandswith a root logon ID.
      • 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

Where to go from here

To ensure that your installation was successful, follow the guidance in Verifying-the-installation.

To start or stop product-related services, see the following topics:

 

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