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

BMC Atrium Discovery Technology Knowledge Update 2015-Mar-1 is a deliverable for BMC Atrium Discovery 9.0, 10.0 and 10.1 series.

A change to the way privileged execution configuration is handled in BMC Atrium Discovery

For a long time already, privilege command execution could be handled using the following methods:

  • through the BMC Atrium Discovery platform configuration - a recommended way described here.
  • using the pattern configuration files - an outdated way that will be eliminated in the nearest future.

In TKU December 2014 major steps have been taken to eliminate the possibility to manage privileged execution through pattern configuration. Further steps will be taken in 2015.

The latest 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 ImpactDirectionattribute 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-Mar-1 is released in three streams:

  • Release compatible with BMC Atrium Discovery 9.0 series
  • Release compatible with BMC Atrium Discovery 10.0 series
  • Release compatible with BMC Atrium Discovery 10.1 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 9.0 series - Installation and upgrade instructions are provided here
  • Atrium Discovery 10.0 series - Installation and upgrade instructions are provided here

  • Atrium Discovery 10.1 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-2015-03-1.xls

New Pattern Modules

VendorProductCategoryPlatformsInstancesVersioningProduct Page
ApacheTikaSearch and DiscoveryUnix, WindowsYYApache Tika
New RelicAPMTransaction Processing Monitors Unix, WindowsYYNew Relic APM
New RelicServersChange and Configuration Management SoftwareUnix, WindowsYYNew Relic Servers
PivotalGreenplum DatabaseRelational Database Management SystemsUnixYYGreenplum Database
opensourcememcachedOther Application Server MiddlewareUnixYYMemcached
ApacheHueWeb Analytics ApplicationsUnixYYApache Hue
AtlassianJiraTeam Collaborative ApplicationsUnix, WindowsYYAtlassian Jira
Symphony EYC

GAIA Application Server

Application Server Software Platforms

UnixYYSymphony EYC GAIA Application Server
OpensourceSensuChange and Configuration Management SoftwareUnixYYSensu
OpensourceRedisNonrelational Database Management SystemsUnixYYRedis
BMCTrueSight IT data AnalyticsEnd-User Query, Reporting, and AnalysisUnix, WindowsYYBMC TrueSight IT Data Analytics

Enhanced Pattern Modules

RFE ref.

Product Page

EnhancementSI Key Change


BMC Performance PerceiverImproved file versioning.N
TKU-2230IBM Tivoli Provisioning Manager
Improved trigger condition.N
TKU-2225IBM DB2 AlphabloxImproved trigger condition.N
TKU-2223IBM Tivoli Service Request ManagerImproved trigger condition.N
TKU-2233IBM Forms Server - Webform ServerImproved trigger condition.N
TKU-2227IBM Tivoli Change and Configuration Management DatabaseImproved trigger condition.N
QM001874492Oracle Business Transaction ManagementImproved file versioning.N

and CommonFunctions/J2EEInferredModel.tplpre

Improved jdbc resources extraction.


Apache HTTPD-based Webservers

Entrust GetAccess

Sun Java System Webserver

The pattern now discovers Entrust GetAccess deployed on Sun Java System Webserver.

QM001874586 (ESC 071378)CA Spectrum

The pattern was updated to support discovery of CA Spectrum deployed on Linux platform.

QM001875100IBM Tivoli License Compliance Manager

Improved versioning.


(Esc 069989)

Oracle Coherence

Improved versioning.

TKU-3620Pivotal RabbitMQ

Improved trigger condition.

TKU-3333Apache Solr

The pattern has been enhanced to model Apache Lucen as a software component of Apache Solr.


QM001874493 (Esc 070864)

Sun Java System Directory Server

The trigger condition was updated and additional false-positive check is now performed after the pattern triggers. These enhancements help to ensure that Sun LDAP software is identified correctly.

QM001875099BMC Analytics for BSMImproved versioning.N
TKU-2426Novell eDirectoryThe pattern was updated to discover the latest version of the Novell eDirectory product. New product name after the recent re-branding is NetIQ eDirectory.N
QM001872767Apache Derby RDBMSThe pattern was enhanced to better handle versioning for Apache Derby deployed on the consolidated hosts.N
QM001875625 (Esc 056176)Microsoft Internet Information Services - Extended Discovery

For ADDM and later, the pattern creates communication relationships links between the Website SoftwareComponent of IIS WebServer SoftwareInstance and the related RDBMS SI.

QM001876018Apache HTTPD-based WebserversImproved active and path versioning.N
QM001876075BMC Performance Manager
Improved versioning.
QM001874751TIBCO Enterprise Message Service
TIBCO BusinessWorks Engine
Improved versioning.N
QM001875176Apache Zookeeper

The Apache Zookeeper pattern was updated to avoid potential imcomplete modeling of Apache Zookeeper components.

QM001875511Oracle RDBMS

Improved versioning.




The pattern was enhanced to create a relationship between the Puppet SI and the memcached SI.


The pattern was enhanced to support Puppet Enterprise 3.7.2.


BMC TrueSight Capacity Optimization

The pattern was updated to reflect the recent re-branding in version 10.0.00, where BMC Capacity Optimization is now called BMC TrueSight Capacity Optimization.

TKU-3607Oracle E-Business Suite 

The pattern was enhanced to support Oracle E-business Suite 12.2 and later.

QM001871852Microsoft SQL Server - Database Detail Pattern

The pattern was enhanced and now creates the Database Detail nodes for databases even then no database size is reported.

TKU-3335Apache SolrThe Apache Solr pattern was enhanced to model the Apache SolrCloud SI.N
QM001876427Oracle ClusterwareMinor improvements.N

Defects Resolved

The following defects have been fixed in this BMC Atrium Discovery Technology Knowledge Update.

 Defect No


Product Page



Problem: The pattern execution might cause an ECA error.

Solution: Code fix.

Oracle Data Integrator

Problem: The pattern execution might cause an ECA error.

Solution: Code fix.

Red Hat JBoss Application Server

Problem: The pattern creates incorrect path to MANIFEST.MF file on Windows platforms which might cause versioning to fail.

Solution: Code fix as a part of enhancement QM001873937.

BMC Performance Perceiver
(Esc 071342)

Problem: The pattern might fail to obtain a Catalina Base directory.

Solution: Code fix.

Apache Tomcat

Problem: The pattern might create IBM Lotus Connections SI without sufficient evidence of the software presence on the host.

Solution: Code fix.

IBM Lotus Connections

(Esc 070780)

Problem: The pattern fails to identify the correct product version when more than one version of the Tibco packages are installed.

Solution: Code fix.

TIBCO Rendezvous

(Esc 071070)

Problem: The pattern might fail to properly discover database detail.

Solution: Code fix.

Sybase Adaptive Server Enterprise -- Old

Problem: The pattern fails to delete the Symantec VERITAS File System SI upon aging.

Solution: Code fix.

Symantec VERITAS Storage Foundation File System

Problem: On Windows platform, the pattern might not retrieve product version correctly.

Solution: Code fix.

BMC Performance Assurance Console


Problem: The pattern might fail to properly discover licensing detail.

Solution: Code fix.



Problem: The pattern execution might cause an ECA error.

Solution: Code fix.

Apache HTTPD-based Webservers

Problem: The pattern execution might cause an ECA error.

Solution: Code fix.

CA AutoSys Workload Automation

Problem: CMDB mapping for SYSTEMMANAGER relationships creates an impact loop which upsets BPPM.

Solution: Code fix.

Default CDM Mapping

Configuration upgrade

In this release the following patterns have the configuration block updated:

Updating to this TKU will reset any custom configuration for these products to the default values.

  • No labels