You can upload and activate a TKU package in a single operation. Before you can do this, the appliance must be in maintenance mode, and Discovery stopped. If not, a warning to this effect is displayed when you attempt to display the Knowledge Update page.

Changes in the pattern configuration block revision number may reset the pattern configuration changes to the default values

If you install a Technology Knowledge Update (TKU) which contains an update to a pattern configuration block that requires its major revision number to be incremented, any end-user configuration changes to that pattern (made through the pattern configuration block) are lost and the default pattern values are restored.

A TKU release contains the following components. You may download one or both of these depending on your license agreement:

  • Technology-Knowledge-Update-YYYY-MM-N-RELEASE.zip
    • Core – Patterns that model various software products.
    • Extended Database discovery – Patterns that extend some of the core database patterns to obtain additional detailed information about certain databases.
    • Middleware discovery – Patterns that obtain detailed information about certain J2EE Application Servers and Web servers
    • Network Device Integration Module with associated Network Device definition files (compatible with BMC Atrium Discovery 8.2.01 and above)* and Printer definition files (compatible with BMC Atrium Discovery 8.3 and above).
    • System – Patterns that detect configuration issues and populate Discovery Conditions and patterns used by the CMDB sync system
  • Extended-Data-Pack-YYYY-MM-N-RELEASE.zip
    • Product Lifecycle – Patterns that populate BMC 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 BMC Atrium Discovery with power and heat consumption figures for various hosts.

Where a TKU upgrade makes changes to syncmapping files (see Default CDM Mapping and Syncmapping block), the initial CMDB syncs after upgrade may result in longer reconciliation times. Examples of such changes are key changes or attribute changes on a CMDB CI.

Hardware Reference Data

This page uploads hardware reference data using the Create and Update option available when importing using the Import Hardware Reference Data page.

Lifecycle reports

The Extended Data Pack provides a means of populating many of the Lifecycle reports that are shown in the OS Product Lifecycle Analysis dashboard.

These supplied zip archives can be uploaded and their content activated without any further processing by following the procedure below.

To upload and activate a TKU package

  1. Ensure that the appliance is in Using maintenance mode, and Discovery is stopped.
  2. From the Model section of the Administration tab, select Knowledge Update.
    The result of the last update is displayed on the Knowledge Update page unless it has been cleared, or no updates have taken place since the appliance was started.
    This screen illustrates the result of the Knowledge Update.
  3. Click New Update to display the Knowledge Update dialogs.
  4. Enter the filename into the File To Upload dialog box, or click Browse... to locate a file.
  5. To upload and perform the update, click Apply.
    This task may take a long time. You can navigate away from this page while the task is running.
    When the task is finished, the page is updated with the results which remain until cleared.

Updating a TKU

When updating a TKU, follow the same procedure for uploading a TKU. The patterns in the previous TKU are automatically deactivated. Where the major version of TKU patterns changes, the new patterns do not become the maintainer of the inferred model created by the patterns from the previous TKU. Where this happens the inferred model created by the previous TKU and that by the new TKU may coexist in parallel until the older one is aged out. You can avoid this by deleting the previous TKU, and consequently removing the inferred model created by its patterns.

Was this page helpful? Yes No Submitting... Thank you
  • No labels