5.0.06: Service Pack 6 for version 5.0


Service Pack 6 is now available for BMC Release Process Management (BRPM) version 5.0. This service pack includes enhancements. 

Enhancements

This service pack includes the following enhancements:

Updates to JBoss management console

From this release, we have added HTTPS support for JBoss management console.

Updates to keystore password

From this release, BRPM allows you to replace cleartext passwords in the standalone.xml files with encrypted values. For more information, see Encrypting keystore password in standalone.xml files.

Updates to internode communication within a cluster

From this release, BRPM supports HTTPS configuration to ensure a more secure connection between the nodes within a cluster. We have added the standalone-full-ha-https.xml file and the standalone-full-https.xml file which will be referred to, when internode communication is set to HTTPS. For more information, see Enabling HTTPS configuration support for internode communication


System requirements updates

This service pack supports Red Hat Enterprise Linux 8.3 operating system.

For a complete list of supported databases, see System-requirements.

Pipeline view for Stages in Plans

You can now view information about the stages within a plan on a pipeline. For more information, see Managing-plans.

Password policy for local users

From this release, passwords for local users must contain 8 to 128 characters, satisfying at least 3 out of 4 conditions, namely, uppercase and lowercase characters, digits and special characters, and must not contain two equal characters in a row. For more information, see Managing users and Managing-your-profile.

Downloading the service pack

This patch includes the full installer of BRPM. For download instructions, see Downloading-the-installation-files

Changes to support WildFly Application Server

Support for WildFly Application Server was introduced in BRPM version 5.0.03.004. If you are upgrading from version 5.0.03.003 or earlier, note these changes:

Feature or change

Version 5.0.03.003 or earlier

Version 5.0.03.004 and later

Reference

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)

(New in Service pack 6) standalone-full-https.xml

(New in Service pack 6)`standalone-full-ha-https.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

No longer required

-

Running the rake tasks

Run from the following directory: <RLMInstallDir>\releases\<versionNo>\RPM

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)

No longer required.

Settings are added to the standalone-full.xml and standalone-full-ha.xml files and (New in Service pack 6) standalone-full-https.xml and standalone-full-ha-https.xml files.

Changes in <RLM_HOME>/bin/start.sh, <RLM_HOME>/bin/stop.sh

A stand-alone instance does not need binding to the node name and IP address.

Contains information about the binding of a stand-alone instance to the node name and IP address

Contains BRPM deployment information

Warning: 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.

-

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Release Process Management 5.0.08