Patch 5 is now available for Release Process Management (RPM) version 5.0.03. This patch includes enhancements.
This patch includes the following enhancements.
With this release, you can mark request templates as global. All the users in the system can create requests using these global templates. You can mark a template global either while creating the template or after creating it.
In addition, when creating a request from a new or an existing template (whether global or not), you can select the application to which you want to assign the request. Applications are available for selection based on the access permissions. For more information, see Managing request templates.
To mark a template as global using REST API, see the PUT and POST methods on REST request templates.
With this release, you can define dependency for a step. A step can be dependent on a request or a specific step of a request. If a step is dependent on a request, the step will not execute unless all the steps of the request are executed. You can define this dependency only if you have the View Deployment Dependency Tab permission. For more information about the permission, see Requests permissions.
Now you can set up any .jpeg, .jpg, png, or .gif image as the logo of your organization in the RPM UI. The logo appears in the upper right corner of the UI. Also, you can add a banner to the Login page to notify users of any important information. For more information, see Setting up logo and banner.
With this release, you can restrict non-root users from viewing the full automation run results for a step. Non-root users can view full results (the script, input parameters for the script, and the script execution results) for a step only if they have the View Full Automation Results permission. Otherwise, they can view only script execution results. For more information, see Viewing automation results.
The following updates are made to the audited changes:
search_termattribute no longer appears.
For more information about audited changes, see Auditing resources.
This patch supports Oracle Database version 12c R2. For the list of supported databases, see System requirements.
In this patch release, the following updates are made to the REST APIs:
This version uses the following third-party software:
|WildFly Application Server||19.1|
|AdoptOpenJDK||1.8 update 252|
|Apache Tomcat web server version |
(Used only in case of Requester UI)
This patch includes the full installer of RPM. For download instructions, see Downloading the installation files.
You can install this patch as a new product installation. For instructions, see Installing.
If you have any of the following versions of RPM, you can upgrade to this patch. For instructions, see Upgrading.
Support for WildFly Application Server was introduced in RPM version 5.0.03.004 and continues in version 5.0.03.005. 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, 5.0.03.005||For more information|
|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.