Technology Knowledge Update 2015-Jan-1

BMC Atrium Discovery Technology Knowledge Update 2015-Jan-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 and TKU January 2015 major steps have been taken to eliminate the possibility to manage privileged execution through pattern configuration. Further steps will be taken in the following releases.

The January 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 2015-Jan-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-01-1.xls

New Pattern Modules

Vendor

Product

Category

Platforms

Instances

Versioning

Product Page

Oracle

Enterprise Data Quality

Automated Software Quality Tools

Windows, Unix

Y

Y

Oracle

WebCenter Suite Plus

Modeling and Architecture Tools

Windows, Unix

Y

Y

Oracle

Developer Suite

Modeling and Architecture Tools

Windows, Unix

Y

Y

Apache

Oozie

Process Automation Middleware

Windows, Unix

Y

Y

Entrust

GetAcess

Identity and Access Management

Windows, Unix

Y

Y

Oracle

Service Architecture Leveraging Tuxedo

Other Application Server Middleware

Windows, Unix

Y

Y

Enhanced Pattern Modules

 

RFE ref.

Product Page

Enhancement

SI Key Change

QM001866049

New product support added.

-

QM001866950  (Esc 067940) 

Improved version handling to take into account service packs and patches.

-

TKU-2909, TKU-2907, TKU-2908

 

 

 

  • added support for Symantec NetBackup v7.6 version.
  • added edition attribute to SoftwareInstance to distinguish Standard and Enterprise editions (TKU-2907, TKU-2908)
  • removed priv_function and priv_execution options from the configuration block.
  • improved process to obtain license name.
  • improved license key extraction process (on UNIX platform it runs in a privileged mode as required).
  • added licensing detail node to discover the following licensing options (TKU-2909):
    • Symantec NetBackup SAP Agent,
    • Symantec NetBackup Option NDMP,
    • Symantec NetBackup Data Protection Optimization Option,
    • Symantec NetBackup Enterprise Disk,
    • Symantec NetBackup Library Based Tape Drive, and
    • Symantec NetBackup Platform Base Complete. 

-

QM001866140

Updated trigger process to discover Symantec NetBackup v6.5.6  on Linux and Solaris servers.

-

 TKU-2906

Added edition attribute to the Symantec VERITAS Storage Foundation SI.

-

QM001865270

Enabled discovery of CA Access Control on Windows hosts.

-

QM001866818 (Esc 065294)

Minor enhancements related to TIBCO_home retrieval.

-

QM001865424

Added privileged execution to CA Directory discovery on Unix hosts.

-

QM001863392 (Esc 065696)

Added support for several minor Microsoft SQL Server versions.

-

Esc 064912

  • Improved versioning.
  • Added support for v9.5
  • Added support for new product braning (CA APM Introscope).

-

TKU-2262

Improved method for distinguishing the type of data collector (IBM Tivoli CAM Data Collector for WebSphere or IBM Tivoli CAM Data Collector for J2EE).

-

-

Added support for "A10 Networks" Load Balancer discovery.

-

TKU-2235

Trigger was updated to cover all possible cases of IBM WebSphere Extended Deployment.

 The pattern was improved to ensure that the information necessary for SI modeling is available.

-

 

Defects Resolved

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

Defect No

Details

Product Page

TKU-2127

Problem: Incorrect version format.

Solution: Code fix.

QM001857838

Problem: IBM Tivoli Asset Discovery for Distributed Server that might replace the IBM Tivoli License Compliance Manager is not supported.

 Solution: The pattern was updated to:

  • support new versions of an agent
  • create relationship to the alternative server component - an IBM Tivoli Asset Discovery for Distributed Server software instance

QM001857838

Problem: IBM Tivoli Asset Discovery for Distributed Server that might replace the IBM License Metric Tool is not supported.

Solution: The pattern was updated to discover a IBM Tivoli Asset Discovery for Distributed Server software instance, and create peer-to-peer relationship with Tivoli Integrated Portal SI.

QM001867324 (Esc 068173) 

Problem: ECA error might happen, as the pattern does not handle error messages in the file that is being parsed.

Solution: Code fix.

QM001867327 (Esc 068173)

Problem: ECA error might happen, as the pattern does not handle the missing value properly.

Solution: Code fix.

QM001868637 (Esc 068752)

Problem: Added support for several Microsoft SQL Server versions.

Solution: Code fix.

TKU-2330

Problem: Incorrect use of version format for earlier releases.

Solution: Code fix.

TKU-2360

Problem: IBM Tivoli Enterprise Monitoring Server currently creates a Containment relationship based on peer to peer communication between the IBM Tivoli Monitoring Enterprise Portal Server SI and  IBM Tivoli Enterprise Monitoring Server instead of using client/server relationship as an evidence.

Solution: Code fix.

TKU-2250

Problem: Misleading information about known versions.

Solution: Code fix.

Esc 064904

Problem: Sybase ASE pattern includes information about obsolete databases.

Solution: Code fix.

QM001856886 (Esc 062310)

Problem: CA Workload Automation pattern requires trigger improvement to enable discovery of the CA Autosys R11 agent.

Solution: Code fix.

Esc 068488

Problem: Improved versioning for the CA SiteMinder Policy Agent SI.

Solution: Code fix.

QM001869958 (Esc 066000)

Problem: The pattern cannot obtain version information for iPlanet Webserver and Sun ONE/Sun Java System Webserver.

Solution: Code fix.

TKU-2434

Problem: The "spindle name" was used for identifying disks on VMAX-1SE

Resolution: Fixed in the code. The product now relates on the ‘Disk ID’.

 

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