IBM Rational ClearCase - Change History
TKU July 2008
The following improvements were made:
- Resolved an issue that prevented the trigger's execution even if a ClearCase Location Broker SI was created for a scanned host.
- Resolved issues that occured if versioning was attempted by using Windows Registry.
TKU September 2008
Improved the capabilities of the Location Broker pattern so that it can retrieve licensing data for IBM Rational ClearCase. By executing an active command, the pattern can now retrieve and store data about maximum licenses, active users, available licenses, and hostname of the License Server. This data is available in the UI and in reports.
TKU February 2009
Resolved an issue that prevented attempting to view the Software Instance node of the Location Broker.
TKU September 2011
The following improvements were made:
- Default UNIX and Windows installation paths can now be set and enabled for use in file versioning through a new Configuration section.
- If the Location Broker trigger process on the Windows platform is not fully qualified, an attempt is made to extract such information from Windows Services.
- Added an alternative Windows registry entry to support a 32-bit installation on a 64-bit edition of Windows.
- Added the WMI Query versioning method to the Location Broker, VOB server, and View Server patterns.
- Optimized the code to extract a version and edition out of package information.
- Added known versions.
TKU August 2013
Updated the ClearCase pattern to create the IBM Rational ClearCase Server SI only when a VOB Server and/or View Server SI is present on the server.
TKU April 2019 and TKU July 2019
Updated the pattern to use runCommand functions.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*