This topic contains information about the updates in this patch and provides instructions for downloading, installing, and upgrading to the patch.
Starting with this release, you can audit all the resources available in the RPM system. You can audit individual (for example, user and team) as well as associated resources (for example, application-environment). You can analyze audit results further to improve efficiency and remove inaccuracies in the system. For more information, see Auditing resources.
Starting with this version, RPM installer generates a self-signed certificate. In addition, RPM no longer supports HTTP protocol. Only HTTPS protocol is supported.
You can use either the self-signed certificate or any other third-party certificate for secure communication. If you are using HTTP in your existing installation, you are prompted to use HTTPS during upgrade. You can provide parameters either to generate a self-signed certificate or add a third-party certificate.
For instructions to generate the self-signed certificate during installation, see Installing BMC Release Process Management (RPM UI) and Installing BMC Release Lifecycle Management Requester UI (Requester UI). To provide the certificate details during upgrade, see Performing the upgrade.
API response to the existing methods in REST APIs contains huge data as the response includes not only data for an item but data for its associated items as well.
This version provides an additional filtering option,
alone, in REST API version 1 (v1) methods for all the items in RPM. This option can have one of the following values, true and false. If set to true, this option returns data only for the item for which the method is being executed. If set to false (default), it returns data for the item as well as its associated items.
In addition, now the
include_except filtering option is now available for all the items in RPM for all the REST API v1 methods. Use these filtering options to limit the API response data, and hence, to decrease the response time.
For more information about these options, see the individual APIs in REST API version 1.
In 5.0.03.003 and earlier versions, to search for a group, in the Search base field, you need to have the absolute path specified upto the folder level in which the group is created. Starting from version 5.0.03.004, in addition to the absolute path, you can provide path only upto domain or forest level. For more information, see Creating LDAP group mapping.
Starting from this version, BMC Release Process Management (RPM) uses WildFly Application Server version to build applications. In earlier versions, RPM uses TorqueBox (JBoss AS).
This version uses the following third-party software:
|WildFly Application Server||18.0.1|
|AdoptOpenJDK||1.8 update 212|
|Apache Tomcat web server version |
(Used only in case of Requester UI)
For download instructions, see Downloading the installation files. For installation instructions, see Installing.
The process to upgrade to the patch is similar to upgrading to any major or minor version. For more information, see Upgrading.
The following table describes the changes in RPM due to the support of WildFly Application Server.
|Feature/ Change||Version prior to 5.0.03.004||5.0.03.004||For more information, see..|
|Change in the RPM 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||Performance tuning|
|Change in the standalone file names|
standalone-ha.xml (for clusters)
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.||Performance tuning|
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.