CA

Unicenter DSM

Change and Configuration Software

UNIX, Windows

Y

Y

CA.Unicenter.DSM

CA

NSM

Performance Management Software

UNIX, Windows

Y

Y

CA.Unicenter.NSM

HP

Application Security Center - Web Inspect

Security and Vulnerability Management Software

Windows

Y

Y

HP.ApplicationSecurityCenter.WebInspect

HP

Discovery Dependency Mapping

Change and Configuration Software

Windows

Y

Y

HP.DiscoveryDependencyMapping

IBM

General Parallel File System (GPFS)

File System Software

UNIX, Windows

N

Y

IBM.GeneralParallelFileSystem

IBM

InfoSphere Information Analyzer

End-User Query, Reporting, and Analysis

UNIX, Windows

Y

Y

IBM.InfoSphereInformationAnalyzer

IBM

Tivoli OMEGAMON

Event Automation Tools

UNIX, Windows

Y

Y

IBM.TivoliOMEGAMON

IBM

PureEdge Webform Server

Software Construction Components

Windows

Y

Y

IBM.PureEdge.WebForm.Server

IBM

Tivoli Data Warehouse

Relational Database Management Systems

UNIX, Windows

Y

Y

IBM.TivoliDataWarehouse

IBM

Tivoli Netcool Security Manager

Identity and Access Management

UNIX

Y

Y

IBM.Tivoli.NetcoolSecurityManager

IBM

WebSphere Transformation Extender

Integration Server Software Platforms

UNIX, Windows

Y

Y

IBM.WebSphere.TransformationExtender

Microsoft

Commerce Server

Order Management

Windows

Y

Y

Microsoft.CommerceServer

Microsoft

System Center Data Protection Manager

Data Protection and Recovery Software

Windows

Y

Y

Microsoft.SystemCenterDataProtectionManager

Microsoft

Office Groove Server

Integrated Collaborative Environments

Windows

Y

Y

Microsoft.OfficeGroove

Microsoft

PerformancePoint Server

End User, Query, and Reporting Analysis

Windows

Y

Y

Microsoft.PerformancePointServer

Oracle

Financial Services

Sevices Operations Management - Finance

UNIX

Y

Y

Oracle.FinancialServices

Oracle

Vantive

Customer Relationship Management

UNIX, Windows

Y

N

Oracle.Vantive

CA

Software Change Manager

Agent pattern trigger made a bit less specific based on customer feedback, but code added to ensure that cross-matching would not lead to an increase in number of SIs created.

N

CA.SoftwareChangeManager

IBM

WebSphere Application Server

Application Server pattern: Added another method to extract product version and edition - if XPath method fails, regular expression parsing is used. Node Agent pattern: Added support for Windows platform Deployment Manager pattern: Added support for Windows platform

N

IBM.WebSphereApplicationServer

IBM

WebSphere Application Server

Additional patterns added to link the Node Agent with its managed Application Server in deployments of WebSphere Application Server Network Deployment edition. Additional patterns added to link the Deployment Manager with its managed Node Agents in deployments of WebSphere Application Server Network Deployment edition.

N

IBM.WebSphere.ApplicationServer.NetworkDeployment

VMware

ESX Server

ESX Server v4 (vSphere 4) introduces tools to obtain license information via a command-line interface. The ESX Server pattern checks for presence of the command-line tool (/usr/bin/vmware-vim-cmd) and if the Foundation user is running with elevated privileges ('priv_execution' configuration option is set to 'true' and 'PRIV_RUNCMD' function has been defined in Foundation Discovery configuration), the pattern will run the command and parse the license information. Additionally, the pattern will no longer erroneously create a Software Instance on hosts where VMware Server 2.x is running. VMware Server 2.x introduced a number of changes in its architecture and now a process that is used by the ESX Server pattern as the trigger is also found in VMware Server 2.x installations. The ESX Server pattern now ensures that the host it has triggered on is actually an ESX Server host before continuing.

N

VMwareVM

VMware

Virtual Machine Software

Additional information (value of 'guestOS' attribute) is parsed from the .vmx file for each VM. This information is stored as 'vm_guest_os' attribute on the VMware VM Software Instance.

N

VMwareVM

N/A

12155

Trigger for the ContentEngineServer pattern in IBM FileNet Content Manager module re-written to follow best-practice guidelines

IBM.FileNetContentManager

21837

12156

Problem: In certain cases, where licensing information has changed, the Symantec VERITAS Storage Foundation for Windows pattern could fail with ECA Engine error. Solution: Code fix in node maintenance code.

Symantec.VERITAS.StorageFoundationWindows

N/A

12159

HyperVConsolidateFromVirtualHost pattern (Microsoft Hyper V module) trigger improved. Now ensures that the Host node it has triggered on has 'serial' attribute set, making the pattern potentially a bit more efficient.

Microsoft.HyperV_Server

N/A

12167

ITMEnterpriseMonitoringServer and ITMEnterprisePortalServer patterns in IBM Tivoli Monitoring module will ensure that they continue only if it is IBM Tivoli Monitoring and not IBM Tivoli OMEGAMON installed.

IBM.TivoliMonitoring

N/A

12171

A minor issue with the algorithm used to link the BEA AquaLogic BPM SI to its related database has been found and fixed. The issue is unlikely to have has much effect in the past, as it was in the backup method and would only result in the failure to create a relationship and no other problems.

BEA.AquaLogic.BPM

21874

12174

Problem: Relationships between SupportDetail nodes and Host nodes (or SoftwareInstance nodes) would stay in place if the Host/SI node attributes related to product lifecycle changed but the product lifecycle patterns do not contain the data to create a mapping to a new SupportDetail node. E.g. Solaris 8 host upgraded to Solaris 10. Sun Microsystems have so far not published the End of Support dates for Solaris 10, hence SupportDetails nodes do not exist for Solaris 10. The host running Solaris 10 now is still linked to Solaris 8 Support Details node. Solution: Code fix to ensure that relationships are correctly maintained in these situations.

All Software and OS Lifecycle patterns

N/A

12184

Execution of BMC Patrol 'pconfig.exe' command in PatrolAgent pattern is now user configurable and disabled by default as the execution of this command is often not allowed in production environment since it presents a potential security risk. NOTE: If this command is not executed, the pattern may not locate related BMC Performance Manager RTServers

BMC.PatrolAgent

21586

12218

Problem: Apache Tomcat pattern uses as part of its key the command-line path and arguments (passed through an MD5 hash) to ensure that unique instances of the application server have been identified. A change in the command-line arguments is regarded as a change in the instance which would create a new SI while the original SI starts ageing. A recent change in a customer's environment where an additional command-line argument has been added has meant that new SI is created every time a Tomcat server has been restarted (and the old SI starting to age out of the model) leading to an unexpected increase in Apache Tomcat SIs.

Solution: New algorithm has been implemented to create the SI key. The SI is now created using the following criteria:

• If 'catalina_base' has been parsed from the process arguments, a grouped SI is created for each instance of Apache Tomcat.
• If 'catalina_base' has not been obtained and 'catalina_home' has been parsed from the process arguments, a grouped SI is created for each installation of Apache Tomcat.
• If neither 'catalina_base' nor 'catalina_home' has been obtained, then a grouped SI is created using the process command and 'classpath' (if available). A hash of this string is used as the group in the grouped key.

This approach makes the model both more accurate as well as making the SI key less susceptible to minor changes in the trigger process args.

The pattern has had its major version number incremented due to the changes to how the key is generated.

ApacheFoundation.Tomcat

21586

12219

Problem: Red Hat JBoss Rules pattern uses as part of its key the command-line path and arguments (passed through an MD5 hash) to ensure that unique installations of the libraries have been identified. A change in the command-line arguments is regarded as a change in the Software Instance which would create a new SI while the original SI starts ageing. A recent change in a customer's environment where an additional command-line argument has been added has meant that new SI is created every time an application server using these libraries has been restarted (and the old SI starting to age out of the model) leading to an unexpected increase in Red Hat JBoss Rules SIs.

Solution: New algorithm has been implemented to create the SI key group. The SI key group is now generated using the following criteria:

• If the path to the JBoss Rules library (i.e. drools-core<n>.jar) is obtained from the command-line args, then this is used as the grouping mechanism to create Software Instances grouped by installation
• If the path to the JBoss Rules library has not been obtained, then the grouping mechanism is a combination of the process command and the 'classpath' from the trigger process. The string created has a hash applied to it to prevent the key from becoming very long. Grouping by installation is again achieved.

The pattern major version has been incremented since the mechanism for SI key creation has been updated.

RedHat.JBossRules

21586

12230

Problem: Red Hat Hibernate patterns use as part of their key the command-line path and arguments (passed through an MD5 hash) to ensure that unique installations of the libraries have been identified. A change in the command-line arguments is regarded as a change in the Software Instance which would create a new SI while the original SI starts ageing. A recent change in a customer's environment where an additional command-line argument has been added has meant that new SI is created every time an application server using these libraries has been restarted (and the old SI starting to age out of the model) leading to an unexpected increase in Red Hat Hibernate SIs.

Solution: New algorithm has been implemented to create the SI key group. The SI key group is now generated using the following criteria:

• If the path to the Hibernate core library or Hibernate Annotations library or Hibernate Entity Manager library (respectively) is obtained from the command-line args, then this is used as the grouping mechanism to create Software Instances grouped by installation
• If the path to the library has not been obtained, then the grouping mechanism is a combination of the process command and the 'classpath' from the trigger process. The string created has a hash applied to it to prevent the key from becoming very long. Grouping by installation is again achieved.

The pattern major version has been incremented since the mechanism for SI key creation has been updated.

RedHat.Hibernate

21586

12248

Problem: BEA AquaLogic Enterprise Security pattern uses as part of its key the command-line path and arguments (passed through an MD5 hash) to ensure that unique installations of the product have been identified. A change in the command-line arguments is regarded as a change in the instance which would create a new SI while the original SI starts ageing. A recent change in a customer's environment where an additional command-line argument has been added has meant that new SI is created every time the WebLogic server running this product has been restarted (and the old SI starting to age out of the model) leading to an unexpected increase in BEA AquaLogic Enterprise Security SIs.

Solution: AquaLogic Enterprise Security pattern has been updated to improve the SI model generated.
 The key for the SI is now created using the following criteria:

• If the path to the product configuration properties file (WLESarme.properties) has been parsed from process arguments, then the key is based on this path combined with the path of the trigger process
• If the path to the product configuration properties file has not been obtained, the key is based on path to the trigger process combined with the classpath obtained from the trigger process args.The string created has a hash applied to it to prevent the key from becoming very long.

• Type and Host key are added to the final SI key.

These changes ensure that the SI key is much less susceptible to minor changes in the trigger process args.

The pattern major version has been incremented due to changes to the SI key creation.

BEA.AquaLogic.EnterpriseSecurity