Page tree
Skip to end of metadata
Go to start of metadata

BMC Atrium Discovery Technology Knowledge Update 2014-Oct-1 is a deliverable for BMC Atrium Discovery 8.3, 9.0 and 10.0 series.

The October 2014 TKU includes changes to the CMDB Sync mapping (introduced in TKU Jul 2014)

  • You can enable BMC Atrium Discovery to set the impact attributes directly, rather than relying on Atrium CMDB’s impact normalization rules. Relationships in Atrium CMDB are marked as being “impactful” by setting the HasImpact attribute to Yes and the ImpactDirection attribute to a suitable value. This new data model will become the default in future releases of BMC Atrium Discovery. To enable HasImpact population and the new data model:

    • In Atrium CMDB, in the Normalization Console Configuration Editor, disable Impact Normalization for the ADDM dataset.

    • On the BMC Atrium Discovery command line, run the following command: tw_options CMDB_SYNC_DATAMODEL=6. Restart tideway services for the change to be taken into account.

  •   You can start using simple static application modeling.
    BMC Atrium Discovery enables you define dynamic automatically-updating application models, using Collaborative Application Mapping and related features. That leads to robust comprehensive application models, but it does require time to investigate the application and define a suitable set of patterns. In some circumstances it is useful simply to manually group some hosts or software instances together to create a “static” application model. Such models are of course not automatically updated, but they are extremely quick and easy to define.
    To define a static application model, add Hosts or SoftwareInstances to a group in BMC Atrium Discovery, and give the group a name that starts with “StaticApp:”, in exactly that form. Do not use sub-groups. That causes the creation of a BMC_Application CI in Atrium CMDB, named after the group. For example, a group named “StaticApp: Example Application” results in a BMC_Application CI with name “Example Application”.

Changes to Oracle Database modeling

  • To support multitenancy introduced in Oracle 12c, the changes to modeling Database Details has been introduced: all the Database Details, like Schemas and Tables, are now linked to the logical databases instead of the Database Software Instance. For versions earlier that Oracle 12c, and for the root database in Oracle 12c and later, the Database Details are also linked to the Software Instance.

  • The old model, where the Database Details are only linked directly to the Software Instances, is outdated.

Release Compatibility

TKU 2014-Oct-1 is released in three streams:

  • Release compatible with BMC Atrium Discovery 8.3 series
  • Release compatible with BMC Atrium Discovery 9.0 series
  • Release compatible with BMC Atrium Discovery 10.0 series


Customers can access this TKU release from the BMC Electronic Product Distribution Website. If you are a customer or partner and do not already have a login please contact your BMC account manager.

Check out this demo if you are unsure how to download from BMC EPD site


The release comprises components packaged as two entities:

  • BMC Atrium Discovery Extended Data Pack, which is a separately licensable product.
    • Product Lifecycle - Patterns that populate Atrium Discovery with information about End-of-Life, End-of-Support, and End-of-Extended-Support for versions of certain host Operating Systems as well as versions of certain software products
    • Hardware Reference Data - Patterns and data import CSV file that populate Atrium Discovery with power and heat consumption figures for various hosts.

Installation and Upgrade

  • Atrium Discovery 8.3 series - Installation and upgrade instructions are provided here
  • Atrium Discovery 9.0 series - Installation and upgrade instructions are provided here
  • Atrium Discovery 10.0 series - Installation and upgrade instructions are provided here

A matrix covering ALL commands executed and ALL files retrieved by the patterns is available to our customers from the BMC Electronic Product Distribution Website. The filename is TKU_Command_File_Matrix-2014-10-1.xls

New Pattern Modules

VendorProductCategoryPlatformsInstancesVersioningProduct Page
MemSQLMemSQLRelational Database Management SystemsUNIXYY


OpenLDAPOpenLDAPIdentity and Access ManagementUNIX, WindowsYY


SaltStackSaltChange and Configuration Management SoftwareUNIXYY

SaltStack Salt

DockerDockerVirtual Machine SoftwareUNIXYY


OpscodeChefSoftware Configuration Management ToolsUNIXYY

Opscode Chef

MicrosoftMessage QueuingEvent-Driven MiddlewareWindowsYY

Microsoft Message Queuing

PivotalRabbitMQEvent-Driven MiddlewareUNIX, WindowsYY

Pivotal RabbitMQ

IBMTivoli Access Manager WebSEALData Integration and Access SoftwareUNIX, WindowsYY

IBM Tivoli Access Manager WebSEAL

Enhanced Pattern Modules

RFE ref.Product PageEnhancementSI Key Change

BMC Remedy AR System

The BMC Remedy AR System Server versioning is improved: active versioning is now a primary versioning method, registry versioning is not used any more.N

Microsoft Windows PowerShell

The Microsoft Windows PowerShell pattern has been improved and creates a RuntimeEnvironment node even when the Microsoft Windows PowerShell is not running during scan.N

CA Directory

The CA Directory pattern now supports discovery of the CA Directory deployed on a UNIX platform. Version 12.0 is now supported.N
QM001860126 Esc 063823 Esc 063812 ISS04362449

Oracle WebLogic Server

The Oracle WebLogic Server pattern was updated with more suitable trigger for discovering instances running as a Windows service. Server name attribute extraction method has been also improved.N

Oracle Hyperion Financial Reporting

The Oracle Hyperion Financial Reporting pattern has improved trigger mechanism with improved discovery of the legacy system version.N

IBM Tivoli Storage Manager

The IBM Tivoli Storage Manager pattern now supports package versioning for HP-UX deployments of IBM Tivoli Storage Manager Client.N

Red Hat JBoss Application Server

The pattern was improved to identify the Red Hat JBoss Application Server edition.N

Oracle Automatic Storage Management

Trigger condition has been update in the Oracle Automatic Storage Management pattern.N

Oracle Coherence

A minor issue related to path truncation has been fixed in the Oracle Coherence pattern.N

Adobe Connect

Simple identification mapping has been improved for Adobe Connect.N

Microsoft Hyper-V Server

The Microsoft Hyper-V pattern was updated to support versions 2012 and 2012 R2.N

HP Performance Agent

The product version identification was improved for HP Performance Agent.N

HP Operations Manager

The product version identification was improved for HP Operations Manager.N

Nginx Webserver

The Nginx Webserver pattern was updated to support the latest versions: 1.4, 1.5 Release 1, 1.5 Release 2, 1.5 Release 3, 1.5 Release 4, and 1.6.N

Sybase Adaptive Server Enterprise

Minor issue related to the install root truncation has been fixed.N

Defects Resolved

The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2014-Oct-1

Defect NoDetailsProduct Page
QM001860176Problem: In some circumstances the Apache Tomcat pattern failed with ECA error. Solution: Code fix.

Apache Tomcat

QM001860805Problem: The Red Hat KVM pattern requires enhancement to treat the wrong UUID format correctly. Solution: Code fix.

Red Hat KVM

TKU-2406Problem: In some circumstances the Oracle Enterprise Single Sign-On pattern failed with ECA error. Solution: Code fix.

Oracle Enterprise Single Sign-On

TKU-1847Problem:The Software Instance type was updated to reflect the recent changes for HP Performance Agent (from HP OpenView Performance Agent to HP Performance Agent). Solution: Code fix.

HP Performance Agent

TKU-2394Problem:IBM LotusConnections pattern creates Software Instances with incorrect branding for modern versions. Solution: Code fix. 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.

IBM Lotus Connections

TKU-2320Problem:The pattern does not account for a recent changes in IBM FileNet Business Process Manager naming. IBM FileNet Business Process Manager has been renamed to IBM Case Foundation. Version 5.2 is now supported and an IBM Case Foundation Content Platform Engine Software Instance is modeled for this version. Solution: Code fix.

IBM FileNet Business Process Manager

TKU-2367Problem:The BMC CONTROL-M pattern populated tw_meta_data_attrs with unnecessary information. Solution: Code fix.


TKU-2299Problem:IBM Rational Jazz Server pattern created a jazz_home attribute even when the value was not discovered. Solution: Code fix.

IBM Rational Jazz Server

TKU-2313Problem: The HP Discovery and Dependency Mapping pattern generates a Software Instance with incorrect type. Solution: Code fix. The SI type is now HP Discovery and Dependency Mapping Inventory.

HP Discovery and Dependency Mapping

TKU-2307Problem: The BMC Performace Analyzer for Servers pattern could retrieve more information on the product version. Solution: Code fix. Increased depth of product version discovery.

BMC Performance Analyzer for Servers

TKU-2324Problem: The IBM InfoShpere Data Event Publisher pattern created Software Instances with incorrect type for IBM WebSphere Data Event Publisher version 9.59 and earlier. Solution: Code fix.

IBM InfoSphere Data Event Publisher

TKU-2345Problem: The HP Data Protector pattern sometimes created a Software Instance with insufficient evidence. Solution: Code fix.

HP Data Protector

TKU-2411Problem: The BMC FootPrints Service Core pattern created a Software Instance when a Tomcat was running on the same host with any BMC product. Solution: Code fix.

BMC FootPrints Service Core

TKU-2266Problem: The Adobe Livecycle pattern used vague conditions for relationship creation with a web application server. Solution: Code fix.

Adobe LiveCycle

TKU-2351Problem: The IBM DB2 Connect pattern was updated with improved file versioning and a new path versioning method. Solution: Code fix.

IBM DB2 Connect

TKU-2392Problem: The Oracle Connection Manager pattern retrieved incorrect product version. Solution: Code fix.

Oracle Connection Manager

TKU-2393Problem: The IBM FileNet Image Import pattern generated a non-informative key. Solution: Code fix.

IBM FileNet Image Import

TKU-2385Problem: The Oracle Secure Enterprise Search pattern did not discover some Oracle Secure Enterprise Search versions. Solution: Code fix.

Oracle Secure Enterprise Search

TKU-2329Problem: The Oracle Enterprise Service Bus pattern reported incorrect version of the Oracle Enterprise Service Bus. Solution: Code fix.

Oracle Enterprise Service Bus

TKU-2327Problem: The IBM Records Manager pattern used non-valid Software Instance type for newer versions (IBM FileNet Records Manager for v5.1 and later). Solution: Code fix.

IBM Enterprise Records

TKU-2366Problem: The BMC BladeLogic Database Automation pattern was updated with improved method for PostgreSQL Database Server software instance identification. Solution: Code fix.

BMC BladeLogic Database Automation

  • No labels