BMC Performance Manager Portal - Change History

TKU June 2008

Updated both patterns in the Performance Manager Portal module to explicitly validate that their trigger processes belong to BMC Performance Manager Portal.

• Console Server:
  • Process is owned by the username that matches the following regular expression: '(?i)patrol' OR
  • Trigger process command-line matches one of the following regular expressions: '(?i)\bbmc' or '(?i)\bpatrol'

• RT Server:
  • Process is owned by the username that matches the following regular expression: '(?i)patrol' OR
  • Trigger process command-line matches the following regular expression: '(?i)\bbmc'

If the validation fails, the pattern is not executed.

TKU May 2010

Enhanced the search for the RT Server host based on an IP address (which enables the pattern to create the relationship between the Performance Manager Portal SI and RT Server SI).

TKU September 2010

Enhanced the search for the RT Server host based on an IP address (which enables the pattern to create the relationship between the Performance Manager Portal SI and RT Server SI).

TKU March 2012

Updated the RTserver pattern to trigger on rtserver64.exe on the Windows platform.

TKU May 2012

Updated the Console Server to use a common function to link to remote BMC Performance Manager Portal RTserver Software Instances.

TKU August 2013

The following improvements were made:

• Set the product version to return three levels.
• Tidied up and updated the code based on the best practice guidelines.
• Added additional metadata known versions.

TKU April 2014

The following improvements were made:

• Updated known versions info in metadata.
• Added a pattern for BMC Performance Manager Portal.

TKU Nov 2014

The following improvements were made to the BMC Performance Manager Portal pattern:

• Added false positive check.
• Improved path versioning.
• Improved handling of the relative path for the Console Server.
• Added active versioning for Unix platforms.

TKU June 2016

Added error checking.