Blade Logic Atrium Integration Guide vs 8.1

www.bmc.com

BMC BladeLogic Atrium Integration 8.1.00 Implementation Guide

Supporting

BMC BladeLogic Server Automation 8.1 BMC Atrium CMDB 2.1, 7.5, 7.6, 7.6.03, and 7.6.04BMC Atrium Integration Engine 7.1, 7.5, 7.6, 7.6.03, and

7.6.04BMC Remedy AR System 7.1, 7.5, 7.6, 7.6.03, and 7.6.04BMC BladeLogic Decision Support for Server Automation 8.1BMC Atrium Discovery and Dependency Mapping 8.2

February 2011

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 INC2101 CITYWEST BLVDHOUSTON TX 77042-2827 USA

Telephone 713 918 8800 or800 841 2031

Fax 713 918 8000

Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000

© Copyright 2009-2011 BladeLogic, Inc.

© Copyright 2009-2011 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.

BladeLogic and the BladeLogic logo are the exclusive properties of BladeLogic, Inc. The BladeLogic trademark is registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BladeLogic 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.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Linux is the registered trademark of Linus Torvalds.

UNIX is the registered trademark of The Open Group in the US and other countries.

The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation.

Restricted rights legendU.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.

http://www.bmc.com

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 [email protected]. (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

http://www.bmc.com/support

mailto:[email protected]

License key and password information

If you have questions about your license key or password, use one of the following methods to get assistance:

■ Send an e-mail message to [email protected].

■ Use the Customer Support website at http://www.bmc.com/support.

4 BMC BladeLogic Atrium Integration Implementation Guide

mailto:[email protected]


ContentsChapter 1 Introducing BMC BladeLogic Atrium Integration 11

Overview of BMC BladeLogic and BMC Atrium CMDB. . . . . . . . . . . . . . . . . . . . . . . . 11BMC BladeLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12BMC BladeLogic Decision Support for Server Automation . . . . . . . . . . . . . . . . . . 12BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Integrating BMC BladeLogic discovered data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Defining data exchange and data mapping definitions. . . . . . . . . . . . . . . . . . . . . . 15Reconciling discovered data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2 Installing BMC BladeLogic Atrium Integration 19

Installation planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Installation worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Upgrading BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installing BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Verifying Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Silent installation of BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . . . . 34Post-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Reconciliation with BMC Atrium Discovery and Dependency Mapping . . . . . . 38Performance settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Uninstalling BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Silent uninstallation of BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . . 45

Chapter 3 Transferring data between BMC BladeLogic and BMC Atrium CMDB 47

Transferring data using BMC Atrium Integration Engine . . . . . . . . . . . . . . . . . . . . . . 47Understanding integration data mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Understanding integration data exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Enabling BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Transferring business service data from BMC Atrium CMDB to BMC BladeLogic . 53Transferring data from BMC BladeLogic to BMC Atrium CMDB . . . . . . . . . . . . . . . . 58

Customizing data mappings between BMC BladeLogic Server Automation and BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Publishing the Product Catalog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Using data federation to view reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62BMC Atrium CMDB to BMC BladeLogic mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Contents 5

Index 85


FiguresBMC BladeLogic Atrium Integration architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Example of an options file for the BMC BladeLogic Atrium Integration silent

installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Example of an options file for the BMC BladeLogic Atrium Integration silent

uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45CI class data mappings created during installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Relationship class data mappings created during installation . . . . . . . . . . . . . . . . . . . 50Data exchanges created during installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Figures 7


TablesInstallation worksheet for BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . 21Compatible products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Installation modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27BMC BladeLogic Decision Support for Server Automation Database Details page

parameters for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28BMC BladeLogic Decision Support for Server Automation Database Details page

parameters for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29BMC BladeLogic Decision Support for Server Automation Database Details for

BMC AIE page Oracle parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29BMC Atrium Integration Engine Details page parameters . . . . . . . . . . . . . . . . . . . . . . 30BMC Atrium CMDB Details page parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30BMC Atrium CMDB CI Relationship Viewer Launch-In-Context Details page

parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31BMC BladeLogic Application Server Profile page parameters . . . . . . . . . . . . . . . . . . 31BMC BladeLogic Decision Support for Server Automation page parameters . . . . . . 32Silent installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35BMC Atrium Integration Engine Details page parameters . . . . . . . . . . . . . . . . . . . . . . 42BMC Atrium CMDB Information page parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43BMC BladeLogic Decision Support for Server Automation Database Details page

SQL Server parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44BMC BladeLogic Decision Support for Server Automation Database Details page

Oracle parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44AR/CMDB Configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Atrium Import Job configuration properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Folders included in the Publish Product Catalog Job . . . . . . . . . . . . . . . . . . . . . . . . . . 61AR/CMDB Configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61BMC_ComputerSystem class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64BMC_IPEndpoint class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66BMC_OperatingSystem class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68BMC_Processor class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71BMC_BIOSElement class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73BMC_NetworkPort class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75BMC_LocalFileSystem class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77BMC_DiskDrive class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79BMC_Memory class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80BMC_VirtualSystemSettingData class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Tables 9


C h a p t e r 1
1 Introducing BMC BladeLogic Atrium Integration
This chapter presents the following topics:

Overview of BMC BladeLogic and BMC Atrium CMDB. . . . . . . . . . . . . . . . . . . . . . . . 11BMC BladeLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12BMC BladeLogic Decision Support for Server Automation . . . . . . . . . . . . . . . . . . 12BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Integrating BMC BladeLogic discovered data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Defining data exchange and data mapping definitions. . . . . . . . . . . . . . . . . . . . . . 15Reconciling discovered data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Overview of BMC BladeLogic and BMC Atrium CMDB

The BMC BladeLogic Atrium Integration enables you to share data about the endpoint computers in your BMC BladeLogic system with the BMC Remedy IT Service Management suite of products—an essential step on the path to a complete change and configuration management solution.

Chapter 1 Introducing BMC BladeLogic Atrium Integration 11

BMC BladeLogic

BMC BladeLogic

BMC BladeLogic enables IT organizations to automate the management of enterprise-class data centers. You can use BMC BladeLogic to

■ build and maintain an inventory of servers and applications ■ manage patches ■ measure and enforce compliance to organizational standards ■ administer all configuration changes to servers and applications■ provision servers with applications and operating systems■ import business services from BMC Configuration Management Database (BMC

Atrium CMDB) using special Synchronization Jobs

These capabilities enable you to manage the complete life cycle of servers and applications in the data center.

BMC BladeLogic Decision Support for Server Automation

BMC BladeLogic Decision Support for Server Automation is a web-based reporting application that provides extensive report capabilities related to your data center servers that are managed by BMC BladeLogic.

BMC BladeLogic Decision Support for Server Automation uses rich data warehouse schema and dimensional modeling principles to access and report on historical data captured by BMC BladeLogic Server Automation.

BMC BladeLogic Atrium Integration uses the BMC BladeLogic Decision Support for Server Automation interface to obtain data that BMC BladeLogic Server Automation acquired.


BMC Atrium CMDB

BMC Atrium CMDB

BMC Atrium CMDB stores information about the configuration items (CIs) in your IT environment and the relationships between them. Data providers, including BMC BladeLogic Atrium Integration, put data into BMC Atrium CMDB, where it is partitioned into separate datasets. This data is then brought together into a consolidated production dataset that you use as the single source of reference for your IT environment.

BMC Atrium CMDB creates a business service view in which each hardware and software asset in the environment is associated with a business service.

Other products, including BMC BladeLogic, can then make use of this business service information.


Integrating BMC BladeLogic discovered data

Integrating BMC BladeLogic discovered dataThe BMC BladeLogic Atrium Integration product facilitates the integration of BMC BladeLogic configuration data with the BMC Asset dataset in the BMC Atrium CMDB.

To transfer discovered data from the BMC BladeLogic database to BMC Atrium CMDB, the discovered data is first transferred from the BMC BladeLogic database to the BMC BladeLogic Decision Support for Server Automation database by using the extract, transform, and load (ETL) tool. BMC BladeLogic Atrium Integration uses BMC Atrium Integration Engine to do the following (see Figure 1):

■ Define data exchange and data mapping parameters.■ Pull data from the BMC BladeLogic Decision Support for Server Automation

database.■ Insert the data into the BMC Atrium CMDB with the BMC BladeLogic Import

Dataset.

For information about the ETL components of BMC BladeLogic Decision Support for Server Automation, see the BMC BladeLogic Decision Support for Server Automation User Guide.

The reconciliation process identifies configuration items (CIs) and merges them into the BMC Asset dataset, as shown in Figure 1:

Figure 1 BMC BladeLogic Atrium Integration architecture

BMC BladeLogic Server Automation

BMC BladeLogic database


BMC BladeLogic database

BMC BladeLogic Decision Support for Server

Automation

data warehouse

tables data views for AIE

ETL process

ETL process

BMC Remedy Action Request System

BMC BladeLogic

import dataset

Other datasets

Other configuration data sources

BMC Asset database

Reconciliation engine

Asset Management Application

Change Management Application

Problem Management Application

Change Management Application

Service Level Management Application

BMC Atrium CMDB

AIE


Defining data exchange and data mapping definitions

Based on this integration model, BMC BladeLogic Atrium Integration performs the following functions, which are completed during product installation:

■ Installs views, tables, indexes, functions, and stored procedures on top of the BMC BladeLogic Decision Support for Server Automation database

■ Defines data exchanges and data mappings in BMC Atrium Integration Engine for the BMC Atrium CMDB CI classes that are discoverable by BMC BladeLogic:

— BMC_ComputerSystem— BMC_OperatingSystem— BMC_IPEndpoint— BMC_Processor — BMC_BIOSElement — BMC_NetworkPort — BMC_LocalFileSystem — BMC_DiskDrive — BMC_Memory — BMC_VirtualSystemSettingData

■ Provides reconciliation rules to the Reconciliation Engine for use during the reconciliation process

■ Installs federated links in the BMC Atrium CMDB console to launch BMC BladeLogic Decision Support for Server Automation reports from the BMC Atrium Explorer

■ Installs a custom command in BMC BladeLogic Server Automation to launch the BMC Atrium Explorer

Defining data exchange and data mapping definitions

BMC Atrium Integration Engine transfers data between the BMC BladeLogic Decision Support for Server Automation database and BMC Atrium CMDB. It consists of the Data Exchange application and the Integration Engine service.

The Data Exchange application is a BMC Remedy Action Request System (BMC Remedy AR System) application that the BMC BladeLogic Atrium Integration installer uses to create data exchanges and data mappings that map source and destination fields. The BMC Atrium Integration Engine service performs the data transfer based on the settings in the Data Exchange application. These two components can reside on different computers.


Reconciling discovered data

For more information about creating data exchanges and data mappings, see the BMC Atrium Integration Engine User Guide.


BMC Atrium CMDB contains datasets, each of which holds a distinct set of configuration data. Datasets can store data from a variety of discovery applications. The same computer system or other CI can exist in more than one dataset.

Data that is transferred from the BMC BladeLogic Decision Support for Server Automation database to BMC Atrium CMDB is initially stored in a special dataset called the BMC BladeLogic Import dataset. The Dataset ID for this dataset is BMC.IMPORT.BL.

To consolidate data from the BMC BladeLogic Import dataset into the BMC Asset dataset, you use the Reconciliation Engine. The Reconciliation Engine uses the BladeLogic Data Reconciliation Process Job to consolidate the data. The reconciliation process consists of an Identification activity and a Merge activity.

Understanding the Identification activity

The Identification activity of the reconciliation process matches instances among multiple datasets, confirming that each represents the same real-life object. Instances are records in a configuration management database; they can represent CIs or relationships.

For example, BMC BladeLogic Atrium Integration and BMC Atrium Discovery and Dependency Mapping detect computer system A and create an instance of computer system A in each of their datasets. The Identification activity compares each dataset with the BMC Asset dataset separately to determine if computer system A already exists in the BMC Asset dataset.

The Identification activity first compares the Token IDs that each discovery source creates based on Microsoft Windows Management Instrumentation scanning technology or UNIX® system calls. Because BMC Atrium Integration Engine transfers 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.

If the Reconciliation Engine cannot match the Token IDs to those in the BMC Asset dataset (or the Token ID attribute is not used in the Identification rule), the Identification activity compares other key attributes (such as Name, SerialNumber, and HostName). If the Identification process determines that the instances match, it assigns the match a reconciliation identity.



If the BMC Asset dataset contains no matching instance, the Reconciliation Engine creates a new instance in the BMC Asset dataset and assigns that instance a reconciliation identity.

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 precedence values 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.

BMC BladeLogic Atrium Integration uses best practice categorization. If you are also using BMC Atrium Discovery and Dependency Mapping, it must also be configured to use best practice categorization for the reconciliation process to work correctly.

For more information about the reconciliation process, see the BMC Atrium CMDB Normalization and Reconciliation Guide.

Renamed servers

In BMC BladeLogic version 8.0 and later, you can rename servers in the BMC BladeLogic environment. Renamed servers will be added as new entries in the BMC Atrium CMDB. The original entries will be deleted from the BMC.IMPORT.BL Dataset.




C h a p t e r 2
2 Installing BMC BladeLogic Atrium Integration
You must run the BMC BladeLogic Atrium Integration installer on a Microsoft Windows computer that has a network connection to BMC Remedy Action Request System (BMC Remedy AR System) and the BMC BladeLogic Decision Support for Server Automation database.


Installation planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Installation worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Upgrading BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installing BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Verifying Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Silent installation of BMC BladeLogic Atrium Integration. . . . . . . . . . . . . . . . . . . . . . 34 Post-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Reconciliation with BMC Atrium Discovery and Dependency Mapping . . . . . . 38 Performance settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Uninstalling BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Silent uninstallation of BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . 45


Installation planning

Installation planning Use this section to plan your installation before you begin to install BMC BladeLogic Atrium Integration.

Installation prerequisites

■ All other products and components must be installed before you install BMC BladeLogic Atrium Integration. These components include

— BMC BladeLogic Application Server — BMC BladeLogic Decision Support for Server Automation — BMC Remedy AR System — BMC Atrium CMDB — BMC Atrium Integration Engine — (optional) BMC Remedy Asset Management

The supported versions are listed in Table 2 on page 24.

■ Database types. The following components must use the same database type (both Oracle or both SQL Server)

— BMC BladeLogic Server Automation— BMC BladeLogic Decision Support for Server Automation

However, the BMC Atrium CMDB database can be of a different type. For example, the BMC BladeLogic Server Automation and BMC BladeLogic Decision Support for Server Automation databases can be Oracle, and the BMC Atrium CMDB database can be SQL Server.

■ At least one server must be enrolled on the Application Server on which BMC BladeLogic Atrium Integration is to be installed.

BMC BladeLogic Atrium Integration installation fails if no servers are enrolled on the Application Server on which BMC BladeLogic Atrium Integration is to be installed or if the Hardware Information configuration object is not distributed on the enrolled server.

■ The BMC BladeLogic application server must be able to resolve the host name of the computer on which you are installing the BMC BladeLogic Atrium Integration.

■ A licensed RSCD agent must be installed on the machine where BMC BladeLogic Atrium Integration is to be installed and the agent should be running.


Installation worksheet

■ Before you install BMC BladeLogic Atrium Integration, ensure that you have restarted the RSCD agent on the BMC BladeLogic Decision Support for Server Automation report server after the installation of BMC BladeLogic Decision Support for Server Automation.

■ BMC BladeLogic Server Automation Console must already be installed on the machine where you are installing BMC BladeLogic Atrium Integration.


The following worksheet lists the parameters that you must provide when you install BMC BladeLogic Atrium Integration. Use the worksheet to collect the data that you will need for the installation.

Table 1 Installation worksheet for BMC BladeLogic Atrium Integration (part 1 of 2)

Installation parameter Value

BMC BladeLogic Application Server (all installed servers)

Host name or IP address

Windows Administrator logon user name (required to log on and install software)

Windows Administrator logon password

BMC Remedy AR System server

BMC Remedy AR System server host name or IP address

BMC Remedy AR System server user name

BMC Remedy AR System password

BMC Remedy AR System Port

Note: If you are using a portmapper service for AR system then enter a value of 0.

BMC BladeLogic Decision Support for Server Automation with Microsoft SQL server database

Database host name or IP address

Database port

Database name

Reports database user name

Password for database user

BMC BladeLogic Decision Support for Server Automation with Oracle database

Database host name or IP address

Database port

Database Instance Name (maximum 8 characters)

Reports database user name

Password for database user



Connection string for advanced connection. For example: Oracle RAC (Real Application Clusters) installation options (if applicable).

The Oracle client/server directory on the BMC Atrium Integration Engine host

The entry in the TNSNAMES.ORA file that references the BMC BladeLogic Decision Support for Server Automation Oracle database

BMC Atrium Integration Engine

The name of the BMC Remedy AR System server hosting the BMC Atrium Integration Engine data exchange application

The BMC Remedy AR System server port number for the BMC Atrium Integration Engine data exchange application


The BMC Remedy AR System server user account name for the BMC Atrium Integration Engine data exchange application

The password for the preceding account

BMC Atrium CMDB

The name of the BMC Remedy AR System server that is hosting BMC Atrium CMDB

The port number for the BMC Remedy AR System server that is hosting BMC Atrium CMDB

The user account name for the BMC Remedy AR System server that is hosting BMC Atrium CMDB

Note: This account must have administrator privileges.

The password corresponding to the preceding user account

BMC Atrium CMDB CI Relationship Viewer Launch-In-Context

The name of the host computer where the BMC Remedy Mid Tier is running

The transfer protocol used by the BMC Remedy Mid Tier (HTTP or HTTPS)

The port number for the BMC Remedy Mid Tier

The name of the BMC Atrium CMDB production datasetId

BMC BladeLogic Application Server Profile for loading content

BMC BladeLogic profile

BMC BladeLogic user account

Password corresponding to the BMC BladeLogic user account listed above

BMC BladeLogic Decision Support for Server Automation for launching reports from BMC Atrium CMDB CI Relationship Viewer

The host name of the computer where BMC BladeLogic Decision Support for Server Automation is installed

Table 1 Installation worksheet for BMC BladeLogic Atrium Integration (part 2 of 2)

Installation parameter Value


Upgrading BMC BladeLogic Atrium Integration

Upgrading BMC BladeLogic Atrium Integration

BMC BladeLogic Atrium Integration does not have an upgrade path. You must remove any installed version of BMC BladeLogic Atrium Integration before installing version 8.1.

If you want to install BMC BladeLogic Atrium Integration 8.1 on a BMC Atrium CMDB setup where version 7.6 or 8.0 of BMC BladeLogic Atrium Integration was previously installed and uninstalled, you must manually delete the following entries from the RE:Precedence form before installing the new version of BMC BladeLogic Atrium Integration:

Class Name Attribute Name Precedence Value

BMC_OperatingSystem <blank> 800

BMC_Printer <blank> 800

BMC_BaseElement CDMachineID 900

NOTE ■ When you upgrade BMC BladeLogic Atrium Integration from an earlier version to 8.1, all

customizations are deleted, including Discovery Job and Snapshot Job history, data exchanges, data mappings, and reconciliation rules.

■ In BMC BladeLogic Atrium Integration 7.6, virtual machines were discovered in the same way as physical computers. Starting with BMC BladeLogic version 8.0, discovering virtual machines is supported. When you execute the Virtual Infrastructure Discovery Job, it populates the VirtualLifeCycle property for all virtual machines. These virtual machines are not updated, but are added as new assets. The previous records are decommissioned along with all associations with other business services.


Installing BMC BladeLogic Atrium Integration


Before you begin■ Make sure that compatible versions of BMC BladeLogic, BMC Atrium CMDB, and

BMC Atrium Integration Engine are installed, licensed, and running.

At the time of this release, the product versions listed in Table 2 have been tested as compatible:

■ You must run the extract, transform, and load (ETL) tool before installing BMC BladeLogic Atrium Integration.

■ You need a user name and password for the EPD site. You can register and obtain credentials at http://www.bmc.com/support.

■ You must obtain a support ID and password for BMC BladeLogic Atrium Integration from your BMC Software sales representative.

■ You need all the information listed in Table 1 on page 21.

NOTE ■ BMC BladeLogic Atrium Integration works with all the supported databases of BMC

BladeLogic Decision Support for Server Automation. For information about this product, see the BMC BladeLogic Decision Support for Server Automation documentation.

■ For the latest information, see the product compatibility matrix on the BMC BladeLogic Support website.

Table 2 Compatible products (part 1 of 2)

Product Compatible versions

Microsoft Windows ■ 2003 Server 32-bit and 64-bit, SP2 and later ■ XP SP2 ■ 2008 Server 32-bit and 64-bit

Note: This platform is for the installer. It is not related to the platforms for other compatible products.


■ 8.1.00

BMC BladeLogic Decision Support for Server Automation

■ 8.1.00

Note: Use this integration component to use the BMC Atrium Explorer to view the server configuration and the server compliance reports.




To download BMC BladeLogic Atrium Integration

1 Take the appropriate step:

■ If you are already logged on to BMC Software Support Home, click Downloads & Patches, and then click Product Downloads (EPD).

■ If you are not logged on, go to at http://www.bmc.com/support and log on.

2 Click Downloads and Patches on the menu on the right side of the page.

3 Click Product Downloads (EPD).

BMC Remedy AR System ■ 7.1.00 Patch 7 ■ 7.5.00 Patch 2■ 7.6.03■ 7.6.04

BMC Atrium CMDB ■ 2.1.00 Patch 5 ■ 7.5.00 Patch 3 ■ 7.6.00■ 7.6.03■ 7.6.04

Note: If you are planning to use BMC Atrium CMDB version 7.6.03 with BMC BladeLogic Atrium Integration 8.1, you must apply BMC Atrium CMDB hotfixes SW00372054 and SW00380385 before installing BMC BladeLogic Atrium Integration 8.1. Contact your BMC support representative to get the hotfixes.

BMC Atrium Integration Engine ■ 7.1.00 patch 7 ■ 7.5.00 patch 3■ 7.6.00 ■ 7.6.03■ 7.6.04

Note: BMC Software recommends using BMC Atrium Integration Engine 7.5.00 Patch 3 or later for best performance, even if you use earlier versions of other components.

(optional) BMC Remedy Asset Management

■ 7.0.03 patch 8 ■ 7.5.00 patch 2 or later

(optional) BMC Atrium Discovery and Dependency Mapping

■ 8.2

Note: BMC Topology Discovery was renamed to BMC Atrium Discovery and Dependency Mapping.

Table 2 Compatible products (part 2 of 2)

Product Compatible versions




4 Follow the instructions for completing the Export Validation & License Terms page. You must select I agree in the Export Compliance Disclaimer and TRIAL AGREEMENT panes.

5 Click CONTINUE.

6 If you have previously entered the support ID for BMC BladeLogic Atrium Integration, go to step 7.

To enter the support ID and password:

A In the My Entitled Products page, click MANAGE SUPPORT IDS.

B In the Manage My Support IDs page, enter the support ID and password, and then click ADD.

C Click BACK TO MY ENTITLED PRODUCTS.

7 If BMC BladeLogic Atrium Integration version 8.1 is not displayed, perform the following actions:

A Click ADDITIONAL PRODUCTS.

B In the Search field, enter BMC BladeLogic Atrium Integration, and then click SEARCH.

8 Select BMC BladeLogic Server Automation.

You can select other items for download at this time.

9 Click CONTINUE.

10 In the Select Product Version page, select the products that you want to download according to operating system, and then click CONTINUE.

11 In the Download files page, click BMC BladeLogic Integration for Atrium 8.1.

12 Follow the instructions to complete the download.

You can download other components at this time.

TIP ■ Case does not matter in this search. ■ You can enter a substring of the product name, such as bladel.



To install BMC BladeLogic Atrium Integration

1 Navigate to the directory where you downloaded the file in step 12.

2 Run BL2AtriumInstaller_8_1_138.exe.

3 Select a language and click OK.

4 Read the Welcome page and click Next.

5 On the License Agreement page, select I agree to the terms of the License Agreement, and click Next.

6 On the Installation Mode page, select one of the installation modes shown in Table 3:

7 Click Next.

8 On the Installation Folder page, accept the default installation directory, or click Browse to select another directory. Click Next.

9 In the Database Type page, select Microsoft SQL Server or Oracle Server, and then click Next.

If you chose Microsoft SQL Server, go to step 10. If you chose Oracle Server database, skip to step 11 on page 28.

10 If you chose Microsoft SQL Server database in step 9, complete the following steps:

Table 3 Installation modes

Mode Description

Typical Installation Installs BMC BladeLogic Atrium Integration and places the integration utilities in the installation folder

Utilities Only Places the integration utilities and installation files in the installation directory but does not perform any installation.

NOTE This page and the following pages refer to the BMC BladeLogic Decision Support for Server Automation database, not the BMC BladeLogic Server Automation database.



A In the BMC BladeLogic Decision Support for Server Automation Database Details page, specify values for the SQL Server database parameters shown in Table 4:

B Click Next.

C Go to step 12 on page 30.

11 If you chose Oracle Server database in step 9 on page 27, complete the following steps:

A In the BMC BladeLogic Decision Support for Server Automation Database Details page, specify values for the Oracle parameters shown in Table 5:

NOTE Before you install BMC BladeLogic Atrium Integration, ensure that you have restarted the RSCD agent on the BMC BladeLogic Decision Support for Server Automation report server after the installation of BMC BladeLogic Decision Support for Server Automation.

Table 4 BMC BladeLogic Decision Support for Server Automation Database Details page parameters for SQL Server

Parameter Description

Host Name or IP Address

name or IP address of the server hosting the SQL Server database

Database Port port number of the database server hosting SQL Server database

Database Instance Name

name of the SQL Server database that contains BMC BladeLogic discovered data

Reports DB User user name of the user that has an account on the SQL Server database

Password for DB User

password of the user that has an account on the SQL Server database

NOTE Before you install BMC BladeLogic Atrium Integration, ensure that you have restarted the RSCD agent on the BMC BladeLogic Decision Support for Server Automation report server after the installation of BMC BladeLogic Decision Support for Server Automation.



B Click Next.

C On the BMC BladeLogic Decision Support for Server Automation Database Details for BMC AIE page, specify values for the Oracle parameters shown in Table 6 on page 29:

D Click Next.

Table 5 BMC BladeLogic Decision Support for Server Automation Database Details page parameters for Oracle


Database Hostname or IP Address

The name or IP address of the server hosting the Oracle database

Note: Enter the actual host name or IP address of the BDSSA DB server, do not use localhost even if it is on the same server as this installation.

Database Port The port number of the database server hosting the Oracle database

System ID The system ID associated with a specific instance of an Oracle database

Note: The System ID for BMC BladeLogic Decision Support for Server Automation for Oracle can be a maximum of 8 characters.

Reports DB User The user name of the user that has an account on the Oracle database


The password of the user that has an account on the Oracle database

Advanced connection options (for example: Oracle RAC installations)

The BMC BladeLogic Atrium Integration installer uses this connection information for Oracle RAC installations.

Enter the Oracle RAC connection string and select the checkbox.

Table 6 BMC BladeLogic Decision Support for Server Automation Database Details for BMC AIE page Oracle parameters


Directory The Oracle client/server directory on the BMC Atrium Integration Engine host

Alias Name The entry in the TNSNAMES.ORA file that references the BMC BladeLogic Decision Support for Server Automation Oracle database



12 On the BMC Atrium Integration Engine Details page, specify values for the parameters shown in Table 7:

13 Accept the default of Yes for Is BMC Atrium CMDB running on BMC Remedy Action Request System specified above, or select No depending on your server deployment.

14 Click Next.

The installation program verifies the information that you entered. If the servers are not running or the information is incorrect, installation cannot proceed.

15 In the BMC Atrium CMDB Details page, specify values for the parameters shown in Table 8 on page 30:

Table 7 BMC Atrium Integration Engine Details page parameters


AIE Hostname The name of the host on which BMC Atrium Integration Engine is running

The value for this parameter must be the unqualified name (not the fully-qualified DNS name).

AR Server Hostname The name of the BMC Remedy AR System server hosting the BMC Atrium Integration Engine data exchange application

AR Server Port The BMC Remedy AR System server port number for the BMC Atrium Integration Engine data exchange application


AR Server User The BMC Remedy AR System server user account name for the BMC Atrium Integration Engine data exchange application

This account must have administrator privileges.

AR Server Password The BMC Remedy AR System server password for the BMC Atrium Integration Engine data exchange server account

Table 8 BMC Atrium CMDB Details page parameters (part 1 of 2)


AR Server The name of the BMC Remedy AR System server that is hosting BMC Atrium CMDB

AR Port Number The port number for the BMC Remedy AR System server that is hosting BMC Atrium CMDB




16 Click Next.

17 The installation program verifies the information that you entered. If the server is not running or the information is incorrect, installation cannot proceed.

18 In the BMC Atrium CMDB CI Relationship Viewer Launch-In-Context Details page, specify values for the parameters shown in Table 9:

19 Click Next.

20 In the BMC BladeLogic Application Server Launch-In-Context page, specify values for the parameters shown in Table 10 on page 31:

21 Click Next.

AR User Name The BMC Remedy AR System server user account name for BMC Atrium CMDB


AR Password The BMC Remedy AR System server password for the BMC Atrium CMDB account

Table 9 BMC Atrium CMDB CI Relationship Viewer Launch-In-Context Details page parameters


BMC Remedy MidTier Host The host where the BMC Remedy Mid Tier is running

https:// or http:// The transfer protocol used by the BMC Remedy Mid Tier

BMC Remedy MidTier Port The port number for the BMC Remedy Mid Tier

BMC Atrium CMDB Asset Dataset

The name of the BMC Atrium CMDB production datasetId

Table 10 BMC BladeLogic Application Server Profile page parameters


BladeLogic Profile The BMC BladeLogic profile

User Account The user account for connecting to BMC BladeLogic

Password The user password for connecting to BMC BladeLogic

Table 8 BMC Atrium CMDB Details page parameters (part 2 of 2)




22 In the BMC BladeLogic Decision Support for Server Automation Launch-In-Context page, specify values for the parameters shown in Table 11:

23 Click Next.

24 In the Choose Categorization Practice page, select one of the following options:

■ Default Categorization ■ Best Practice Categorization

25 Click Next.

26 In the Pre-Installation Summary page, review your installation choices.

27 Click Install.

A series of on-screen messages are displayed as the installation proceeds. Installation may take 20 minutes or longer.

At the end of installation, a dialog box indicates whether installation was successful or problems occurred and displays the location of the log file.

28 Click OK.

29 In the BMC BladeLogic Atrium Integration 8.1 Installation Completed page, click Done.

Where to go from here

1. Activate the data exchanges in the BMC Atrium Engine Data Exchange Console.

For more information about the data exchanges that are created automatically in BMC Atrium Integration Engine after installing BMC BladeLogic Atrium Integration, see “Understanding integration data exchanges” on page 51. For more information about activating data exchanges, see the BMC Atrium Integration Engine User Guide.

Table 11 BMC BladeLogic Decision Support for Server Automation page parameters


BMC BladeLogic Reports Server

The host name of the computer where BMC BladeLogic Decision Support for Server Automation is installed.

NOTE You must choose the type of categorization that is consistent with the discovery providers that are populating data into the BMC Atrium CMDB.


Verifying Data Transfer

2. Create Indexes as explained in “Performance settings” on page 40.

You can set schedules on BL_LOAD_SRVR_PROPS as desired. All other exchanges are triggered by this exchange.

3. Customize BMC BladeLogic data mappings. See “Customizing data mappings between BMC BladeLogic Server Automation and BMC Atrium CMDB” on page 59 for more details.

4. Run the extract, transform, and load (ETL) tool.

For information about the ETL components of BMC BladeLogic Decision Support for Server Automation, see the BMC BladeLogic Decision Support for Server Automation User Guide.

5. Restart the BMC Atrium Integration Engine service.

During installation, BMC BladeLogic Atrium Integration creates data exchanges and data mappings in BMC Atrium Integration Engine for the CI classes and relationship classes that are discoverable by BMC BladeLogic. For more information about these created data exchanges and data mappings, see “Transferring data using BMC Atrium Integration Engine” on page 47.

Verifying Data Transfer

You can look in the BMC Atrium Integration Engine log files to verify that the data transfer between the BMC BladeLogic Decision Support for Server Automation database and BMC Atrium CMDB completed successfully. On computers running the 32-bit Microsoft Windows operating system, the log files are stored in the following directory (unless you selected another directory path during installation):

C:\Program Files\BMC Software\BMC Atrium Integration Engine\serverName\service\log\

For more information about logging and debugging, see the BMC Atrium Core Troubleshooting Guide.

NOTE A data transfer is complete when all active data exchanges have run. If you examine the CIs before this, the data might appear inconsistent (for example, an instance of BMC_ComputerSystem might not be associated yet with an instance of BMC_OperatingSystem because the data exchanges are run in a particular order).

If you decide to run the data exchanges manually, select the BL_LOAD_SRVR_PROPS data exchange. Then click Run Now on the BMC Atrium Integration Engine Data Exchange console and start this exchanges.


Silent installation of BMC BladeLogic Atrium Integration


BMC BladeLogic Atrium Integration includes the option for a silent installation.

To install BMC BladeLogic Atrium Integration silently

1 In a text editor, create an options file and add the installation options that you want. See Figure 2 for an example.

In the example in Figure 2, note the following:

-P sets the installation directory for the product. For example:

-P installLocation=C:\Program Files\BMC Software\BL2AI\8.1.00

Figure 2 Example of an options file for the BMC BladeLogic Atrium Integration silent installation

-P installLocation=C:\Program Files\BMC Software\BL2AI\8.1.00-A featureBL2Atrium-J INSTALL_SET=TYPICAL-J DATABASE_TYPE=ORACLE-J IS_CMDB_ON_AR_SERVER=true-J SCHEMA_HOST=vm-w23-blg167-J SCHEMA_PORT=1521-J SCHEMA_INSTANCE=BDSSA167-J SCHEMA_LOGIN=BSARA_DW-J SCHEMA_PASSWORD=sa-J DE_AR_SERVER_NAME=vm-w23-blg88-J DE_AR_PORT=46262-J DE_AR_USER=Demo-J DE_AR_PASSWORD=-J CMDB_AR_SERVER_NAME=vm-w23-blg88-J CMDB_AR_PORT=46262-J CMDB_AR_USER=Demo-J CMDB_AR_PASSWORD=-J MIDTIER_SERVER_NAME=vm-w23-blg88-J MIDTIER_PROTOCOL=HTTP-J MIDTIER_PORT=8080-J ASSET_DATASET=BMC.ASSET-J USER_PROFILE_NAME=vm-rlnx-rds1094-J USER_ACCOUNT_NAME=BLAdmin-J USER_ACCOUNT_PASSWORD=DES\:84bcde1cc68f855608839e457d4e2050-J USER_ROLE=BLAdmins-J BDSSA_SERVER_NAME=vm-lnx-aa07.bmc.com-J BDSSA_COMMUNICATIONS_PROTOCOL=HTTP-J CATEGORIZATION_PRACTICE=DEFAULT_CATEGORIZATION_PRACTICE-J AIE_ALIAS=BDSSA167-J AIE_HOST_ORACLE_SERVER_CLIENT_LOCATION=C:\oracle\product\10.2.0\client_1



-A indicates the products and features you want to install, this must always be set to featureBL2Atrium.

-J Install options and their values.

Use the following guidelines for your options file:

■ Each option must be on a single line.■ Values for options may contain spaces.■ Comment lines are allowed within the file (comments start with the # character).

2 Navigate to the folder where the installer is located.

3 Run the installation program with the -i silent option as follows:

BL2AtriuminstallerName -i silent -DOPTIONS_FILE= "silentOptionsFilePath"

■ Use an absolute path to the options file.

■ Enclose the path in double quotation marks (").

For Example:

BL2AtriumInstaller_8_1_131.exe -i silent -DOPTIONS_FILE="C:\Installers\options_file_inst.txt"

Table 12 lists the options that are available for the silent installation:

Table 12 Silent installation options (part 1 of 3)

Option Description

installLocation Path to the installation directory.

INSTALL_SET Installer mode. Valid values are:

■ TYPICAL■ MINIMAL

DATABASE_TYPE Database type for BMC BladeLogic Decision Support for Server Automation. Valid values are:

■ ORACLE■ SQL_SERVER

IS_CMDB_ON_AR_SERVER

Valid values are:

■ True■ False

SCHEMA_HOST Host Name or IP address of the database server hosting the BMC BladeLogic Decision Support for Server Automation database.



SCHEMA_PORT Database port number of the database server hosting the BMC BladeLogic Decision Support for Server Automation database.

SCHEMA_INSTANCE The database instance of the BMC BladeLogic Decision Support for Server Automation database.

■ For Oracle - SID (Site Identifier)■ For MS SQL - database name

SCHEMA_LOGIN User Name for connecting to the BMC BladeLogic Decision Support for Server Automation database.

SCHEMA_PASSWORD Password for connecting to the BMC BladeLogic Decision Support for Server Automation database.

DE_AR_SERVER_NAME

Host Name or IP address of the BMC Remedy AR System server for the BMC Atrium Integration Engine data exchange application.

DE_AR_PORT Port number of the BMC Remedy AR System server for the BMC Atrium Integration Engine data exchange application.


DE_AR_USER User Name for connecting to the BMC Remedy AR System server for the BMC Atrium Integration Engine data exchange application.

DE_AR_PASSWORD Password for connecting to the BMC Remedy AR System server for the BMC Atrium Integration Engine data exchange application.

CMDB_AR_SERVER_NAME

Host Name or IP address of the BMC Remedy AR System server that is hosting BMC Atrium CMDB.

CMDB_AR_PORT Port number of the BMC Remedy AR System server that is hosting BMC Atrium CMDB.


CMDB_AR_USER User Name for connecting to the BMC Remedy AR System server that is hosting BMC Atrium CMDB.

CMDB_AR_PASSWORD

Password for connecting to the BMC Remedy AR System server that is hosting BMC Atrium CMDB.

MIDTIER_SERVER_NAME

Host Name or IP address of Remedy Mid Tier host.

MIDTIER_PROTOCOL The transfer protocol used by the BMC Remedy Mid Tier. Valid values are:

■ HTTP■ HTTPS

MIDTIER_PORT BMC Remedy Mid Tier Port.

ASSET_DATASET The name of the BMC Atrium CMDB production datasetId.

USER_PROFILE_NAME Name of the BMC BladeLogic authentication profile used to connect to the BMC BladeLogic Application Server.


Option Description


Post-installation tasks

Post-installation tasks After you install BMC BladeLogic Atrium Integration, you must perform these configuration tasks.

USER_ACCOUNT_NAME

User Name for connecting to the BMC BladeLogic Application Server.

USER_ACCOUNT_PASSWORD

Password for connecting to the BMC BladeLogic Application Server.

Use the Server Automation Console Maintenance Tool to generate the encrypted string for the password. The tool is available in the utilities folder of your BMC BladeLogic installation. For example:

C:\Program Files\BMC Software\BladeLogic\8.1\utilities.

The file name is:

ServerAutomationConsoleMaintenanceTool.cmd.

USER_ROLE The user role to be used in BMC BladeLogic.

BDSSA_SERVER_NAME

Host Name or IP address of a machine where BMC BladeLogic Decision Support for Server Automation reports server is installed.

BDSSA_COMMUNICATIONS_PROTOCOL

The transfer protocol used by the BMC BladeLogic Decision Support for Server Automation server. Valid values are:

■ HTTP■ HTTPS

CATEGORIZATION_PRACTICE

Categorization practice to classify CIs in BMC Atrium CMDB. Valid values are:

■ DEFAULT_CATEGORIZATION_PRACTICE■ BEST_CATEGORIZATION_PRACTICE

AIE_ALIAS To be used only when the BMC BladeLogic Decision Support for Server Automation database is Oracle.

The Oracle client/server directory on the BMC Atrium Integration Engine host (in other words: the directory above the BIN directory where the SQL*Plus software is installed.

AIE_HOST_ORACLE_SERVER_CLIENT_LOCATION

To be used only when the BMC BladeLogic Decision Support for Server Automation database is Oracle.

The entry in the NETWORK/ADMIN/tnsnames.ora file under the AIE_ALIAS directory that references the BMC BladeLogic Decision Support for Server Automation Oracle database.


Option Description


Reconciliation with BMC Atrium Discovery and Dependency Mapping


Perform the following tasks to add FQDN (Fully-Qualified Domain Name) values to the servers in BMC BladeLogic in the DNS_DOMAIN_NAME property.

To create the NSH Script Job

1 Copy the following files

■ addServerProperty.nsh■ getDetailsOfMachineAndAddProperty.nsh■ getWindowsMachineFQDNName.bat

from

<BMC BladeLogic Atrium Integration installation folder>\NSHScripts

to

<BMC BladeLogic installation folder>default is C:\Program Files\BMC Software\BladeLogic\8.1\NSH

2 Open a Windows Command Prompt or a Shell.

3 Browse to the BMC BladeLogic installation folder.

4 Type nsh and press Enter.

5 Set the BL_AUTH_PROFILE_NAME environment variable to your user profile. Use the following command from the NSH command prompt:

export BL_AUTH_PROFILE_NAME = profileName

6 Set the BL_RBAC_ROLE environment variable to your role. Use following command from the NSH prompt:

export BL_RBAC_ROLE = roleName

roleName should be BLAdmins or its equivalent.

NOTE Before performing this procedure, ensure that your user has BLAdmins permissions (or equivalent).



Best practice: Run a simple blcli command, such as Server listAllServers, to ensure the credentials are working properly.

Refer to the Setting up a Network Shell Client to run in proxy mode section in the BMC BladeLogic Server Automation Administration Guide for more details.

7 Use the following command to execute the addServerProperty.nsh script:

nsh addServerProperty.nsh

This creates an NSH Script named ADDM in the ADDMNSHSCRIPTS folder inside the Depot workspace in the BladeLogic console.

Another NSH Script Job, ADDM_NSHSCRIPT_JOB is created in the ADDM_NSHSCRIPT_JOB folder in the Jobs workspace.

8 Execute the ADDM_NSHSCRIPT_JOB NSH Script Job on all the enrolled servers on which you want to populate the DNS_DOMAIN_NAME server property.

9 After you execute the job, the DNS_DOMAIN_NAME property for the target servers is populated with the appropriate value (the FQDN of the target).

NOTE ■ The NSH Script Job must be scheduled to run before every run of ETL to make sure that

the DNS_DOMAIN_NAME server property is populated for any new servers that are added.

■ The DNS_DOMAIN_NAME server property must be set to Used in Reports in the Property Dictionary.

■ If the NSH Script Job is not run, no data is transferred to the CMDB.

■ If you want to rerun the scripts, you must delete ADDMNSHSCRIPTS from the Depot group and ADDM_NSHSCRIPT_JOB from the Job group.

■ You must map the BMC Atrium CMDB Domain attribute to the BMC BladeLogic DNS_DOMAIN_NAME attribute in the BladeLogic to Atrium Customization (see “Customizing data mappings between BMC BladeLogic Server Automation and BMC Atrium CMDB” on page 59 for more details), before you restart the BMC Atrium Integration Engine service.


Performance settings

Performance settings

After installing BMC BladeLogic Atrium Integration and before using it, you must perform the following procedure for the data that BMC BladeLogic Atrium Integration transfers to BMC Atrium CMDB.

Use the AR System Administration Console to perform this task. See the BMC Remedy Action Request System Configuration Guide and BMC Atrium Integration Engine User’s Guide for the version of BMC Remedy AR System that you are using.

Before you begin

You must have a user account on the BMC Remedy AR System with privileges to perform these operations.

To create indexes in BMC Atrium Integration Engine

1 Use the BMC Remedy Developer Studio to create indexes on the following forms (see Introduction to Application Development with BMC Remedy Developer Studio for more details):

■ Index on BMC_BaseElement on TokenId ■ Index on BMC_BaseElement on CDMachineID ■ Index on BMC_BaseElement on CDMachineID, Name ■ Index on BMC_BaseElement on CDMachineID, VersionNumber

2 Provide Fast Thread and List Thread (minimum and maximum depending on the number of CPUs).

3 Tune the AR database:

■ Create separate disks for data and logs. ■ Ensure cursor sharing is done at the database level. ■ Move index and log into separate tablespaces. ■ Use the following query on an Oracle database to generate statistics on all tables

in the schema and their indexes:

execute dbms_stats.gather_database_stats (estimate_percent>10, cascade>TRUE);

■ Make sure that the tablespace has enough free space (for details see the Performance Tuning for Business Service Management white paper).


Troubleshooting

4 The autoextend on next command adds to the size of the tablespace if the amount of data exceeds the current size of the tablespace. It adds to the tablespace according to its SIZE value and continues extending the tablespace until it runs out of disk space. To avoid this, set the AUTOEXTEND ON NEXT value to 512 using the following command:

ALTER DATABASE DATAFILE 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\AR75\ARSYS' AUTOEXTEND ON NEXT 4M ;

Troubleshooting

Log files

Installation and uninstallation logs are created in your TEMP directory. The installation log file is named bl2atrium_install_log.txt. The uninstallation log file is named bl2atrium_uninstall_log.txt.

Known issues

Problem: You consistently get error #3317 for update mode in the Inst_001_aiemain.log file.

Solution: Modify the chunksize parameter in the <Atrium Core Installation Directory>\aie\service\service\conf\aie.cfg file from 100000 to around 250000.

NOTE For better performance, BMC Software recommends that you disable the debug logs of all data exchanges in the BMC Atrium Integration Engine.

If you need the debug logs for the exchanges, set the debug log size to more than 10MB as follows:

1. Login to the BMC Remedy AR System server using the BMC Remedy User tool.

2. Open the BMC Atrium Integration Engine console.

3. Open any data exchange that starts with BL.

4. On the Advanced Settings tab, set Max Debug Size (Bytes) to 10485760 or more.

5. Click on Apply to All Exchanges.

Save and close the exchange.


Uninstalling BMC BladeLogic Atrium Integration

Problem: You get an error similar to the following:

Failure during SQL operation to the database ORA-04030: out of process memory when trying to allocate 254476 bytes

Solution: On the database server hosting AR System's database, do the following:

■ Set Virtual Memory to minimum 13GB and maximum 16GB.

■ Set a /3GB startup switch. (For details on how to set this switch, refer to http://technet.microsoft.com/en-us/library/bb124810%28EXCHG.65%29.aspx).


Before you begin

You must deactivate the data exchanges before uninstalling of BMC BladeLogic Atrium Integration. For more information about deactivating data exchanges, see the BMC Atrium Integration Engine User Guide.

To uninstall BMC BladeLogic Atrium Integration

1 Navigate to the installation directory. The default is C:\Program Files\BMC Software\BL2AI\8.1.00.

2 Open the directory named UninstallBMCBL2Atrium.

3 Double-click uninstall.exe

4 In the Uninstall BMC BladeLogic Atrium Integration page, click Next.

5 In the BMC Atrium Integration Engine Details page, specify values for the parameters shown in Table 13 on page 42:

Table 13 BMC Atrium Integration Engine Details page parameters (part 1 of 2)


AR Server The name of the BMC Remedy AR System server hosting the BMC Atrium Integration Engine data exchange application

AR Server Port The BMC Remedy AR System server port number for the BMC Atrium Integration Engine data exchange application


http://technet.microsoft.com/en-us/library/bb124810%28EXCHG.65%29.aspx

http://technet.microsoft.com/en-us/library/bb124810%28EXCHG.65%29.aspx


6 Accept the default value in the Is BMC Atrium CMDB running on the same AR Server as AIE Data Exchange Application option, or select No depending on your server deployment.

7 Click Next.

8 In the BMC Atrium CMDB Information page, specify values for the parameters shown in Table 14:

9 Click Next.

10 In the Schema Uninstall for BMC BladeLogic Atrium Integration 8.1 page, accept the default to uninstall the schema, or select No.

11 Click Uninstall.

12 In the BMC BladeLogic Decision Support for Server Automation Database Information page, select Microsoft SQL Server or Oracle Server, and then click Next.

If you chose Microsoft SQL Server, go to step 13. If you chose Oracle Server database, skip to step 14 on page 44.

13 If you chose Microsoft SQL Server database in step 12 on page 43, complete the following steps:

AR Server User The BMC Remedy AR System server user account name for the BMC Atrium Integration Engine data exchange application


AR Server Password The BMC Remedy AR System server password for the BMC Atrium Integration Engine data exchange server account

Table 14 BMC Atrium CMDB Information page parameters


AR Server The name of the BMC Remedy AR System server that is hosting BMC Atrium CMDB

AR Server Port The port number for the BMC Remedy AR System server that is hosting BMC Atrium CMDB

AR Server User The BMC Remedy AR System server user account name for BMC Atrium CMDB


AR Server Password The BMC Remedy AR System server password for the BMC Atrium CMDB account

Table 13 BMC Atrium Integration Engine Details page parameters (part 2 of 2)




A In the BMC BladeLogic Decision Support for Server Automation Database Details page, specify values for the SQL Server parameters shown in Table 15:

B Click Uninstall.

C Go to step 15.

14 If you chose Oracle Server database in step 12 on page 43, complete the following steps:

A In the BMC BladeLogic Decision Support for Server Automation Database Details page, specify values for the Oracle parameters shown in Table 16:

B Click Uninstall.

15 In the BMC BladeLogic Atrium Integration 8.1 uninstallation completed successfully page, click Done.

Table 15 BMC BladeLogic Decision Support for Server Automation Database Details page SQL Server parameters



The name or IP address of the server hosting the SQL Server database

Database Port The port number of the database server hosting the SQL Server

Database Name The name of the SQL Server database that contains BMC BladeLogic discovered data

Reports DB User The user name of the user that has an account on the SQL Server database

Password for DB User The password of the user that has an account on the SQL Server database

Table 16 BMC BladeLogic Decision Support for Server Automation Database Details page Oracle parameters



The name or IP address of the server hosting the Oracle database

Database Port The port number of the database server hosting the Oracle database

System ID The system ID associated with a specific instance of an Oracle database

Reports DB User The user name of the user that has an account on the Oracle database


The password of the user that has an account on the Oracle database


Silent uninstallation of BMC BladeLogic Atrium Integration


BMC BladeLogic Atrium Integration includes the option for a silent uninstallation.

To uninstall BMC BladeLogic Atrium Integration silently

1 In a text editor, create an options file and add the uninstallation options that you want. See Figure 3 for an example.

In the example in Figure 3, note the following:

-P indicates the installation directory of BMC BladeLogic Atrium Integration. For example:

-P installLocation=C:\Program Files\BMC Software\BL2AI\8.1.00

-U indicates the products and features you want to uninstall, this must always be set to featureBL2Atrium.

-J Install options and their values.

Figure 3 Example of an options file for the BMC BladeLogic Atrium Integration silent uninstallation

-P installLocation=C:\Program Files\BMC Software\BL2AI\8.1.00-U featureBL2Atrium-J INSTALL_SET=TYPICAL-J DATABASE_TYPE=ORACLE-J IS_CMDB_ON_AR_SERVER=true-J SCHEMA_HOST=vm-w23-blg167-J SCHEMA_PORT=1521-J SCHEMA_INSTANCE=BDSSA167-J SCHEMA_LOGIN=BSARA_DW-J SCHEMA_PASSWORD=sa-J DE_AR_SERVER_NAME=vm-w23-blg88-J DE_AR_PORT=46262-J DE_AR_USER=Demo-J DE_AR_PASSWORD=-J CMDB_AR_SERVER_NAME=vm-w23-blg88-J CMDB_AR_PORT=46262-J CMDB_AR_USER=Demo-J CMDB_AR_PASSWORD=-J USER_PROFILE_NAME=vm-rlnx-rds1094-J USER_ACCOUNT_NAME=BLAdmin-J USER_ACCOUNT_PASSWORD=DES\:84bcde1cc68f855608839e457d4e2050-J USER_ROLE=BLAdmins



Use the following guidelines for your options file:

■ Each option must be on a single line.■ Values for options may contain spaces.■ Comment lines are allowed within the file (comments start with the # character).

2 Navigate to the folder where the uninstall program is located.

3 Run the uninstall program with the -i silent option as follows:

BL2AtriumuninstallerName -i silent -DOPTIONS_FILE= "silentOptionsFilePath"

■ Use an absolute path to the options file.

■ Enclose the path in double quotation marks (").

For Example:

<BL-Atrium Installation Directory>\UninstallBMCBL2Atrium\uninstall.exe -i silent -DOPTIONS_FILE="C:\Installers\options_file_uninst.txt”

See Table 12 on page 35 for a list of options that are available for the silent installation.


C h a p t e r 3
3 Transferring data between BMC BladeLogic and BMC Atrium CMDB
This chapter describes how discovered data is transferred between the BMC BladeLogic Decision Support for Server Automation database and BMC Atrium CMDB.


Transferring data using BMC Atrium Integration Engine . . . . . . . . . . . . . . . . . . . . . . 47 Understanding integration data mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Understanding integration data exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Enabling BMC BladeLogic Atrium Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Transferring business service data from BMC Atrium CMDB to BMC BladeLogic . 53 Transferring data from BMC BladeLogic to BMC Atrium CMDB . . . . . . . . . . . . . . . 58

Customizing data mappings between BMC BladeLogic Server Automation and BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Publishing the Product Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Using data federation to view reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 BMC Atrium CMDB to BMC BladeLogic mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Transferring data using BMC Atrium Integration Engine

The following sections describe how BMC Atrium Integration Engine transfers data from the BMC BladeLogic Decision Support for Server Automation database to BMC Atrium CMDB.


Understanding integration data mappings


A data mapping in BMC Atrium Integration Engine defines how data in the BMC BladeLogic Decision Support for Server Automation database corresponds to data in BMC Atrium CMDB and which actions need to taken when data is transferred between them. That is, data mappings explicitly define the mapping between columns in the BMC BladeLogic Decision Support for Server Automation database and the attributes of a BMC Atrium CMDB CI or relationship class.

When you install BMC BladeLogic Atrium Integration, the data mappings required to transfer data are created automatically in the BMC Atrium Integration Engine. The BMC Atrium CI class data mappings are shown in Figure 4. The BMC Atrium CMDB relationship class data mappings are shown in Figure 5 on page 50.

Figure 4 CI class data mappings created during installation

BMC BladeLogic Atrium Integration creates the following data mappings:

■ BL_DEL_BIOSELEMENT ■ BL_DEL_COMPUTERSYSTEM



■ BL_DEL_DISKDRIVE ■ BL_DEL_IPENDPOINT■ BL_DEL_LOCALFILESYSTEM ■ BL_DEL_MEMORY ■ BL_DEL_NETWORKPORT ■ BL_DEL_OPERATINGSYSTEM■ BL_DEL_PROCESSOR ■ BL_DEL_VIRTUALSYSTEM ■ BL_LOAD_SRVR_PROPS■ BL_PULL_BIOSELEMENT ■ BL_PULL_COMPUTERSYS_CO ■ BL_PULL_COMPUTERSYSTEM■ BL_PULL_DISKDRIVE ■ BL_PULL_IPENDPOINT■ BL_PULL_LOCALFILESYSTEM ■ BL_PULL_MEMORY ■ BL_PULL_NETWORKPORT ■ BL_PULL_OPERATINGSYSTEM■ BL_PULL_PROCESSOR ■ BL_PULL_VIRTUALSYSTEM



Figure 5 Relationship class data mappings created during installation

BMC BladeLogic Atrium Integration creates the following relationship class mappings:

■ BL_PULL_BIOSELEMENT_RELATIONSHIP ■ BL_PULL_DISKDRIVE_RELATIONSHIP ■ BL_PULL_IP_RELATIONSHIP ■ BL_PULL_LOCALFILESYSTEM_RELATIONSHIP ■ BL_PULL_MEMORY_RELATIONSHIP ■ BL_PULL_NETWORK_RELATIONSHIP ■ BL_PULL_OS_RELATIONSHIP ■ BL_PULL_PROCESSOR_RELATIONSHIP ■ BL_PULL_VIRTUALSYSTEM_RELATIONSHIP

For more information about the data mapping process, see the BMC Atrium Integration Engine User Guide.


Understanding integration data exchanges


A data exchange is a set of rules that define how data is transferred between the BMC BladeLogic Decision Support for Server Automation database and BMC Atrium CMDB. Data that is transferred into BMC Atrium CMDB normally populates multiple CI classes and the relationship classes that connect them.

When you install BMC BladeLogic Atrium Integration, the data exchanges required to transfer data are created automatically in the BMC Atrium Integration Engine. These data exchanges are shown in Figure 6:

Figure 6 Data exchanges created during installation

BMC BladeLogic Atrium Integration creates the following exchanges:

■ BL_CALL_INIT_1 ■ BL_CALL_INIT_2 ■ BL_DEL_BIOSELEMENT■ BL_DEL_COMPUTERSYSTEM■ BL_DEL_DISKDRIVE■ BL_DEL_IPENDPOINT■ BL_DEL_LOCALFILESYSTEM



■ BL_DEL_MEMORY■ BL_DEL_NETWORKPORT■ BL_DEL_OPERATINGSYSTEM■ BL_DEL_PROCESSOR■ BL_DEL_VIRTUALSYSTEM ■ BL_LOAD_SRVR_PROPS■ BL_PULL_BIOSELEMENT■ BL_PULL_BIOSELEMENT_RELATIONSHIP ■ BL_PULL_COMPUTERSYS_CO ■ BL_PULL_COMPUTERSYSTEM■ BL_PULL_DISKDRIVE■ BL_PULL_DISKDRIVE_RELATIONSHIP ■ BL_PULL_IP_RELATIONSHP ■ BL_PULL_IPENDPOINT■ BL_PULL_LOCALFILESYSTEM■ BL_PULL_LOCALFILESYSTEM_RELATIONSHIP ■ BL_PULL_MEMORY■ BL_PULL_MEMORY_RELATIONSHIP■ BL_PULL_NETWORKPORT■ BL_PULL_NETWORKPORT_RELATIONSHIP ■ BL_PULL_OPERATINGSYSTEM■ BL_PULL_OPERATINGSYSTEM_RELATIONSHIP ■ BL_PULL_PROCESSOR■ BL_PULL_PROCESSOR_RELATIONSHIP ■ BL_PULL_VIRTUALSYSTEM ■ BL_PULL_VIRTUALSYSTEM _RELATIONSHIP

For more information about the data exchange process, see the BMC Atrium Integration Engine User Guide.

NOTE The data exchanges created by BMC BladeLogic Atrium Integration are inactive by default. To transfer instances for a single class, you must activate the set of data exchanges for that class. To transfer instances for all classes, you must activate the set of data exchanges for all classes. Use the Active/Inactive button in BMC Atrium Integration Engine to activate the data exchanges.


Enabling BMC BladeLogic Atrium Integration

Enabling BMC BladeLogic Atrium IntegrationEnabling the BMC BladeLogic Atrium Integration is a prerequisite for Atrium Import Jobs, BladeLogic to Atrium Customization and the Publish Product Catalog Job.

The following task is required once per application server:

To enable BMC BladeLogic Atrium Integration

1 On the BMC BladeLogic Application Server command line, run the following command to start the Application Server Administration console:

2 From the bladmin prompt, run the following command to enable configuration and synchronization:

3 From the bladmin prompt, run the following command to make sure the AppServer value is set correctly:

4 Restart the BMC BladeLogic Application Server and the BMC BladeLogic Server Automation console.

Transferring business service data from BMC Atrium CMDB to BMC BladeLogic

BMC BladeLogic does not support the concept of business services. For example, by looking at a particular server managed by BMC BladeLogic, it is not possible to determine which business services might be affected if the server changes.

However, business service information is available in BMC Atrium CMDB. Transferring data from BMC Atrium CMDB to the BMC BladeLogic database pulls business service information from BMC Atrium CMDB and associates it with the corresponding servers in BMC BladeLogic as a custom property. You can then create smart groups based on this custom property to determine the relationships between business services and servers.

blasadmin

set AppServer EnableAtriumIntegration true

show AppServer EnableAtriumIntegration



Transferring data from BMC Atrium CMDB to the BMC BladeLogic database involves importing a list of affected business services and Virtual Life Cycle Data. This process is implemented as a special Synchronization Job type called the Atrium Import Job. All instances of the Atrium Import Job share a common configuration.

To configure and schedule a Synchronization Job

1 Choose Atrium Integration >Configuration from the Configuration menu and enter the following BMC Atrium CMDB details on the AR/CMDB Configuration tab:

2 Click Test Connection to verify that the credentials that you entered are correct.

3 In the BMC BladeLogic Server Automation console, choose Configuration > Atrium Integration > Atrium Import Job Configuration from the menu bar.

4 In the Atrium Import Job Configuration tab, click to open each of the five groups of configuration parameters.

5 Specify values for the configuration properties described in Table 18:

NOTE Enabling the BMC BladeLogic Atrium Integration is a prerequisite for Atrium Import Jobs. See “Enabling BMC BladeLogic Atrium Integration” on page 53 for more details.

Table 17 AR/CMDB Configuration parameters


Host Name/IP Address Host name or IP address of the computer where BMC Atrium CMDB is installed

CMDB Port Port used for communicating with BMC Atrium CMDB


CMDB User User Name for connecting to BMC Atrium CMDB

CMDB Password Password for connecting to BMC Atrium CMDB

Table 18 Atrium Import Job configuration properties (part 1 of 4)

Configuration property Description

General Atrium CMDB Details

Production Dataset name The name of the BMC Atrium CMDB production dataset (BMC Asset)



List of Computer System class names

The computer system class names

Only instances of these classes are transferred from BMC Atrium CMDB while the impact on the business services is determined. The class names must be specified in the following format: nameSpace:className (for example, BMC.CORE:BMC_BaseElement).

CMDB multi-tenancy attribute name

BMC Atrium CMDB attribute name used to verify the company name Default value is AccountID.

If this attribute is not available, you can specify any attribute of theBMC_BaseElement class to use instead.

Company name Company name is compared with the value in the CMDB attribute as set in CMDB multi-tenancy attribute name. Business services are copied to BMC BladeLogic from the CMDB only if the two company names match.

If you do not specify a value, all business services and computer systems are analyzed and transferred to BMC Bladelogic.

Business Service and its Associations Details

Business Service class name The name of the business service class

For example, BMC Atrium CMDB provides the BMC_BusinessService class to identify business services. The class name must be specified in the following format: nameSpace:className (for example, BMC.CORE:BMC_BusinessService).

Relationship linking Business Service and Infrastructure CI

The name of the relationship class that links business service CIs to infrastructure CIs.

The class name must be specified in the following format: nameSpace:className (for example, BMC.CORE:BMC_Dependency).

Relationship linking Business Service CIs

The name of the relationship class that links business service CIs to business service CIs

You can edit this property if the class name is other than BMC_Dependency. The class name must be specified in the following format: nameSpace:className (for example, BMC.CORE:BMC_Dependency).

Direction of relationship linking Business Service CIs

The direction of the connection between the business service CIs

If the business service CI is the source of the relationship instance connecting it with another business service CI, the value is OUT.

If the business service CI is the destination of the relationship instance connecting it with another business service CI, the value is IN.





Infrastructure CI Relationship Details

Choose one of the following options:

■ Use Service Impact relationship to traverse Infrastructure CIs ■ Use Infrastructure CI Class Name(s) to traverse Infrastructure CIs

You must provide different information, depending upon which option you choose.

Use Service Impact relationship to traverse Infrastructure CIs

Service Impact relationship class name

The name of the relationship class that is used to associate impact and direction among CIs

The name must be specified in the format: nameSpace:className

Example: BMC.CORE:BMC_BaseElement

Direction of Service Impact relationship

The direction of the impact from the infrastructure CI (which is connected to the business service) to another CI (or Computer System CI).

This property can have one of the following values: IN or OUT.

List of Infrastructure CI class names

A list of class names used to represent Infrastructure CIs

Example: BMC.CORE:BMC_SoftwareServer or BMC.CORE:BMC_Application

Use Infrastructure CI Class Name(s) to traverse Infrastructure CIs

List of Infrastructure CI class names

A list of class names used to represent Infrastructure CIs (for example, BMC.CORE:BMC_SoftwareServer or BMC.CORE:BMC_Application)

Note: Use this property only if BMC Service Impact Manager is not present.

Direction of relationship linking Infrastructure CIs

The direction of the relationship linking the CI (connected to a business service) to another CI (or the Computer System CI).

This property can have one of the following values: IN or OUT.

Depth of CI graph traversal The maximum number of levels that must be traversed from the infrastructure CI to reach the impacting computer system CI

The default value is 0, which means unlimited.

BladeLogic Property Details

Server custom property to store impacted Business Services

A read-only property that represents the name of the server class custom property that is used by the Atrium Import Job to store business service names that are impacted by BMC BladeLogic-managed servers

Custom property value separator The separator used to separate multiple business service names

The default separator is a comma (,).





6 Click the Save icon.

7 Open the Jobs workspace and create a job folder to store your Synchronization Job.

8 Right-click on a job folder and choose New > Atrium Import Job.

9 Enter a name and optional description for the job.

10 Select a folder for the job, and then click Next.

11 (optional) Set up job run notifications.

12 Click Next.

13 Choose the appropriate option:

■ To run the job immediately, select Execute job now. ■ To schedule the report to run at another time or periodically, click the New

Schedule icon . Set up the schedule, and then click OK. ■ To run the job manually later, select no option, and then click OK.

14 Click Next.

Virtual Life Cycle Data

VSSD Class Name The name of class that stores Virtual System Setting Data.

For example, BMC Atrium CMDB provides the BMC_VirtualSystemSettingData class, which stores Virtual Life Cycle Data such as Owner, Proposed Expiry Date, Reconciliation Id, and Creation Date.

The class name must be specified in the following format: nameSpace:className (for example, BMC.CORE: BMC_VirtualSystemSettingData)

Rel Linking VSSD & CIs The name of the relationship class that links Virtual System Setting Data CIs to Computer System CIs.

The class name must be specified in the following format: nameSpace:className (for example, BMC.CORE:BMC_SettingsOf).

NOTE

You should

Because business service CIs change infrequently, you can initially set the schedule to run weekly. You can reset the schedule later to run more often.




Transferring data from BMC BladeLogic to BMC Atrium CMDB

15 (optional) Select a property and then click the Edit Property icon to change the value of the property.

16 Click Next.

17 (optional) Use the controls to add, change, or delete permissions.

18 Click Finish.

19 (optional) To run the Synchronization Job manually, if you did not make a selection in step 13 on page 57 right-click the job and choose Execute.

Transferring data from BMC BladeLogic to BMC Atrium CMDB

Transferring data from BMC BladeLogic Server Automation to BMC Atrium CMDB involves two steps. The first is installing the BMC BladeLogic Atrium Integration which creates the jobs on the BMC BladeLogic Application Server, tables and views on BMC BladeLogic Decision Support for Server Automation, and exchanges on the BMC Atrium Integration Engine. The next step is optional and involves customizing the data mappings on BMC BladeLogic to control what to transfer.

NOTE For more information about these features, see the Permissions and Properties topics in Chapter 16 of the BMC BladeLogic User Guide.

NOTE Enabling the BMC BladeLogic Atrium Integration is a prerequisite for BladeLogic to Atrium Job Configuration. See “Enabling BMC BladeLogic Atrium Integration” on page 53 for more details.


Customizing data mappings between BMC BladeLogic Server Automation and BMC Atrium CMDB

Customizing data mappings between BMC BladeLogic Server Automation and BMC Atrium CMDB

Use the following procedure to map your BMC BladeLogic data to your BMC Atrium CMDB.

To customize data mappings between BMC BladeLogic Server Automation data sources and BMC Atrium CMDB classes

1 Choose Atrium Integration >Configuration from the Configuration menu and enter the BMC Remedy AR System and BMC Atrium CMDB details.

2 Run a Test connection on the BMC BladeLogic Decision Support for Server Automation panel and the AR/CMDB Configuration tab to make sure the connection is working.

3 Choose Atrium Integration >BL to Atrium Job Customization from the Configuration menu in BMC BladeLogic Server Automation.

4 In the BladeLogic to Atrium Customization dialog box, select a CMDB Class. The CMDB Class Attributes for the class are listed below. The appropriate BBSA Data Source is displayed along with the selectable BBSA Data Attributes.

The appropriate AIE Rule/Constant is displayed. For more details on AIE Rules and Constants, see your BMC Atrium Integration Engine documentation.

■ To add a new mapping, select the appropriate attributes and click Add.

■ To update an existing mapping, select it from the Attribute Mappings list and modify the mapping details. Click Update to apply the modifications.

■ To delete a mapping, select a mapping from the Attribute Mappings list and click Delete.

■ To restore the defaults, click Restore Defaults. This restores all of the initial defaults that are configured for the selected CMDB class when the BMC BladeLogic Atrium Integration is installed.

Only the default mappings for the selected class are restored, mappings of other classes remain unchanged.


Publishing the Product Catalog


The Publish Product Catalog Job retrieves a list of component templates, Virtual Guest Packages (VGP), and System Packages (SP), and publishes those to Product Catalog (PC). The Product Catalog is an application that runs on AR System and stores your hardware and software metadata. It is also known as the DML (Formerly DSL).

Component templates are published only if the ATRIUM_SYNC_ENABLED property is set to true.

The Publish Product Catalog Job is supported only for BMC Atrium CMDB version 7.6.04 and above.

NOTE ■ If there is a failure during customization due to a connection error/failure, the changes

are rolled back to the last working state with appropriate error messages.

■ Some mappings appear dimmed. These are disabled and cannot be updated or deleted. These are either primary keys or they are critical for the reconciliation job to work on the CMDB and must be transferred.

■ The following attributes are automatically generated by BMC Atrium CMDB. BMC Software recommends that you do not customize the mappings of these attributes.

■ InstanceId■ LastScanDate■ ModifiedDate■ ClassId■ CreateDate■ LastModifiedBy■ ReconciliationIdentity■ AttributeDataSourceList■ SystemClassId■ SystemName

■ To map enumeration-type BMC Atrium CMDB class attributes, verify the valid values for the attribute can have and then map only those values as constants. To verify the valid attribute values open the BMC Atrium CMDB class in the BMC Atrium CMDB user interface, find the relevant attribute, and the corresponding valid values. For more details see your BMC Atrium CMDB documentation.

NOTE Only a user with the BLAdmins role can execute the Publish Product Catalog Job. If the Publish Product Catalog Job is run by a user with any other role, the job fails.



VGPs, SPs, and component templates must be located in the following folders to be included in the Publish Product Catalog Job.

To publish the product catalog

1 If you have already configured the CMDB in your BMC BladeLogic Console, proceed to step 4.

2 Choose Atrium Integration >Configuration from the Configuration menu and enter the following BMC Atrium CMDB details on the AR/CMDB Configuration tab:

3 Click Test Connection to verify that the credentials that you entered are correct.

4 In Folders > BladeLogic > Jobs select Publish Product Catalog Job.

5 In the General panel, you name the job and give it a description.

Table 19 Folders included in the Publish Product Catalog Job

Artifact Location

component templates Component Templates\CSM_Application_Packages

VGPs Depot\CSM_Virtual_Guest_Packages

SPs Depot\CSM_OS_Packages

NOTE If there are two or more system packages, virtual guest packages, or component templates with same name and the same manufacturer, then only one entry is added in the Product Catalog.

NOTE Enabling the BMC BladeLogic Atrium Integration is a prerequisite for Publish Product Catalog Jobs. See “Enabling BMC BladeLogic Atrium Integration” on page 53 for more details.

Table 20 AR/CMDB Configuration parameters


Host Name/IP Address Host name or IP address of the computer where BMC Atrium CMDB is installed

CMDB Port Port used for communicating with BMC Atrium CMDB


CMDB User User Name for connecting to BMC Atrium CMDB

CMDB Password Password for connecting to BMC Atrium CMDB


Using data federation to view reports

6 In the Default Notifications panel, define default notifications that are generated when the job completes. Default notifications can take the form of e-mails or SNMP traps. For more information, see the Managing Jobs chapter in the BMC BladeLogic User Guide.

7 In the Schedules panel, schedule the job to execute immediately, at a specific time in the future, or on a recurring basis, and define notifications that are issued when the job runs. For more information, see the Managing Jobs chapter in the BMC BladeLogic User Guide.

8 In the Properties panel, there is a list of properties automatically assigned to each object. In this list, you can modify the value of any properties that are defined as editable. For more information, see the section about setting values for system object properties in the BMC BladeLogic User Guide.

9 In the Permissions list, grant roles access to any objects created in the system, such as jobs, servers, or depot objects. Using the Permissions panel, you can add individual permissions to an object. You can also set permissions by adding ACL templates or ACL policies. For more information, see the section about defining permissions for a system object in the BMC BladeLogic User Guide.

10 Click Finish to run the Publish Product Catalog Job.

Using data federation to view reports BMC BladeLogic Atrium Integration supports launch-in-context from the BMC BladeLogic Server Automation console and from the BMC Atrium Explorer.

The BMC BladeLogic Atrium Integration installer prompts for information about BMC Remedy Mid Tier, BMC Atrium CMDB, BMC BladeLogic Decision Support for Server Automation, and BMC BladeLogic Server Automation.

To view server reports from the BMC BladeLogic Server Automation console

1 In BMC BladeLogic Server Automation console, open the Servers workspace.

2 Right-click a server and choose Run Custom Command.

3 In the Command Selection dialog box, select Launch CI Viewer, and then click OK.

4 In the Launch CI Viewer dialog box, confirm that the selected server is in the Selected Servers pane.

5 Click Execute.


Using data federation to view reports

6 The default web browser opens with the BMC Remedy Action Request System logon page.

7 Enter a user name and password for BMC Remedy AR System, and click Log In.

8 In the BMC Atrium Explorer, right-click a BMC BladeLogic server, and choose Launch in Context > BMC SA Reports > Configuration to view the server configuration report.

To view the server compliance report, choose Launch in Context > BMC SA Reports > Compliance.

To view server reports from the BMC Atrium Explorer

1 Navigate to the BMC Atrium Core console.

2 Click Browse Instances in the navigation bar.

3 In the Browse Instances window, type search criteria to search for instances of the BMC_ComputerSystem class, and then click Search.

4 In the Search Results table, select a server in the BMC.ASSET or BMC.IMPORT.BL dataset.

5 Click Atrium Explorer.

6 In the BMC Atrium Explorer window, right-click a server, and choose Launch in Context > BMC SA Reports > Configuration to view the server configuration report.

To view the server compliance report, choose Launch in Context > BMC SA Reports > Compliance.


BMC Atrium CMDB to BMC BladeLogic mapping


The following tables list the details of the mapping of BMC Atrium CMDB attributes to BMC BladeLogic attributes. One table describes each class in BMC Atrium CMDB.

Table 21 BMC_ComputerSystem class (part 1 of 3)

Attribute in CMDB Attribute in BMC BladeLogic Comments

Where to find the attribute in BMC BladeLogic

CDMachineID NAME The name of the machine as enrolled in BMC BladeLogic

Server properties

Name FQ_HOST FQ_HOST property from Server Properties in format host name:domain

Example: vm-w23-bld27:bmc.com

Server properties

TokenId NAME for physical servers; VIRTUAL_ENTITY_TYPE or VIRTUAL_ENTITY_ID for virtual servers

For physical servers, identical to the NAME attribute

For virtual machines, one of the following forms:

■ EntityType:EntityId for VMware and Microsoft Hypervisor:

VI-UUID:EntityIdHYPERV-ID:EntityId

■ EntityId for all other virtual machines

Example: VI-UUID:VM123456

For physical servers, Server properties.

For virtual servers, from the Configuration menu, select Property Dictionary View. Under System Object, expand Built-In Property Classes. Click the Virtualization class, then click the Instances tab on the right. Double-click a particular instance to see the attribute values.

HostName NORMALIZED_HOSTNAME/Host

If (NORMALIZED_HOSTNAME is Null) then Host else NORMALIZED_HOSTNAME

NORMALIZED_HOSTNAME is a custom property that is created by the NSH Job that uses the getNormalizedHostname.sh script that comes with the installer

Server properties



Domain FQ_HOST Domain obtained from the FQ_HOST attribute in Server Properties

Server properties

Category Constant value populated: Hardware

Item If you selected Best Practice categorization during installation, then Item gets a constant value of Processing Unit. Otherwise, it gets a constant value of Machine.

Type If you selected Best Practice categorization during installation, then Type gets a constant value of Server. Otherwise, it gets a constant value of BMC Discovered

LastScanDate LAST_UPDATED_DATE

Last Modified date Server properties

MarkAsDeleted Based on whether the server is decommissioned or not the entry might be soft deleted. Possible values: Yes or No

PrimaryCapability Constant value: Server

NameFormat When the CDMachineID is a fully qualified name then the value of NameFormat is Token. Otherwise, the value is HostName.

ShortDescription Same as TokenID

Notes STATE:Agent Status Server properties

Description DESCRIPTION Server properties

DatasetId Constant value BMC.IMPORT.BL

isVirtual IS_VIRTUAL ■ Yes if the server is a virtual machine

■ No if the server is not a virtual machine

Server properties






ManufacturerName Manufacturer 1. Right-click the server in the Folder menu.

2. Select Browse.

3. Select Hardware Information > Machine Summary.

SerialNumber SerialNumber

Model Model

NumberOfSlots NumberOfProcessors

TotalPhysicalMemory Memory Total Memory available on the server

Table 22 BMC_IPEndpoint class (part 1 of 3)



CDMachineID NAME for physical servers; VIRTUAL_ENTITY_TYPE or VIRTUAL_ENTITY_ID for virtual servers

In case of a physical server, identical to the NAME attribute

If it is a virtual machine, it takes one of the following forms:

■ VI-UUID:EntityId for VMware

■ HYPERV-ID:EntityId for Microsoft

■ EntityId for other types of VMs




Name andAddress

ADDRESS If the value of PROXY_IP_ADDRESS is Null, then the value of Name and Address is IP_ADDRESS. Otherwise it is PROXY_IP_ADDRESS

PROXY_IP_ADDRESS is a custom property that you can use if you have proxy servers proxies.

1. Live browse.

2. Expand Hardware Information > Operating System > Network Connections.

3. View the right pane.

AddressType Constant value IPv4







DNSHostName DNSIPADDRESS 1. Live browse.



Category If you selected Best Practice categorization during installation, then Category gets a constant value of Miscellaneous. Otherwise it gets a constant value of System Settings.

1. Live browse.



Item If you selected Best Practice categorization during installation, then Item gets a constant value of Address. Otherwise it gets a constant value of Network

Type If you selected Best Practice categorization during installation, then Type gets a constant value of IP Address. Otherwise, it gets a constant value of BMC Discovered.

LastScanDate LastScanned Last Modified date

MarkAsDeleted Based on whether the server is decommissioned or not this entry might be soft deleted

NameFormat Constant value IP

ProtocolType Constant value IPv4

ShortDescription NODENAME 1. Live browse.








SubnetMask NETMASK 1. Live browse.



TokenId DNSIPADDRESS If the value of PROXY_IP_ADDRESS is Null, then the value of Name and Address is IP_ADDRESS. Otherwise it is PROXY_IP_ADDRESS

PROXY_IP_ADDRESS is a custom property that you can use if you have proxy servers proxies.

1. Live browse.



Table 23 BMC_OperatingSystem class (part 1 of 3)



CDMachineID NAME for physical servers; VIRTUAL_ENTITY_TYPE or VIRTUAL_ENTITY_ID for virtual servers

If this is a physical server, CDMachineID is identical to the NAME attribute








Name OS_NAME Server properties






Model PRODUCT:SYSTEMDIRECTORY

PRODUCT:SYSTEMDIRECTORY

1. Live browse.

2. Expand Hardware Information > Operating System.

3. Look for the OS Details row on the right pane.

Category If you selected Best Practice categorization during installation, then Category gets a constant value of Software. Otherwise, it gets a constant value of System Settings.

Item If you selected Best Practice categorization during installation, then Item gets a constant value of Operating System Software. Otherwise it gets a constant value Operating System

Type If you selected Best Practice categorization during installation, then Type gets a constant value of Standard OS. Otherwise it gets a constant value of BMC Discovered.


Server properties

LastScanDate LastScanned Last Modified Date

ManufacturerName OS_VENDOR Server properties

NameFormat OSName

OSType One of the following:

■ Windows XP■ Windows 2000 ■ Windows 2003 ■ AIX ■ LINUX ■ SunOS ■ Solaris ■ HPUX ■ Other

Server properties






PatchNumber OS_PATCHLEVEL If OS_NAME contains the word Windows, PatchNumber is an empty string; otherwise, the value is copied from OS_PATCHLEVEL.

Server properties

ServicePack OS_PATCHLEVEL IF OS_NAME contains the word Windows, this value is entered from OS_PATCHLEVEL.

Server properties

ShortDescription PRODUCT 1. Live browse.

2. Expand Hardware Information > Operating System.

3. Look for the OS Details row on the right pane.

SystemDirectory SYSTEMDIRECTORY Server properties

VERSION VERSION Server properties

TokenId PRODUCT;SYSTEMDIRECTORY

PRODUCT;SYSTEMDIRECTORY

Server properties






Table 24 BMC_Processor class (part 1 of 2)



CDMachineID NAME for physical servers; VIRTUAL_ENTITY_TYPE and VIRTUAL_ENTITY_ID for virtual servers

If this is a physical server, CDMachineID is identical to the Name attribute

If this is a virtual machine, it takes one of the following forms:







Name DeviceID 1. Live browse.

2. Expand Hardware Information > Hardware > Processor.



Category Constant value Hardware

Type If you selected Best Practice categorization during installation, then Type gets a constant value of CPU. Otherwise it gets a constant value of BMC Discovered.

MaxClockSpeed SPEED (in MHz) 1. Live browse.



ManufacturereName Manufacturer As above



Item If you selected Best Practice categorization during installation, then Item gets a constant value of Component. Otherwise it gets a constant value of Processor.

Model Model 1. Live browse.



TokenId DeviceID As above

NameFormat DeviceID or Processor Name

If the OS is Windows, the value of NameFormat is DeviceID. Otherwise it is ProcessorName.

As above

ShortDescription DeviceID As above

MarkAsDeleted Based on whether the server is decommissioned or not the entry might be soft deleted

Description Description 1. Live browse.



Table 24 BMC_Processor class (part 2 of 2)





Table 25 BMC_BIOSElement class (part 1 of 2)



CDMachineID Name for physical servers; Entity type and Entity Id for virtual servers

In case of a physical server, identical to the Name attribute









Category If you selected Best Practice categorization during installation, then Category gets a constant value of Software. Otherwise it gets a constant value of System Settings.

Type If you selected Best Practice categorization during installation, then Type gets a constant value of BIOS/Firmware. Otherwise it gets a constant value of BMC Discovered.

If you selected Best Practice categorization during installation, then Type gets a constant value of BIOS/Firmware. Otherwise it gets a constant value of BMC Discovered.

VersionNumber Version 1. Live browse.

2. Expand Hardware Information.

3. Select the Hardware node.


BuildNumber Build Number As above

Name As above



Item If you selected Best Practice categorization during installation, then Item gets a constant value of Operating System Software. Otherwise it gets a constant value of BIOS.

TokenId Version or Name If the OS is Windows, the value of TokenId is the Windows version. Otherwise it is the name of the operating system.

NameFormat Constant value BiosName

ShortDescription Name


NOTE BMC BladeLogic Server Automation does not discover BIOS element details on IBM AIX and HP-UX platforms. This means that BIOS element details are not imported to the BMC Atrium CMDB.

Table 25 BMC_BIOSElement class (part 2 of 2)





Table 26 BMC_NetworkPort class (part 1 of 2)




If this is a physical server, CDMachineID is identical to the Name attribute








PermanentAddress MAC Address Note: BMC BladeLogic Server Automation does not detect the MAC Address for disconnected NICs.

1. Live browse.

2. Expand Hardware Information > Hardware > Network Cards.

3. Select the Network Cards node.


Short Description Product Name As above

DatasetId Constant value: BMC.IMPORT.BL


Type If during installation Best Practice categorization selected then constant value Network Interface Card

Else constant value BMC Discovered

Item If, during installation, Best Practice Categorization is selected

then constant value Card

else constant value BMC Discovered




2. Expand Hardware Information > Hardware > Network Cards.

3. Select the Network Cards node.


NetworkAddresses MAC Address Note: BMC BladeLogic Server Automation does not detect the MAC Address for disconnected NICs.

As above

Name MAC Address Note: BMC BladeLogic Server Automation does not detect the MAC Address for disconnected NICs.

As above

ManufacturerName manufacturer As above

Model Model As above

TokenId Interface Name or MAC Address

InterfaceName:macAddress where InterfaceName is not null and macAddress is not null

Note: BMC BladeLogic Server Automation does not detect the MAC Address for disconnected NICs.

NameFormat Constant value MACAddress


Table 26 BMC_NetworkPort class (part 2 of 2)





Table 27 BMC_LocalFileSystem class (part 1 of 2)













Category If during installation Best Practice categorization is selected, then Category gets a constant value of Miscellaneous.

Otherwise, it gets a the value of System Settings

Type If during installation Best Practice categorization is selected, then Type gets a constant value of Local File System.

Otherwise, it gets a constant value of BMC Discovered.

Item If during installation Best Practice categorization is selected, then Item gets a constant value of Instance.

Otherwise, it gets a constant value of File System.


2. Expand Hardware Information > Hardware > Logical Storage Device.




TokenId DeviceID 1. Live browse.



ShortDescription DeviceID As above

NameFormat Constant value DeviceID




MarkAsDeleted Based on whether the server is decommissioned or not the entry might be soft deleted.

Table 27 BMC_LocalFileSystem class (part 2 of 2)





Table 28 BMC_DiskDrive class (part 1 of 2)

Attribute in CMDB Attribute in BMC BladeLogic Comments Where to find the attribute in BMC BladeLogic












Type If during installation Best Practice categorization selected then constant value Disk Drive

Else constant value BMC Discovered

Item Keep blank columns, to be populated using Categorization Rules


2. Expand Hardware Information > Hardware > Physical Storage Device.


ManufacturerName Manufacturer As above

SerialNumber Serial Number As above

Size Capacity measured in KB As above

TokenId DeviceID As above

Model Model As above



ShortDescription DEVICEID As above

Description Description As above

NameFormat Name for physical servers; Entity type and Entity Id for virtual servers

Constant value DeviceID


Table 29 BMC_Memory class (part 1 of 2)














Item If during installation Best Practice categorization selected then constant value Component

Else constant value Memory Card

Type If during installation Best Practice categorization selected then constant value Component

Else constant value Memory Card

Table 28 BMC_DiskDrive class (part 2 of 2)

Attribute in CMDB Attribute in BMC BladeLogic Comments Where to find the attribute in BMC BladeLogic



Name Tag 1. Live browse.



TokenId Tag As above

NameFormat Constant value Tag

Model Model 1. Live browse.



ManufacturerName Manufacturer As above

Speed Speed As above

FormFactor FormFactor As above

MemoryType MemoryType MemoryType can be any one of the following:

DRAM, Synchronous DRAM, Cache DRAM, EDO, EDRAM, VRAM, SRAM, RAM, ROM, Flash, EEPROM, FEPROM, EPROM, CDRAM, 3DRAM, SDRAM, SGRAM, RDRAM, DDR

If the MemoryType is not one of the above, the value of this attribute is Other.

As above

Description Description As above

Capacity Capacity As above


Table 29 BMC_Memory class (part 2 of 2)





NOTE BMC BladeLogic Server Automation does not discover memory details on Solaris and AIX platforms. This means that memory details are not imported to the BMC Atrium CMDB.

Table 30 BMC_VirtualSystemSettingData class (part 1 of 2)



CDMachineID Server_Name The name of the machine as enrolled in BMC BladeLogic

Server Properties

TokenId VIRTUAL_ENTITY_TYPE + VIRTUAL_ENTITY_ID


■ EntityType:EntityId for VMware and Microsoft Hypervisor:

VI-UUID:EntityIdHYPERV-ID:EntityId

■ EntityId for all other virtual machines


Select the Configuration tab. Click Property Dictionary View. Expand the Built-In Property Class under System Object in the Property Dictionary pane. Select Virtualization. Select Instances in the right pane. Double-click the instance that you want to browse.


Category Constant value Unknown

Item Constant value Unknown

Type Constant value Unknown

ProposedDecommissionDate EXPIRY DATE The expiry date of the VM Select the Configuration Tab. Click Property Dictionary View. Expand Built-In Property Class under System Object in the Property Dictionary Pane. Select LifeCycle. Select Instances in the right pane. Double-click the instance that you want to browse.



OwnerName Owner As above

VirtualSystemType VIRTUAL_ENTITY_TYPE

Entity_Type assigned in the Virtualization instance, one of:

■ VMware ■ Solaris Container ■ LPAR ■ Microsoft Hyper-V ■ Other

As above

Name SERVER_NAME FQ_HOST property from Server Properties in format hostname:domain

Example: vm-w23-bld27:bmc.com

Server Properties

LastScanDate LastScanned Last Modified Date


Table 30 BMC_VirtualSystemSettingData class (part 2 of 2)






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

Aactivities

identification 16merge 17

AIE. See BMC Atrium Integration Engineattribute mapping 64

BBMC Atrium CMDB

transferring data to BMC BladeLogic 47BMC Atrium Discovery and Dependency Mapping 25BMC Atrium Integration Engine 14BMC Atrium Integration Engine, transferring data with 47BMC BladeLogic

transferring data to BMC Atrium CMDB 47BMC BladeLogic Import dataset 16BMC BladeLogic Integration for Atrium

about 12installing 19uninstalling 42

BMC BladeLogic Integration to Atriumprerequisites 20upgrading 23

BMC Software, contacting 2BMC_BIOSElement class 73BMC_ComputerSystem class 64BMC_Dependency class 55BMC_DiskDrive class 79BMC_IPEndpoint class 66BMC_LocalFileSystem class 77BMC_Memory class 80BMC_NetworkPort class 75BMC_OperatingSystem class 68BMC_Processor class 71BMC_VirtualSystemSettingData class 82business services

importing 54transferring data 53

CCI class data mappings 48

CI classes 15CI mapping 64configuring synchronization jobs 53, 54customer support 3

Ddata

creating exchanges 15creating mappings 15integrating discovered 14integration exchanges 51integration mappings 48reconciling discovered 16transferring between BMC BladeLogic and BMC

Atrium CMDB 47transferring using business service extraction 53transfers, completion of 33

data exchanges 51BL_CALL_INIT 33BL_LOAD_SRVR_PROPS 33integration 51running manually 33

data federation, using to view reports 62data mappings

CI class 48relationship class 50

discovered dataintegrating BMC BladeLogic 14

downloading the product 25

Eexchanges

data integration 51data, running manually 33

extract, transform, and load (ETL) tool 14

Ffederation, data, viewing reports with 62

85

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

IImport dataset 16importing

Atrium Import Job 54business services 54

installation prerequisites 20installing

BMC BladeLogic Integration for Atrium 19data exchanges and 51prerequisites 24

installing the product 27integrating discovered data 14integration

architecture, BMC BladeLogic 14data exchanges 51data mappings 48

Jjobs

Atrium Import Job 54configuring synchronization 53, 54

Mmapping

CIs to attributes 64merge activity 17

OOracle RAC 22

Pprerequisites 20prerequisites, installation 24product

downloading 25installing 27

product support 3

RRAC 22reconciling discovered data 16relationship class data mappings 50renamed servers 17reports

viewing 62viewing server compliance 62viewing server configuration 62

86 BMC BladeLogic Atrium Integration Implementation

viewing with data federation 62

Sscheduling

synchronization jobs 53, 54server compliance reports, viewing 62server configuration reports, viewing 62servers

renamed in BMC BladeLogic 17SID 36SP 60support, customer 3synchronization jobs, configuring and scheduling 53, 54

Ttechnical support 3Token ID 16transferring data 53

about 47using BMC Atrium Integration Engine 47using business service extraction 53

Uuninstalling BMC BladeLogic Integration for Atrium 42upgrading 23

VVGP 60viewing

reports by using data federation 62server compliance reports 62server configuration reports 62

Guide

Notes

*193946**193946**193946**193946*

*193946*

Blade Logic Atrium Integration Guide vs 8.1

Documents

program filesbmc

program filesbmc

logical storage

installation

bmc atrium

bmc software

bmc atrium

bmc atrium