In TKU June 2008 the pattern module was updated to include the following changes:
Pattern added to enable identification and versioning of Tideway Foundation Lifecycle Management
The key used for Foundation components is now composed of 'type' and 'host.key' rather than 'name' and 'host.key'. The reason for the change is that 'name' also contains the hostname of the host being scanned and using the hostname as part of the SI key is against best practice recommendations.
Regular expressions used when matching processes that trigger Foundation component patterns were improved slightly
The pattern now links the BAI to the SIs on the basis of version as well as SI type.
In TKU November 2008 the pattern module was updated to include the following changes:
With the release of Tideway Foundation 7.1.6, each of the main components making up Tideway Foundation were given a watchdog process with the same name as the trigger process. To prevent each of the six patterns triggering twice - once on the child and once on the parent, code has been added to terminate a pattern if it triggers on a child process rather than its parent.
In TKU February 2010 the pattern module was updated to include the following changes:
With the release of BMC Atrium Discovery and Dependency Mapping 8.1,two additional patterns have been added - Report Service and SQL Provider Service.
Also a check has been added to assign the appropriate SI type to the product based on its version. All versions above 8.0 have their SI type set to BMC Atrium Discovery and Dependency Mapping <Component Name> .
In TKU March 2010 the Foundation/ADDM BAI pattern was updated to create a BAI key that is not affected by version changes, preventing duplicate BAIs being created if the product was updated and then re-scanned.
In TKU October 2010 two updates were made:
In TKU February 2010 the pattern module FoundationSecurity and FoundationAppliance were updated to add known Versions of BMC Atrium Discovery and Dependency Mapping.(bug #15405)
In TKU July 2012 the following changes were made:
In TKU October 2012 ADDM_BAI pattern changed to create SI instead of BAI.
In TKU July 2013 FoundationSecurity pattern functionality was extended to retrieve ADDM configuration. New versioning method was added. Cluster attributes are now populated as well as Consolidation/Scanning Appliance details. Relationship links are created between the ADDM components.
In TKU August 2013 the expected results from the identify_host function was changed from list to string. In addition, the SI type is now set to the modern name for the product if version is not known.
In TKU September 2013 format of related_rdbms_sis_search() function was updated
In TKU April 2014 consolidation and scanning appliances details extraction and link management were updated. Also we have updated search for the related Proxy SIs.
In TKU June 2014 "proxy_name" attribute had been changed to "instance".
In TKU August 2014, the pattern was updated to model additional attributes for the Software Instance:
In TKU February 2016, the pattern was updated to implement such changes:
In TKU October 2016, the pattern was updated to implement such changes:
In TKU April 2019 the following changes were made:
In TKU March 2020 publisher and product attribute were added.