Skip to end of metadata
Go to start of metadata

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

The September 2014 TKU includes changes to the CMDB Sync mapping (introduced between TKU Mar 2014 and TKU Jul 2014)

  • When you synchronize with the CMDB the first time, the BMC_ComputerSystem CIs mapped from partition Host nodes are updated and their PartitionIds are set.
  • When you synchronize with the CMDB the first time, the BMC_ComputerSystem CIs mapped from Cisco Nexus NetworkDevice nodes are updated and their PartitionIds are set (data only discovered with ADDM 9.0 SP3).
  • 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-Sep-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

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

New Pattern Modules

VendorProductCategoryPlatformsInstancesVersioningProduct Page
TeradataAster DatabaseRelational Database Management SystemsUNIXYN

Teradata Aster Database

OracleCommunications Data ModelRelational Database Management SystemsUNIXYY

Oracle Communications Data Model

OracleReal Application TestingDatabase Development and Management ToolsUNIXYY

Oracle Real Application Testing

Puppet LabsPuppetChange and Configuration Management SoftwareUNIX, WindowsYY

Puppet Labs Puppet

OracleAirlines Data ModelRelational Database Management SystemsUNIXYY

Oracle Airlines Data Model

OracleRetail Data ModelRelational Database Management SystemsUNIXYY

Oracle Retail Data Model

TeradataViewpoint PortalAdvanced Analytics SoftwareUNIXYY

Teradata Viewpoint Portal

Open SourceJenkinsDevelopment Languages, Environments and ToolsUNIX, WindowsYY

Jenkins

SailpointIdentityIQIdentity and Access ManagementUNIX, WindowsYY

Sailpoint IdentityIQ

ApacheActiveMQApplication Server Software PlatformsUNIX, WindowsYY

Apache ActiveMQ

MicrosoftDHCP serverData Integration and Access SoftwareWindowsYY

Microsoft DHCP server

Enhanced Pattern Modules

 

RFE ref.Product PageEnhancementSI Key Change
QM001853407-Minor improvements to J2EEInferredModel pattern.N
Esc 062769

Microsoft Hyper-V Server

The pattern has been improved to better identify related UNIX virtual machines and the Microsoft Hyper-V server.N
QM001856957 (Esc 062310)

Microsoft Internet Information Services

The pattern now supports Microsoft Internet Information Services version 7.0, 7.5, 8.0, and 8.5.N
QM001857051 (Esc 062153)

J2EEInferredModel and RDBMS_Functions patterns were updated in perspective of Oracle WebLogic Server deep discovery.

Improved identification of databases hosted on the Oracle WebLogic Server.N
QM001789877

Oracle Application Server Extended Discovery

Added extended discovery of the Oracle Application Server.N
Idea 1574

Microsoft SQL Server

Discovery of Microsoft SQL Server 2000 Edition has been improved. The pattern now allows using an alternative database query versioning method.N
QM001857358

Oracle Clusterware

Cluster modeling has been improved in the Oracle Clusterware pattern. The cluster key has been enhanced.Y
Esc062112

Microsoft Windows PowerShell (BETA)

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
QM001858520

Oracle WebLogic Server

The path versioning has been improved in the Oracle WebLogic Server pattern.N
TKU-2355, TKU-2353

Apache Tomcat

The Apache Tomcat pattern has been updated with new attributes (listening_ports and short_name).N
QM001857216

Microsoft SQL Server

The Microsoft SQL Server pattern now discovers more versions of the Microsoft SQL Server (version table updated).N

Defects Resolved

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

 

Defect NoDetailsProduct Page
TKU-2361Problem: For IBM Tivoli Netcool/OMNIbus Software Instance, the link to the documentation does not work. Solution: Code fix.

IBM Tivoli Netcool-OMNIbus

TKU-2310Problem: The pattern did not recognize a new product name introduced in version 5.5 and higher (Embarcadero DB Change Manager). Solution: Code fix.

Embarcadero Change Manager

TKU-2312Problem: The pattern did not support Embarcadero Performance Center version 2.7.3. Solution: Code fix.

Embarcadero Performance Center

TKU-2311, TKU-2309Problem: The Embarcadero DBArtisan pattern reported incorrectly a product version for Embarcadero DBArtisan version 8.7 and later. Solution: Code fix.

Embarcadero DBArtisan

TKU-2309Problem: The Embarcadero DBArtisan pattern reported incorrectly a product version for Embarcadero DBArtisan version 8.7 and later. Solution: Code fix.

Embarcadero Change Manager

TKU-2328Problem: The pattern creates SoftwareInstances with incorrect type. Solution: Code fix.

CA Software Change Manager

TKU-2213Problem: The pattern reported incorrectly a product version for IBM WebSphere Enterprise Service Bus major versions. Solution: Code fix.

IBM WebSphere Enterprise Service Bus

TKU-2373, Esc062112Problem: The Microsoft Windows PowerShell pattern creates SoftwareInstance instead of RuntimeEnvironment node. Solution: Code fix. Note: The RuntimeEnvironment is created even when the Microsoft Windows PowerShell is not running during scan.

Microsoft Windows PowerShell

TKU-2333Problem: The BMC Patrol Agent pattern does not set instance for Patrol KM SoftwareComponents. Solution: Code fix.

BMC Patrol Agent

TKU-2356Problem: IBM Rational Asset Analyzer pattern fails to correctly expand install_root. Solution: Code fix.

IBM Rational Asset Analyzer

TKU-2357Problem: The pattern failed to correctly parse license detail nodes (TKU-2357). Solution: Code fix.

IBM Rational Performance Tester

TKU-2341Problem: BMC Batch Impact Manager searches a file that contains version in the wrong location. Solution: Code fix.

BMC Control-M Batch Impact Manager

QM001857184Problem: The Oracle Traffic Director pattern does not trigger in some circumstances. Solution: Code fix.

Oracle Traffic Director

QM001857233 (Esc 062654)Problem: File versioning could fail on UNIX, if the log file was in an alternative location. The Sybase Adaptive Server Enterprise pattern could fail retrieving a version from a log file, if the file was not available in the default location. Solution: Code fix. Alternative method of log information retrieval added.

Sybase Adaptive Server Enterprise

TKU-2315Problem: The IBM Cognos PowerPlay pattern did not support the new product name introduced in version 8.4 (IBM Cognos Business Intelligence PowerPlay). Solution: Code fix.

IBM Cognos PowerPlay

TKU-2349Problem: The IBM DB2 RDBMS pattern does not parse license file correctly. Solution: Code fix.

IBM DB2 RDBMS

TKU-2303Problem: The Autonomy IDOL pattern did not support the new product name introduced in version 10.0 (HP Autonomy IDOL). New versions are now supported (10.3 and 10.5) Solution: Code fix.

Autonomy IDOL

TKU-2362Problem: IBM Tivoli Netcool/Webtop pattern extracts build from version incorrectly. Solution: Code fix.

IBM Tivoli Netcool Webtop

TKU-2358Problem: IBM Tivoli CAM for SOA Platforms fails to create Communication relationship with IBM Tivoli Enterprise Monitoring Server on Windows. Solution: Code fix.

IBM Tivoli CAM for SOA Platform

TKU-2131Problem: The IBM Alphablox pattern fails to correctly identify cell name on WebSphere Application Server. Solution: Code fix.

IBM DB2 Alphablox

TKU-2314Problem: HP Openview Performance Insight has incorrect si_type (HP OVPI instead of the HP OpenView Performance Insight). Solution: Code fix.

HP Openview Performance Insight

TKU-2115Problem: BMC Impact Manager package versioning was corrected. Solution: Code fix.

BMC Impact Manager

QM001856706 (Esc 062306/062249)Problem: TIBCO Rendezvous ECA Error Solution: Code fix.

TIBCO Rendezvous

  • No labels

2 Comments

  1. Unknown User (petrus.johansson@ikea.com)

    Sorry to say, the Apache Tomcat pattern does not discover the instance name and I could not see any code for this in the Sept TKU pattern. Can someone please fix this?

    1. Thank you, Petrus, this is fixed now.