Patch 1: version 4.6.00.01

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

Updates

Patch 1 provides the following updates:

(US194726) You can now simultaneously create multiple requests for different environments. For more information, see Managing-requests and REST-requests.
(US195877) Multiple administrators can simultaneously add users to the same group from different sessions without overwriting other administrators' changes. For more information, see the To edit a group section in Managing-groups.

(US193753) In addition to XML files, you can also import and export applications as JSON files.
(US194381) When exporting and importing applications with automations, Resource Automations are also exported and imported, together with the Automation scripts used in the request templates.

For information about issues corrected in this patch, see Known-and-corrected-issues. To find the fixed issues for the 4.6.00.01 version, you can sort the issues in the table by the Corrected in column.

Downloading BMC Release Process Management version 4.6.00.01

Perform the following steps to download the patch:

Create a directory in which to place the downloaded files.
Note
On Windows computers, ensure that the directory is only one level into the directory structure. The Electronic Product Distribution (EPD) package creates a directory in the temporary directory when you extract the files, and the directory that contains the installation image must not be in a directory deeper than two levels into the directory structure.
Go to http://www.bmc.com/available/epd.html.
At the logon prompt, enter your user ID and password, and then click Submit.
On the Export Compliance and Access Terms page, provide the required information, agree to the terms of the agreements, and click Continue.
Click the Product Patches tab.
Select the profile you want from the Select Profile list, if you have multiple profiles, or if you are accessing this site for the first time, create an EPD profile to specify the platforms that you want to see, as described in the EPD site help. Otherwise, go to step 7.
Expand BMC Application Management Suite > BMC Application Management Suite 2.6.00 > BMC Release Lifecycle Management (License Add-on 4.6.00) and then expand BMC Release Process Management 4.6.00 to show its downloadable files.
Select the following link for download:
- BMC Release Process Management 4.6.00 Patch 1 Manual Upgrade
Click Download (FTP) or Download Manager:
- Download (FTP) places the selected items in an FTP directory, and the credentials and FTP instructions are sent to you in an email message.
- Download Manager enables you to download multiple files consecutively, and to resume an interrupted download if the connection drops.
  This method requires a one-time installation of the Akami NetSession client program on the target computer and is usually the faster and more reliable way to transfer files. A checksum operation is used to verify file integrity automatically.
Save the .war file to a temporary directory.

Upgrading BMC Release Process Management to version 4.6.00.01

Note

If your current BMC Release Process Management version is earlier than 4.6.00.00, upgrade to the major version 4.6.00.00, and then upgrade to version 4.6.00 Patch 1.

Log on as an administrator to the server that hosts the database and save a backup of the database before performing the upgrade.
Stop the BMC Release Process Management service for the current version.
Note
If you run several instances of BMC Release Process Management connected to the same database for load balancing and clustering purposes, also stop the BMC Release Process Management service for these instances.
On the command line, run the following command:
- (Windows) dir <RLM_HOME>\releases
- (Linux or Solaris ) cd <RLM_HOME>/releases
Note
Complete steps 3 through 13 on all the other hosts that are part of the cluster.
Create a directory with the following name: 4.6.00.01\RPM.
Copy the downloaded brpm.war file to the <RLM_HOME>\releases\4.6.00.01\RPM folder.
Extract the brpm.war file by using Java Archive Tool, UnZip, 7-Zip, or any other file extractor.
For example, for Java Archive tool, use the following command:
%JAVA_HOME%\bin\jar.exe -xvf <RLM_HOME>\releases\4.6.00.01\RPM\brpm.war
Copy the following configuration files from <RLM_HOME>\releases\4.6.00.00 <or your previous product version>\RPM\config to <RLM_HOME>\releases\4.6.00.01\RPM\config:
- database.yml
- automation_settings.rb
- smtp_settings.rb
- wicked_pdf_config.rb
- carrierwave_settings.rb
Go to <RLM_HOME>\releases\4.6.00.01\RPM\config, and then open the torquebox.yml file in a text editor.
For the stomp parameter, change the host value from localhost to the server IP address or the domain name of your current BMC Release Process Management server.
Note
You can copy the valid host value from the torquebox.yml file located in <RLM_HOME>\releases\<4.6.00>\RPM\config.
Save your changes to the torquebox.yml file.
Go to <RLM_HOME>\server\jboss\standalone\deployments and then open the RPM-knob.yml file in a text editor.
Change the application root from <RLM_HOME>\releases\4.6.00.00<or your previous product version>\RPM to <RLM_HOME>\releases\4.6.00.01\RPM.
Save your changes to the RPM-knob.yml file.
On the command line, navigate to <RLM_HOME>\bin and run the following executable file:
- (Windows) setenv.bat
- (UNIX) setenv.sh , using the . ./setenv.sh command
In the same command line window as the previous step, navigate to <RLM_HOME>\releases\4.6.00.01\RPM\config and run the following code:
jruby -S rake --verbose db:migrate RAILS_ENV=production
Start the BMC Release Process Management service.

After the upgrade

Refer to Additional actions after the patch upgrade for steps that you must complete, depending on the release from which you are upgrading.