Patch 2: version 4.4.00.02

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:

  • (US188330) You can now create new requests by cloning your existing requests without creating a request template. For more information, see Managing-requests.
  • (US189149) You can now set the automatically start requests at the specified date and time. For more information, see Managing-requests.

This patch contains various fixes to the BMC Release Package and Deployment product.

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 should 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 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 you want to see, per 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 (as described in the following sections), select the following links for download:
    • BMC Release Process Management 4.4.00 Patch 2 Manual Upgrade
    • BMC Varalogix Q Deployment Automation 4.4.00 Patch 2 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. Extract the contents of the .zip files that you downloaded and store them in a temporary directory.
    The patch includes the .war file for BMC Release Process Management and the .zip file for BMC Package and Deployment.

Upgrading BMC Release Process Management to 4.4.00.02

Note

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

  1. Log on as an administrator to the server that hosts the database, and save a backup of the database before performing the upgrade.
  2. Stop the BMC Release Process Management service for the current version.
  3. On the command line, run the following command: 
    • (Windows) dir <RLM_HOME>\releases
    • (Linux or Solaris ) cd <RLM_HOME>/releases
  4. Create a directory with the following name: 4.4.00.02\RPM. Copy the downloaded brpm.zip file to the <RLM_HOME>\releases\4.4.00.02\RPM folder.
  5. 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.02\RPM\brpm.zip
  6. Copy the following configuration files from <RLM_HOME>\releases\4.4.00.01\RPM\config to <RLM_HOME>\releases\4.4.00.02\RPM\config:
    • database.yml
    • automation_settings.rb
    • smtp_settings.rb
    • wicked_pdf_config.rb
    • carrierwave_settings.rb
  7. Go to <RLM_HOME>\releases\4.4.00.02\RPM\config, and then open the torquebox.yml file in a text editor.

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

  9. Save your changes to the torquebox.yml file.
  10. Go to <RLM_HOME>\server\jboss\standalone\deployments, and then open the RPM-knob.yml file in a text editor.
  11. Change the application root from <RLM_HOME>\releases\4.4.00.01<or your previous product version>\RPM to <RLM_HOME>\releases\4.4.00.02\RPM
  12. Save your changes to the RPM-knob.yml file.
  13. 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

  14. Go to <RLM_HOME>\releases\4.4.00.02\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
  15. Start the BMC Release Process Management service.

After the upgrade

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

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page:brpd44.Patch 2] could be found]. Click on this message for details.

Related topics

 Known and corrected issues for the BMC Release Lifecycle Management suite

 Known and corrected issues for BMC Release Process Management

 Known and corrected issues for BMC Release Package Deployment

 

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