Upgrading from version 2.5 to 2.5.x

Use the procedure in this topic to upgrade from BMC Release Process Management version 2.5 to any available minor version or patch.

Before you begin

Ensure that the following conditions are met:

• BMC Release Process Management is running successfully on your computer.
• You have located the installation directories (for example, in the BRPM HOME folder).
• The database that stores BMC Release Process Management 2.5 data can also be used to store product data after the upgrade.
• The upgrade file is available as a WAR file.

To upgrade from 2.5 to 2.5.x

1. Prepare the upgrade files:
   1. As an administrator, log on to the server that hosts the database and back up the database.
   2. Download the zip file that corresponds to your platform and to the build to which you want to upgrade.
       For example, to upgrade to BMC Release Process Management 2.5.01 on Linux, you would download BRPM-Linux-2.5.01-Build-18.zip.
   3. Unzip this file to a temporary location (for example, BRPM_LATEST_BINARIES).
2. Upgrade the web application archive (WAR) file:
   1. Turn off the BMC Release Process Management service:
      • (Windows) Click Start > Run > services.msc.
      • (UNIX) Enter /etc/init.d/bmcrpm.
   2. Back up the contents of the <BRPM_HOME>\server\webapps\brpm directory.
   3. Download the latest version of the BMC Release Process Management 2.5 upgrade or patch WAR.
   4. Delete the contents of the <BRPM_HOME>\server\webapps\brpm directory (do not delete the directory itself).
   5. Open a command prompt and change to the <BRPM_HOME>\server\webapps\brpm directory.
   6. Extract the WAR file, using the following command:
      %JAVA_HOME%\bin\jar.exe -xvf "<BRPM_LATEST_BINARIES>\BRPM\Disk1\files\SmartRelease_2.war"
   7. Restore the following configuration files from the backup:
      config/database.yml
      config/smtp_settings.rb
      config/wicked_pdf_config.rb
   8. Restore the application files in the automation_results directory from the backup to <BRPM_HOME>\server\webapps\brpm.
3. Upgrade JRUBY:
   1. Navigate to <BRPM_HOME>\lib.
   2. Back up the jruby directory, and then delete the jruby directory.
   3. Navigate to <BRPM_HOME>\lib and run the following command:
      unzip <BRPM_LATEST_BINARIES>\BRPM\Disk1\files\1fcf998eaa4d.zip
       This command creates a new jruby directory.
       Use a zip file extraction tool on Windows.
   4. (UNIX only) Run the following command:
      chmod +x <BRPM_HOME>\lib\jruby\bin*
4. Migrate the database:
   1. Create a temporary directory (for example, /tmp/db_upgrade say <TEMP_UPGRADE_DIR>).
   2. Navigate to that temporary directory (for example, run the following command: cd <TEMP_UPGRADE_DIR>).
   3. Run the following command:
      unzip <BRPM_LATEST_BINARIES>\BRPM\Disk1\files\1fcf998eaaaf.zip
       Use a zip file extraction tool on Windows.
   4. Set the JRUBY path as follows:

      • Windows: 

        
        set PATH=%PATH%;<BRPM_HOME>\lib\jruby\bin
            set RAILS_ENV=production
        

      • UNIX: 

        
        PATH=$PATH:<BRPM_HOME>/lib/jruby/bin
             export PATH
             RAILS_ENV=production
             export RAILS_ENV
        
   5. Copy the config/database.yml file from the backup into the config directory under <TEMP_UPGRADE_DIR>.
       This makes the current temporary rails environment point to the 2.5.00 database.
   6. From the <TEMP_UPGRADE_DIR> directory, run the following command:
      jruby -S rake db:migrate RAILS_ENV="production"
       This command migrates the database from 2.5.00 to the latest level.
5. Turn on the BMC Release Process Management service:
   • (Windows) Click Start > Run > services.msc.
   • (UNIX) Enter /etc/init.d/bmcrpm.
6. Watch the ?<BRPM_HOME>\server\logs\localhost.<date>.log file until the following message is displayed: org.kares.jruby.rack.WorkerContextListener INFO : started 3 worker(s).
7. Open your web browser and ensure that the new version number appears during logon.
8. Delete the <TEMP_UPGRADE_DIR> directory.