Upgrade process overview
This topic provides an overview of the upgrade process and illustrates the supported upgrade paths for BMC Release Process Management (BRPM) and BMC Release Lifecycle Management Requester UI (now called Release Process Management - Requester UI, 5.0.03.001 onward).
Upgrade process
The upgrade process consists of the following stages:
- Stage 1: Prepare for upgrade—During this stage, you identify the files that you must download from the BMC Electronic Product Distribution (EPD) site, where those files are located, and how to access the files and download them. In this stage, you perform various tasks to set up the installation environment, to ensure that required ports are available, and to determine the bundled components that you might also want to install.
- Stage 2: Perform the upgrade—In this stage, you perform the actual upgrade of the product. BRPM enables you to upgrade to a new installation folder or to the same installation folder as your current version. RLM Requester UI (now called RPM Requester UI, 5.0.03.001 onward) can be upgraded only to the same installation folder. You might also need to complete some preparatory tasks before you begin the upgrade, and perform additional tasks after the upgrade.
Supported upgrade paths
You can upgrade to:
Version | Upgrade path |
|---|---|
BRPM 5.0.05 | 5.0.04.x, 5.0.03.x, 5.0.02, 5.0.01.0x, and 5.0.00 |
BRPM 5.0.04 | 5.0.03.x, 5.0.02, 5.0.01.0x, and 5.0.00 |
BRPM 5.0.03.x | 5.0.02, 5.0.01.001, 5.0.01, 5.0.00, and BRPM 4.8.x |
BRPM 5.0.02 | 5.0.01.001, 5.0.01, 5.0.00, and BRPM 4.8.x |
BRPM 5.0.01.00 | BRPM 4.8.x. and 5.0.00.x |
BRPM 5.0.00.01 | BRPM 4.6.x, 4.8.x, and 5.0.00 |
BRPM 5.0.00 | BRPM 4.6.x and 4.8.x |
You can upgrade to RLM Requester UI (now called RPM Requester UI, 5.0.03.001 onward) 5.0.x from the 5.0.0x version.
Changes due to support for WildFly Application Server
Support for WildFly Application Server was introduced in BRPM version 5.0.03.004 and continues in version 5.0.04. If you are upgrading from version 5.0.03.003 or earlier, note these changes.
Feature/ Change | Version 5.0.03.003 or earlier | Version 5.0.03.004 and later | For more information |
|---|---|---|---|
Change in the BRPM Home Directory | <RLMInstallDir>\releases\<versionNo>\RPM | <RLMInstallDir>\releases\<versionNo>\RPM\portal.war\WEB-INF | - |
Automation job concurrency and other product settings moved | Present in the torquebox.yml file | Present in the wildfly.xml file | |
Change in the standalone file names | standalone.xml standalone-ha.xml (for clusters) | standalone-full.xml standalone-full-ha.xml (for clusters) | - |
Change in the location of deployment information | RLMInstallDir/server/jobss/standalone/deployments/RPM-knob.yml contains the deployment information. | This information is now contained in the CURRENT_RPM_PATH environment variable in the <RLMHome>/bin/start.sh file. | |
STOMP Host URL | Needed by Requester UI | Not needed any more | - |
Running the rake tasks | Need to be run from the following directory: <RLMInstallDir>\releases\<versionNo>\RPM | Need to be run from the following directory: <RLMInstallationDirectory>\releases\<versionNo>\RPM\portal.war\WEB-INF | - |
Configuration settings for JBoss and HornetQ | RLMInstallDir/server/jobss/standalone/configuration/standalone.xml RLMInstallDir/server/jobss/standalone/configuration/standalone-ha.xml (for clusters) | Not needed anymore. Settings added to the standalone-full.xml and standalone-full-ha.xml files. | |
Changes in <RLM_HOME>/bin/start.sh, <RLM_HOME>/bin/stop.sh | A standalone instance does not need binding to the node name and IP address. |
Caution: Do not copy these files from the existing installation. If you have customized these files in the existing installation, make those changes in the upgraded environment again. |
Where to go next