Patch 9 for Service Pack 1: version 4.3.01.09
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 Package Deployment (formerly BMC VaraLogix Q Deployment Automation) product:
- (US182475) During deployment performed via the BMC Release Package Deployment API console you can now select channels by adding the [-c <channel1> <channel2> <channeln>] parameters to the instance deploy command. For more information, see Commands.
- (US182466) You can now search for a specific instance, package, environment, repository, route, channel, channel template, or server via the BMC Release Package Deployment API console by using the argument name or the argument ID. For more information, see Commands.
Downloading the patch
Perform the following steps to download the patch:
Create a directory in which to place the downloaded files.
- Go to http://www.bmc.com/available/epd.html.
- At the logon prompt, enter your user ID and password, and click Submit.
- On the Export Compliance and Access Terms page, provide the required information, agree to the terms of the agreements, and click Continue.
- 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.
- Verify that the correct profile is displayed for your download purpose, and select the Product Patches tab.
- 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.
- For a manual upgrade (as described in the following sections), select the following link for download:
- VaraLogix Q Deployment Automation 4.3.01 Patch 9 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.
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.
Upgrading BMC Release Package and Deployment to 4.3.01.09
- 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.09\Q.
- 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
- (Windows) Through the Services dialog box:
- Extract the contents from the BMC Release Package Deployment version 4.3.01.09 .zip file to a newly created folder (for example, Q).
- Copy the <RLM_HOME>\releases\<previous version>\Q\app\config\database.php file from the previous installation directory, or update the database.php file.
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
- 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/
- Execute the following command:
- (Windows): run patch
- (UNIX): ./run patch
Execute the following command:
- (Windows): run loadpacks
- (UNIX): ./run loadpacks
- In <RLM_HOME>\apache-server\conf\httpd.conf file replace all the occurrences of 4.3.01.08 (or the directory, where the last version of BMC VaraLogix Q Deployment Automation sources is stored) by 4.3.01.09.
Replace all the occurrences of 4.3.01.08 (or your product version) by 4.3.01.09 in the following files:
- (Windows):
- <RLM_HOME>\bin\startQEngine.bat
- (UNIX):
- <RLM_HOME>/bin/startQEngine.sh
- <RLM_HOME>/bin/stopQEngine.sh
- (Windows):
- 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
- (Windows) Through the Services dialog box:
(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.09 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.09/Q).
- (Windows):
- 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.
Related topic