Technology Knowledge Update 2015-Feb-1

BMC Atrium Discovery Technology Knowledge Update 2015-Feb-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 February 2015 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-Feb-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

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 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-02-1.xls

New Pattern Modules

Vendor

Product

Category

Platforms

Instances

Versioning

Product Page

Apache

Falcon

Process Automation Middleware

UNIX

Y

Y

Apache

Sqoop

Database Development and Management Tools

UNIX

Y

Y

Apache

Spark

End-User Query, Reporting, and Analysis

UNIX

Y

Y

Cloudera

Manager

Clustering and Availability Software

UNIX

Y

Y

Cloudera

CDH

Clustering and Availability Software

UNIX

Y

Y

Cloudera

Impala

End-User Query, Reporting, and Analysis

UNIX

Y

Y

Opensource

GitHub

Development Languages, Environments, and Tools

UNIX

Y

Y

Oracle

Communications Billing and Revenue Management

Data Integration and Access Software

UNIX

Y

Y

Apache

Pig

Data Integration and Access Software

UNIX

Y

Y

Oracle

Secure Global Desktop

Virtual User Interface Software

UNIX

Y

Y

BMC

Visualizer

Performance Management Software

Windows

Y

Y

Apache

Solr

Search and Discovery

Windows, UNIX

Y

Y

Enhanced Pattern Modules

 

RFE ref.

Product Page

Enhancement

SI Key Change

QM001871226

Updated trigger to make it effective for Windows 2003 and Windows 2008 deployments. Enhanced false positive check.

N

TKU-3274

Improved messaging.

N

QM001872453 (Esc 070392)

The pattern was enhanced to improve discovery of J2EE (EAR/WAR) applications.

N

Esc 069995

Minor improvements for supported versions.

N

QM001871979 (070227)

Enhanced the method for retrieving config file.

N

TKU-2238

Add agent_id attribute to the IBM Tivoli License Compliance Manager Agent SI

N

TKU-3194

Minor improvements.

N

TKU-3263

Updated privileged execution commands

N

TKU-3391

Minor improvements.

N

QM001871816,
 Esc 070019

Minor improvements for supported versions.

N

ESC 069989

Improved versioning.

N

TKU-3275

This pattern was updated with more known versions, improved product version extraction, new alternative trigger, and enhanced active versioning command.

N

TKU-2103

Improved model for the latest versions of BMC Batch Discovery.

N

TKU-2226

Updated trigger condition.

N

TKU-2077

Improved linking of IBM Tivoli Application Dependency Discovery Manager Server SI with the database.

N

TKU-2170

McAfee Common Management Agent SI type is updated to reflect the latest branding.

N

TKU-2229

Updated trigger condition.

N

-

Minor improvements.

N

-

Minor improvements.in known_versions attribute in metadata.

N

-

Minor improvements of products attribute in metadata.

N

-

Minor improvements of products attribute in metadata.

N

TKU-3433

Improved method for install_root extraction.

N

ISS04349428 (Esc 069110)

Improved method for install_root_extraction.

N

TKU-3338, TKU-3343

Minor improvements.

N

TKU-3262

Improved active versioning for correct processing of embedded Puppet deployment.

N

-

Minor improvements.

N

TKU-3207

Improved trigger condition.

N

-

Minor improvements.

N

-

Improved file versioning.

N

-

Added support for Oracle Forms on Weblogic 10g

N

-

Minor improvements.

N

Defects Resolved

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

 

 Defect No

Details 

Product Page

TKU-3211

Problem: The pattern could fail to create the Entrust GetAccess Software Instance due to the excessively strict false positive check.

Solution: Code fix.

QM001871090

Problem: BMC Visualizer is not discovered.

Solution: The pattern provided.

QM001870726

Problem: In certain cases, the pattern might not trigger.

Solution: Code fix.

QM001867996

Problem: In CMDB, the ITSM CI is completely disconnected from all relevant AR System CIs, because SoftwareComponents related to a second order SoftwareInstances are not synchronized to CMDB.

Solution: The pattern was updated and now creates a containment relationship between BMC Remedy IT Service Management Suite SI and SoftwareComponents it contains.

TKU-2379

Problem: Incorrect branding for SAP Business Explorer.

Solution: Code fix.

Esc 070157

Problem: Sometimes the WebSphere Aplication Server cell/node is not modeled correctly.

Solution: Code fix.

QM001872250 

Problem: See QM001872250.

Solution: Code fix.

TKU-3063

Problem: BMC Performance Assurance Agent Collector sometimes does not create necessary relationship to the related SIs.

Solution: Code fix.

TKU-2395

Problem: Borland CaliberRM SI might have incorrect SI type.

 Solution: Code fix.

TKU-2075 

Problem: IBM Rational Build Forge sometimes does not create necessary relationship to the database.

Solution: Code fix.

QM001870607

Problem: Progress OpenEdge gives insufficient information in product version.

Solution: Code fix.

TKU-2855

Problem: BMC Control-M SI might have incorrect key.

Solution: Code fix.

TKU-3252

Problem: IBM Business Process Center SI might have incorrect SI type.

Solution: Code fix.

TKU-3219

Problem: Incorrect branding for CA Access control.

Solution: Code fix.

TKU-3318

Problem: Docker pattern creates Detail nodes with inadequate short_names.

Solution: Code fix.

TKU-3344 

Problem: BEA AquaLogic Enterprise Security amd BEA WebLogic Integration patterns report incorrect product_version.

Solution: Code fix.

TKU-3301

Problem: Microsoft DNS Server reports incorrect product_version.

Solution: Code fix.

TKU-3208

Problem: Apache HTTPD-based Webservers Extended Discovery sometimes does not extract the server_root correctly.

Solution: Code fix.

TKU-2101

Problem: BMC Patrol Dashboard does not correctly report EOL data due to missing known versions and incorrect product version retrieval.

Solution: Code fix.

Esc 069611

Problem: The IBM InfoSphere Metadata Workbench and IBM InfoSphere QualityStage SI's are not created.

Solution: Code fix.

Esc 061570

Problem: Some hosts link to the Oracle cluster incorrectly.

Solution: Code fix.

 

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