Performing the upgrade

This topic describes how to upgrade your installed version of BMC Release Process Management to version 4.6.00 and versions 4.6.00.02 and later. For the upgrade instructions to the BMC Release Process Management 4.6.00.01 patch version, see the individual patch topic under Release-notes-and-notices.

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 the new version
By using a fresh database for the new version

Use the following instructions to upgrade your BMC Release Process Management to version 4.6.00 or 4.6.00.02 and later:

Before you begin
To upgrade the product to a new installation folder
To upgrade the product to the same installation folder as your current version
After the upgrade
Using a rake task to remove groups and teams
Related topics

Before you begin

Before you begin the upgrade process, verify the following items:

You can upgrade BMC Release Process Management to version 4.6.00 or later only from version 4.3.00 or later.
BMC recommends that you back up your automation results by performing the following steps:
1. Copy the RLM\automation_results folder to the RLM\automation_results_backup folder.
2. Perform the upgrade.
3. After the upgrade, if you need to restore the automation results, copy the RLM\automation_results_backup folder to overwrite the RLM\automation_results folder.
For more information, see Upgrading from 4.4.x to 4.6.x version.
BMC recommends that you install the product with administrator privileges (on Windows) or superuser privileges (on Linux or Solaris). You can install the product as a normal user without Administrator privileges (on Windows) or Superuser privileges (on Linux or Solaris), but you cannot register the product as a service.
Verify that your environment meets the requirements listed in System-requirements and verify that you have prepared the installation environment.
When upgrading to BMC Release Process Management version 4.6 with an existing database and more than 1,000 existing requests, we recommend that before you install the application you increase the amount of memory that the installer can utilize to avoid possible issues. To do this, change the value of the _JAVA_MAXIMUM_HEAP_SIZE property in the appropriate file.

For example:
- For a Windows environment — setup.bin file
  Change from:
  set _JAVA_MAXIMUM_HEAP_SIZE=-Xmx512m
  
  To:
  set _JAVA_MAXIMUM_HEAP_SIZE=-Xmx1024m
- For a Linux environment — setup.sh file
  Change from:
  _JAVA_MAXIMUM_HEAP_SIZE=-Xmx512m
  
  To:
  _JAVA_MAXIMUM_HEAP_SIZE=-Xmx1024m

If you are installing the BMC Release Process Management product on a UNIX platform, ensure that no rvm environment is in the path of the installation.
Download and extract the BMC Release Process Management zip files in your preferred location.
Save a backup of your database. In case of any issues with the product upgrade, revert your database to the backup and perform the upgrade again.
BMC recommends that you stop the BMC Release Process Management server before you upgrade the product database to the new version.
If you have custom views of the teams_roles and teams_users tables in the database, back up and delete your custom views before upgrading to version 4.6.00. The installer drops these tables during installation. However, if the tables are in use, the installer cannot drop the tables and the installation fails. After successfully upgrading to version 4.6.00, you can restore your views.
If you experience any problems with the installation, see Troubleshooting.

During the upgrade, ensure that you meet the following requirements:

For HTTP/HTTPS and messaging system ports, use different port numbers for version 4.6.00 and your current product version.
All passwords must contain at least one letter, at least one number, and at least one non-alphanumeric symbol.

The automation results from your current product version are automatically copied to the BMC Release Process Management version 4.6.00/4.6.00.02 installation folder.

To upgrade the product to a new installation folder

Start the installation program:
- Windows:
  - If you are installing the product with administrator privileges:
    1. Go to <BRLM_Installation_Folder>\RLM\Disk1.
    2. Right-click setup.cmd.
    3. From the pop-up menu, click Run as administrator.
  - If you are installing the product as a normal user, click setup.cmd.
- Linux:
  1. Log in as a root user.
  2. Navigate to <BRLM installation folder>\RLM\Disk1.
  3. To make the installation file executable, run the following command:
    chmod -R +x .
  4. To start the installation program, run the following command:
    ./setup.sh
The BMC Release Process Management 4.6.x Installer opens.
Click Next.
The License Agreement pane displays.
On the License Agreement pane, select I agree to the terms of the license agreement, and then click Next.
The Directory Selection pane displays.
On the Directory Selection pane, specify the directory path for the BMC Release Process Management version 4.6.x installation, and then click Next.
The Installation type pane displays.
On the Installation type pane:
- Select Installer is started with root privileges so perform full installation, if you started the installation program with Administrator or root privileges.
- Select Install solution files and configurations. Do not perform tasks that require special rights if you started the installation program without Administrator or root privileges.
Click Next.
The Select features pane displays.
On the Select features pane, make sure that Upgrade BMC Release Process Management to 4.6.x is selected, and then click Next.
The Migration of data of previous RPM versions pane displays.
On the Migration of data of previous RPM versions pane:
1. From the Copy data from list, select your current BMC Release Process Management version.
2. In Existing installation location, enter the directory path to your current version of BMC Release Process Management.
  Tip
  The default installation folder for BMC Release Process Management releases is the following:
  - Windows: C:\Program Files\BMC Software\RLM\releases\<Release_Version>\BRPM
  - Linux/Solaris: /opt/bmc/RLM/releases/<Release_Version>/BRPM
3. From Database migration:
  - Select Update database to save your data from the existing database and update the database to version 4.6.x.
  - Select Clean database to delete your data from the existing database and update the database to version 4.6.x.
    Note
    Issues might occur if you do not select Clean database. For more information, see Upgrading without database migration clean up on the Upgrade-issues topic.
4. (Optional) Select the Copy SMTP configuration settings check box if you want to save your SMTP settings.
5. (Optional) In the Cluster installation section, ensure that the Skip Database modifications check box is selected if you are installing the product application files and are not making changes to the database.
  Note
  You can use the Skip Database modifications option if you install the BMC Release Process Management product to a node in a cluster and you already have installed the same version of the application and database on another node of the same cluster. For more information, see High-availability-deployment.
Click Next.
The JRE Information pane displays.
On the JRE Information pane:
- If you want to use Java Runtime Engine (JRE) provided with BMC Release Process Management version 4.6.x, select Use bundled JRE (version 1.7.0_09).
- If you want to use Java Runtime Engine (JRE) installed on your computer, ensure that Use bundled JRE (version 1.7.0_09) is not selected, and then in Select JRE path, specify the directory path to the JRE installation files on your computer.
Click Next.
The Server HTTP/HTTPS Port Information pane displays.
On the Server HTTP/HTTPS Port Information pane:
- If you want to use HTTP to access the BMC Release Process Management application server, in HTTP Port enter the HTTP port number.
- If you want to use the Secure Sockets Layer (SSL) to access the BMC Release Process Management application server:
  1. Select Enable SSL.
  2. In HTTPS Port, enter the port number for the SSL connection.
  3. In Private Key, specify the directory path to the private key for SSL encryption.
  4. In Certificate File, specify the directory path to the certificate for SSL connection.
  5. In Passphrase, enter the passphrase for your certificate.
Click Next.
The Super User Details pane displays.
On the Super User Details pane, specify the various details for the BMC Release Process Management super user and then click Next.
The Torquebox Super User Details pane displays.
Notes
- The Super User Details pane is not available if you selected to update your database on the Migration of data of previous RPM versions pane.
- The super user is the first user who has administrator access permissions to use BMC Release Process Management.
On the TorqueBox Super User Details pane, enter the username and password for the TorqueBox superuser, and then click Next.
The Messaging system details pane displays.
On the Messaging system details pane, specify the following details to connect to the messaging system server:
- Host: Host address for the messaging system server. 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.
- Port: Port for the messaging system server. The default port value is 5445.
- User: User name for the messaging system server.
- Password: Password of the messaging system server.
Click Next.
The Database details pane displays.
On the Database details pane, click Next.
The Email Notification details pane opens.
On the Email Notification details pane:
Note
The Email Notification details pane is not available if you selected to copy your SMTP settings from the previous BMC Release Process Management on the Migration of data of previous RPM versions pane.
- Select No Email Notifications if you do not want to use the email notifications.
  Note
  You can configure email notifications later from the BMC Release Process Management application. For more information, see Changing-the-email-notification-configuration-manually.
- Select Use SMTP to configure Simple Mail Transfer Protocol (SMTP) server details:
  - SMTP Server: Enter the name or address of the SMTP server used for sending emails.
  - SMTP Port: Enter the SMTP server port. The default SMTP server port is 25.
  - SMTP Domain: Enter the domain name for your SMTP server. Domain name is the part of the user name after xyz@ in your email address. For example, if your user name is redmine@example.net, your domain name is example.net.
  - SMTP Authentication: Select the authentication mechanism for your SMTP service.
  - SMTP User: Enter the user name used to connect to the SMTP server. For example, redmine@example.net.
  - SMTP Password: Enter the password used to connect to the SMTP server.
  - TLS: Select TLS if your SMTP server requires a secure connection and is using TLS.
Click Next.
The Installation Preview pane displays.
On the Installation Preview pane, verify the details for the BMC Release Process Management 4.6.x installation such as the installation path, the selected features, and total disk space that will be used, and then click Install.
The BMC Release Process Management version 4.6.x installation process begins.

To upgrade the product to the same installation folder as your current version

Start the installation program:
- Windows:
  - If you are installing the product with administrator privileges:
    1. Go to <BRLM_Installation_Folder>\RLM\Disk1.
    2. Right click setup.cmd.
    3. From the pop-up menu, click Run as administrator.
  - If you are installing the product as a normal user, click setup.cmd to start the installation program.
- Linux:
  1. Log on as a root user.
  2. In the terminal, go to <BRLM installation folder>\RLM\Disk1.
  3. To make the installation file executable, run the following command:
    chmod -R +x .
  4. To start the installation program, run the following command:
    ./setup.sh
The BMC Release Process Management 4.6.x Installer opens.
Click Next.
The License Agreement pane displays.
On the License Agreement pane, select I agree to the terms of the license agreement, and then click Next.
The Directory Selection pane displays.
On the Directory Selection pane, specify the directory path for the BMC Release Process Management version 4.6.x installation, and then click Next.
The Destination Problem pane displays.
On the Destination Problem pane, click Next.
The Installation type pane displays.
On the Installation type pane:
- Select Installer is started with root privileges so perform full installation, if you started the installation program with Administrator or root privileges.
- Select Install solution files and configurations. Do not perform tasks that require special rights if you started the installation program without Administrator or root privileges.
Click Next.
The Select features pane displays.
On the Select features pane, make sure that Upgrade BMC Release Process Management to 4.6.x is selected, and then click Next.
The Migration of data of previous RPM versions pane displays.
On the Migration of data of previous RPM versions pane:
1. In the Copy data from list, make sure that your current BMC Release Process Management version is selected.
2. In Existing installation location, make sure that the directory path to your current version of BMC Release Process Management is specified.
  Tip
  The default installation folder for BMC Release Process Management releases is the following:
  - Windows: C:\Program Files\BMC Software\RLM\releases\<Release_Version>\RPM
  - Linux/Solaris: /opt/bmc/RLM/releases/<Release_Version>/RPM
3. From Database migration:
  - Select Update database to save your data from the existing database and update the database to version 4.6.x.
  - Select Clean database to delete your data from the existing database and update the database to version 4.6.x.
Click Next.
The JRE Information pane displays.
On the JRE Information pane:
- If you want to use Java Runtime Engine (JRE) provided with BMC Release Process Management version 4.6.x, select Use bundled JRE (version 1.7.0_09).
- If you want to use Java Runtime Engine (JRE) installed on your computer, ensure that Use bundled JRE (version 1.7.0_09) is not selected, and then in Select JRE path, specify the directory path to the JRE installation files on your computer.
Click Next.
The TorqueBox Super User Details pane displays.
On the TorqueBox Super User Details pane, enter the username and password for the TorqueBox superuser, and then click Next.
On the Messaging system details pane, specify the following details to connect to the messaging system server, and then click Next.
Note
The Messaging system details pane displays only if your current messaging system password does not match the following pattern:
- At least one letter
- At least one number
- At least one non-alphanumeric symbol
- Host: Host address for the messaging system server. 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.
  32Port: Port for the messaging system server. The default port value is 5445
- User: User name for the messaging system server.
- Password: Password of the messaging system server.
The Installation Preview pane displays.
On the Database details pane, specify the following details to connect to the database server, and then click Next.
- Database: Select your database type, either POSTGRESQL, ORACLE, or SQL_SERVER.
- Host: Host address for the database system server. 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.
- Port: Port for the database system server. The default port value is 5432 (PostgreSql), 1521 (Oracle), and 1433 (SQL_Server).
- RPM Database/SID Name: Specify a database name or identifier (for example, bmc_rpm_db).
- RPM Database User: User name for the database system server.
- RPM Database Password: Password of the database system server.
On the Installation Preview pane, verify the details for the BMC Release Process Management 4.6.x installation such as the installation path, the selected features, and total disk space that will be used, and then click Install.
The BMC Release Process Management version 4.6.x installation process begins.

After the upgrade

After you complete the installation, you might need to perform the following tasks:

If you installed the product without administrator or root privileges, you must start product services whenever you restart your computer. For more information, see Starting-and-stopping-product-services.
To verify that the installation was completed successfully, access the product interface. For more information, see Accessing-the-interface.

To remove groups and teams automatically created during database migration, see Using a rake task to remove groups and team.

Using a rake task to remove groups and teams

When converting an existing BMC Release Process Management version 4.4 database to version 4.6, the database migration process recreates the team and role permissions that currently exist in the application. This action results in a number of teams and groups that, while accomplishing the task, do not necessarily fit into a holistic Role Base Access Control (RBAC) strategy. For a reasonably complicated BMC Release Process Management installation, this action can result in dozens or even hundreds of groups and roles to remove.

The following rake task removes all of the automatically created teams and groups from the database. This rake task is intended for BMC Release Process Management administrators and BMC consultants to assist in a structured RBAC transition. The existing users whose groups and roles are removed by the rake task will not be able to perform their duties until you create new roles and groups for them.

jruby -S rake app:remove_automatic_groups_and_teams

The rake task works entirely by the name of the object and according to the following rules:

Groups and teams that match the following criteria will be deleted completely with no recovery:
- Any group that ends with "-group" (for example, Group.where("name like '%-group%'")
- Any team that ends with "created team" (for example, Team.where("name like '%created Team%'")
Automatically created roles are left in place and have names such as Deploy, Coordinator, Deployer-admin, and so on.