Getting Started Guide: BMC Bladelogic Client Automation Configuration Discovery Integration For CMDB

BMC BladeLogic Client Automation Configuration
Discovery Integration for CMDB

Getting Started Guide
Supporting
BMC BladeLogic Client Automation Configuration
Discovery Integration for CMDB 8.3.00
January 2014
www.bmc.com
Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information
about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada
Address BMC SOFTWARE INC Telephone 713 918 8800 or Fax 713 918 8000
2101 CITYWEST BLVD 800 841 2031
HOUSTON TX 77042-2827
USA
Outside United States and Canada
Telephone (01) 713 918 8800 Fax (01) 713 918 8000
© Copyright 2008–2014 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent
and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and
logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the
property of their respective owners.
IBM and AIX are trademarks or registered trademarks of International Business Machines Corporation in the United States, other
countries, or both.
Java, Solaris, and Sun are the trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries.
Linux is the registered trademark of Linus Torvalds.
Oracle is a registered trademark of Oracle Corporation.
UNIX is the registered trademark of The Open Group in the US and other countries.
BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is
subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted
rights notices included in this documentation.
Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF
THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to
restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS
252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX
77042-2827, USA. Any contract notices should be sent to this address.
Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer
Support by telephone or e-mail. To expedite your inquiry, see “Before contacting BMC.”
Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support. From this
website, you can
■ read overviews about support services and programs that BMC offers
■ find the most current information about BMC products
■ search a database for issues similar to yours and possible solutions
■ order or download product documentation
■ download products and maintenance
■ report an issue or ask a question
■ subscribe to receive proactive e-mail alerts when new product notices are released
■ find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and
telephone numbers
Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or
send an e-mail message to customer_support@bmc.com. (In the subject line, enter SupID:<yourSupportContractID>, such
as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.
Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:
■ product information
— product name
— product version (release number)
— license number and password (trial or permanent)
■ operating system and environment information
— machine type
— operating system type, version, and service pack or other maintenance level such as PUT or PTF
— system hardware configuration
— serial numbers
— related software (database, application, and communication) including type, version, and service pack or
maintenance level
■ sequence of events leading to the issue
■ commands and options that you used
■ messages received (and the time and date that you received them)
— product error messages
— messages from the operating system, such as file system full
— messages from related software
3
License key and password information
If you have questions about your license key or password, contact BMC as follows:
■ (USA or Canada) Contact the Order Services Password Team at 800 841 2031, or send an e-mail message to
ContractsPasswordAdministration@bmc.com.
■ (Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or
send an e-mail message to password@bmc.com.
■ (Asia-Pacific) Contact your BMC sales representative or your local BMC office.
4 BMC BladeLogic Client Automation Configuration Discovery Integration for CMDB Getting Started Guide
Contents
About this book 13
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
BMC BladeLogic Client Automation documents . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
BMC Atrium Core documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
BMC Atrium CMDB documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 1 Introducing configuration discovery integration 19

Overview of BMC Atrium CMDB integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
The role of BMC BladeLogic Client Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
The role of BMC Atrium Integrator (AI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
The role of the BMC Definitive Software Library . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
The role of the Normalization Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
The roll of the Federation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Overview of Configuration Discovery Integration for CMDB program . . . . . . . . . . . 21
Overview of the data integration process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Discovering configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Preference-based discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
How application discovery works in BMC BladeLogic Client Automation. . . . . 25
Configuration Discovery Integration for CMDB filter and import process . . . . . 26
Normalizing discovered data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Normalization settings for Configuration Discovery Integration for CMDB. . . . 27
Key attribute normalization for identifying duplicate CIs . . . . . . . . . . . . . . . . . . . 28
Qualified versus unqualified CIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Software title usage data federation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Requirements for implementing software title usage data federation . . . . . . . . . 29
Changes that occur following implementation of data federation . . . . . . . . . . . . 30
Defining Jobs and Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Reconciling discovered data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Understanding the identification activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Understanding the merge activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Understanding the purge activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Contents 5
Chapter 2 Installing the integration module 39
Estimating storage requirements for BMC BladeLogic Client Automation discovered
data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Installing Configuration Discovery Integration for CMDB . . . . . . . . . . . . . . . . . . . . . . 41
Classes extended during CDI installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Upgrading Configuration Discovery Integration for CMDB. . . . . . . . . . . . . . . . . . . . . 46
Uninstalling Configuration Discovery Integration for CMDB . . . . . . . . . . . . . . . . . . . 49
Chapter 3 Customizing the integration 53

Improving data transfer performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Improving scanning performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Filtering import data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Filtering by application name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Filtering by application location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Appendix A Key attributes populated for identifying configuration items 59
Appendix B BMC Atrium Integrator 67

BMC Atrium Integrator job details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
BMC Atrium Integrator Transformation Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
BMC Atrium Integrator CI class mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Pull_ars_inv_machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Pull_ars_inv_application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Pull_ars_inv_Bios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Pull_ars_inv_monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Pull_ars_inv_network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Pull_ars_inv_networkcard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Pull_ars_inv_os. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Pull_ars_inv_patch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Pull_ars_inv_person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Pull_ars_inv_printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Pull_ars_inv_processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Pull_ars_inv_storage_DiskDrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Pull_ars_inv_storage_LocalFileSystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Pull_ars_inv_storage_FloppyDrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Pull_ars_inv_storage_CDROMDrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Pull_ars_inv_videocard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
BMC Atrium Integrator relationship mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Machine-Application relationship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Machine-BIOS relationship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Machine-Monitor relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Machine-Network relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Machine-Patch relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Machine DiskDrive relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Machine FloppyDrive relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Machine CDROMDrive relationship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Machine LocalFileSystem relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Machine-Videocard relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Machine-Printer relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Machine-Processor relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Machine-OS relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Machine-Person relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Machine-NetworkCard relationship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
NetworkCard-Network relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Index 103
Contents 7
Figures
Integration architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Configuration Discovery Integration for CMDB filter and import process . . . . . . . . 26
Reconciling datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figures 9
Tables
Configuration data discovered by the Scanner Service . . . . . . . . . . . . . . . . . . . . . . . . 23
Normalization settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
BMC Atrium CMDB dataset names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
TokenID population from configuration discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
List of keys by class for a non-trusted best match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Discovered classes and identification rules used during the identification activity . 35
Prerequisite products and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuration Discovery Integration for CMDB installation worksheet . . . . . . . . . . 42
Prerequisite products and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Example of configuring transformations and jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Key attributes used for inserting, updating, and deleting . . . . . . . . . . . . . . . . . . . . . . 54
Key attributes used to populate the TokenId . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Example of configuring transformation on five instances . . . . . . . . . . . . . . . . . . . . . . 68
Primary Key Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Data Field Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Tables 11
Data Field Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Machine-application relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Machine-Application attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Machine-BIOS relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Machine-BIOS attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Machine-monitor relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Machine-monitor attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Machine-network relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Machine-network attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Machine-patch relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Machine-patch attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Machine-disk drive relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Machine disk drive attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Machine-floppy drive relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Machine-floppy drive attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Machine CDROM drive relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Machine CDROM drive attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Machine-local file system relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Machine local file system attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Machine-card relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Machine-card attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Machine-printer relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Machine-printer attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Machine-processor relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Machine-processor attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Machine-operating system relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Machine-operating system attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Machine-person relationship foreign keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Machine-person attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Machine-network card relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Machine-network card attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
NetworkCard-Network relationship foreign key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
NetworkCard-Network attribute field mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
About this book
This guide contains overview, installation, configuration, and administrative
information about the BMC BladeLogic Client Automation Configuration Discovery
Integration for CMDB program. This integration program enables you to share data
about the endpoint computers in your BMC BladeLogic Client Automation system
with the BMC IT Service Management suite of products—an essential step along the
path to a complete change and configuration management solution.
Like most BMC documentation, this book is available in printed and online formats.
To request printed books or to view online books and notices (such as release notes
and technical bulletins), see the Customer Support website at
http://www.bmc.com/support. Most product shipments also include the books on a
documentation CD.
NOTE
Online books are formatted as PDF or HTML files. To view, print, or copy PDF books, use the
free Adobe Reader from Adobe Systems. If your product installation does not install the
reader, you can obtain the reader at http://www.adobe.com.
The software also offers online Help. To access Help, press F1 within any product or
click the Help button in graphical user interfaces (GUIs).
Audience
This guide is for executive decision makers and the system administrator responsible
for implementing the integration.
About this book 13

Related publications
Related publications
The following related publications supplement this book and the online Help:
This section describes the related documentation for the BMC BladeLogic Client
Automation product. Unless otherwise noted, softcopy documentation is available
from the Electronic Product Distribution (EPD) site at http://webapps.bmc.com/epd
and from the Support site at http://www.bmc.com/support.
BMC BladeLogic Client Automation documents

The following table shows the BMC BladeLogic Client Automation documentation.
Title Description Audience

BMC BladeLogic Client Introduces you to BMC BladeLogic Client Automation Everyone
Automation Concepts Guide products and solutions and defines basic concepts
about core technology.
BMC BladeLogic Client Helps you configure and administer Policy Administrators
Automation Policy Management Management and the Policy Service plug-in. This
User Guide guide also includes integration procedures for
directory services, such as Active Directory, ADAM,
and Sun™ ONE Directory.
BMC BladeLogic Client Provides hardware requirements (such as processing Everyone
Automation Release Notes speed, disk space, and RAM) and operating system
requirements for supported platforms.
BMC BladeLogic Client Helps you design an infrastructure for your enterprise, Users
Automation Installation Guide and provides instructions for first-time installations
and upgrades.
BMC BladeLogic Client Provides instructions about running queries of Administrators
Automation Report Center User inventory information, configuring the Inventory and
Guide Logging plug-in, configuring endpoints, and
integrating Report Center with other BMC BladeLogic
Client Automation applications.
BMC Configuration Automation Describes how to use Deployment Management and Administrators
for Clients Deployment Manager Content Replicator to control and monitor the
Guide distribution of content and applications across
heterogeneous server platforms and data centers.
Deployment Manager extensions to Report Center and
Application Packager are also described.
BMC Atrium Core documents

BMC BladeLogic Client Provides information about packaging software for Administrators
Automation Application Packager distribution to desktops or servers. This guide also
User Guide includes information about command-line usage,
policies, XML templates, and Windows system
macros.
BMC BladeLogic Client Provides reference information, such as command-line Users
Automation Reference Guide options, tuner properties, proxy properties,
transmitter properties, channel properties, channel
parameters, channel states, ports, and log IDs with
associated log messages.
BMC Atrium Core documents

The following table shows the BMC Atrium Core documentation.

BMC Atrium Core The BMC Atrium Core solution works with other BMC Atrium Administrators
Administrator’s Guide solutions to facilitate the alignment of your IT organization
with business priorities. BMC Atrium Core provides tight
integration across management tools used in your IT
environment, saving your IT organization time and money.
BMC Atrium Core includes the following component
products:
■ BMC Atrium Configuration Management Database (BMC

Atrium CMDB), which stores information about the
configuration items (CIs) in your IT environment and the
relationships between them.
■ BMC Atrium Integrator, which transfers data between an

external datastore and BMC Atrium CMDB.
Spoon User guide For more information, refer
Pentaho. http://wiki.pentaho.com/display/EAI/Spoon+User+Guide
About this book 15

BMC Atrium CMDB documents
BMC Atrium CMDB documents

The following table shows the BMC Atrium Configuration Management Database
(BMC Atrium CMDB) documentation.
Title Document provides Audience Format

BMC Atrium CMDB Hierarchical diagram of all classes in the Administrators Print and PDF
Common Data Model Common Data Model (CDM) including
Diagram unique attributes and applicable
relationships
BMC Atrium CMDB Information about BMC Atrium CMDB IT leaders and Print and PDF
Concepts and Best concepts and best practices for planning administrators
Practices Guide your implementation
BMC Atrium CMDB Data Description and details of super classes, Administrators HTML (product
Model Help subclasses, attributes, and relationship DVD only)
classes for each class. Contains only
information about the CDM at first, but
can be updated to include information
about data model extensions you install.
BMC Atrium CMDB Information about creating API Administrators Print and PDF
Developer’s Reference programs, using C and web services API and programmers
Guide functions and data structures, and a list
of error messages
BMC Atrium CMDB Information about installing and Administrators Print and PDF
Installation and configuring BMC Atrium CMDB,
Configuration Guide including permissions, class definitions,
reconciliation, and federation
BMC Atrium CMDB Information about Java™ classes, Programmers HTML (product
Javadoc API Help methods, and variables that integrate DVD only)
with BMC Atrium CMDB
Mapping Your Data to Mappings of common IT objects to the Administrators Spreadsheet, print,
BMC Atrium CMDB appropriate class in which to store them, and PDF
Classes whether part of the Common Data
Model or an extension. Also includes
information about further categorizing
instances using key attributes.
BMC Atrium CMDB Combined index of all guides Everyone Print and PDF
Master Index
BMC Atrium CMDB Help for using and configuring BMC Users and Product Help
Online Help Atrium CMDB, available by clicking administrators (available from
Help in the product interface Help links after
installed)
BMC Atrium CMDB Information about new features, open Everyone Print and PDF
Release Notes issues, and resolved issues
Conventions
Title Document provides Audience Format

BMC Atrium CMDB Information about resolving issues with Administrators, Print and PDF
Troubleshooting Guide BMC Atrium CMDB components, programmers,
including API, filter, and console error and BMC Support
messages and their solutions. personnel
BMC Atrium CMDB Information about using BMC Atrium Users Print and PDF
User’s Guide CMDB, including searching for and
comparing configuration items (CIs) and
relationships, relating CIs, viewing
history, and launching federated data
Conventions
This book uses the following special conventions:
■ All syntax, operating system terms, and literal examples are

presented in this typeface.
■ Variable text in path names, system messages, or syntax is displayed in italic text:
testsys/instance/fileName
■ The symbol => connects items in a menu sequence. For example, Actions => Create
Test instructs you to choose the Create Test command from the Actions menu.
About this book 17

Conventions
Chapter
1
Introducing configuration discovery
1
integration
This chapter describes the integration model for data in the BMC BladeLogic Client
Automation database and the role of the BMC BladeLogic Client Automation
Configuration Discovery Integration for CMDB (Configuration Discovery Integration
for CMDB) program in the transfer and reconciliation of this data. This chapter
presents the following topics:
Overview of BMC Atrium CMDB integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

The role of BMC BladeLogic Client Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
The role of BMC Atrium Integrator (AI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
The role of the BMC Definitive Software Library . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Overview of Configuration Discovery Integration for CMDB program . . . . . . . . . . . 21
Overview of the data integration process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Discovering configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Preference-based discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
How application discovery works in BMC BladeLogic Client Automation. . . . . 25
Configuration Discovery Integration for CMDB filter and import process . . . . . 26
Normalization settings for Configuration Discovery Integration for CMDB. . . . 27
Software title usage data federation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Requirements for implementing software title usage data federation . . . . . . . . . 29
Changes that occur following implementation of data federation . . . . . . . . . . . . 30
Defining Jobs and Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Reconciling discovered data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Understanding the identification activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Understanding the merge activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Understanding the purge activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Overview of BMC Atrium CMDB integration
Overview of BMC Atrium CMDB integration

BMC Atrium Configuration Management Database (BMC Atrium CMDB) stores
information about the configuration items (CIs) in your IT environment and the
relationships between them. A CI is an instance of an entity that is part of your
environment and has configurable attributes specific to that instance. These entities
can be physical (such as a computer system), logical (such as an installed instance of a
software program), or conceptual (such as a business service). For example, a
discovered application server is represented by a CI that defines the attributes of the
host computer, and the application that it hosts is represented by a CI that defines the
attributes of the software. A relationship defines the dependency of the application
on the application server.
Data providers, such as discovery applications, put data into BMC Atrium CMDB,
where it is partitioned into separate datasets. The Reconciliation Engine component
enables you to reconcile these datasets into a consolidated production dataset that
you use as the single source of reference for your IT environment. Data consumers
such as the BMC Remedy Asset Management product, read data from the production
dataset.
The role of BMC BladeLogic Client Automation

The Scanner Service is the BMC BladeLogic Client Automation component that
discovers CIs in your environment. It collects hardware, software, system, and
logging information about IT assets including servers, desktops, laptops, and mobile
devices across major platforms. The Scanner Service sends this configuration data to
the Inventory database in BMC BladeLogic Client Automation.
The role of BMC Atrium Integrator (AI)

Atrium Integrator enables you to transfer data from external data stores to BMC
Atrium Configuration Management Database (BMC Atrium CMDB) classes. You can
connect to a wide variety of input sources using connectors such as JDBC, ODBC,
JMS, native databases, web services, and complex XML. Atrium Integrator provides
you with the ability to clean and transform your data before putting it into BMC
Atrium CMDB.
Atrium Integrator replaces BMC Atrium Integration Engine. You can continue using
BMC Atrium Integration Engine for existing data mappings and exchanges, but BMC
recommends that you use Atrium Integrator for all new data transfers.
The BMC Atrium Integrator transfers data from the BMC BladeLogic Client
Automation Inventory database to BMC Atrium CMDB.
The role of the BMC Definitive Software Library
The role of the BMC Definitive Software Library

BMC Definitive Software Library (DSL) is a central repository of approximately
10,000 approved Product Dictionary (PD) entries and Software Library Items (SLIs).
PD entries are definitive, normalized names and descriptions of software
applications, which you can use to ensure that IT always refers to an application the
same way in all contexts. SLIs reside in a list of URLs that link to the physical
locations of all available software packages approved for distribution within your
enterprise. The DSL enables you to facilitate software license management and
software deployment by adding or modifying PD entries and SLIs.
The role of the Normalization Engine

Normalization is the process of standardizing data in the Configuration Discovery
Integration for CMDB (BMC.IMPORT.CONFIG) dataset into the Product Catalog in
BMC Atrium CMDB.
The roll of the Federation Manager

When properly configured, Configuration Discovery Integration for CMDB can work
with Federation Manager to federate software title usage data in the BMC BladeLogic
Client Automation Configuration Discovery Integration for CMDB Inventory
database with the BMC Atrium CMDB. The ability to federate software title usage
data from the Inventory database enables the software title usage component in the
BMC Remedy Asset Management product to access software title usage data from the
BMC Atrium CMDB.
Overview of Configuration Discovery

Integration for CMDB program
The Configuration Discovery Integration for CMDB program enables the transfer of
data from the BMC BladeLogic Client Automation Inventory database to the BMC
Atrium CMDB. The integration program has no interface other than the installation
program that installs the following components:
■ a set of views on top of the Inventory database
■ Jobs and Transformation in the BMC Atrium Integrator for the CI classes and
relationship classes that are discoverable by the Scanner Service.

Overview of the data integration process
■ federated links for BMC BladeLogic Client Automation
■ reconciliation definitions in the Reconciliation Engine for use during the

identification phase
Overview of the data integration process

The integration of BMC BladeLogic Client Automation configuration data begins
with the discovery process in the Scanner Service and ends with the transfer process
into BMC Atrium CMDB. Between these activities, the following activities are
performed, as shown in Figure 1 on page 22:
1. The Scanner Service discovers inventory data on the endpoints and sends the data
to the Inventory database.
2. Jobs, transformations and data mapping parameters must be defined using BMC
Atrium Integrator to transfer discovered data between the Inventory database and
BMC Atrium CMDB.
3. The reconciliation process identifies CIs and merges them into the BMC Asset
dataset.
Figure 1 Integration architecture
Note: This figure shows the former name of the

BMC BladeLogic Client Automation product,
which was BMC Configuration Management.
Discovering configuration data
Based on this integration model, the functionality provided by Configuration

Discovery Integration for CMDB consists of the following activities, which are
completed during program installation:
■ Installs a schema or set of super views on top of the BMC BladeLogic Client
Automation database
■ Defines Jobs and Transformation in the BMC Atrium Integrator for the BMC trium
CMDB CI classes and relationship classes that are discoverable by Report Center
■ Creates federation links for BMC BladeLogic Client Automation software title
usage data and provides reconciliation rules to the Reconciliation Engine for use
during the identification phase of the reconciliation process
Discovering configuration data

Table 1 contains the CIs that are discovered by the Scanner Service that are transferred
to the BMC Atrium CMDB.
Table 1 Configuration data discovered by the Scanner Service

CI type Example of attributes collected
Computer system Host name, domain, serial number
Operating system Type, version, patch number, and service pack
BIOS Type and version number
Software product Name, version, and manufacturer
Patch information Description, patch number, and severity
Hardware Processor, disk drive, network port, network card, and monitor
Logical network IP address and subnet
File system Model, manufacturer, and serial number
To view detailed lists of the CIs and relationships imported to the BMC Atrium
CMDB, see Appendix B, “BMC Atrium Integrator.”

Preference-based discovery
Preference-based discovery
If BMC BladeLogic Client Automation and other BMC discovery products, like BMC
Atrium Discovery and Dependency Mapping, discover configuration data on an
endpoint, BMC BladeLogic Client Automation becomes the preferred provider of the
following common classes:
■ BMC_BIOSElement
■ BMC_Card
■ BMC_CDROMDrive
■ BMC_DiskDrive
■ BMC_FloppyDrive
■ BMC_LocalFileSystem
■ BMC_Monitor
■ BMC_Patch
■ BMC_Processor
■ BMC_Product
If you deploy BMC BladeLogic Client Automation to discover CIs on an endpoint

that BMC Atrium Discovery and Dependency Mapping previously discovered, and
those CIs were imported into and reconciled with the BMC Asset dataset, the
following actions occur:
■ BMC Atrium Discovery and Dependency Mapping detect the Scanner Service on
the endpoint.
NOTE
For BMC Atrium Discovery and Dependency Mapping to detect whether the
Scanner Service is present on the endpoint, the BMC BladeLogic Client
Automation Scanner Service Trace option must be activated. For more information
about configuring the Scanner Service, see the BMC BladeLogic Client Automation
Installation Guide and the BMC BladeLogic Client Automation Report Center User
Guide.
■ BMC Atrium Discovery and Dependency Mapping stop discovering instances of

the BMC BladeLogic Client Automation preferred classes.
■ When BMC Atrium Discovery and Dependency Mapping discover CIs on the
endpoint again, these products continue to collect information about the parent CI
and mark all CIs previously discovered for deletion. For information about the
deletion process, see “Understanding the purge activities” on page 38.
■ BMC Atrium Discovery and Dependency Mapping discover instances of all other
classes that are not preference-based.
How application discovery works in BMC BladeLogic Client Automation
■ When you reconcile the discovered data to the production dataset, merge
precedence is applied to the instances discovered and imported by both discovery
products.
For details, see “Understanding the merge activity” on page 37.
NOTE
If you use both BMC BladeLogic Client Automation and other BMC or third-party
discovery providers, BMC recommends that you import and reconcile the preferred
classes only from BMC BladeLogic Client Automation to BMC Atrium CMDB. If you
do use multiple discovery providers for the preferred classes, the attribute values
must be populated identically. For a list of the key attributes and how they are
populated, see Appendix A, “Key attributes populated for identifying configuration
items.”
You can use other discovery providers to discover CIs that are not preferred classes
and reconcile them according to the class and attribute merge precedence.
How application discovery works in BMC BladeLogic Client

Automation
The Scanner Service in BMC BladeLogic Client Automation provides the following
discovery methods for application software titles and the results of both methods are
saved in the inventory database.
Application discovery method

For all non-Windows applications, Scanner Service discovers applications by
discovering shortcuts and applications that were installed with MSI installers.
Because no post-discovery filtering is applied to the discovered applications, the
results can contain duplicate entries that do not qualify as applications.
Software title discovery method

For all Windows applications, the Scanner Service uses the application discovery
methods and the software title discovery method to discover Windows applications.
In the software discovery method, the Scanner Service looks for installed applications
in entries in Add or Remove Programs in the Control Panel and searches for
executables under the Program Files folder. A set of filters and reconciliation rules act
on the collected software titles to eliminate noise and duplicates.

Configuration Discovery Integration for CMDB filter and import process
Configuration Discovery Integration for CMDB filter and

import process
After you run discovery on an endpoint, you import the new and revised records, as
well as those marked for deletion, to datasets in BMC Atrium CMDB. Table 3 on
page 32 lists the classes that BMC BladeLogic Client Automation can import to BMC
Atrium CMDB.
After you import the data to the import dataset, you use the Reconciliation Engine to
compare and merge the discovered configuration data with the production dataset.
For information about reconciliation, see “Reconciling discovered data” on page 32.
To reduce the amount of data that needs to be stored and reconciled, the person acting
as Discovery Manager should filter and import only the configuration data required
by the consuming applications.
Figure 2 illustrates when Configuration Discovery Integration for CMDB filters and
imports discovered data to BMC Atrium CMDB.
Figure 2 Configuration Discovery Integration for CMDB filter and import process
After the CIs are discovered by the Scanner Service and stored in the Inventory
database, Configuration Discovery Integration for CMDB
■ installs a set of database views (prefixed with mrb_inv_) that represent a subset of
the data found in the Inventory database
The selected data identifies CIs that, in compliance with ITIL standards, belong in
BMC Atrium CMDB.
Normalizing discovered data
■ maps the views in the Inventory database to the classes and attributes in BMC
Atrium CMDB
Specifically, Configuration Discovery Integration for CMDB creates data exchange

definitions and CI class and relationship class data mappings in BMC Atrium
Integrator for the classes that are discoverable by BMC BladeLogic Client
Automation.
■ filters the data through the application_bsm and the app_location_bsm database
tables
For additional information, see “Filtering import data” on page 55.

Normalization is the process of standardizing discovered data, not only for
consistency in your consuming applications, but also to enable the reconciliation
process in BMC Atrium CMDB to identify duplicate CIs from multiple providers and
merge the data collected by each provider.
BMC BladeLogic Client Automation normalizes software titles in the Inventory

database against the DSL before the BMC Atrium Integrator pulls in the data for
mapping.
Normalization settings for Configuration Discovery

Integration for CMDB
This feature normalizes data in Configuration Discovery Integration for CMDB
dataset (BMC.IMPORT.CONFIG) dataset into the Product Catalog in BMC Atrium
CMDB. The normalization engine can work with AR System Server and BMC Atrium
CMDB 7.5 and later. For more information about normalization, see the BMC Atrium
CMDB Normalization and Reconciliation Guide.
Configuration settings
The normalization engine is enabled by default and loads the data that is integrated
into the BMC Atrium CMDB. When you install the Configuration Discovery
Integration for CMDB module, the configuration settings in Table 2 are set for the
BMC.IMPORT.CONFIG dataset.

Key attribute normalization for identifying duplicate CIs
Table 2 Normalization settings

Option Default value Value set for normalization
Normalization Type CTI Name
Unapproved Handling Reject Accept
Normalization Mode Continuous Continuous
NewProductHandling Return Error" Create Entry in Product Catalog
Trusted Dataset UnTrusted UnTrusted
Normalization jobs
The Normalization job also uses the configuration settings in Table 2 to normalizes
data between BMC.IMPORT.CONFIG dataset and the Product Catalog. When you
install the Configuration Discovery Integration for CMDB, the installation program
creates the following two jobs for the BMC.IMPORT.CONFIG dataset:
■ The CDI_Continuous_NEJob job starts immediately and begins normalizing data as

the data is populated in the BMC.IMPORT.CONFIG dataset.
■ The CDI_Batch_NEJob job does not run unless you start it. After you start it, it runs
daily, but you can change the default schedule time. You do not need to run this
normalization job unless you want to normalize all of the data in the
BMC.IMPORT.CONFIG dataset.

The TokenId attribute, inherited from the BMC_BaseElement class, uniquely identifies
the resource represented by the CI. The TokenId value is set when the resource is
discovered, sometimes by using a combination of other attribute values.
Qualified versus unqualified CIs

A CI with all of the values necessary to construct the associated TokenId in an instance
is considered a qualified CI.
A CI without all of the values necessary to construct the TokenId is considered

unqualified, and the TokenId is set to NULL. A TokenId might be set to NULL if the CI
was discovered by a third-party discovery product or the CI was entered manually.
Software title usage data federation
Software title usage data federation

When properly configured, Configuration Discovery Integration for CMDB can work
with Federation Manager to federate software title usage data in the BMC BladeLogic
Client Automation Configuration Discovery Integration for CMDB Inventory
database with the BMC Atrium CMDB. The ability to federate software title usage
data from the Inventory database enables the software title usage component in the
BMC Remedy Asset Management product to access software title usage data from the
BMC Atrium CMDB.
Requirements for implementing software title usage data

federation
To implement software title usage federation requires that you perform the following
actions:
■ Install the Software Usage schema in the Inventory database.
■ Use the Software Title Discovery method during installation of Configuration

Discovery Integration for CMDB.
■ Ensure that the SQL Server Agent is running on the Inventory database.
■ Configure a Federation Manager plug-in (BCAC_DISCOVERY_PLUGIN) to access

the new database view that is created during the installation of Configuration
Discovery Integration for CMDB. This procedure is described in “Installing
Configuration Discovery Integration for CMDB” on page 41 and “Upgrading
Configuration Discovery Integration for CMDB” on page 46.
If you install the Configuration Discovery Integration for CMDB after you install
Software Usage schema, the software_title_usage data is automatically loaded into
mrb_inv_software_title_usage view. If you install Configuration Discovery
Integration for CMDB without the schema, you cannot see the software title usage
data in the CMDB.
For information about configuring the Software Usage component to use the
federated data, see the documentation for BMC Remedy IT Service Management
7.6.00 and later.

Changes that occur following implementation of data federation
Changes that occur following implementation of data

federation
Following installation and configuration for software title usage data federation, the
following changes occur in the Inventory database schema and BMC Atrium CMDB:
■ Creation of the mrb_inv_software_title_usage view, which is used by Federation

Manager.
■ Creation of the following job and procedure, which refresh software title usage
data in the mrb_inv_software_title_usage view:
— SQL Server: The cdi_federation_title_usage job.

— Oracle: The cdi_federation_title_usage procedure.
The new job and procedure are scheduled to run every Sunday at 4:00 P.M.
■ Creation of the BCAC_DISCOVERY_PLUGIN plug-in for Federation Manager.
■ Creation of the BCAC_Software_Usage federation class, which includes the

following attribute names and field IDs:
Attribute name Field ID

BCAC_Integration_ID 530060000
Product_Name 240001002
Last_Used_Date 400016300
Num_Times_Used_in_30_Days 303964100
■ Extension of the BCAC_Integration_ID attribute in Base_Element class, which

holds the unique application data value in BMC_Product class and has the
following attribute name and field ID:
BCAC_Integration_ID = 530060000 (maximum length is 254)
■ Addition of a new mapping in pull_ars_inv_application Class Mapping, with

BMC_Product.BCAC_Integration_ID and
MRB_INV_APPLICATION.(MACHINE_ID:CMDBNAME)
Defining Jobs and Transformations
Defining Jobs and Transformations

BMC Atrium Integrator enables you to transfer data between the Inventory database
in BMC BladeLogic Client Automation and BMC Atrium CMDB. It consists primarily
of Job, Transformation and hops.
■ The BMC Atrium Integrator service performs the actual data transfer based on the
settings in the Data Exchange application. These two components can reside on
different computers.
■ A transformation is the combination of steps and hops that make an integration

between source and target data stores possible. It reads data from the source data
store, transforms it according to the rules that you specify, and stores it in the target
data store.
■ A transformation consists of a series of steps. Steps define the input and output
data stores as well the clean up or adjustment actions that you might want to
perform on the data before adding it to BMC Atrium CMDB.
■ Steps are connected by hops, which indicate the direction of the data flow.
■ A job defines the order in which a series of transformations are run so that the
dependencies of the individual transformations are met.
■ A repository is a relational database in which you can store your transformations

and jobs. You can also use a repository to store the logs that are generated when
executing transformations and jobs.
For more information about creating a job in the BMC Atrium Integrator Spoon
application, see the Spoon User Guide at
http://wiki.pentaho.com/display/EAI/Spoon+User+Guide.
For more information about creating a job using AI console, see Creating a job in
Atrium Integrator section in BMC Atrium Core guide.

Normalization is the process of standardizing discovered data, not only for
consistency in your consuming applications, but also to enable the reconciliation
process in BMC Atrium CMDB to identify duplicate CIs from multiple providers and
merge the data collected by each provider.


The TokenId attribute, inherited from the BMC_BaseElement class, uniquely
identifies the resource represented by the CI. The TokenId value is set when the
resource is discovered, sometimes by using a combination of other attribute values.
Qualified versus unqualified CIs

A CI with all of the values necessary to construct the associated TokenId in an
instance is considered a qualified CI.
A CI without all of the values necessary to construct the TokenId is considered

unqualified, and the TokenId is set to NULL. A TokenId might be set to NULL if the
CI was discovered by a third-party discovery product or the CI was entered
manually.
Reconciling discovered data

BMC Atrium CMDB enables you to create datasets, each of which holds a distinct set
of configuration data. Datasets can store data from a variety of discovery applications
for the BMC Atrium CMDB. The same computer system or other CI can exist in more
than one dataset.
Data that is transferred from the Inventory database to the BMC Atrium CMDB is
stored in a special dataset. The BMC Foundation Discovery and Topology Discovery
data transfer creates a second dataset, and existing BMC Remedy Asset Management
data resides in a third dataset. Table 3 shows the dataset names and associated IDs.
Table 3 BMC Atrium CMDB dataset names

Data created by Dataset name Dataset ID
BMC Remedy Asset Management BMC Asset BMC.ASSET
BMC BladeLogic Client Automation BMC Configuration Import BMC.IMPORT.CONFIG
BMC Atrium Discovery and Dependency Mapping BMC Topology Import BMC.IMPORT.TOPO
(BMC Foundation Discovery and Topology Discovery)
After data is transferred, discovered data remains separate from data in the BMC
Asset dataset. To create one unified dataset of all your asset data, you can use the
Reconciliation Engine. After the configuration data has been reconciled, it can be used
by consumers of BMC Atrium CMDB.
Reconciling discovered data
The Reconciliation Engine uses the following Reconciliation Engine jobs to

consolidate data from the BMC Configuration Import and BMC Topology Import
datasets into the BMC Asset dataset:
■ Configuration Discovery Reconciliation Process—reconciles the BMC

Configuration Import dataset with the BMC Asset dataset
■ Topology Discovery Reconciliation Process—reconciles the BMC Topology Import

dataset with the BMC Asset dataset
The reconciliation process consists of identification, merge, and purge activities.
Reconciliation Definitions
This section describes in detail how the Reconciliation Engine within the BMC
Atrium CMDB reconciles instances from discovery sources.
The Reconciliation Engine uses reconciliation definitions to compare each discovery

dataset with the master dataset (BMC Asset). The identification activity determines if
a discovery dataset instance matches an existing instance or is a new instance. In the
Merge activity, the Reconciliation Engine merges all attributes from all discovery
datasets where values match. If field-level data does not match, precedence values
determine which data prevails.
BMC Configuration Discovery and BMC Foundation Discovery and Topology

Discovery (TD) use the same scanning technology to discover system components,
which enables the two discovery sources to create standardized TokenIDs and
reconcile matching instances.
The following table describes how the EIE creates a TokenID from configuration
database fields and relates it to BMC CM view classes and BMC Atrium CMDB
classes.
Table 4 TokenID population from configuration discovery

Mrb attribute copied to
CMDB Class Mrb View TokenID
BMC_ComputerSystem mrb_inv_machine name.machine_domain
BMC_Product name: mrb_inv_application version
BMC_OperatingSystem mrb_inv_os name
BMC_Card mrb_inv_videocard device_id
BMC_CDROMDrive mrb_inv_storage device_id
BMC_FloppyDrive mrb_inv_storage device_id
BMC_DiskDrive mrb_inv_storage device_id
BMC_LocalFileSystem mrb_inv_storage device_id
BMC_Processor mrb_inv_processor device_id

Understanding the identification activity
Table 4 TokenID population from configuration discovery

Mrb attribute copied to
CMDB Class Mrb View TokenID
BMC_Printer mrb_inv_printer hostname:name
BMC_Patch mrb_inv_patch name:hot_fix_id
BMC_Monitor mrb_inv_monitor device_id
BMC_BIOS_Element mrb_inv_bios version
BMC_NetworkPort mrb_inv_networkcard interface_name:mac_ad
dress
BMC_IPEndpoint mrb_inv_network address
BMC_Person mrb_inv_person username:domain_nam
e
The following table describes the list of keys the Reconciliation Engine uses when the
TokenID is not sufficient to determine a match. These identification rules provide a
non-trusted best match.
Table 5 List of keys by class for a non-trusted best match

CMDB Class CI Attributes
BMC_BIOSElement Name
BMC_ComputerSystem HostName, Domain,
PrimaryCapability and
SerialNumber
BMC_NetworkPort Name
BMC_Product NameFormat, Name,
Model, VersionNumber
and InstallLocation
BMC_Patch NameFormat and Name
BMC_Person NameFormat and Name

The identification activity matches instances among multiple datasets, confirming
that each represents the same real-life object. Instances are records in a configuration
management database, whether they represent CIs or relationships.
EXAMPLE
Suppose that the BMC BladeLogic Client Automation Scanner Service and BMC Foundation
Discovery and Topology Discovery detect computer A and create an instance of computer A
in each of their datasets. The Reconciliation Engine compares each dataset with the BMC Asset
dataset separately to determine if computer A already exists in the BMC Asset dataset.
The identification activity first compares Token IDs that each discovery source creates
based on Windows Management Instrumentation (WMI) scanning technology or
UNIX® system calls. Because BMC Atrium Integrator pulls relationship data that
relates child components (such as disk drives or IP addresses) with their parent
computer systems, the Reconciliation Engine considers Token IDs unique to each
computer system.
Qualified CIs are readily selected by the identification rules for merging to the BMC
Asset dataset and are assigned a reconciliation identity
If a TokenId is unqualified, the identification process compares other key attributes

(for example, Name and SerialNumber) to the instances in the BMC Asset dataset to
find the best match.
Table 6 shows the classes discovered by the Scanner Service and the Configuration
Discovery Integration for CMDB identification rules used by the Reconciliation
Engine to determine whether instances match. These identification rules are shown in
the order in which they are used. If a specific rule fails, then the next rule in the list is
tried (if any).
Table 6 Discovered classes and identification rules used during the identification activity
(part 1 of 2)
CMDB Class Identification Rule
BMC_BIOSElement 'TokenId' = $TokenId$ AND 'TokenId' != "0"
'TokenId' = "0" AND 'Name' = $Name$
BMC_Card 'TokenId' = $TokenId$ AND 'TokenId' != "0" AND 'ClassId' = "BMC_CARD"
BMC_CDROMDrive 'TokenId' = $TokenId$ AND 'TokenId' != \"0\" AND 'ClassId' =
\"BMC_CDROMDrive\"

Table 6 Discovered classes and identification rules used during the identification activity
(part 2 of 2)
CMDB Class Identification Rule
BMC_ComputerSystem 'TokenId' = $TokenId$ AND'TokenId' != "0"
( 'SerialNumber' != $\NULL$ AND 'HostName' != $\NULL$ AND 'Domain' !=

$\NULL$ ) AND ( 'SerialNumber' = $SerialNumber$ AND 'HostName' =
$HostName$ AND 'Domain' = $Domain$ )
'SerialNumber' = $SerialNumber$ AND 'HostName' = $HostName$ AND (

'Domain' = $\NULL$ OR 'Domain' = "") AND ( 'SerialNumber' != $\NULL$
AND 'HostName' != $\NULL$)
( 'HostName' != $\NULL$ AND 'Domain' != $\NULL$ ) AND ( 'HostName' =

$HostName$ AND 'Domain' = $Domain$ )
'HostName' = $HostName$ AND 'PrimaryCapability' = "Server" AND (

'HostName' != $\NULL$ AND 'SerialNumber' = $\NULL$ ) AND ( 'Domain' =
$\NULL$ OR 'Domain' = "")
'SerialNumber' = $SerialNumber$ AND SerialNumber' != $\NULL$

AND'PrimaryCapability' != "Server"
BMC_DiskDrive 'TokenId' = $TokenId$ AND 'TokenId' != \"0\" AND 'ClassId' =
\"BMC_DiskDrive\"
BMC_FloppyDrive 'TokenId' = $TokenId$ AND 'TokenId' != \"0\" AND 'ClassId' =
\"BMC_FloppyDrive\"
BMC_IPEndpoint 'TokenId' = $TokenId$ AND 'TokenId' != "0" AND 'ClassId' =
"BMC_IPENDPOINT"
BMC_LocalFileSystem 'TokenId' = $TokenId$ AND 'TokenId' != "0" AND 'ClassId' =
"BMC_LOCALFILESYSTEM"
BMC_Monitor 'TokenId' = $TokenId$ AND 'TokenId' != "0"
BMC_NetworkPort 'TokenId' = $TokenId$ AND 'TokenId' != "0"
('TokenId' = "0" OR $TokenId$ = "0") AND 'Name' = $Name$
BMC_OperatingSystem 'TokenId' = $TokenId$ AND 'TokenId' != "0"
BMC_Patch 'TokenId' = $TokenId$ AND 'TokenId' != "0"
'Name' = $Name$ AND 'NameFormat' = "Name"
BMC_Printer 'TokenId' = $TokenId$ AND 'TokenId' != "0" AND 'ClassId' = "BMC_PRINTER"
BMC_Processor 'TokenId' = $TokenId$ AND 'TokenId' != "0"
BMC_Product 'TokenId' = $TokenId$ AND 'TokenId' != "0"
'NameFormat' = $NameFormat$ AND 'Name' = $Name$
'Model' = $Model$ AND 'VersionNumber' = $VersionNumber$ AND
('InstallLocation' like "" OR 'InstallLocation' = $\NULL$)
'Model' = $Model$ AND 'InstallLocation' = $InstallLocation$ AND
('VersionNumber' like "" OR 'VersionNumber' = $\NULL$)
BMC_Persona 'ClassId' = "BMC_PERSON" AND 'TokenId' = $TokenId$ AND 'TokenId' != "0"
'ClassId' = "BMC_PERSON" AND 'Name' = $Name$ AND 'NameFormat' =
"UserName"
Understanding the merge activity
a
The BMC Identity Discovery product has precedence over the classes discovered by the Scanner Service.
If the BMC Asset dataset contains no matching instance, the Reconciliation Engine
creates a new instance in BMC Atrium CMDB, as shown in Figure 3 on page 37.
Figure 3 Reconciling datasets
Understanding the merge activity

After the Reconciliation Engine identifies the data, it merges it into the BMC Asset
dataset. Matching instances become a single instance that represents the computer
system. CIs that do not match a BMC Asset instance become new instances.
The merge activity compares precedences between a source dataset and the BMC
Asset dataset, chooses the data with the highest precedence, and writes that data to
the BMC Asset dataset. You can specify precedence at the dataset, the class, or the
attribute level.
EXAMPLE
Assume that the BMC Configuration Import dataset shows that computer system A has no
CDROM drive, while the BMC Topology Import dataset shows that it does. The merge activity
populates the BMC_CDROMDrive attribute in the BMC Asset dataset with the BMC
Foundation Discovery and Topology Discovery value, because any value takes precedence
over a null value.

Understanding the purge activities
For more information about the reconciliation process, see the BMC Atrium CMDB
Installation and Configuration Guide.
Understanding the purge activities

Purge activities remove instances from the import datasets that have been marked for
deletion. When the Scanner Service no longer discovers an existing CI, a BMC Atrium
Integrator data exchange marks the instance as Deleted. The data exchanges that
handle deletion are similar to those that transfer new and updated configuration data
from the Inventory database. The data exchanges that mark deleted items have names
beginning with Pull_Keys_ars_inv, and by default they run every 24 hours.
If a computer system is deleted, BMC Atrium Integrator also sets the MarkAsDeleted
flag for the components related to the computer system. These related components
remain deleted until a purge job runs in BMC Asset and purges them. A discovery
source can rediscover a computer or component in the future and enter a new record
for it. If the TokenId of a rediscovered component matches that of a deleted record,
and the BMC Asset purge job has not yet run, BMC Asset can reinstate a deleted
record.
For more information about marking CIs for deletion, see the BMC Atrium CMDB
Installation and Configuration Guide.
Chapter
2
2 Installing the integration module
This chapter describes how to install, uninstall, and upgrade the BMC BladeLogic
Client Automation Configuration Discovery Integration for CMDB (Configuration
Discovery Integration for CMDB) program.
This chapter presents the following topics:
Estimating storage requirements for BMC BladeLogic Client Automation discovered

data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Installing Configuration Discovery Integration for CMDB . . . . . . . . . . . . . . . . . . . . . . 41
Upgrading Configuration Discovery Integration for CMDB . . . . . . . . . . . . . . . . . . . . 46
Uninstalling Configuration Discovery Integration for CMDB . . . . . . . . . . . . . . . . . . . 50
Estimating storage requirements for BMC

BladeLogic Client Automation discovered data
This section describes how to estimate the BMC Atrium CMDB storage requirements
for the data discovered by BMC BladeLogic Client Automation Scanner Service. You
can estimate storage requirements by using the following factors:
■ number of rows in the BMC BladeLogic Client Automation database views

■ classes of data that you want to import
■ level of detail (number of fields) for each CI
To estimate the storage requirements per CI
1 Import a subset of data from a set of computers that are representative of the
general computer makeup of the company.
2 Obtain the CMDB data size.

Estimating storage requirements for BMC BladeLogic Client Automation discovered data
3 From the data size, derive the storage requirements per CI.
EXAMPLE
If the Acme company’s CMDB requires 50 GB for 6 million imported CIs, the storage per CI is
as follows: 50 GB/6 million = 8 KB
With one full database backup, six daily incremental backups, and transaction log backups
online, you can recover a database in the worst situation (the database is corrupted on the day
before a full database backup is performed). If Acme follows this practice, it needs an
additional 75 GB as follows:
■ 50 GB for full database backup space
■ 15 GB (daily change rate at 5% [2.5 GB daily * 6 days]) for incremental database backup
space
■ 10 GB transaction log space
Acme also needs extra capacity for database backup file swapping (that is, space required to
perform a full database backup before it can delete the previous set of online backup files).
With all the preceding considerations, the needed capacity is as follows:
■ 50 GB (CMDB)
■ 50 GB (database growth and other non-predictable needs)
■ 75 GB (weekly database files)
■ 50 GB (most current database backup files)
Total = 225 GB
Compare the 8 KB used in this example with your storage requirements per CI and then
derive your BMC Atrium CMDB storage requirements. After this, perform the same exercise
for the other data sources that will populate BMC Atrium CMDB.
Installing Configuration Discovery Integration for CMDB
Installing Configuration Discovery Integration

for CMDB
The procedures in this section describe how to perform a fresh installation of the
Configuration Discovery Integration for CMDB program or an upgrade from an
earlier version. Before you begin the installation process, you must create a plug-in to
enable software title usage data in the BMC Atrium CMDB using Federation
Manager, and download the installation files.
Before you begin
Verify that you have completed the following prerequisite tasks:
Note:
Install the Atrium Integrator server component on the same computer on which the
AR System server and BMC Atrium CMDB are installed. Since the Atrium Integrator
server allows you to connect to remote repositories, you need not separately install
the Atrium Integrator client on the same computer.
■ Installed the required products and components listed in Table 7.
Table 7 Prerequisite products and components

Prerequisite products Version Description
BMC BladeLogic Client ■ 8.3.00 Discovers configuration items (CIs) in
Automation your environment and stores them in
the Inventory database.
(BMC Configuration
Automation for Clients) To select the Software Title Discovery
option for the SQL Server platform,
ensure that the SQL Server Agent is
running on the Inventory database.
BMC Remedy AR System ■ 8.1.00 Provides the AR System platform and
the corresponding Approval Server and
■ 8.0.00 Assignment Engine.
BMC Atrium CMDB ■ 8.1.00 Provides the BMC Configuration Import
dataset and the Reconciliation Engine.
■ 8.0.00
BMC Atrium Integrator ■ 8.1.00 Transfers CIs from the external data
store into BMC Atrium CMDB.
■ 8.0.00
For more information about installing these products and components, see the
appropriate product documentation on the BMC Customer Support website at
http://www.bmc.com/support.

■ Filled in the worksheet in Table 8 on page 42, which contains the information for
which you will be prompted during installation.
Table 8 Configuration Discovery Integration for CMDB installation worksheet

Parameters Description Enter your information
BMC AI Details window
AR Server The name of the BMC Remedy AR System
server hosting the BMC Atrium Integrator
and CMDB is running.
AR Port Number The BMC Remedy AR System server port
number for the BMC Atrium Integrator and
CMDB is running.
AR User Name The BMC Remedy AR System server user
account name for the BMC Atrium
Integrator data exchange application. This
user must have administrator privileges.
AR Password The BMC Remedy AR System server
password for the BMC Atrium Integrator
and CMDB.
BMC Config. Mgmt. Details window
Machine Name or IP Address The name and port number of the computer
CMS Port Number hosting the BMC BladeLogic Client
Automation Common Management Services
(CMS). This computer enables federated
applications like BMC BladeLogic Client
Automation CMS to connect to BMC Atrium
CMDB and display details about CIs
BMC CM Config. Discovery (CD) Database Details window
Machine Name or IP Address The name of the server hosting the Microsoft
SQL Server or Oracle® database.
Database Name The name of the SQL Server database that
(SQL Server only) contains BMC BladeLogic Client
Automation discovered data.
Database Port The port number of the database server
hosting the SQL Server or Oracle database.
System ID The system ID associated with a specific
(Oracle only) instance of an Oracle database.
Inventory User Password The password for the Inventory user that
you created in BMC BladeLogic Client
Automation.
System Administrator User The user account name for the SQL Server or
Name Oracle database.
System Administrator Password The password for the SQL Server or Oracle
database.
To locate and download Configuration Discovery Integration for CMDB
1 Navigate to the BMC Customer Support website at

http://www.bmc.com/support.
2 Download the Configuration Discovery Integration for CMDB installer file

(CDIInstaller.exe) to a temporary folder.
To install Configuration Discovery Integration for CMDB
1 Navigate to the temporary folder, and double-click CDIInstaller.exe.
2 On the Introduction window, click Next.
3 On the License Agreement window, select I accept the terms of the license agreement,
and click Next.
4 On the Choose Install Folder window, accept the default installation directory, or
click Choose to select another directory, and click Next.
5 To install the Configuration Discovery Integration for CMDB program, perform

the following actions; otherwise, skip to step 6 to download only the utilities.
A Select Install BMC Configuration Discovery Integration (CDI) 8.3.00 and click Install.
B Skip to step 7.
6 To download only the utilities for the Configuration Discovery Integration for
CMDB, perform the following actions:
A Select Only Download the BMC Configuration Management Discovery Integration

8.3.00 Utilities to download product uninstall utilities, and click Install.
B On the BMC Configuration Discovery Integration (CDI) 8.3.00 Utilities

Downloaded Completed window, click Done.
7 On the BMC Atrium CMDB Details window, fill in the BMC Atrium CMDB
settings, and click Next.
8 On the BMC Config. Mgmt. Details window, fill in the required text boxes, and
click Next.
9 On the BMC CM Config. Discovery (CD) Database Details window, accept the
default to use Microsoft SQL Server as your BMC BladeLogic Client Automation
database, or select Oracle to use an Oracle database, and click Next.

10 On the BMC CM Config. Discovery (CD) Database Details window, fill in the
required database settings, and click Next.
11 On the Install BMC Config. Discovery Integration (CDI) Schema 8.3.00 window,
accept the default to install schemas (views) on the discovered data in the BMC
BladeLogic Client Automation database or select No, and click Next.
12 On the Install BMC Config. Discovery Integration (CDI) Schema 8.3.00 window,
select the discovery method to use, and click Next.
■ If this is a fresh installation of Configuration Discovery Integration for CMDB,

select Software Title Discovery. You must select this option to federate software
title usage data in the BMC Atrium CMDB.
■ If this is an upgrade from an earlier version of Configuration Discovery

Integration for CMDB, see “Upgrading Configuration Discovery Integration for
CMDB” on page 46 for more information about application discovery methods.
13 On the Choose Categorization practice window, select Best Practice Categorization.
NOTE
If you have previously transferred data into BMC Atrium CMDB or you are using the
BMC Foundation Discovery and Topology Discovery 1.4.00 product as a discovery tool,
you must select Default product categorization (BMC BladeLogic Client Automation
and BMC Foundation Discovery and Topology Discovery must use the same product
categorization scheme).
14 Click Next, and skip to step 15 on page 44.
15 On the Pre-Installation Summary window, review your installation choices and if

necessary, use the Previous and Next buttons to navigate the installation windows
and change settings.
16 Click Install.
A dialog box appears saying that the schemas were installed successfully.
17 Click OK.
18 On the BMC Configuration Discovery Integration Install Complete window, click

Done.
If errors occurred during the installation, you can use the installation log file to
troubleshoot the problems. You can find the installation log at the following
location:
C:\Program Files\BMC Software\CDI\8.3.00\install.log
During installation, the Configuration Discovery Integration for CMDB

installation program creates data exchanges and data mappings in BMC Atrium
Integrator for the CI classes and relationship classes that are discoverable by the
Scanner Service. The Transformation for each of the classes form a set consisting of
Pull_ars_inv_*, Pull_Keys_ars_inv_*, and Machine-* Relationship viewed in

Pentaho tool under Import.Config.Dataset repository.
NOTE
By default, the CDI_INVDB_JOBS andCDI_INVDB_DELETE_JOBS jobs created by
Configuration Discovery Integration for CMDB are not scheduled. Before scheduling, go to
Spoon tool and disable the hobs of unwanted transformation so that corresponding classes
will not get populated in CMDB. It is recommended to schedule
CDI_INVDB_DELETE_JOBS once in a week for better performance. For better
performance, it is recommended to enable the Use Cache checkbox in CMDBOutput step
in PULL_ARS_INV_* Transformation.
You can use the BMC Atrium Integrator log files to verify that the data transfer
between the Inventory database and BMC Atrium CMDB completed successfully.
On computers running the Microsoft Windows operating system, the log files are
stored in the following folder:
C:\Program Files\BMC Software\ARSystem\Arserver\Db\arcarte.log
You can also view the required information from UDM:TransformationLog and
UDM:JobLog for Transformation and jobs related log.
For more information about logging and debugging, see the BMC Atrium
Integrator Core Guide.
To enable a plug-in to access software title usage data in the BMC Atrium
CMDB using Federation Manager
1 Log on to the AR System mid tier console.
2 In the Atrium Core Console, choose Applications => Federation Manager.
3 On the Plugin page, select BCAC_DISCOVERY_PLUGIN, and click Show XML and
copy the content.
Note: If the inventory password is changed after installing CDI, then you must
change the password in BBCA_Discovery_Plugin.
4 Paste the XML content in the pluginsvr_config.xml file:

Classes extended during CDI installation
A Using a text editor, open the following file: installDirectory\BMC

Software\AtriumCore\cmdb\plugins\shared\pluginsvr_config.xml.
B In the pluginsvr_config.xml file, locate the following commented lines:


C Paste the XML content between the two commented lines, and save the file.
5 Restart the AR System server and the Tomcat web server.
Classes extended during CDI installation

During installation of CDI, CDI uses the CMDB Extension loader to extend the
attributes of the classes listed in the following table.
Class name Attribute name Max length fieldId

BMC_Software InstallLocation unlimited (0) 530035000
BMC_BaseElem CDIntegrationID 64 530008700

ent
BMC_BaseElem CDMachineID 64 530008600
ent
BMC_BaseElem DictionaryId 255 530035200
ent
BMC_BaseElem BCAC_Integration_ID 254 530060000
ent
Upgrading Configuration Discovery

When upgrading from an earlier version of Configuration Discovery Integration for
CMDB, you need to determine how to handle changes that were made to the
discovery methods in more recent versions of the module.
Upgrading Configuration Discovery Integration for CMDB
For more information about the different application discovery methods, see “How
application discovery works in BMC BladeLogic Client Automation” on page 25.
During the upgrade, you must select an application discovery method for data that
will integrate with the CMDB.
■ If you select Software Title Discovery, the preferred method, you lose all existing
application discovery data in the CMDB. The lost data is eventually replaced with
the new software titles, but if you had tickets assigned to the corresponding CIs,
you break those associations. If you select this method, you must also install the
Software Usage schema.
Should you choose this option and then decide that you want to revert to the older
method of integrating data, you must uninstall and then reinstall the
Configuration Discovery Integration for CMDB module.
■ If you select Application Discovery, the data integration process does not change.
Before you begin
Upgrade the BMC Remedy AR System, BMC Atrium CMDB, BMC Atrium
Integrator, and BMC Asset Management prerequisite products to the versions shown
in Table 9 on page 47.
Table 9 Prerequisite products and components

Prerequisite products Version Description
BMC BladeLogic Client ■ 8.3.00 Discovers configuration items (CIs) in
Automation your environment and stores them in
the Inventory database.
BMC Remedy AR System ■ 8.1.00 Provides the AR System platform and
■ 8.0.00 the corresponding Approval Server and
Assignment Engine.
BMC Atrium CMDB ■ 8.1.00 Provides the BMC Configuration Import
■ 8.0.00 dataset and the Reconciliation Engine
BMC Atrium Integrator ■ 8.1.00 Transfers CIs from the external data
■ 8.0.00 store into BMC Atrium CMDB
■ Export NGIE: Delta in CSV. If upgrading from AIE to AI then get all delta from
corresponding DataExchange like PULL_ARS_INV_* and store it in file.

To upgrade Configuration Discovery Integration for CMDB
1 Uninstall your currrent version of Configuration Discovery Integration for CMDB

as described in the next section.
2 Run the installation program as described in “Installing Configuration Discovery

Integration for CMDB ” .
3 Upgrade the BMC BladeLogic Client Automation infrastructure service, the

transmitter, and the other channels (including the Scanner Service) to 8.3.00. For
more information about the upgrade process for BMC BladeLogic Client
Automation components, see the BMC BladeLogic Client Automation Installation
Guide.
4 Using the BMC BladeLogic Client Automation 8.3.00 Schema Manager, upgrade
the Inventory schema.
5 Install Configuration Discovery Integration for CMDB 8.3.00 using the steps under
“Installing Configuration Discovery Integration for CMDB ”.
To enable a plug-in to access software title usage data in the BMC Atrium
CMDB using Federation Manager
1 Log on to the AR System mid tier console.
2 In the Atrium Core Console, choose Applications => Federation Manager.
3 On the Plugin page, select BCAC_DISCOVERY_PLUGIN, and click Show XML and
copy the content.
4 Paste the XML content in the pluginsvr_config.xml file:
A Using a text editor, open the following file: installDirectory\BMC

Software\AtriumCore\hostName\cmdb\plugins\shared\pluginsvr_config.xml.
B In the pluginsvr_config.xml file, locate the following commented lines:


C Paste the XML content between the two commented lines, and save the file.
5 Restart the AR System server and the Tomcat web server.
To perform post-upgrade tasks
1 Rerun the BMC BladeLogic Client Automation Scanner Service on all endpoints.
2 Launch BMC Atrium Integrator.
3 Navigate to NGIE:Delta form and type PULL_ARS_INV_% in TrasName field.
4 Click Search.
5 From the search results, modify the Ar delta field with value taken before upgrade
so that data will be pulled or updated based on Ar Delta(last_modified_time).
6 Deactivate the appropriate transformation by disabling hobs. For more information, refer
http://wiki.pentaho.com/display/EAI/.06+Hops.
7 Navigate to Mid-tier->Atrium integrator, and schedule CDI_INVDB_JOBS.
8 Schedule CDI_INV_DELETE_JOBS to once in a week.
9 Launch BMC Atrium CMDB.
10 Run the Reconciliation Engine, and verify the data in the BMC BladeLogic Client
Automation database, the BMC Import Configuration dataset, and the BMC Asset
dataset.
NOTE
By default, the CDI_INVDB_JOBS andCDI_INVDB_DELETE_JOBS jobs created by
Configuration Discovery Integration for CMDB are not scheduled. Before scheduling, go to
Spoon tool and disable the hobs of unwanted transformation so that the corresponding
classes will not get populated in CMDB. It is recommended to
schedule CDI_INVDB_DELETE_JOBS once in a week for better performance.For better

performance, it is recommended to enable Use Cache checkbox in CMDBOutput step in
PULL_ARS_INV_* Transformation.

Uninstalling Configuration Discovery Integration for CMDB
Uninstalling Configuration Discovery

The following procedure describes how to uninstall Configuration Discovery
Integration for CMDB.
Note:
■ If you are upgrading from CDI 8.2.00 or earlier, refer older version of CDI
documentation to uninstall CDI.
To uninstall Configuration Discovery Integration for CMDB
1 Navigate to C:\Program Files\BMC Software\CDI\8.3.00\.
2 Double-click Uninstall Configuration Discovery Integration.exe.
3 On the Uninstall Configuration Discovery Integration window, click Next.
4 On the BMC (AI) Details window, perform the following actions, and click Next:
A Accept the current value or type the name of the AR System server hosting the
BMC Atrium Integrator and CMDB in AR Server.
B In AR Port Number, type the appropriate port number.
C In AR User Name, accept the current value or type the user account name for the
BMC Atrium Integrator data exchange application.
D In AR Password, type the password for the BMC Atrium Integrator data
exchange server account.
5 On the Uninstall BMC Config. Discovery Integration Schema 8.3.00 window, select
one of the following options, and click Next.
■ Accept the default to uninstall schemas (views) on the discovered data in the
Inventory database.
■ Select No to manually uninstall the schema.
6 On the BMC CM Config. Discovery (CD) Database Details window, accept the
default to use SQL Server as your BMC BladeLogic Client Automation Inventory
database, or select Oracle to use an Oracle database, and click Next.
7 Complete one of the following actions:
■ If you accepted the default to use a SQL Server database on the BMC CM
Configuration Discovery (CD) Database Details window, complete the
following steps:
A In Machine Name or IP Address, accept the default value, or type the name of the
server hosting the SQL Server database.
B In Database Name, accept the default, or type the name of the database that
contains BMC BladeLogic Client Automation discovered data.
C In Database Port, accept the default value, or type the port number you want to
use for the database server hosting the SQL Server database.
D In System Administrator User Name, accept the default value, or type the user
account name you want to use for the SQL Server database.
E In System Administrator Password, type the password for the SQL Server
database.
F Skip to step 8 on page 51.
■ If you decided to use an Oracle database on the BMC CM Configuration

Discovery (CD) Database Details window, complete the following steps:
A In Machine Name or IP Address, accept the default value, or type the name of the
server hosting the Oracle database.
B In System ID, accept the default value, or type the system identifier for the Oracle
database.
C In Database Port, accept the default value, or type the port number you want to
use for the database server hosting the Oracle database.
D In System Administrator User Name, accept the default value, or type the user
account name you want to use for the Oracle database.
E In System Administrator Password , type the password for the Oracle database.
8 Click Uninstall.
A dialog appears saying that the schemas were uninstalled successfully.
9 Click OK.
10 On the BMC Configuration Discovery Integration (CDI) 8.3.00 Uninstallation

completed successfully window, click Done.

If errors occurred that prevented the program from completely uninstalling the
program, you can use the log file to troubleshoot the problem. You can find the log
file at the following location:
C:\Program Files\BMC Software\CDI\8.3.00\uninstall.log
Chapter
3
3 Customizing the integration
This chapter describes how to customize BMC BladeLogic Client Automation
Configuration Discovery Integration for CMDB (Configuration Discovery Integration
for CMDB) for your environment.
This chapter presents the following topics:
Improving data transfer performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Improving scanning performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
......................................................................... 55
Filtering import data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Filtering by application name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Filtering by application location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Improving data transfer performance

You can increase the data transfer speed between the external data store and BMC
Atrium Configuration Management Database (BMC Atrium CMDB) by splitting jobs
into multiple jobs and running them separately.
When you split an existing job to run as multiple BMC Atrium Integrator Jobs, you
must configure the Transformation Pull_ars_inv_machine to run first and then trigger
all other transformations.
In addition, for example, certain Transformation such as those for patches or

applications might process more data than other transformations and hence these
transformations should be run on separate Jobs.
Table 10 shows one way to create jobs and group transformation.

Improving scanning performance
Table 10 Example of configuring transformations and jobs

Job Transformations triggered upon completion
Application job Pull_ars_inv_machine
Pull_ars_inv_application
Machine-Application Relationship
For more information about how to create Jobs and Transformation, see the BMC
Atrium Core Guide.
Improving scanning performance

The BMC Atrium Integrator key used to insert, update, and delete discovered data in
the BMC BladeLogic Client Automation database is the value of the seq_id attribute.
Seq_id is a sequence number generated by BMC BladeLogic Client Automation.
Using seq_id to insert, update, and delete data reduces database performance
(especially during a full scan) because the same set of data gets deleted and
reinserted, this time with different seq_ids.
To improve performance, the seq_id attribute has been replaced with a combination
of one or more key attributes for each class, as shown in Table 11.
Table 11 Key attributes used for inserting, updating, and deleting (part 1 of 2)
Class Key attributes used for inserting, updating, and deleting
BMC_ComputerSystem mrb_inv_machine.machine_id
BMC_OperatingSystem mrb_inv_os.machine_id; mrb_inv_os.name
BMC_Product mrb_inv_application.machine_id;
mrb_inv_application.CMDBName
BMC_Person mrb_inv_person.CMDBName
BMC_NetworkPort mrb_inv_networkcard.machine_id;
mrb_inv_networkcard.interface_name;
mrb_inv_networkcard.mac_address
BMC_IPEndpoint mrb_inv_network.machine_id; mrb_inv_network.address
BMC_CDROMDrive; mrb_inv_storage.machine_id; mrb_inv_storage.device_id
BMC_FloppyDrive;
BMC_DiskDrive;
BMC_LocalFileSystem
BMC_Processor mrb_inv_processor.machine_id;
mrb_inv_processor.device_id
BMC_Monitor mrb_inv_monitor.machine_id; mrb_inv_monitor.device_id
BMC_Card mrb_inv_videocard.machine_id;
mrb_inv_videocard.device_id
Filtering import data
Table 11 Key attributes used for inserting, updating, and deleting (part 2 of 2)
Class Key attributes used for inserting, updating, and deleting
BMC_BIOS mrb_inv_bios.machine_id;
mrb_inv_bios.device_id
BMC_Printer mrb_inv_printer.machine_id;
mrb_inv_printer.device_id
BMC_Patch mrb_inv_patch.machine_id; mrb_inv_patch.CMDBName
With this replacement in key attributes, a full scan results in a BMC Atrium Integrator
update operation (based on the value of the last_modified_time attribute) rather than
a more costly (in terms of performance) delete and insert operation.
Filtering import data

The BMC BladeLogic Client Automation database contains two tables that enable you
to restrict the data that is imported into BMC Atrium CMDB:
■ application_bsm and app_location_bsm
These tables are installed in the BMC BladeLogic Client Automation database
when you install Configuration Discovery Integration for CMDB.
■ Application_bsm
This table lists the applications that you plan to import. App_location_bsm lists the
directory paths to these applications to make sure only one CI for each application
suite is imported.
Filtering by application name

A large number of applications might be scanned by BMC BladeLogic Client
Automation and saved in the BMC BladeLogic Client Automation database.
However, you might be interested in only a subset of these applications. In this case,
you can specify which applications to import using the application_bsm table.

Filtering by application location
To filter applications by name
1 Log in to the BMC BladeLogic Client Automation database.
2 Run the appropriate SQL command to filter the applications you want to import.
For example, for all applications with names that start with Microsoft or Adobe,
use the following SQL command:
"insert into application_bsm (select distinct product from mrb_inv_application where

product like ‘Microsoft%’ or product like ‘Adobe%’)"
This SQL command queries mrb_inv_application and retrieves all applications

whose product names start with Microsoft or Adobe. Duplicate entries are
eliminated and the product names are inserted into application_bsm.
3 Log in to BMC Remedy User.
4 In the Quick Links bar of the Home page, click AIE Console.
5 On the Data Exchange Console, click CI Class Mappings in the navigation bar.
6 On the CI Class Mapping Console, double-click the

PULL_ARS_INV_APPLICATION data mapping.
7 On the CI Class Mapping Information dialog, select the Query tab.
8 In External Data Store Query on the Data Key Query tab, add the following query:
"Product in (select * from application_bsm)"

For any one application, there can be multiple CIs discovered. The app_location_bsm
table specifies one location (or representative CI) of an application, and eliminates
duplicate listings.
To filter applications by location
1 Log in to the BMC BladeLogic Client Automation database.
2 Use the following SQL command to populate app_location_bsm:
"insert into app_location_bsm (select distinct product, location from mrb_inv_application

where location like ‘xxx%’)"
Replace xxx with the application path. For example:
C:\Program Files\Microsoft Office\OFFICE11\Winword.exe
Add additional or statements as needed for each application path.
3 Log in to BMC Remedy User.
4 In the Quick Links bar of the Home page, click AIE Console.
5 On the Data Exchange Console, click CI Class Mappings in the navigation bar.
6 On the CI Class Mapping Console, double-click the

PULL_ARS_INV_APPLICATION data mapping.
7 On the CI Class Mapping Information dialog, select the Query tab.
8 In External Data Store Query on the Data Key Query tab, add the following query:
"Location in (select location from app_location_bsm)

Appendix
A
Key attributes populated for
A
identifying configuration items

During the identification phase of the reconciliation process, if the TokenId attribute
is unqualified, additional best-match identification rules try to match other key
attributes. Table 12 shows how these other key attributes are populated for the classes
that BMC BladeLogic Client Automation can discover. The Key attributes column
lists the attributes in the order in which they are tested in the identification rules.
Based on the operating system, the key attributes are populated as follows:
■ For computers running a Microsoft Windows operating system, WMI calls and
registry fields collect the information. WMI scanning technology serves as a basis
for creating TokenIds by each discovery source.
■ For computers running a UNIX operating system (Linux®, Sun Solaris™, HP-UX,
and IBM® AIX), system calls and system commands collect the information. In
some cases, the platform, class, or key attribute does not support UNIX-based
system calls.
Table 12 Key attributes used to populate the TokenId (part 1 of 8)

Class Key attributes OS Key attribute value populated with Comments
TokenId Windows VersionNumber (Win32_Bios.Version)
BMC_BIOSElement
UNIX BIOS name

Name Windows Win32_Bios.Name
UNIX BIOS name
NameFormat All BiosName
ShortDescription Windows Win32_Bios.Name
UNIX BIOS name

TokenId Windows Win32_VideoController.DeviceID
BMC_Card
UNIX Logical name (DeviceID) On UNIX, only BMC

BladeLogic Client
Automation
discovers video
cards.
Name Windows Win32_VideoController.DeviceID
UNIX Logical name
NameFormat All DeviceID
ShortDescription Windows Win32_VideoController.Description
Win32_VideoController.Caption
Win32_VideoController.Caption BMC Foundation
Discovery and
Topology Discovery
(when the card type
is VideoCard).
UNIX Logical name (DeviceID)
TokenId Windows DeviceID
BMC_CDROMDrive
UNIX Logical name

Name Windows Win32_CDROMDrive.DeviceID
UNIX Logical Name
ShortDescription Windows Win32_CDROMDrive.Name
Win32_CDROMDrive.Caption
Win32_CDROMDrive.Caption BMC Foundation
Discovery and
Topology Discovery.
UNIX Logical name
TokenId All HostName:Domain
BMC_ComputerSystem
Name All 1. HostName:Domain Both BMC

BladeLogic Client
Automation and
BMC Foundation
Discovery and
Topology Discovery.
All 2. HostName If Domain is empty
or NULL BMC
BladeLogic Client
Automation only.
All 3. FQN (fully-qualified domain name BMC Foundation
resolved by the DNS server) Discovery and
Topology Discovery
only.
All 4. IP Address BMC Foundation
Discovery and
Topology Discovery
only.
NameFormat All 1. Token Pairs with Name
value 1.
All 2. HostName Pairs with Name
value 2.
All 3. DNS Pairs with Name
value 3.
All 4. IP Pairs with Name
value 4.
ShortDescription All 1. HostName Pairs with
NameFormat 2.
3. FQN (fully-qualified domain name Pairs with
resolved by the DNS server) NameFormat 3.
4. IP address Pairs with
NameFormat 4.
BMC_DiskDrive
UNIX Logical name

Name Windows Win32_DiskDrive.DeviceID
UNIX Logical Name
ShortDescription Windows Win32_DiskDrive.Name
Win32_DiskDrive.Caption
Win32_DiskDrive.Caption BMC Foundation
Discovery and
Topology Discovery.
UNIX Logical name

BMC_FloppyDrive
UNIX Logical name

Name Windows Win32_FloppyDrive.DeviceID
UNIX Logical Name
NameFormat all DeviceID
ShortDescription Windows Win32_FloppyDrive.Name
Win32_FloppyDrive.Caption
Win32_FloppyDrive.Caption BMC Foundation
Discovery and
Topology Discovery.
UNIX Logical name
TokenId All IP Address
BMC_LocalFileSystem BMC_IPEndpoint
Name All IP Address

NameFormat All IP
ShortDescription All IP Address
TokenId Windows Win32_LogicalDisk.DeviceID Such as C:.

UNIX Full path name of the device Such as
/dev/dsk/c0t0d0s0.
Name Windows Win32_LogicalDisk.DeviceID
UNIX Logical Name
NameFormat DeviceID
ShortDescription Windows Win32_LogicalDisk.Name
Win32_LocalFileSystem.Caption
Win32_LocalFileSystem.Caption BMC Foundation
Discovery and
Topology Discovery.
UNIX Logical name
TokenId Windows Win32_DesktopMonitor.DeviceID
BMC_Monitor
UNIX Logical name (DeviceID) On UNIX, only BMC

BladeLogic Client
Automation
discovers monitors.
Name Windows Win32_DesktopMonitor.DeviceID
UNIX Logical name
ShortDescription Windows Win32_DesktopMonitor.Description
Win32_DesktopMonitor.Caption
Win32_DesktopMonitor.Caption BMC Foundation
Discovery and
Topology Discovery.
UNIX Logical name (DeviceID)
TokenId All Interface Name:Mac Address If the MAC address
BMC_NetworkPort
or interface name
cannot be retrieved,
the TokenId should
not be populated
and the best-match
attributes should be
used for
identification.
If the MAC address
is not available, do
not populate the
configuration item
(CI).
Name All Mac Address MAC address
format: [0-9,A-F][0-
9,A-F][0-9,A-F][0-
9,A-F][0-9,A-F][0-
9,A-F]. Example:
a:b:0:0:cc:ad is
represented as
0A0B0000CCAD.
NameFormat All MACAddress
ShortDescription All Interface Name

TokenId Windows Win32_OperatingSystem.Name
BMC_OperatingSystem
UNIX Operating system name

Name All Name
NameFormat Windows OSName:SystemDirectory:DeviceName
UNIX OSName
ShortDescription Windows Win32_OperatingSystem.Name
Win32_OperatingSystem.Caption
Win32_OperatingSystem.Caption BMC Foundation
Discovery and
Topology Discovery.
UNIX Logical name
TokenId All Repository_Id
BMC_Patch
(BMC BladeLogic (if the BMC BladeLogic Client

Client Automation Automation Patch Service is installed)
only) or
ServicePackInEffect:HotFixID
(HotFixID is from
Win32_QuickFixEngineering)
TokenId Windows ServicePackInEffect:HotFixID (from
(BMC Foundation Win32_QuickFixEngineering)
Discovery and (if Win32_QuickFixEngineering.Service
Topology Discovery PackInEffect is not null)
only) or
CSDVersion:HotFixID
(CSDVersion is from
Win32_OperatingSystem and HotFixID
is from Win32_QuickFixEngineering)
Name All TokenId (if non-NULL TokenId)
or
Name (if NULL)

NameFormat All Token (if non-NULL TokenId)
or
Name (if NULL)

ShortDescription All HotFixID
TokenId All UserName:Domain UserName is
BMC_Person
mandatory, and if
Domain is not
present, the TokenId
is not populated.
Only BMC
BladeLogic Client
Automation
discovers
BMC_Person.
Name All UserName:Domain (non-NULL
Domain)
or
UserName (NULL domain)
NameFormat All UserName:Domain (non-NULL
Domain)
or
UserName (NULL domain)
ShortDescription All UserName
TokenId Windows HostName:Win32_Printer.Name Local printer.
(BMC BladeLogic Client
BMC_Printer
Automation only)
UNIX HostName:Logical Name

Name Windows HostName:Win32_Printer.Name Local printer.
NameFormat All HostName:PrinterName
ShortDescription Windows HostName:Win32_Printer.Name Local printer.
TokenId All IP Address Network printer.

(BMC Foundation Discovery and
BMC_Printer
Topology Discovery only)
or
DNS Name
Name All IP Address Network printer.
or
DNS Name
NameFormat All IP (if Name is IP Address)
FQNQ (if Name is DNS)
ShortDescription All IP Address Network printer.
or
DNS Name

TokenId Windows Win32_Processor.DeviceID
BMC_Processor
UNIX Logical Name of that computer

Name Windows Win32_Processor.DeviceID
UNIX Logical Name
NameFormat Windows DeviceID
UNIX ProcessorName
ShortDescription All Win32_Processor.DeviceID
Win32_Processor.Name BMC Foundation
Discovery and
Topology Discovery
TokenId all ProductName:Version:InstallLocation InstallLocation is an
BMC_Product
install directory or
folder where the
product is installed
(not the location of a
binary executable).
Name UNIX Model:VersionNumber:InstallLocation BMC BladeLogic
or Client Automation
CDI and BMC
Model:VersionNumber (if Foundation
InstallLocation is not available) Discovery and
Topology Discovery
Windows Model:VersionNumber:InstallLocation BMC Foundation
or Discovery and
Model:VersionNumber (if Topology Discovery
InstallLocation is not available)
Windows ExecutableLocation BMC BladeLogic
Model:InstallLocation (if Version is not CDI on Windows
available
NameFormat UNIX ProductName:Version:InstallLocation BMC BladeLogic
Client Automation
CDI and BMC
Foundation
Discovery and
Topology Discovery
Windows ExecutableLocation BMC Foundation
or Discovery and
ProductName:Version Topology Discovery
Windows ExecutableLocation BMC BladeLogic
ProductName:InstallLocation CDI on Windows
ShortDescription All Product Name
Appendix
B
B BMC Atrium Integrator
This appendix contains detailed information about the BMC Atrium Integrator Jobs
and Transformation details created in BMC Atrium Integrator after installing BMC
BladeLogic Client Automation Configuration Discovery Integration for CMDB
(Configuration Discovery Integration for CMDB).
BMC Atrium Integrator job details

The BMC Atrium Integrator consists of the following two jobs:
■ CDI_INV_JOBS
■ CDI_INV_DELETE_JOBS
The CDI_INV_JOBS job consists of the PULL_INV_* AND MACHINE_* relationship

transformation.
BMC Atrium Integrator Transformation Details

This section provides details about the transformations the AI performs. The Atrium
Integrator pulls the subset of Configuration Discovery data exposed by BBCA Views.
This subset qualifies as Configuration Item (CI) data in the BMC Atrium CMDB. AI
transformations then map BBCA Views and columns to BMC Atrium CMDB classes
and attributes.
Transformations names have the prefix Pull_ars_ (for example,

Pull_ars_inv_machine). BBCA views have the prefix mrb (for example,
mrb_inv_machine). You can use the constant names in queries.

BMC Atrium Integrator Transformation Details
Table 13 Example of configuring transformation on five instances

Transformation Transformation triggered upon completion
Pull_ars_inv_machine Pull_ars_inv_application
Pull_ars_inv_bios
Pull_ars_inv_monitor
Pull_ars_inv_networkcard
Pull_ars_inv_os
Pull_ars_inv_patch
Pull_ars_inv_person
Pull_ars_inv_printer
Pull_ars_inv_processor
Pull_ars_inv_storage_CDROMDrive
Pull_ars_inv_storage_DiskDrive
Pull_ars_inv_storage_FloppyDrive
Pull_ars_inv_storage_LocalFileSystem
Pull_ars_inv_videocard
Pull_ars_inv_application Machine-Application Relationship
Pull_Keys_ars_inv_bios Machine-Application Relationship
Pull_ars_inv_monitor Machine-Monitor Relationship
Pull_ars_inv_network Machine-Network Relationship
NetworkCard-Network Relationship
Pull_ars_inv_networkcard Pull_ars_inv_network
Machine-NetworkCard Relationship
Pull_ars_inv_os Machine-OS Relationship
Pull_ars_inv_patch Machine-Patch Relationship
Pull_ars_inv_person Pull_Machine_Person_Relationship
Pull_ars_inv_printer Machine-Printer Relationship
Pull_ars_inv_processor Machine-Processor Relationship
Pull_ars_inv_storage_CDROMDrive Machine CDROMDrive Relationship
Pull_ars_inv_storage_DiskDrive Machine CDROMDrive Relationship
Pull_ars_inv_storage_FloppyDrive Machine FloppyDrive Relationship
BMC Atrium Integrator CI class mappings
Table 13 Example of configuring transformation on five instances

Transformation Transformation triggered upon completion
Pull_ars_inv_storage_LocalFileSystem Machine LocalFileSystem Relationship
Pull_ars_inv_videocard Machine-VideoCard Relationship
BMC Atrium Integrator CI class mappings

A CI Class data mapping defines how data in the source corresponds to data in the
target and which actions to take when transferring between them. This section
provides instructions for creating data mappings between an external data store and
the attributes of a BMC Atrium Configuration Management Database (BMC Atrium
CMDB) CI class.
Extensibility
You can add new fields to BBCA Views, and build your own AI mappings and data
exchanges to map data to CMDB attributes. If you map to existing CMDB classes
and attributes, you can implement relatively quickly. Otherwise, you can write a
CDM extension and create your own reconciliation rules.
Oracle data types

Except for two of the data types, varchar and datetime, the data types shown in this
appendix are applicable to both Oracle and SQL Server databases. The varchar and
datetime data types are specific to SQL Server. For Oracle, the corresponding data
types are varchar2 and date, respectively.
Defining primary keys

A primary key uniquely identifies a row of data. You must specify the attributes of
the CI class and the corresponding fields in the external data store that together make
up the primary key. After a data transfer, the primary key is the link that matches a
record in the external data store with its counterpart in BMC Atrium CMDB.
Defining data field mapping

You must define data field mappings to specify which fields or attributes should be
transferred during a data exchange.

Pull_ars_inv_machine
Pull_ars_inv_machine
CI Type: Computer System
Table 14 Primary Key Mapping

CMDB Class:BMC.CORE:BMC_ComputerSystem BBCA View: mrb_inv_machine
CDIntegrationID machine_id
Table 15 Data Field Mapping

CMDB Class:
BMC.CORE:BMC_ComputerSystem BBCA View: mrb_inv_machine Constant Value
DatasetId “BMC.IMPORT.CONFIG”
TokenId name:machine_domain
Model model
ManufacturerName manufacturer
ShortDescription name
Description description
Category category “Hardware”
Type Type "Machine or Processing
Unit"
Item Item “BMC Discovered or
Desktop or Server, Server”
Name CMDBName
NameFormat CMDBFormatName
CDMachineID machine_id
SerialNumber serial_number
TotalPhysicalMemory memory
Domain machine_domain
Workgroup domain
HostName name
isVirtual MachineStatus Yes/No
LastScanDate scantime
PrimaryCapability primary_capability
MarkAsDeleted No
External data store query

machine_id NOT IN (select machine_id from mrb_inv_machine where (name
= '' OR name IS NULL))
CI Type: Application

CMDB Class: BMC.CORE: BMC_Product BBCA View: mrb_inv_application
Name CMDBName
CMDB Class: BMC.CORE:BMC_Product BBCA View: mrb_inv_application Constant Value

TokenId CMDBToken
Model product
VersionNumber version
ShortDescription product
Category category “Software”a
Type Type "Applicationa"

Item item “BMC Discovered”a
NameFormat CMDBNameFormat
CDIntegrationID seq_id
InstallLocation location
DictionaryId DictionaryID
BCAC_Integration_ID machine_id:CMDBName
MarkAsDeleted No

Pull_ars_inv_Bios
a Definitive Media Library (DML) values prevail, and overwrite Category, Type, and
Item values
Pull_ars_inv_Bios
CI Type: BIOS

CMDB Class: BMC.CORE: BMC_Bios_Element BBCA View: mrb_inv_bios
CMDB Class: BBCA View: mrb_inv_bios Constant Value

BMC.CORE:BMC_Bios_Element
TokenId version
Model model
Category Category Software or
System Settings
Type type BIOS or Operating System
Software
Item item BMC Discovered or
Bios/Firmware
Name name
NameFormat BiosName
CDIntegration ID seq_id
CMDB Class: BBCA View: mrb_inv_bios Constant Value

BMC.CORE:BMC_Bios_Element
BuildNumber build_number
MarkAsDeleted No
CI Type: Monitor

CMDB Class: BMC.CORE:BMC_Monitor BBCA View: mrb_inv_monitor
Name device_id

CMDB BBCA View: mrb_inv_monitor Constant Value
Class:BMC.CORE:BMC_Monitor
DatasetId "BMC.IMPORT.CONFIG"
TokenID device_id
Model model
ShortDescription description
Category Category “Hardware”
Type Type "Monitor or Peripheral"
Item item BMC Discovered or
Monitor
Name device_id
NameFormat DeviceID
MarkAsDeleted No

Pull_ars_inv_network
Pull_ars_inv_network
CI Type: Network Port

CMDB Class: BMC.CORE:BMC_IPEndpoint BBCA View: mrb_inv_Network
Name address

CMDB BBCA View: Constant Value
Class:BMC.CORE:BMC_IPEndpoint mrb_inv_Network
TokenID address
ShortDescription address
Category category System Settings or
Miscellaneous
Type Type Network or Address
Item Item BMC Discovered or IP
Address
Name address
NameFormat “IP”
Address address
AddressType IPv4
MarkAsDeleted No
Pull_ars_inv_networkcard
CI Type: NetworkCard
Pull_ars_inv_os

CMDB Class: BMC.CORE: BMC_NetworkPort BBCA View: mrb_inv_networkcard
ShortDescription interface_name
PermanentAddress mac_address
CMDB BBCA View: Constant Value

mrb_inv_networkcard
Class:BMC.CORE:BMC_NetworkPort
TokenID interface_name:mac_address
Model model
Type Type Network or Card
Item Item BMC Discovered or
Network Interface Card
Name mac_address
NameFormat MACAddress
CDIntegrationID ip_address
NetworkAddresses mac_address
MarkAsDeleted No
Pull_ars_inv_os
CI Type: OperatingSystem

CMDB Class: BMC.CORE: BMC_OperatingSystem BBCA View: mrb_inv_OS
Name name

Pull_ars_inv_patch
CMDB BBCA View: mrb_inv_OS Constant Value

Class:BMC.CORE:BMC_OperatingSyste
m
DatasetId "BMC.IMPORT.CONFIG”
TokenID name
Model name
Category “System Settings or category
Software”
Type Type Operating System or
Operating System
Software
Item Item BMC Discovered or
Standard OS
Name name
NameFormat OSName:SystemDirectory:Dev
ice Name or OSName
SerialNumber serial_number
OSType name
MarkAsDeleted No
Pull_ars_inv_patch
CI Type: Patch

CMDB Class: BMC.CORE: BMC_OperatingSystem BBCA View: mrb_inv_OS
Name CMDBName
Pull_ars_inv_person
CMDB Class:BMC.CORE:BMC_Patch BBCA View: mrb_inv_patch Constant Value

TokenID CMDBToken
ShortDescription hot_fix_id
Description fix_description
Category category “System Settings or
Software”
Type type “Patch or Software
Application/ System”
Item item “BMC Discovered or
Patch”
NameFormat “Name or Token”
ServicePack fix_description
PatchNumber hotf_fix_id
MarkAsDeleted No
Pull_ars_inv_person
CI Type: Person

CMDB Class: BMC.CORE: BMC_Person BBCA View: mrb_inv_person
Name CMDBName
CMDB Class:BMC.CORE:BMC_Person BBCA View: mrb_inv_person Constant Value

TokenID CMDBToken
ShortDescription username

CMDB Class:BMC.CORE:BMC_Person BBCA View: mrb_inv_person Constant Value

CDIntegrationID person_id
FirstName firstname
LastName lastname
Email n/a
PersonDepartment n/a
CI Type: Printer

CMDB Class: BMC.CORE: BMC_Person a BBCA View: mrb_inv_person b
CMDB Class:BMC.CORE:BMC_Person a BBCA View: mrb_inv_person b Constant Value

TokenID hostname:name
Model model
Type type “Printer or Peripheral”
Item item “BMC Discovered or
Printer/Multifunction”
Name hostname:name
NameFormat “HostName:PrinterName”
CDIntegrationID ptr_id
a BMC_BMCPrinter is a new class in CMDB 2.0, and it is a sub class of

BMC_ComputerSystem
b This integration adds the column ptr_id in mrb_inv_printer to have a prefix for the
seq_id.
CI Type: Processor

CMDB Class: BMC.CORE: BMC_Processor BBCA View: mrb_inv_processor
Name device_id

CMDB Class:BMC.CORE:BMC_Processor BBCA View: mrb_inv_pprocessor Constant Value
TokenID device_id
Model model
ShortDescription device_id
Type type “Processor or Component”
Item item “BMC Discovered or CPU”
Name device_id
MaxClockSpeed speed
MarkAsDeleted No

CI Type: Disk Drive

CMDB Class: BMC.CORE: BMC_DiskDrive BBCA View: mrb_inv_storage
Name device_id
CMDB Class:BMC.CORE:BMC_DiskDrive BBCA View: mrb_inv_storage Constant Value

TokenID device_id
Model model
Type “Storage or Disk Drive”
Item item “BMC Discovered or CPU”
Name device_id
NameFormat “DeviceID”
Serial Number serialnumber
Size capacity
MarkAsDeleted No
CI Type: Local File System

CMDB Class: BMC.CORE: BMC_LocalFileSystem BBCA View: mrb_inv_storage
Name device_id
CMDB BBCA View: mrb_inv_storage Constant Value

Class:BMC.CORE:BMC_LocalFileSystem
TokenID device_id
Model model
Category category "System Settings or
Miscellaneous"
Type “File System or Instance”
Item item “BMC Discovered or Local
File System”
Name device_id
MarkAsDeleted No

CI Type: Floppy Drive

CMDB Class: BMC.CORE: BMC_FloppyDrive BBCA View: mrb_inv_storage
Name device_id

Class:BMC.CORE:BMC_FloppyDrive
TokenID device_id
Model model
Type “Storage or Disk Device”
Item item “BMC Discovered or Disk
Drive”
Name device_id
MarkAsDeleted No
CI Type: CDROM Drive

CMDB Class: BMC.CORE: BMC_CDROMDrive BBCA View: mrb_inv_storage
Name device_id

Class:BMC.CORE:BMC_CDROMDrive
TokenID device_id
Model model
Drive”
Name device_id
MarkAsDeleted No

CI Type: Videocard

CMDB Class: BMC.CORE: BMC_Card BBCA View: mrb_inv_videocard
Name device_id
CMDB Class:BMC.CORE:BMC_Card BBCA View: mrb_inv_videocard Constant Value

TokenID device_id
Model model
Drive”
Name device_id
MarkAsDeleted No
NOTE
The Category, Item, and Type attributes for each class will change based on the
categorization applied during the installation of CDI.
BMC Atrium Integrator relationship mappings
BMC Atrium Integrator relationship mappings

Each relationship class in BMC Atrium Configuration Management Database (BMC
Atrium CMDB) defines one configuration item (CI) class as the source member of the
relationship and another CI class as the destination member of the relationship.
In the BMC Atrium Integrator there will be two CMDB lookup for the primary class
attribute and the secondary class attribute. The relationship can be instantiated using
one CI instance of each of these classes or any of their subclasses. For more
information about BMC Atrium CMDB relationship class data mappings, see the
BMC Atrium Core Guide.
The following sections describe the relationship class data mappings created in BMC
Atrium Integrator after installing Configuration Discovery Integration for CMDB.
Machine-Application relationship
This section describes the relationship keys mapping and the attribute field mapping
for the machine-application relationship created in BMC Atrium Integrator after
installing Configuration Discovery Integration for CMDB.
Relationship keys mapping

The Relationship Keys Mapping tab on the BMC Atrium Integrator Relationship
Class Mapping Information window enables you to specify the foreign key in the CI
classes that you want to use to create the relationship mapping. The following table
shows the foreign key defined for the machine-application relationship.
Table 46 Machine-application relationship foreign key

Primary class attribute Secondary class attribute
BMC_ComputerSystem.CDIntegrationID BMC_Product.CDMachineID
Attribute field mapping

The Attribute Field Mapping tab on the BMC Atrium Integrator Relationship Class
Mapping Information window enables you to map data to attributes of your
relationship instances other than instance ID and class ID. The following table shows
the relationship class attribute and the CI class attribute mappings that are defined for
the machine-application relationship.

Machine-BIOS relationship
Table 47 Machine-Application attribute field mappings

Relationship class attributes CI class attributes
BMC_HostedSystemComponents.Source.ClassId BMC_ComputerSystem.ClassId
BMC_HostedSystemComponents.Destination.Cl BMC_Product.ClassId
assId
BMC_HostedSystemComponents.DatasetId BMC_ComputerSystem.constant|BMC.IMPORT.CONFIG
BMC_HostedSystemComponents.Name BMC_ComputerSystem.constant|INSTALLEDSOFTWARE
BMC_HostedSystemComponents.Source.Dataset BMC_ComputerSystem.DatasetId
Id
BMC_HostedSystemComponents.Destination.Cl BMC_Product.DatasetId
assId
Machine-BIOS relationship
for the machine-BIOS relationship created in BMC Atrium Integrator after installing
Configuration Discovery Integration for CMDB.

The Relationship Keys Mapping tab on the BMC Atrium Integrator Relationship Class
Mapping Information window enables you to specify the foreign key in the CI classes
that you want to use to create the relationship mapping. Table 48 shows the foreign
key defined for the machine-BIOS relationship.
Table 48 Machine-BIOS relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_Product.CDMachineID

relationship instances other than instance ID and class ID. Table 49 shows the
relationship class attribute and the CI class attribute mappings that are defined for the
machine-BIOS relationship.
Machine-Monitor relationship
Table 49 Machine-BIOS attribute field mappings

BMC_HostedSystemComponents.Source.ClassI BMC_ComputerSystem.ClassId
d
BMC_HostedSystemComponents.Destination. BMC_Product.ClassId
ClassId
BMC_HostedSystemComponents.Source.Datas BMC_ComputerSystem.DatasetId
etId
BMC_HostedSystemComponents.Destination. BMC_Product.DatasetId
DatasetId
Machine-Monitor relationship
for the machine-monitor relationship created in BMC Atrium Integrator after

key defined for the machine-monitor relationship.
Table 50 Machine-monitor relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_Monitor.CDMachineID

machine-monitor relationship.

Machine-Network relationship
Table 51 Machine-monitor attribute field mappings

BMC_HostedSystemComponents.Source.Class BMC_ComputerSystem.ClassId
Id
BMC_HostedSystemComponents.Destination. BMC_Monitor.ClassId
ClassId
BMC_HostedSystemComponents.Name BMC_ComputerSystem.constant|SYSTEMHARDWARE
etId
BMC_HostedSystemComponents.Destination. BMC_Monitor.DatasetId
DatasetId
Machine-Network relationship
for the machine-network relationship created in BMC Atrium Integrator after

key defined for the machine-network relationship.
Table 52 Machine-network relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_IPEndpoint.CDMachineID

machine-network relationship.
Machine-Patch relationship
Table 53 Machine-network attribute field mappings

BMC_HostedSystemComponents.Source.Clas BMC_ComputerSystem.ClassId
sId
BMC_HostedSystemComponents.Destination. BMC_IPEndpoint.ClassId
ClassId
BMC_HostedSystemComponents.Name BMC_ComputerSystem.constant|HOSTEDACCESSPOINT
BMC_HostedSystemComponents.Source.Data BMC_ComputerSystem.DatasetId
setId
BMC_HostedSystemComponents.Destination. BMC_IPEndpoint.DatasetId
DatasetId
Machine-Patch relationship
for the machine-patch relationship created in BMC Atrium Integrator after installing

key defined for the machine-patch relationship.
Table 54 Machine-patch relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_Patch.CDMachineID

machine-patch relationship.

Machine DiskDrive relationship
Table 55 Machine-patch attribute field mappings

Id
BMC_HostedSystemComponents.Destination. BMC_Patch.ClassId
ClassId
etId
BMC_HostedSystemComponents.Destination. BMC_Patch.DatasetId
DatasetId
Machine DiskDrive relationship

for the machine DiskDrive relationship created in BMC Atrium Integrator after

key defined for the machine disk drive relationship.
Table 56 Machine-disk drive relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_DiskDrive.CDMachineID

machine disk drive relationship.
Machine FloppyDrive relationship
Table 57 Machine disk drive attribute field mappings

BMC_HostedSystemComponents.Source.ClassId BMC_ComputerSystem.ClassId
BMC_HostedSystemComponents.Destination.Cl BMC_DiskDrive.ClassId
assId
BMC_HostedSystemComponents.Source.Dataset BMC_ComputerSystem.DatasetId
Id
BMC_HostedSystemComponents.Destination.Da BMC_DiskDrive.DatasetId
tasetId
Machine FloppyDrive relationship

for the machine-floppy drive relationship created in BMC Atrium Integrator after

key defined for the machine-floppy drive relationship.
Table 58 Machine-floppy drive relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_FloppyDrive.CDMachineID

machine-floppy drive relationship.

Machine CDROMDrive relationship
Table 59 Machine-floppy drive attribute field mappings

d
BMC_HostedSystemComponents.Destination.Cl BMC_FloppyDrive.ClassId
assId
BMC_HostedSystemComponents.Source.Datase BMC_ComputerSystem.DatasetId
tId
BMC_HostedSystemComponents.Destination.D BMC_FloppyDrive.DatasetId
atasetId
Machine CDROMDrive relationship

for the machine CDROM drive relationship created in BMC Atrium Integrator after

The Relationship Keys Mapping tab on the BMC Atrium Integrator Relationship
Class Mapping Information window enables you to specify the foreign key in the CI
classes that you want to use to create the relationship mapping. Table 60 shows the
foreign key defined for the machine CDROM drive relationship.
Table 60 Machine CDROM drive relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_CDROMDrive.CDMachineID

machine CDROM drive relationship.
Machine LocalFileSystem relationship
Table 61 Machine CDROM drive attribute field mappings

d
BMC_HostedSystemComponents.Destination.Cl BMC_CDROMDrive.ClassId
assId
tId
BMC_HostedSystemComponents.Destination.D BMC_CDROMDrive.DatasetId
atasetId
Machine LocalFileSystem relationship

for the machine local file system relationship created in BMC Atrium Integrator after

key defined for the machine local file system relationship.
Table 62 Machine-local file system relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_LocalFileSystem.CDMachineID

machine local file system relationship.

Machine-Videocard relationship
Table 63 Machine local file system attribute field mappings

Id
BMC_HostedSystemComponents.Destination. BMC_LocalFileSystem.ClassId
ClassId
BMC_HostedSystemComponents.Name BMC_ComputerSystem.constant|FILESYSTEMPARTITION
BMC_HostedSystemComponents.Source.Data BMC_ComputerSystem.DatasetId
setId
BMC_HostedSystemComponents.Destination. BMC_LocalFileSystem.DatasetId
DatasetId
Machine-Videocard relationship
for the machine-card relationship created in BMC Atrium Integrator after installing

key defined for the machine-card relationship.
Table 64 Machine-card relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_Card.CDMachineID

machine-card relationship.
Machine-Printer relationship
Table 65 Machine-card attribute field mappings

d
BMC_HostedSystemComponents.Destination.C BMC_Card.ClassId
lassId
tId
BMC_HostedSystemComponents.Destination.D BMC_Card.DatasetId
atasetId
Machine-Printer relationship
for the machine-printer relationship created in BMC Atrium Integrator after installing

key defined for the machine-printer relationship.
Table 66 Machine-printer relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_Printer.CDMachineID

machine-printer relationship.

Machine-Processor relationship
Table 67 Machine-printer attribute field mappings

BMC_Dependency.Source.ClassId BMC_ComputerSystem.ClassId
BMC_Dependency.Destination.ClassId BMC_Printer.ClassId
BMC_Dependency.DatasetId BMC_ComputerSystem.constant|BMC.IMPORT.CONFIG
BMC_Dependency.Name BMC_Printer.constant|PRINTERCONNECTIVITY
BMC_Dependency.Source.DatasetId BMC_ComputerSystem.DatasetId
BMC_Dependency.Destination.DatasetId BMC_Printer.DatasetId
Machine-Processor relationship
for the machine-processor relationship created in BMC Atrium Integrator after

key defined for the machine-processor relationship.
Table 68 Machine-processor relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_Processor.CDMachineID

machine-processor relationship.
Table 69 Machine-processor attribute field mappings

Id
BMC_HostedSystemComponents.Destination. BMC_Processor.ClassId
ClassId
Machine-OS relationship
Table 69 Machine-processor attribute field mappings

etId
BMC_HostedSystemComponents.Destination. BMC_Processor.DatasetId
DatasetId
Machine-OS relationship
for the machine-operating system relationship created in BMC Atrium Integrator
after installing Configuration Discovery Integration for CMDB.

key defined for the machine-operating system relationship.
Table 70 Machine-operating system relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_OperatingSystem.CDMachineID

machine-operating system relationship.
Table 71 Machine-operating system attribute field mappings

d
BMC_HostedSystemComponents.Destination. BMC_OperatingSystem.ClassId
ClassId

Machine-Person relationship
Table 71 Machine-operating system attribute field mappings

BMC_HostedSystemComponents.Name BMC_ComputerSystem.constant|SYSTEMOS
etId
BMC_HostedSystemComponents.Destination. BMC_OperatingSystem.DatasetId
DatasetId
Machine-Person relationship
for the machine-person relationship created in BMC Atrium Integrator after installing

keys defined for the machine-person relationship.
Table 72 Machine-person relationship foreign keys

External data store attribute CI class attribute
mrb_inv_machine_person_rel.machine_id BMC_ComputerSystem.CDIntegrationID
mrb_inv_machine_person_rel.person_id BMC_CPerson.CDIntegrationI

machine-person relationship.
Table 73 Machine-person attribute field mappings

BMC_Dependencys.Source.ClassId BMC_ComputerSystem.ClassId
BMC_Dependency.Destination.ClassId BMC_Person.ClassId
BMC_Dependency.DatasetId BMC_ComputerSystem.constant|BMC.IMPORT.CONFIG
BMC_Dependency.Name BMC_Person.Name
Machine-NetworkCard relationship
Table 73 Machine-person attribute field mappings

BMC_Dependency.Source.DatasetId BMC_ComputerSystem.DatasetId
BMC_Dependency.Destination.DatasetId BMC_Person.DatasetId
BMC_Dependency.MarkAsDeleted BMC_ComputerSystem.constant|No
Machine-NetworkCard relationship
for the machine-network card relationship created in BMC Atrium Integrator after

key defined for the machine-network card relationship.
Table 74 Machine-network card relationship foreign key

BMC_ComputerSystem.CDIntegrationID BMC_NetworkPort.CDMachineID

machine-network card relationship.
Table 75 Machine-network card attribute field mappings

d
BMC_HostedSystemComponents.Destination. BMC_NetworkPort.ClassId
ClassId

NetworkCard-Network relationship
Table 75 Machine-network card attribute field mappings

etId
BMC_HostedSystemComponents.Destination. BMC_NetworkPort.DatasetId
DatasetId
for the NetworkCard-Network relationship created in BMC Atrium Integrator after

keys defined for the NetworkCard-Network relationship.
Table 76 NetworkCard-Network relationship foreign key

NetworkPort.Machine_id IPEndpoint.Machine_id
NetworkPort.CDIntegrationID IPEndpoint.Name

NetworkCard-Network relationship.
Table 77 NetworkCard-Network attribute field mappings

BMC_Dependency.DatasetId BMC_NetworkPort.constant|BMC.IMPORT.CONFIG
BMC_Dependency.Name BMC_NetworkPort.constant|DEVICESAPIMPLEMENTATION
BMC_Dependency.Source.DatasetId BMC_NetworkPort.DatasetId
BMC_Dependency.Source.ClassId BMC_NetworkPort.ClassId
Table 77 NetworkCard-Network attribute field mappings

BMC_Dependency.Destination.ClassId BMC_IPEndpoint.ClassId
BMC_Dependency.Destination.DatasetId BMC_IPEndpoint.DatasetId

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
A
AIE. See BMC Atrium Integration Engine CDI_Continuous_NEJob normalization job 28
application discovery methods 25 cdi_federation_title_usage job for SQL Server 30
assigning a reconciliation identity 35 cdi_federation_title_usage procedure for Oracle 30
attributes CI types, discovered by BMC Configuration Management
MarkAsDeleted attribute for purge activities 38 23
normalizing key attributes 28 comparing TokenIds 35
computer systems
deleting instances and related components 38
B discovering 23
Configuration Discovery Integration for CMDB
BCAC_DISCOVERY_PLUGIN plug-in for Federation filter and import process 26
Manager 29 uninstalling 49
BCAC_Software_Usage federation class 30 upgrading 46, 53
BIOS, discovering 23 verifying the data transfer 45
BMC Asset dataset 32 configuration items
BMC Atrium CMDB deleting 38
data integration process 22 preventing duplication through normalization 28
described 20 qualified vs. unqualified 28
prerequisite version 41, 47 conventions, documentation 17
BMC Atrium Configuration Management Database. See creating a unified dataset 32
BMC Atrium CMDB customer support 2
BMC Atrium Integration Engine
described 20
prerequisite version 41, 47
purge activities 38
D
required settings for installation 42 Data Exchange application, described 20
role in the integration process 22, 31, 35 dataset names 32
BMC BladeLogic Client Automation Definitive Software Library, described 21
See also Scanner Service deleting
prerequisite version 41, 47 computer system instances 38
role in data discovery 20 configuration items 38
BMC BladeLogic Client Automation Configuration discovered data
Discovery Integration for CMDB. See Configuration filtering during import 55
Discovery Integration for CMDB integrating 22
BMC Configuration Automation for Clients. See BMC normalizing 27
BladeLogic Client Automation transferring 31
BMC Configuration Import dataset 32 discovering
BMC Remedy AR System BIOS 23
prerequisite version 41, 47 computer systems 23
BMC Software, contacting 2 file systems 23
BMC.IMPORT.CONFIG dataset settings 27 hardware 23
logical networks 23
operating systems 23
C patch information 23
software products 23
CDI_Batch_NEJob normalization job 28
Index 103
duplicate configuration items, preventing through

normalization 28 M
Machine CDROMDrive relationship 92
Machine DiskDrive relationship 90
E Machine FloppyDrive relationship 91
Machine LocalFileSystem relationship 93
electronic documentation 13 Machine-BIOS relationship 86
Machine-Monitor relationship 87
Machine-Network relationship 88
F Machine-NetworkCard relationship 99
Machine-OS relationship 97
federating software title usage data
Machine-Patch relationship 89
database schema changes 30
Machine-Person relationship 98
implementation requirements 29
Machine-Printer relationship 95
file systems, discovering 23
Machine-Processor relationship 96
filtering discovered data during import 55
Machine-Videocard relationship 94
filtering import data
MarkAsDeleted attribute 38
for BMC Atrium CMDB 26
matching instances among multiple datasets 34
using application location 55
merge activity, understanding 37
using application name 55
mrb_inv_software_title_usage view 30
H N
hardware, discovering 23
NetworkCard-Network relationship 100
Help, online 13
non-Windows applications, application discovery method
25
I normalization jobs 28
normalization settings
identification activity, understanding 34 BMC.IMPORT.CONFIG dataset options 27
identification rules, using 35 described 27
import process normalizing data using the Definitive Software Library 27
filtering data 55
preparing for CMDB 26
improving scanning performance 54 O
installation prerequisites 41, 47
online Help 13
installation worksheet 42
operating systems, discovering 23
installing super views 23
integrating discovered data 22
integration discovery
creating federation links and providing reconciliation P
rules 23, 32 patch information, discovering 23
defining data exchanges and data mappings 23 populating key attributes 59
installing schema 23 precedence among datasets 37
Inventory Service. See Scanner Service product categorization
best practice option 44
default option 44
K product dictionary entries 21
product support 2
key attributes
publications, related 14
normalizing 28
populating 59
Q
L qualified configuration items, described 28
logical networks, discovering 23
R
Reconciliation Engine
described 20
jobs 33
reconciling discovered data 32
related publications 14
relating child components 35
S
same configuration items existing in multiple datasets 32
Scanner Service
application discovery methods 25
described 20
scanning performance, improving 54
software products, discovering 23
software title discovery method for applications 25
software title usage data federation
database schema changes 30
implementation requirements 29
specifying precedence 37
super views, installing 23
support, customer 2
T
technical support 2
transferring discovered data 31
U
uninstalling the module 49
unqualified configuration item, described 28
upgrading the module 46, 53
using identification rules 35
W
Windows applications, application discovery method 25
Index 105
Notes
*106412*
*106412*
*106412*
*106412*
*106412*

Getting Started Guide: BMC Bladelogic Client Automation Configuration Discovery Integration For CMDB

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Getting Started Guide: BMC Bladelogic Client Automation Configuration Discovery Integration For CMDB

Uploaded by

Copyright:

Available Formats

BMC BladeLogic Client Automation Configuration

Discovery Integration for CMDB

© Copyright 2008–2014 BMC Software, Inc.

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC

Chapter 1 Introducing configuration discovery integration 19

Chapter 3 Customizing the integration 53

Appendix A Key attributes populated for identifying configuration items 59

Appendix B BMC Atrium Integrator 67

About this book 13

BMC BladeLogic Client Automation documents

Title Description Audience

Title Description Audience

BMC Atrium Core documents

Title Description Audience

■ BMC Atrium Configuration Management Database (BMC

■ BMC Atrium Integrator, which transfers data between an

About this book 15

BMC Atrium CMDB documents

Title Document provides Audience Format

Title Document provides Audience Format

■ All syntax, operating system terms, and literal examples are

About this book 17

Overview of BMC Atrium CMDB integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 1 Introducing configuration discovery integration 19

Overview of BMC Atrium CMDB integration

The role of BMC BladeLogic Client Automation

The role of BMC Atrium Integrator (AI)

The role of the BMC Definitive Software Library

The role of the Normalization Engine

The roll of the Federation Manager

Overview of Configuration Discovery

■ a set of views on top of the Inventory database

Chapter 1 Introducing configuration discovery integration 21

■ federated links for BMC BladeLogic Client Automation

■ reconciliation definitions in the Reconciliation Engine for use during the

Overview of the data integration process

Figure 1 Integration architecture

Note: This figure shows the former name of the

Based on this integration model, the functionality provided by Configuration

Discovering configuration data

Table 1 Configuration data discovered by the Scanner Service

Chapter 1 Introducing configuration discovery integration 23

If you deploy BMC BladeLogic Client Automation to discover CIs on an endpoint

■ BMC Atrium Discovery and Dependency Mapping stop discovering instances of

For details, see “Understanding the merge activity” on page 37.

How application discovery works in BMC BladeLogic Client

Application discovery method

Software title discovery method

Chapter 1 Introducing configuration discovery integration 25

Configuration Discovery Integration for CMDB filter and

Specifically, Configuration Discovery Integration for CMDB creates data exchange

For additional information, see “Filtering import data” on page 55.

Normalizing discovered data

BMC BladeLogic Client Automation normalizes software titles in the Inventory

Normalization settings for Configuration Discovery

Chapter 1 Introducing configuration discovery integration 27

Table 2 Normalization settings

■ The CDI_Continuous_NEJob job starts immediately and begins normalizing data as

Key attribute normalization for identifying duplicate CIs

Qualified versus unqualified CIs

A CI without all of the values necessary to construct the TokenId is considered