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

BMC Atrium Discovery Technology Knowledge Update 2014-Dec-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 December 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 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-Dec-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-2014-12-1.xls

New Pattern Modules

VendorProductCategoryPlatformsInstancesVersioningProduct Page
OracleLoader for HadoopData Integration and Access SoftwareUNIXYY

Oracle Loader for Hadoop

IBMEndpoint ManagerChange and Configuration Management SoftwareWindows, UNIXYYIBM Endpoint Manager
BMCCONTROL-M for HadoopWorkload Scheduling and Automation SoftwareUNIXYYBMC CONTROL-M for Hadoop
ApacheChukwaAdvanced Analytics SoftwareUNIXYYApache Chukwa
ApacheFlumeOther System SoftwareUNIXYY

Apache Flume

OracleFormsOther Development and Deployment SoftwareWindows, UNIXYYOracle Forms
OracleSQL Connector for HDFS SoftwareData Integration and Access SoftwareUNIXYYOracle SQL Connector for HDFS

Enhanced Pattern Modules

RFE ref.Product PageEnhancementSI Key Change
QM001865450 (Esc 065280)Oracle WebLogic ServerImproved path versioning to retrieve the product version for BEA WebLogic Application Server SIs.N
QM001865923 (Esc 064904,
Esc 066008)
Sybase Adaptive Server Enterprise -- OldModified regex to extract installation root containing /sybase from -e option in argsN
QM001861696 (Esc 065914)Oracle CoherenceImproved coherence home extraction.N
QM001864243 (Esc 066950) Microsoft Dynamics CRMAdded alternative configdb registry key to obtain database information.N
QM001866884IBM DB2 RDBMS

The pattern now obtains protocols information from active versioning.

N
QM001866145Microsoft Exchange Server

Added support for situation where powershell command returns details of multiple DAGs.

N
QM001865820IBM DB2 RDBMSThe pattern has been enhanced to retrieve extra information from active versioning.N
QM001866950Veritas NetBackup

The pattern was updated with:

  • improved,more granular file versioning, and
  • default netbackup_home path (C:\Program Files\Veritas\).
N
QM001865781 Fulfilled request to add Hardware Reference Data to the listed hardware.N
QM001866805
(Esc 067066) 

Symantec VERITAS Storage Foundation File System

The pattern now supports "kcmodule -a" (introduced HP-UX 11i v2) as alternative to the obsolete "kmadmin -s".

N
QM001865450
(Esc 065280)
Oracle WebLogic ServerImproved path versioning.N
Esc 066552IBM Tivoli Netcool-Impact

Updated trigger process to support modern versions. An attempt is now made to initially retrieve Impact installation home from NCHOME environment variable.
Updated parsing of output from nci_server command.

N
QM001866327
(Esc 066719)
Oracle RDBMS

The pattern was improved to handle the following situation: "User doesn't have enough privilege to perform the operation". Privileged execution of crs_stat -v is now performed where user doesn't have enough privilege to perform such operation.

N
QM001864736 (Esc 065746)BMC Patrol AgentThe pattern uses updated default UNIX path.N
Idea 5537 Informatica PowerCenter

The Informatica PowerCenter discovery has been enhanced. The SI key now contains information about domains.infra file used as a source.

 The SI name now contains the information about domains.

Install root retrieval has been enhanced.

The pattern now builds communication relationships with the related processes.

 Y

Defects Resolved

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

Defect NoDetailsProduct Page
QM001864923

Problem: The pattern fails when a resources candidate path begins with "." symbol.

Solution: Code fix.

IBM WebSphere Application Server
QM001863909

Problem: A conflict between the IBM Hardware and Oracle Clusterware patterns result in the following situation: IBM HostContainer is created and immediately deleted.

Solution: Code fix.

Oracle Clusterware
QM001865432

Problem: IBM Business Process Manager pattern needs to be updated to identify both process server and process center, as well as the correct versions. 

Solution: Code fix.

IBM Business Process Manager
  • No labels