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


BMC Atrium Discovery Technology Knowledge Update 2010-Mar-1 is a deliverable for the Tideway Foundation platform version 7.2 and later as well as BMC Atrium Discovery version 8.0 and 8.1.

Release Compatibility

TKU 2010-Mar-1 is released in three streams:

  • Release compatible with Tideway Foundation 7.2 (subset - does not contain patterns which require TWF 7.3)
  • Release compatible with Tideway Foundation 7.3 and BMC Atrium Discovery 8.0
  • Release compatible with BMC Atrium Discovery 8.1

Note

TKU March (TKU 2010-Mar-1) is not compatible with nor supported on versions of Tideway Foundation before v7.2

Download

Customers can access this TKU release from either the BMC Electronic Product Distribution Website or the Tideway Downloads site (Download Area->latesttku). If you're 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 of four components packaged as two licensable entities:

  • BMC Atrium Discovery Technology Knowledge Update
    • Core - Patterns that model various software products
    • Database detail - Patterns that extend some of the core database patterns to obtain additional detailed information about certain databases
  • BMC Atrium Discovery Extended Data Pack
    • 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.

To see some of the highlights of this release visit the March In The Spotlight Page

Installation and Upgrade

  • Foundation 7.2/7.3 and Atrium Discovery 8.0 - Installation and upgrade instructions are provided here
  • Atrium Discovery 8.1 - 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 as part of the TKU download

Technology Knowledge Update

New Software Instance Patterns

Vendor Product Category Platforms Instances Versioning Module
Ab Initio Graphical Development Environment Data, Access, Analysis, and Delivery Software Windows Y Y

AbInitio.GDE

BMC BladeLogic Server Automation Suite Change and Configuration Software UNIX, Windows Y Y

BMC.BladeLogic.ServerAutomationSuite

BMC Corporate Directory Manager Identity and Access Management Windows Y Y

BMC.CorporateDirectoryManager

BMC Recovery Manager Data Protection and Recovery Software UNIX, Windows Y Y

BMC.RecoveryManager

BMC PATROL DashBoard Network Management Software UNIX, Windows Y Y

BMC.PATROL_DashBoard

Microsoft Office Project Portfolio Server Project and Portfolio Management Windows Y Y

Microsoft.OfficeProjectPortfolioServer

Microsoft ProClarity Analytics Server Content Management Windows Y Y

Microsoft.ProClarityAnalyticsServer

SAP BusinessObjects Data Integrator End-User Query, Reporting, and Analysis UNIX, Windows Y Y

SAP.BusinessObjects.DataIntegrator

Symantec VERITAS Configuration Manager Change and Configuration Software UNIX, Windows Y Y

Symantec.VERITASConfigurationManager

Enhanced Software Instance Patterns

Vendor Product Enhancement SI Key Change Pattern Module
BEA WebLogic Application Server Pattern enhanced to determine whether the discovered Application Server is an administration server, and if it is to obtain JMX port information (can be used for deeper J2EE discovery in the future). JMX port information added as an attribute to the SI N

BEA.WebLogicApplicationServer

BMC BladeLogic Client Automation BladeLogic Client Automation Tuner Pattern enhanced to ensure that the SI type of the product is set to 'BMC Configuration Management Tuner' if the version of the product is 7.2 or below. Additionally, the pattern enhanced to obtain more configuration information Y

BMC.BladeLogic.ClientAutomation

IBM WebSphere Application Server Application Server, Node Agent and Deployment Manager patterns enhanced to obtain JMX port information (can be used for deeper J2EE discovery in the future). JMX port information added as an attribute to the SI. Additionally, the longest component of the SI key for each of these patterns is now hashed using MD5 sum to ensure that the overall length is less than 200 characters to prevent issues with export to external databases Y

IBM.WebSphereApplicationServer

Oracle RDBMS Oracle Database Server pattern enhanced by an addition of another method of retrieving ORACLE_HOME (required for detailed modelling of the product) N

Oracle.OracleRDBMS

SAP (Business Objects) BusinessObjects Enterprise An additional pattern - BusinessObjects Enterprise Designer added to the existing pattern module N

BusinessObjects.BusinessObjectsEnterprise

Bugs Fixed

The following bugs have been fixed in BMC Atrium Discovery Technology Knowledge Update 2010-Mar-1

Case No Defect No Details Pattern Module
N/A 11933 Problem: Most patterns that model clusters needed to have one of the attributes updated to conform to Taxonomy changes made in ADDM 8.0 and allow automatic display of that attribute ('id' - cluster ID) Solution: The following patterns were updated: Citrix Presentation Server HP ServiceGuard IBM HACMP Microsoft Cluster Server Oracle Clusterware Sun Cluster

Citrix.PresentationServer
HP.ServiceGuard
IBM.HACMP
Microsoft.MSCluster
Oracle.Clusterware
Sun.SolarisCluster

22743 12610 Problem: An OEM release of Acresso FlexNet Publisher License Server Manager (ex-FlexLM) was not being identified as such. Sybase license this product and call it: Sybase SySAM License Manager Solution: Acresso FlexNet Publisher License Server Manager pattern updated to ensure that if Sybase SySAM License Manager is found, a correct SI type is used

Acresso.FLEXnetPublisher

23345 12821 Problem: A number of patterns can create an SI key that is longer than 200 characters which causes issues with export of data to certain systems (some databases and to CMDB) Solution: The longest component of the SI key in each of these patterns has had an MD5 hash applied to it to generate a much shorter string to ensure overall SI key length is below 200 characters.

Acresso.FLEXnetPublisher
BEA.AquaLogic.BPM
CA.SiteMinder
CA.WilyIntroscope
HP.MercurySiteScope
HP.VMM
IBM.DB2.ContentManager
IBM.Tivoli.NetcoolImpact
MySQL_AB.MySQL_RDBMS
Oracle.Coherence
Sun.JavaSystemWebserver

N/A 12956 Problem: One of the runCommand() calls in BMC Impact Manager pattern may not work correctly on certain UNIX platforms due to the assumptions about the login shell Solution: The runCommand() call in the pattern modified to work with various UNIX shells

BMC.ImpactManager

N/A 12962

Problem: SI type was incomplete in the patterns within the BMC ADDM (Legacy) pattern module. The publisher of the product was not included.

Solution: Patterns updated to include publisher information.
NOTE: The SI key for each pattern has changed due to this change in the SI type

BMC.ADDM

ISS03565916 12977 Problem: SI key length produced by the Oracle.PeopleSoft.PIA WebServer can exceed 200 characters in length which causes issues with export of data to certain systems (some databases and to CMDB) Solution: The longest component of the SI key in this pattern has had an MD5 hash applied to it to generate a much shorter string to ensure overall SI key length is below 200 characters.

Oracle.PeopleSoft.PIA

N/A 12985 Problem: The BAI key that models the Tideway Foundation / BMC ADDM 8.x product is created in such a way that if the product is upgraded and then the host scanned, a new BAI is created instead of the BAI just having its version attributes updated Solution: BAI pattern updated to create a BAI key that is not affected by version changes

Tideway.Foundation

N/A 12992 Problem: BMC BladeLogic Client Automation pattern could exit with an ECA Engine error if the configuration file containing version information could not be accessed or parsed Solution: Error handling improved

BMC.BladeLogic.ClientAutomation

ISS03570358 12996 Problem: Sophos AV (Unix) pattern could exit with an ECA Engine error if the configuration file containing version information could not be accessed Solution: Error handling improved

Sophos.AntiVirus

N/A 12998 Problem: BMC Remedy AR System second-order SI pattern would if list of applications installed was obtained via a database query, exit with an ECA Engine error due to an incorrectly initialized list Solution: Pattern updated with correct initialization code

BMC.RemedyARSystem

N/A 13019 Problem: In cases where product minor version of IIS is obtained via registry query in Service/Webserver patterns and equals to 0, the minor version isn't going to be added to full product version Solution: Code fix to ensure that minor version if obtained is always added to the full product version

Microsoft.IIS

N/A 13020 Problem: Oracle Workflow pattern can exit with an ECA Engine error when scanning UNIX hosts if the active command that determines whether the product is installed fails due to file access restrictions Solution: Error handling improved

Oracle.Workflow

  • No labels