Upgrading from version 4.3.00 to 4.3.01

This topic explains how to upgrade (or migrate) the BMC Release Lifecycle Management solution from version 4.3.00 to 4.3.01 (4.3 Service pack 1).

Before you begin
To upgrade (or migrate) to the latest version of suite products
Where to go from here

When you upgrade (or migrate), the new installation does not replace the product files related to the older version. During the upgrade, you can choose to upgrade in either of the following ways:

By migrating the earlier version's database to version 4.3.01
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.
If your Linux environment has the DISPLAY variable set to export your display to a remote system, ensure that the remote system has an X Window server installed and configured.
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 suite products

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.
- Linux:
  1. Log on as root and navigate to BRLM/Disk1.
  2. Enter the chmod -R +x . command.
  3. Enter the ./setup.sh command.
On the first page of the BMC Release Lifecycle Management Installer wizard, click Next.
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)
Provide the directory path for installing this solution by clicking Browse, and then click Next.

Warning
Note
The directory that you select for the product installation must be empty for the installation to complete successfully.
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: Installs the solution as a normal user
  Warning
  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.
Select the products and components that you want to upgrade, and then click Next. You can upgrade to the latest 4.3.01 version of both BMC Release Lifecycle Management suite components, or you can select to upgrade to the latest version of only the BMC Release Process Management product or the VaraLogix Q Deployment Automation product.
- Install BMC Release Process Management: Installs version 4.3.01 of the BMC Release Process Management product
- Install VaraLogix Q Deployment Automation UI: Installs version 4.3.01 of the BMC VaraLogix Q Deployment Automation product
- Install VaraLogix Q Deployment Engine: Installs the deployment engine for the BMC VaraLogix Q Deployment Automation product
  
  Warning
  Note
  Do not select Install PostgreSQL, as you are migrating from an existing database.
  Feature selection page
  (Click the image to expand it)
If you are installing the BMC VaraLogix Q Deployment Automation UI, the Deployment Action Packs page lists the action packs for the various types of middleware objects. Select action packs based on the middleware type that you want to manage, and then click Next.

Warning
Note
If you have modified any of your actions, they will not be updated with fixes from BMC. In order to avoid this, delete the scripts that you have modified before the upgrade.
If after the upgrade your action scripts were not modified, delete the unmodified scripts and execute the run loadpacks <pack name> command from the <rlm path>/releases/4.3.01/Q directory.

Deployment action packs information
(Click the image to expand it)
If you are installing BMC Release Process Management, on the BMC Release Process Management Migration Information page specify details for migrating your database to version 4.3.01 of BMC Release Lifecycle Management, and then click Next:
1. Select BMC Release Process Management 4.3.00 from the Copy data from list to migrate the existing version 4.3.00 BMC Release Process Management database.
2. Click Browse and provide the directory location of the product from which you want to migrate:
  If you are migrating from version 4.3.00, your product might be installed at RLM\releases\4.3.0\RPM
  For example, C:\Program Files\BMC Software\RLM\releases\4.3.0\RPM.
3. Database migration: Select one of the following options:
  - Update database: Migrates your database to version 4.3.01
  - Clean database (reset data contents): Deletes your database and creates a new database for version 4.3.01
4. Select the Copy other settings too (SMTP configuration etc.) check box if you want to copy your email notification settings to version 4.3.01.
BRPM Migration information
(Click the image to expand it)
If you are installing the BMC VaraLogix Q Deployment Automation UI, on the BMC VaraLogix Q Deployment Automation Migration information page specify upgrade details:
1. Select BMC VaraLogix Q Deployment Automation UI 4.3.00 from the Copy data from list.
2. Click Browse and provide the directory location of the product from which you want to migrate in the Existing installation location field.
  For example, C:\Program Files\BMC Software\RLM\releases\4.3.0\Q
3. Select either the the Update database or Clean database option, depending on whether you want to clean the existing database, or keep the data as is and upgrade it to current version.
4. Click Next.
  
  VaraLogix Q Deployment Automation Migration information
  (Click the image to expand it)
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)
If you are installing BMC Release Process Management, specify details for the HTTP port of this product, and then click Next.
The HTTP port is the Tomcat server port for BMC Release Process Management (default port: 8080). If you are already using the default port, specify an alternate port.
You can also choose to enable SSL settings for your Tomcat server by selecting the Enable SSL check box. If you enable your SSL settings, then you must specify the HTTPS port (default: 8443) and the private key, certificate file, and passphrase.

Warning
Note
The passphrase is used to set up the Java keystore. For more information, see Obtaining-test-SSL-certificates.
BMC Release Process Management HTTP/HTTPS port information
(Click the image to expand it)
If you are installing the BMC VaraLogix Q Deployment Automation UI, specify details for the HTTP port of this product, and then click Next.
The HTTP port is the port of the Apache server for BMC VaraLogix Q Deployment Automation (default port: 80). If you are already using the default port, specify an alternate port, or stop the application which uses that port. If you have a previous BMC Release Lifecycle Management instance using this port, stop the bmcrlmapache-4.3.0 service.
You can also choose to enable SSL settings for your Apache server by selecting the Enable SSL check box. If you enable your SSL settings, then you must specify the HTTPS port (default: 443) and the private key, certificate file, and passphrase.
Warning
Note
If in the step 4 you selected the non-root installation, then the HTTP Port number that you specify must be greater than 1000.

BMC VaraLogix Q Deployment Automation HTTP/HTTPS port information
(Click the image to expand it)
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.
Warning
Note
- If you selected the Update database option on the BMC VaraLogix Q Deployment Automation Migration page, the data you enter on the Super User Details page relate only to the BMC Release Process Management component product installation.
- If you selected the Update database option on the BMC Release Process Management Migration page, the data you enter on the Super user information page relate only to the VaraLogix Q Deployment Automation component product installation.
- If you selected to update the database for both suite products, the Super User Details page is not displayed.
Super user information
(Click the image to expand it)
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
Warning
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)
On the Database details page, specify the following details for the database that you want to use for the BMC Release Process Management and BMC VaraLogix Q Deployment Automation component products, and then click Next.
Warning
Note
- Depending on which products you selected to upgrade, several parts of the Database Details page may be grayed-out.
- If you are using the PostgreSQL or the SQL Server database, then specify different schema for the BMC Release Process Management and the BMC VaraLogix Q Deployment Automation component products.
- If you are using the Oracle database, then you can use the same schema, but you must specify a different user name. This applies to both the component products, BMC Release Process Management and BMC VaraLogix Q Deployment Automation.
- Database: You can select one of the following options in the list displayed as shown in the following image. When you select one of the following databases, the default port is automatically displayed.
  - POSTGRESQL (Default port 5432)
  - ORACLE (Default port 1521)
  - SQL_SERVER (Default port 1433)
- Host: Specify the computer name of the server where your database is installed.
- Port: Specify the port of the server that you used for installing your database. Depending on the database you selected earlier, the default port is automatically displayed.
- RPM 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 Name details. This information relates only to the BMC Release Process Management component product.
- RPM Database User: Specify the user name of the database instance that you used while creating it at the time of the database installation. This information relates only to the BMC Release Process Management component product.
- RPM Database Password: Specify the password of the database instance that you used while creating it at the time of the database installation. This information relates only to the BMC Release Process Management component product.
- Q Database/Service 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 Service Name details. This information relates only to the BMC VaraLogix Q Deployment Automation component product.
- Q Database User: Specify the user name of the database instance that you used while creating it at the time of the database installation. This information relates only to the BMC VaraLogix Q Deployment Automation component product.
- Q Database Password: Specify the password of the database instance that you used while creating it at the time of the database installation. This information relates only to the BMC VaraLogix Q Deployment Automation component product.
  Warning
  Note
  If you are performing the migration for both BMC Release Process Management and VaraLogix Q Deployment Automation, the Database details page is grayed-out. The database details from the previous version are used.
  The Database details page is only editable if the No migration required option was selected on the BRPM and VaraLogix Q Deployment Automation migration pages (steps 7 and 8).
  Database Details for BMC Release Process Management migration
  (Click the image to expand it)
  
  Database Details for BMC VaraLogix Q Deployment Automation migration
  (Click the image to expand it)
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.
- 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.
  
  Warning
  Note
  If you selected Copy other settings too (SMTP configuration etc.) on the BRPM Migration information page, the Email Notifications Details page is not displayed.
  The SMTP server details from the previous version will be used.
  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 details
  (Click the image to expand it)
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.
(Optional, BMC Release Process Management product only) To see the installation log, click View Log.
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