Patch 12 for Service Pack 1: version 4.3.01.12

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 various fixes to the BMC Release Package and Deployment (formerly BMC VaraLogix Q Deployment Automation) product, and the following update:

You can now add the encrypted package property via the application programming interface (API). For more information, see Commands.

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 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.3.30 > BMC Release Lifecycle Management (Package and Deployment, Process Management, and Application Automation) 4.3.01 and then expand BMC Release Lifecycle Management 4.3.01 to show its downloadable files.

    Alternatively, you can access the patch download files from the Licensed Products tab:

    1. In the Filter Products field, enter BMC VaraLogix Q Deployment Automation to locate the product, and then click Go. The link to the product displays in the right pane.
    2. Click the BMC VaraLogix Q Deployment Automation link, and then click the Patches tab.
    3. Select the 4.3.01 version from the Version list, and click Go.
  8. For a manual upgrade (as described in the following sections), select the following link for download:
    •  VaraLogix Q Deployment Automation 4.3.01 Patch 12 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 content of the .zip files that you downloaded and store them in a temporary directory.
    The patch includes a .zip file for BMC VaraLogix Q Deployment Automation.

     

    Note

    If you want to apply the patch as a fresh product installation through an installation wizard (rather than perform a manual upgrades, as described in step 8 above), choose one of the following download links:

    • To install the BMC Release Lifecycle Management suite, including BMC Release Process Management and  BMC VaraLogix Q Deployment Automation, select the BMC Release Lifecycle Management 4.3.01 > BMC Release Lifecycle Management 4.3.01 Patch 12 link for the appropriate platform, either Windows or Linux.
    • To install just BMC VaraLogix Q Deployment Automation, expand BMC VaraLogix Q Deployment Automation (at the root level) and select the  BMC VaraLogix Q Deployment Automation 4.3.01 > BMC VaraLogix Q Deployment Automation 4.3.01  Patch 12 link for the appropriate platform, either Windows or Linux.

    After downloading and extracting, run the installer as described in Installing-Service-Pack-1.

Upgrading BMC Release Package and Deployment to 4.3.01.12

  1. Create a directory with an appropriate name. BMC recommends that you use the release name for the directory, for example <RLM_HOME>\releases\4.3.01.12\Q. 
  2. Stop the following services:
    • (Windows) Through the Services dialog box:
      • BMC Release Lifecycle Management - Apache
      • BMC Release Lifecycle Management - Engine
    • (UNIX) Through the command line, by going to <RLM_4.3.01_install_directory>/bin and running the following commands:
      • ./stopQEngine.sh
      • ./brlmapache stop
  3. Extract the contents from the BMC Release Package Deployment version 4.3.01.12 .zip file to a newly created folder (for example, Q).
  4. Copy the <RLM_HOME>\releases\<previous version>\Q\app\config\database.php file from the previous installation directory, or update the database.php file.

  5. Specify the path to PHP home and Oracle Instant Client directories in the system PATH property via environment variables or from the command line:

    • (Windows): set PATH=<RLM_4.3.01_install_directory>\lib\php;<RLM_4.3.01_install_directory>\lib\oracle-instant-client;%PATH%
    • (UNIX): export PATH=<RLM_4.3.01_install_directory>/lib/php/bin/:<RLM_4.3.01_install_directory>/lib/oracle-instant-client:$PATH

    Note

    Ensure that no other PHP locations are specified in the PATH variable. If other paths are specified, remove them before proceeding to the next steps.

  6. Go to the following directory:
    • (Windows): <RLM_4.3.01_install_directory>\releases\<version>\Q\
    • (UNIX): <RLM_4.3.01_install_directory>releases/<version>/Q/
  7. Execute the following command:
    • (Windows): run patch
    • (UNIX): ./run patch

  8. Execute the following command:

    • (Windows): run loadpacks
    • (UNIX): ./run loadpacks

    Note

    During the execution of the run loadpacks command, line by line enter the sequential numbers of packs which you want to install. Press ENTER after each line. When you are done, press Q. To select all of the packs, press A. To select none of the packs, press N.

    If you made any changes to the action scripts through the product user interface, those changes will not be overwritten by the scripts of the new patch.

  9. In <RLM_HOME>\apache-server\conf\httpd.conf file replace all the occurrences of 4.3.01.11 (or the directory, where the last version of BMC VaraLogix Q Deployment Automation sources is stored) by 4.3.01.12.

  10. Replace all the occurrences of 4.3.01.11 (or your product version) by 4.3.01.12 in the following files: 

    • (Windows):
      • <RLM_HOME>\bin\startQEngine.bat
    • (UNIX):

      • <RLM_HOME>/bin/startQEngine.sh
      • <RLM_HOME>/bin/stopQEngine.sh
  11. Start the following services:
    • (Windows) Through the Services dialog box:
      • BMC Release Lifecycle Management - Apache
      • BMC Release Lifecycle Management - Engine
    • (UNIX) Through the command line, by going to <RLM_4.3.01_install_directory>/bin and running the following commands:
      • ./startQEngine.sh
      • ./brlmapache start

  12. (Optional) If you use the BMC VaraLogix Q Deployment Automation API service, modify your service to run with the new location of the version 4.3.01.12 of source files:

    • (Windows):
      • On the command line, go to the API service installation directory (the default API service installation location is C:\Program Files (x86)\VaraLogix)
      • Run the following command: VAPIService -config -Home "<NEW_SOURCE_LOCATION>"
    • (UNIX):

      • In the text editor, open the /etc/init.d/qapid file.
      • Update the value of the Q_HOME variable to point to the new path of BMC VaraLogix Q Deployment Automation (for example, /opt/bmc/RLM/releases/4.3.01.12/Q).
  13. Close the browser that was used for accessing the previous version, clear your browser's cache, and then try accessing new version of BMC VaraLogix Q Deployment Automation. Verify that the new patch version is displayed on the version tooltip in the user interface.

Note

If the installation completed successfully, depending on your security settings, you may need to change the permission on the RLM_4.3.01_install_directory/releases/<version>/Q/app/tmp directory to 777.

Upgrading Deployment Engine only to 4.3.01.12

  1. Create a directory with an appropriate name. BMC recommends that you use the release name for the directory, for example <RLM_HOME>\releases\4.3.01.12\Q. 
  2. Stop the following service:
    • (Windows) Through the Services dialog box:
      • BMC Release Lifecycle Management - Engine
    • (UNIX) Through the command line, by going to <RLM_4.3.01_install_directory>/bin and running the following commands:
      • ./stopQEngine.sh
  3. Extract the contents from the BMC Release Package Deployment version 4.3.01.12 .zip file to a newly created folder (for example, Q).
  4. Copy the <RLM_HOME>\releases\<previous version>\Q\app\config\database.php file from the previous installation directory, or update the database.php file.

  5. Replace all the occurrences of 4.3.01.11 (or your product version) by 4.3.01.12 in the following files: 

    • (Windows):
      • <RLM_HOME>\bin\startQEngine.bat
    • (UNIX):

      • <RLM_HOME>/bin/startQEngine.sh
      • <RLM_HOME>/bin/stopQEngine.sh
  6. (Windows only): Add the USE_ZEND_ALLOC system variable:
    1. Go to Control Panel > System > Advanced System Settings.
    2. Click Environment Variables button
    3. Under System variables, click New.
    4. In the Variable name field, enter USE_ZEND_ALLOC
    5. In the Variable value field, enter '0' (the Zero symbol), and then click OK.
    6. Restart the computer.
  7. Start the following service:
    • (Windows) Through the Services dialog box:
      • BMC Release Lifecycle Management - Engine
    • (UNIX) Through the command line, by going to <RLM_4.3.01_install_directory>/bin and running the following commands:
      • ./startQEngine.sh

Related topic

Known-and-corrected-issues

 

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