IBM WebSphere MQ - Change History
2008
TKU November 2008
In November TKU we enhanced the IBM WebSphere MQ pattern, and added the capability to display the queue in the Software Instance. This produces more simplicity in identifying the queue related to the SI. It is still possible to report on that attribute as well.
TKU December 2008
In December TKU we resolved a minor issue in the IBM WebSphere MQ where certain characters in the package name regular expressions were not correctly escaped which could lead to version not being extracted.
Characters in regular expressions are now correctly escaped.
2010 - 2014
TKU November 2010
In TKU November 2010 active versioning for legacy versions of the product was added (full details are in the main documentation
TKU February 2011
In TKU February 2011 new version of IBM WebSphere MQ was verified and added to list of known versions.
TKU May 2011
In TKU May 2011 new pattern for IBM WebSphere MQ Client was added.
TKU August 2011
In TKU August 2011 changed name of attribute "queue" to "queue_manager".
TKU August 2014
In TKU August 2011, the following changes occurred:
- the pattern now supports new versions 7.1.0, 7.5, and 8.0,
- new attributes added:
- listening_ports
- expected_ports
- listening_ports
- added additional attributes:
- install_root
- member_of_clusters
- queue_manager attribute was substituted with instance attribute
2015 - 2019
TKU April 2015
In TKU April 2015 the pattern was updated with the following changes:
- The following problem was resolved: The pattern might fail to identify the install_root value.(QM001876126)
- The following problem was resolved: The pattern might fail to retrieve complete information about running instances.(QM001873032)
TKU November 2016
In TKU Nov 2015 usage of model.host() was replaced as the SI can be run on Cluster(DRDC1-7213).
TKU June 2017
In TKU Jun 2017 Extended discovery pattern was slightly updated with new regex to not run PRIV_RUN if regular command returned correct output (DRDC1-8896).
TKU September 2017
In TKU Jun 2017 updated code for hosting_node identification
- Privilege command execution configuration using the pattern configuration block has been deprecated. A recommended method through the BMC Atrium Discovery platform configuration is described here.
TKU April 2019
In TKU April 2019 the following changes were made:
- Pattern runCommands updated.
TKU July 2019
In TKU July 2019 the following changes were made:
- Commands escaped to allow space in install_root path (DRDC1-13345)
2020 - present
TKU March 2021
In TKU March 2021 the following changes were made:
- Added new SI type for installations with no active queues (DRDC1-14962)
TKU April 2022
In TKU April 2022 we added the _runmqsc_path attribute to the IBM WebSphere MQ Series Queue Manager SoftwareInstance. This attribute will only be populated if we successfully run the runmqsc command. It means the Extended Discovery pattern will only trigger if it knows it can run runmqsc.
TKU October 2022
In TKU October 2022, the setting of the _runmqsc_path attribute by the execution of the runmqsc command was corrected so as to enable the extended pattern to execute even if the queue manager is not clustered (DRDC1-19674)
Comments
Log in or register to comment.