IBM WebSphere MQ - Change History

TKU November 2008

Added the capability to display the queue in the Software Instance.

TKU December 2008

Resolved an issue related to the package name regular expressions that led to incorrectly discovered versions.

TKU November 2010

Added active versioning for legacy versions of the product.

TKU February 2011

Verified a new version of IBM WebSphere MQ and added it to the list of known versions.

TKU May 2011

Added a new pattern for the IBM WebSphere MQ Client.

TKU August 2011

Changed the name of the attribute "queue" to "queue_manager".

TKU August 2014

The following improvements were made:

• Added support for versions 7.1.0, 7.5, and 8.0.
• Added new attributes:
  • listening_ports
    
  • expected_ports
• Added additional attributes:
  • install_root
  • member_of_clusters
• Substituted the queue_manager attribute with an instance attribute.

TKU April 2015

The following improvements were made:

• Resolved an issue with the failing identification of the install_root value (QM001876126).
• Resolved an issue with incomplete information about running instances (QM001873032).

TKU November 2016

Resolved an issue with model.host() (DRDC1-7213).

TKU June 2017

Extended the pattern with a new regex to not run PRIV_RUN if the regular command returns a correct output (DRDC1-8896).

TKU September 2017

The following improvements were made:

• Updated code for hosting_node identification.
• Deprecated privilege command execution configuration through the pattern configuration block. A recommended method is the BMC Atrium Discovery platform configuration.

TKU April 2019

Updated the pattern to use runCommand functions.

TKU July 2019

Commands escaped to enable a space in the install_root path (DRDC1-13345).

TKU March 2021

Added a new SI type for installations with no active queues (DRDC1-14962).

TKU April 2022

Added the  _runmqsc_path attribute to the IBM WebSphere MQ Series Queue Manager SoftwareInstance. This attribute is only populated if we successfully run the runmqsc command. Hence, the Extended Discovery pattern will only trigger if it knows it can run runmqsc.

TKU October 2022

Enhanced the setting of the _runmqsc_path attribute by the execution of the runmqsc command. Hence, the extended pattern will execute even if the queue manager is not clustered (DRDC1-19674).