5.0.03.002: Patch 2 for Service Pack 3

This topic contains information about the updates in this patch and provides instructions for downloading and installing the patch.

Enhancements

Version 5.0.03.002 provides the following enhancements.

New rake tasks to purge inactive records from a database

You can now run rake tasks to purge inactive records for the following entities from the database:

Version tags
Components
Environments
Plans

A common rake task is available to delete inactive or archived version tags, components, and environments. A separate rake task is available to purge archived plans from the database.

You can choose to delete records for either a single entity or for all the entities from the database. For more information, see Purging inactive records from the BRPM.

Security enhancements

This section describes the security enhancements in this patch.

Restrictions on uploading files in BMC Release Process Management

In the earlier releases, there were no restrictions on the type of files that users could upload in BMC Release Process Management application. Now, using the File Upload Validation settings in BRPM, administrators can specify the allowed file extensions (as a comma-separated list) and the MIME types associated with the file extension.

You can now upload only those files that are specified in the File Upload Validation settings. The following figure shows the file upload settings in BRPM (System > Settings > General).

For a list of default file extensions and file types supported by BRPM, see Specifying general settings.

Restrictions on login attempts with incorrect credentials

In the earlier releases, you could log on to the BMC Release Process Management application with an incorrect username or password for any unlimited number of times.

With this release, if you try to log on to the application with incorrect credentials for five times consecutively, your user account is locked.

Once locked, only administrators or user roles that have the Unlock User permission can unlock a user account. You can only unlock a user account for active users. A user with a locked account cannot access the BMC Release Process Management application either from the UI or the REST APIs. This behavior is applicable for local authentication only and does not affect LDAP users.

You can change the number of times a user can try to log on based on your organization's needs. For more information, see Specifying general settings.

Restrictions on changing the login name for a user

While creating a user in BMC Release Process Management application, one needs to specify a Login name for the user. In the earlier releases, the Login field was editable. Logs display data according to the user login name. If the login name changes, you would not be able to trace the logs for activities of a particular user.

Starting this release, after you add a new user, you cannot change the Login name while editing a user. The login attribute is also restricted from the REST users API call.

For more information, see Managing users.

Restricted access for requests and reports

In the earlier releases, there was no restriction on the timeline for viewing historical data for requests or for reports. For example, one could view requests that occured a couple of years back by using the date filters on the Requests UI. This can cause performance issues as the application would have to handle a huge volume of historical data.

With this release, administrators can restrict this timeline by specifying the Report/Request Date Filter Range settings for viewing requests and reports. The following figure shows the Report/Request Date Filter Range in the Settings (System > Settings > General) menu.

For more information, see Specifying general settings.

Usability enhancements

This section describes the usability enhancements in this patch.

User name displayed in the server log file

With this release, the server.log file (located at /opt/bmc/RLM/server/jboss/standalone/logs) shows data according to the user that performs the actions on the BRPM application.

In the following figure, log data is displayed for the admin user.

Azul Java bundled with BMC Release Process Management

The RPM Server component that uses bundled Java environment will be shipped with Azul Java version 1.8 update 192. There is no functional impact to your environment. If you are upgrading to the patch, the Oracle Java in your earlier environment is replaced by Azul Java and no manual configuration is required. For more information, see Support for Java Open link .

Downloading the patch

To download the patch, go to the BMC Release Process Management 5.0.03 page on the BMC Electronic Product Downloads site and download the installation files for the patch.

For download instructions, see Downloading the installation files.

Installing the patch

The process to install the patch is similar to installing any major or minor version.

For more information, see Installing.

Upgrading to the patch

The process to upgrade to the patch is similar to upgrading to any major or minor version.

Note

If you upgrade to this patch, the production.rb file (located at RLMhome\releases\ProductVersion\RPM\config\environments) gets replaced by a new instance of the file. If you have made changes to the production.rb file, ensure that you back up the file, and update the changes to the file after the upgrade.

For more information, see Upgrading.

Page tree