In TKU Feb 2010 Product modelling was redesigned: added functionality to extract a license information from database, information about installed applications into server; functionality to create relationships with other Remedy AR System components: Flashboard, Mid-Tier; added assotiation to "armonitor" process. Also System Second-Order SI and Flashboard were created.
In TKU March a major bug was fixed, which prevented from the correct running of Server pattern when a Database query was encountered.
After the fix, the pattern runs correctly.
In TKU August 2010 there were some slight changes to prevent race conditions that could occur when the Software Instance was searched for before it was added to the datastore
Additionally, the patterns that execute 'reg query' command on the Windows hosts no longer use 'cmd /c' to execute it, but do so directly as use of 'cmd /c' is not required.
Also, Server name added to Software instance name attribute.
In TKU September 2010 the AR Server pattern was updated to improve parsing of database instance information for Microsoft SQL Server, as well as a fix being applied to the code block that creates the communication relationships between the AR Server SI and DB server SI.
In TKU November 2010 the Mid Tier pattern was updated. Triggered attribute was changed. Additionally the pattern was optimized.
From TKU December 2010 the database queries are only run if the relevant option is set in the pattern configuration. By default this option is enabled
In TKU January 2011 the Remedy AR System pattern now supports querying Microsoft SQL Server and Oracle Database Server on a specific IP address and port, if this kind of configuration (IP address and port) has been discovered by the core MS SQL or Oracle DB Server patterns.
In TKU February 2011 the MidTier pattern was changed from using a key group of install root to a key of install root, type and host key.
In TKU March 2011 the MidTier pattern was changed to trigger on 'Apache Tomcat Application Server' and 'RedHat JBoss Application Server' SI. Previously the pattern used to trigger on 'BMC Remedy AR System Server' SI. With these changes the relationships are also modified to create dependency relationship with triggering SI and communication relationship with configured AR Servers.
In TKU April 2011 AR Server pattern was modified to extract related RDBMS details from either 'ardb.cfg'file (in case of remote DB location) or 'ar.cfg'file (in case of local database). Registry version was corrected to support instance, specific for the triggering process. server_nameis currently extracted from 'ar.cfg' file as well. Some small optimization enhancements were additionally done.
Furthermore, an issue was resolved in the AR System pattern that would lead to the pattern exiting with an ECA Engine error (due to an incorrectly initialized hash table) if the list of applications was obtained via a database query.
In TKU June 2011 way the AR Server pattern creates link with related RDBMS was modified. Also installation directory extraction regexes were updated. Configuration file name was updated either.
Other change in TKU Jun 2011 File versioning for AR Server version 7.1 is now supported (RFE QM001702506).
In TKU July 2011 way the AR Server pattern creates link with related RDBMS was slightly updated. Now the pattern processes default database name for MS SQL correctly.
Other major change in TKU July 2011 is modeling of BMC AR Server Group. BMC Remedy AR System SI can now also be modeled as BMC AR Server Group with containment of members of Group which are AR Servers and Database Server with which they are communicating.
In TKU August 2011 the AR Server pattern has been modified to properly link MSSQL Oracle RDBMS instances. The key, based on installation directory was fixed.
In TKU September 2011 the AR Server pattern has been modified to properly destroy obsolete links with the related Oracle RDBMS instances. AR System pattern had been updated to manage links with the contained SIs.
In TKU October 2011 the datastore search calls made in the pattern module have been reviewed and their efficiency improved where appropriate
In TKU November 2011 some additional attributes were removed from Server pattern, db_name attribute was added. System pattern was updated to fix issue with database queries, when AR Server SI was not providing necessary DB details.
In TKU January 2012 the Server pattern was updated to support Oracle clusters. The search for a Microsoft SQL Server database was modified to search for a DatabaseDetail node attached to the Microsoft SQL Server SI.
In TKU April 2012 several updates were included in the pattern module. For Server pattern server_name extraction from ARSystemInstalledConfiguration.xml file was abandoned as this file does not reflect changes of server name. Oracle SQL query for System pattern was updated as column names for this type of database differ from other AR System database types. MidTier pattern now supports WebLogic Application Server. File versioning in Flashboards pattern was switched to active method of versioning.
In In TKU May 2012 configuration file extraction for JBoss Application Server in MidTier pattern has been fixed. The issue with incorrect version number extraction had been fixed for Flashboards pattern.
In TKU August 2012 fixed issue with incorrect DB Server linking when there are several Microsoft SQL Servers on the host with the same database name.
In TKU October 2012 regex for server_name extraction was updated. Applications running within AR System are now represented as SoftwareComponent nodes to assist in Collaborative Application Mapping.
In TKU March 2013 the System and MidTier patterns triggers were updated to make them more strict.
In TKU May 2013 BMC Remedy AR Server pattern was enhanced. Added support for relationship creation with MS SQL Server when DB name is not specified in AR Server configuration
In TKU July 2013 the alternate method of obtaining configuration file name was added into MidTier pattern.
In TKU August 2013 additional application GUIDs were added to the table that maps these to installed Remedy applications allowing for creation of Software Component nodes representing these (if discovered).
In TKU September 2013 Oracle RDBMS linking code was updated. Now AR Server pattern searches for the related Oracle instances by service_name, Oracle Active DataGuard configuration is now also supported.
In TKU November 2013 related database name was added into the BMC Remedy AR System SI key and Oracle search queries were updated to support multiple service_names
In TKU December 2013 various regular expressions no longer match on commented-out lines in configuration files.
In TKU February 2014 Remedy Mid-Tier pattern was enhanced through addition of an additional file versioning approach for installations running on Apache Tomcat, as well as through addition of package versioning when running on the Windows platform (QM001813443)
In TKU June 2014 the alternate validation approach has been added for MidTier pattern to detect the component within a non-default Apache Tomcat installation (QM001829182).
In TKU October 2014, the BMC Remedy AR System Server versioning is improved: active versioning as now a primary versioning method, registry versioning is not used any more (QM001859037).
In TKU September 2015 a link between Remedy Mid-Tier and related Atrium SSO instance is supported.
In TKU January 2016 trigger for Server pattern was updated.
TKU April 2016
Inqueries to Oracle DB were updated (DRDC1-4759)
In TKU June 2016 the pattern was updated with the following changes:
In TKU September 2016 new Common Functions were implemented into the pattern. 'System' pattern now properly detects RDBMS Server instance to run SQL queries if it resides behind the Load Balancer.
In TKU June 2017 trigger for MidTier pattern was updated.
In TKU July 2017 Smart Reporting pattern was updated with fixes for Unix platforms. It is now bound to the related host.
In TKU September 2017 the following changes were made :
In TKU January 2019 package versioning was updated, success_login_cred value for Oracle RDBMS related databases changed to success_login_credential.
In TKU February 2019 linking between Oracle Database and Remedy AR was updated.
In TKU April 2019 the following changes were made: