Technology Knowledge Update 2014-Jan-1


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

The January 2014 TKU includes changes to the CMDB Sync mapping

  • During data synchronization to the CMDB, FunctionalComponent nodes representing CAM Functional Components are mapped to BMC_ConcreteCollection CIs.
  • When you synchronize with the CMDB the first time, the BMC_ComputerSystem CIs mapped from HostContainer nodes are updated and their TokenIds are set.
  • When you synchronize with the CMDB the first time, all BMC_ApplicationService CIs are updated and their TokenIds are set.

Release Compatibility

TKU 2014-Jan-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 (ships with this release)

Download

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

Contents

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.00 - Installation and upgrade instructions are provided here
  • Atrium Discovery 9.0.00 - 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-01-1.xls

In this Release

New Pattern Modules

Vendor

Product

Category

Platforms

Instances

Versioning

Product Page

Apache

Hadoop

Clustering and Availability Software

UNIX

Y

Y

BMC

Middleware Management - Performance and Availability

Process Automation Middleware

UNIX/Windows

Y

Y

IBM

Tivoli Monitoring for Virtual Environments

Transaction Processing Monitors

UNIX/Windows

Y

Y

Enhanced Pattern Modules

RFE ref.

Product

Enhancement

SI Key Change

Product Page

QM001804892

Apache Tomcat

Apache Tomcat pattern enhanced to improve discovery on Microsoft Windows platform. Furthermore, file versioning approach improved slightly

N

QM001806214

BMC CONTROL-M

BMC CONTROL-M/Agent pattern registry versioning enhanced through inclusion of additional registry keys.

N

QM001809731

IBM Tivoli Monitoring

Patterns in IBM Tivoli Monitoring module enhanced through addition of active versioning.

N

QM001812140

Apache Tomcat

Apache Tomcat pattern updated with an improvement to active versioning approach on the UNIX platforms.

N

QM001812568

Microsoft System Center Configuration Manager

Microsoft System Center Configuration Manager pattern enhanced with alternate package name regex to be able to handle new versions of product.

N

QM001813091

Adobe ColdFusion

Adobe ColdFusion patterns were significantly updated to add support for v10 of the product. This has necessitated some changes to the model created and an update to the SI key.

Y

#TKU-2048

Microsoft Exchange Server

Microsoft Exchange Server pattern trigger improved with additional trigger condition.

N

#TKU-2052

OS Support Details

OS Support Details for Red Hat Enterprise Linux 5.x and 6.x updated

N/A

#TKU-2070

IBM InfoSphere Replication Server

IBM InfoSphere Replication Server pattern updated to use correct SI type for legacy versions.

N

-

IBM Tivoli CAM for SOA Platform

Patterns enhanced with an improved active versioning approach.

N

-

IBM Tivoli CAM for Transactions\\ IBM Tivoli Data Warehouse

Patterns enhanced with addtion of active versioning approach.

N

Atrium Discovery System patterns\\

FunctionalComponent nodes representing CAM Functional Components are mapped to BMC_ConcreteCollection

Defects Resolved

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

Defect No

Details

Product Page

QM001808424

Problem: Not able to discover Microsoft Exchange Server Cluster. Exchange 2013 pattern does not identify all servers. Specifically, it does not identify the "client access" server (CAS role). Solution: Code update. Pattern has been split into two to obtain Database Availability Groups variant on installation.

#TKU-1507

Problem: BMC ProactiveNet Analytics Server pattern code to create Detail nodes for each installed monitor merges information from multiple monitors with similar name into a single Detail node due to the way it parses output of the command that provides listing of installed monitors. Solution: Code fix. Parsing of the output improved. Furthermore, Detail nodes are no longer created by default as this could lead to performance degradation due to potentially a very high number of nodes being created. List of installed monitors is stored as an attribute on the SI instead.

#TKU-1558

Problem: IBM Rational Software Analyzer Server pattern has a weak trigger condition. Solution: Code fix. Trigger condition improved.

#TKU-2025

Problem: IBM Domino Server pattern for Windows platform should set 'install_dir' attribute on the created SI to support discovery of IBM Lotus Quickr. Solution: Code fix.

#TKU-2034

Problem: Microsoft Lync Server Application Components are currently modelled as software instances but should be modelled as software components. Solution: Pattern updated.

#TKU-2045

An issue with the code to create a relationship between Oracle Business Process Management SI and related software instances was resolved.

Problem: CMDB sync patterns that map some Atrium Discovery node attributes to Atrium CMDB CI sometimes does not set unique enough values for ADDM RE Identification Rules to identify these. This regularly ends up in Duplicated CIs problems for BMC_ComputerSystem CIs mapped from HostContainer nodes. Solution: TokenId is now populated for these CIs with unique enough values.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*