IBM Lotus Connections - Change History - Documentation for BMC Discovery content reference
Daniel Davis 
TKU October 2010
In TKU October 2010 IBM Lotus Connections pattern was updated to support Unix platform.
TKU November 2010
In TKU November 2010 an optimization was added to the pattern so that if on a UNIX/Linux host being discovered, the pattern was triggered by an IBM WebSphere Application Server process that was spawned by another WebSphere Application Server process (one parent process spawning many child processes), the pattern realizes this and stops in order to prevent the same code being executed for each child process.
TKU February 2012
In TKU February 2012 instead of jave process the pattern now triggers on created and confirmed IBM WebSphere Application Server SoftwareInstance.
TKU June 2012
In TKU June 2012 the false positive check has been improved and obsolete SI management has been added. Key of the SI has been updated as well.
TKU April 2013
In TKU April 2013 there was a slight tightening of the trigger process
TKU August 2014
In TKU August 2014 the pattern was updated to support alternative possible registry.xml file location.
TKU October 2014
In TKU October 2014, the pattern was updated to support versions 3.0, 4.5, and 5.0. For versions 4.5 and 5.0 the Software Instance type was updated to IBM Connections. An alternative file versioning method was introduced on Windows platforms.
TKU April 2019 & TKU July 2019
In TKU April 2019 and TKU July 2019 the pattern runCommands were updated
[Go Back To Product Page | IBM Lotus Connections]
