Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Patch 1: version 4.4.00.01

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

Updates

This patch contains the following updates to the BMC Release Process Management product: 

  • (US180411) You can now add your own plugins written in Ruby to the BMC Release Process Management application. For more information, see Managing-plugins.
  • (US179336) You can now see the active and archived status for properties and when you access components with REST API. For more information, see REST-components.

Downloading the patch

Perform the following steps to download the patch:

  1. 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 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.

  2. Go to http://www.bmc.com/available/epd.html.
  3. At the logon prompt, enter your user ID and password, and then click Submit.
  4. On the Export Compliance and Access Terms page, provide the required information, agree to the terms of the agreements, and click Continue.
  5. If you are accessing this site for the first time, create an EPD profile to specify the languages and platforms that you want to see, by using the EPD site help; otherwise, skip to step 6.
  6. Verify that the correct profile is displayed for your download purpose, and select the Product Patches tab.
  7. Expand BMC Application Management Suite > BMC Application Management Suite 2.5.00 > BMC Release Lifecycle Management (Package and Deployment, Process Management, and Application Automation) 4.4.00 and then expand BMC Release Lifecycle Management 4.4.00 to show its downloadable files.
  8. For a manual upgrade, select the following link for download:
    • BMC Release Process Management 4.4.00 Patch 1 Manual Upgrade
  9. 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.
  10. Save the .zip file to a temporary directory.

Upgrading BMC Release Process Management to 4.4.00.01

Note

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

  1. As an administrator or root user, log on to the server that hosts the database
  2. Save a backup of the database before performing the upgrade.
  3. Stop the BMC Release Process Management service for the current version.
  4. From the command line, run the following command: 
    • (Windows) dir <RLM_HOME>\Releases
    • (Linux or Solaris ) cd <RLM_HOME>/Releases
  5. Create a directory with the following name: 4.4.00.01\RPM. Copy the downloaded brpm.war file to the <RLM_HOME>\Releases\4.4.00.01\RPM folder.
  6. Extract the brpm.zip 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.4.00.01\RPM\brpm.zip.
  7. Copy the following configuration files from <RLM_HOME>\releases\4.4.00.00\RPM\config to <RLM_HOME>\releases\4.4.00.01\RPM\config:
    • database.yml
    • automation_settings.rb
    • smtp_settings.rb
    • wicked_pdf_config.rb
    • carrierwave_settings.rb
  8. Go to <RLM_HOME>\releases\4.4.00.01\RPM\config, and then open the torquebox.yml file in a text editor.
  9. For the web parameter, change the context value to "/brpm".

  10. For the stomp parameter, change the host value from localhost to server IP address or 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.4.00>\RPM\config.

  11. Save your changes to the torquebox.yml file.
  12. Go to <RLM_HOME>\server\jboss\standalone\deployments, and then open the RPM-knob.yml file in a text editor.
  13. Change the application root from <RLM_HOME>\Releases\4.4.00.00\RPM to <RLM_HOME>\Releases\4.4.00.01\RPM
  14. Save your changes to the RPM-knob.yml file.
  15. Go to <RLM_HOME>\bin and run the following executable file:

    • (Windows) setenv.bat
      (UNIX) setenv.sh

      Note

      On UNIX, run the file with the following command:

      . ./setenv.sh

  16. Go to <RLM_HOME>\Releases\4.4.00.01\RPM\config and run the following code:

    jruby -S rake --verbose db:migrate

    Note

     See Specifying-the-product-environment-during-the-database-migration if the following error appears during rake task execution:

     rake aborted!database configuration does not specify adapter
  17. Start the BMC Release Process Management service.

After the upgrade

After you perform upgrade to BMC Release Process Management version 4.4.00.01, complete the necessary steps as described in Additional-actions-after-the-patch-upgrade.

Related topic

Known and corrected issues

 

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