BMC BladeLogic Client Automation - Change History
TKU February 2010
Modified the pattern to work correctly with version 7.5 of the product.
TKU March 2010
The following improvements were made for older product versions:
- File versioning is attempted from the properties.txt file and from the BCACInstalledConfiguration.xml file.
- For package versioning, the pattern checks additionally for "BMC CM Tuner".
- The pattern attempts to obtain port information from the properties.txt file and admin.properties file (on UNIX machines) and the BCACInstalledConfiguration.xml file.
- The pattern searches through additional locations for the map file.
- Depending on the product version, the pattern sets "BMC Configuration Management Tuner" SI type (for versions prior to 7.3) and "BMC BladeLogic Client Automation Tuner" SI type (in any other case).
- Improved error handling when dealing with non existent xpaths.
TKU May 2010
Improved search performance.
TKU July 2010
Improved performance.
TKU August 2010
Updated the pattern to prevent race conditions occurring when the Software Instance is searched for before it is added to the datastore.
TKU September 2010
Updated the links to remote Software Instances.
TKU March 2012
Updated the pattern to check that install_root
or workspace
are defined before use.
TKU June 2012
The following improvements were made:
- Added support for IPv6.
- Replaced the part of code with the
related_sis_search
function.
TKU July 2012
Fixed an issue with adding a list to the node set.
TKU November 2012
Updated the pattern to set a product version in a 3-level format.
TKU February 2013
Updated pattern to set type as "BMC Configuration Management Tuner" for versions prior to 7.3.
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.