Upgrading from version 2.4 to version 2.5

Use the procedure in this topic to upgrade from BMC Release Process Management version 2.4 to 2.5.

Before you begin

Before starting the migration, you must set up the environment or have the following configurations:

• Default authentication or Lightweight Directory Access Protocol (LDAP) is configured in version 2.4.
• Your environment complies with the requirements in Supported-platforms-for-version-2-5-00.

To upgrade from version 2.4 to 2.5

1. Ensure that Remote Desktop Connection is available to the server that you want to host BMC Release Process Management 2.5.
2. Install BMC Release Process Management using the standard installer, as described in Installing-directly or Installing-silently-using-an-options-file.
    During the installation, do not specify the same database used by version 2.4, so that it does not get overwritten. Specify a new, unique name for the 2.5 database, such as brpm_2_5.
3. Migrate version 2.4 data from its database to the new 2.5 database:
   • To migrate from a MySQL database to an Oracle database, see Migrating-data-from-a-MySQL-database-to-an-Oracle-database.
   • To migrate from a Postgres database to an Oracle database, use the same migration task, but use the Postgres Java Database Connectivity Java Archive (JDBC JAR) while configuring the source connection.
4. Open a command prompt and switch to the directory where BMC Release Process Management is installed (for example, C:\BRPM\server.
5. Ensure that the PATH environment variable includes C:\BRPM\lib\jruby\bin and that no other ruby runtimes are specified in this variable.
6. Enter jruby -S rake db:migrate.
7. After the database schema migrates successfully from version 2.4 to version 2.5 (this might take some time), start the BMC Release Process Management version 2.5 Tomcat service.
8. Log on to the product with the same credentials as used in product version 2.4.