Atrium Integrator 7.6.04 User´s Guide

www.bmc.com

Atrium Integrator 7.6.04

Users Guide

January 2011

If you have comments or suggestions about this documentation, contact Information Design and Development by email at [email protected].

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

DB2, IBM, and Informix are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

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

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.

YoSu

Su

Yoht

Su

In senSuyo

Be

Ha

Customer Support

u can obtain technical support by using the Support page on the BMC Software website or by contacting Customer pport by telephone or email. To expedite your inquiry, please see Before Contacting BMC Software.

pport website

u can obtain technical support from BMC Software 24 hours a day, 7 days a week attp://www.bmc.com/support. From this website, you can:

Read overviews about support services and programs that BMC Software offers.Find the most current information about BMC Software products.Search a database for problems similar to yours and possible solutions.Order or download product documentation.Report a problem or ask a question.Subscribe to receive email notices when new product versions are released.Find worldwide BMC Software support center locations and contact information, including email addresses, fax numbers, and telephone numbers.

pport by telephone or email

the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813 or d an email message to [email protected]. (In the Subject line, enter pID:, such as SupID:12345.) Outside the United States and Canada, contact ur local support center for assistance.

fore contacting BMC Software

ve 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 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 problem

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

If yme

License key and password information

ou have a question about your license key or password, contact Customer Support through one of the following thods:

E-mail [email protected]. (In the Subject line, enter SupID:, such as SupID:12345.)

In the United States and Canada, call 800 537 1813. Outside the United States and Canada, contact your local support center for assistance.

Submit a new issue at http://www.bmc.com/support.

CAdding an attribute to the BMC_DiskDrive class . . . . . . . . . . . . . . . . . . . . . . . . . . 31Transferring Calbro data to BMC Atrium CMDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Creating a data transfer job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Opening the job and transformations in Spoon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Editing the job in Spoon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Running the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Verifying that the transferred data is in BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . 49Monitoring the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50ontents

BMC Atrium Core documentation 9

Chapter 1 Understanding Atrium Integrator 13

Atrium Integrator value proposition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Overview of Atrium Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Calbro Services user story. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Atrium Integrator terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Overview of the data transfer process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Atrium Integrator components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Manage Data Stores tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Integration Job Builder wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Atrium Integrator console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Spoon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Carte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Performance considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Preparing to transfer data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Accessing the Atrium Integrator console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 2 Scenario for transferring data to BMC Atrium CMDB 27

Source data organization at Calbro Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Mapping source data to BMC Atrium CMDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Mapping relationship classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Preparing to transfer Calbro Services data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Creating a dataset for the Calbro data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Creating a database connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Contents 5

6Chapter 3 Working with data store connections 53

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Supported data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Creating a new data store connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

RPC Ports in BMC Atrium CMDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Editing a data store connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Deleting a data store connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 4 Creating a job 61

Creating a simple job through the Integration Job Builder wizard. . . . . . . . . . . . . . . . 62High-level steps for creating a job through the Integration Job Builder wizard . 62Creating a job through the Integration Job Builder wizard . . . . . . . . . . . . . . . . . . . 64

Creating a complex job in Spoon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Creating a job to migrate data from a development server to a production server.

82

Chapter 5 Editing jobs and transformations 85

Opening your job or transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Mapping the Integration Job Builder wizard output to Spoon steps . . . . . . . . . . . . . . 87Connecting transformation steps or job entries in Spoon. . . . . . . . . . . . . . . . . . . . . . . . 88

Creating a hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Reversing the direction of a hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Disabling a hop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Deleting a hop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Specifying the condition on which a job entry is executed . . . . . . . . . . . . . . . . . . . 89Transformation hop colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Adding intermediate steps to a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Adding intermediate steps to a transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Editing transformation steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Editing transformation properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Launching several copies of a step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Changing data mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Exploring a database connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Browsing source data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Changing source configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Chapter 6 Running and monitoring a job 105

Running a job from the Atrium Integrator console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Running a job in Spoon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Monitoring jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Viewing job history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Viewing job details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Changing the job schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Users Guide

Chapter 7 Debugging and troubleshooting jobs 113

Troubleshooting Atrium Integrator console issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Job fails to run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Job not displayed on the Atrium Integrator console . . . . . . . . . . . . . . . . . . . . . . . 115Job not running from the Atrium Integrator console. . . . . . . . . . . . . . . . . . . . . . . 116

Troubleshooting errors displayed in Spoon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Location of log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Error connecting to a Microsoft SQL Server database using Windows Authentication

in Spoon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Atrium Integrator Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Chapter 8 Migrating jobs to a production server 125

Appendix A Moving from BMC Atrium Integration Engine to Atrium Integrator 127

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Index 131Contents 7

8 Users Guide

B T

AU

BA

BCD

B7.

Note: This Help is provided in HTML and is available on the BMC Atrium Core media. It is not available on the BMC Customer Support site.

BDMC Atrium CMDB 7.6.04 ata Modeling Guide

Best practices for using the classes that BMC provides for BMC Atrium CMDB (both the CDM and extensions) to model complex business entities, focusing on the use of multiple related CIs to model

Configuration managers, application administrators, and asset analysts.MC Atrium Core documentation

This section describes the complete set of BMC Atrium Core documentation, including manuals, help systems, videos, and so on.

Unless otherwise noted, documentation is available free of charge on the BMC Atrium Core documentation media (DVD or Electronic Product Download bundle) and on the BMC Customer Support site, at http://www.bmc.com/support.

To find this documentation on the BMC Customer Support site, choose Product Documentation > Supported Product A-Z List > BMC Atrium CMDB Enterprise Manager >7.6.04

itle Description Audience

trium Integrator 7.6.04 ser's Guide

Information about defining source and target connections, creating jobs and transformations, editing and monitoring jobs, and other Atrium Integrator concepts.

Users who are responsible for setting up data transfer integrations between external data stores and BMC Atrium CMDB.

MC Atrium CMDB 7.6.04 dministrator's Guide

Information about setting permissions, configuring federation, modifying the data model, configuring an impact model, and other administrative tasks in BMC Atrium Configuration Management Database (BMC Atrium CMDB).

Configuration managers, application administrators, and asset analysts.

MC Atrium CMDB 7.6.04 ommon Data Model iagram

Hierarchical diagram of all classes in the Common Data Model (CDM), including unique attributes and applicable relationships.


MC Atrium CMDB 6.04 Data Model Help

Description and details of superclasses, subclasses, attributes, and relationship classes for each class. Contains only information about the CDM at first, but you can update it to include information about data model extensions that you install.

Configuration managers, application administrators, and asset analysts.BMC Atrium Core documentation 9

an entity rather than on general information about a class or attribute.

10


B7.

BNR

B7.

BU

BYE

BC

BCG

TMC Atrium CMDB 6.04 Javadoc Help

Information about Oracle Java classes, methods, and variables that integrate with BMC Atrium CMDB.


Application programmers.

MC Atrium CMDB 7.6.04 ormalization and econciliation Guide

Information about normalizing data in BMC Atrium CMDB and reconciling CIs from different data providers into a single production dataset.


MC Atrium CMDB 6.04 Online Help

Help for using and configuring BMC Atrium CMDB, including Atrium Integrator, BMC Atrium Product Catalog, Reconciliation Engine, Normalization Engine, and so on.

Note: This Help is provided in HTML and is available through the Help links in the BMC Atrium CMDB user interface. It is not available on the BMC Customer Support site.

Configuration managers, application administrators, asset analysts, and users that work with CIs and need to understand the relationships that exist within BMC Atrium CMDB.

MC Atrium CMDB 7.6.04 ser's Guide

Information about using BMC Atrium CMDB, including searching for and comparing CIs and relationships, relating CIs, viewing history, running impact simulations, and viewing federated data.

Users that work with CIs and need to understand the relationships that exist within BMC Atrium CMDB.

MC Atrium Core: Taking our Data Into Production nd to End

End-to-end high-level steps for bringing data into BMC Atrium CMDB from a third-party source and making it available in your production dataset.

Note: This Flash video is available on the BMC Atrium Core media. It is not available on the BMC Customer Support site.


MC Atrium Core 7.6.04 ompatibility Matrix

Information about the BMC Atrium Core configurations that are expected to work together based on design, testing, or general understanding of the interaction between products.

Note: Download the BMC Atrium Core 7.6.04 Compatibility Matrix from the BMC Customer Support site at http://www.bmc.com/support/reg/remedy-compatibility-tables.html?c=n.


MC Atrium Core 7.6.04 oncepts and Planning uide

Information about CMDB concepts and high-level steps for planning and implementing BMC Atrium Core.

Anyone who wants to learn about and understand BMC Atrium Core products, CMDBs in general, and the functionality of BMC Atrium CMDB in particular.IT leaders, configuration managers, application administrators, and asset analysts are some who will benefit from this information.

itle Description AudienceUsers Guide

BD

BIn

BM

BPG

BR

BT

BW

BED

BE

TMC Atrium Core 7.6.04 evelopers Reference Guide

Information about creating API programs using C API functions and data structures.

Application administrators and programmers.

MC Atrium Core 7.6.04 stallation Guide

Information about installing, upgrading, and uninstalling BMC Atrium Core features.

Application administrators.

MC Atrium Core 7.6.04 aster Index

Combined index of all guides. Everyone.

MC Atrium Core 7.6.04 roduct Catalog and DML uide

Information about configuring the Product Catalog and DML, adding products, and creating aliases for products, manufacturers, and categorizations.

System administrators, IT managers, network managers, and other qualified personnel who are familiar with their computing and networking environment.

MC Atrium Core 7.6.04 elease Notes

Information about new features, known issues, and other late-breaking topics.

Everyone.

MC Atrium Core 7.6.04 roubleshooting Guide

Information about resolving issues with BMC Atrium Core components, including API, filter, and console error messages and their solutions.

Application administrators, programmers, and BMC Support personnel.

MC Atrium Core 7.6.04 eb Services Help

Information about using BMC Atrium Core Web Services, including how to publish and find interfaces in the Web Services Registry, set versions, disambiguate web services, configure security policies and encryption, and use BMC Atrium Core Web Services data structures and operations.


Application administrators and programmers.

MC Atrium Integration ngine 7.6.04 ADK eveloper's Guide

Information about how to build adapters that can transfer information between an external data store and either BMC Remedy AR System forms or BMC Atrium CMDB.

Developers who have a basic understanding of BMC Atrium Integration Engine and want to build adapters that can exchange data between two data sources.

MC Atrium Integration ngine 7.6.04 Online Help

Help for using and configuring BMC Atrium Integration Engine.

Note: This Help is provided in HTML and is available through the Help links in the BMC Atrium Integration Engine user interface. It is not available on the BMC Customer Support site.

Users who are responsible for setting up data transfer integrations between external data stores and either BMC Atrium CMDB or BMC Remedy AR System.

itle Description AudienceBMC Atrium Core documentation 11

12


BE

MBC

TMC Atrium Integration ngine 7.6.04 User's Guide

Information about creating data exchanges and data mappings, defining rules and queries, activating event-driven data exchanges, defining connection settings, and other BMC Atrium Integration Engine concepts.

Users who are responsible for setting up data transfer integrations between external data stores and either BMC Atrium CMDB or BMC Remedy AR System.

apping Your Data to MC Atrium CMDB 7.6.04 lasses

Spreadsheet that maps common IT objects to the appropriate class, whether part of the CDM or an extension. This spreadsheet also includes information about further categorizing instances using key attributes, and best practices for creating normalized relationships.


itle Description AudienceUsers Guide

Preparing to transfer data (page 24) Accessing the Atrium Integrator console (page 24)Chapter

1 Understanding Atrium IntegratorAtrium Integrator is an integration engine that enables you to transfer data from external data stores to BMC Atrium Configuration Management Database (BMC Atrium CMDB) classes. You can connect to a wide variety of input sources using connectors such as JDBC, ODBC, JMS, native databases, web services, and complex XML. Atrium Integrator provides you with the ability to clean and transform your data before putting it into BMC Atrium CMDB.

Atrium Integrator replaces BMC Atrium Integration Engine. You can continue using BMC Atrium Integration Engine for existing data mappings and exchanges, but BMC recommends that you use Atrium Integrator for all new data transfers. BMC Atrium Integration Engine will be deprecated in a future release.

The following topics are provided:

Atrium Integrator value proposition (page 14) Overview of Atrium Integrator (page 14) Calbro Services user story (page 15) Datasets (page 16) Atrium Integrator terminology (page 17) Overview of the data transfer process (page 17) Atrium Integrator components (page 18) Performance considerations (page 23)Chapter 1 Understanding Atrium Integrator 13

14


A

Otrium Integrator value propositionYour IT management data resides in multiple repositoriesfor example, in an SQL table, an XML file, and a non-BMC discovery dataset. You want to load this data into the BMC Atrium CMDB.

You can use Atrium Integrator to load data from multiple external repositories into the BMC Atrium CMDB. You can define how external data maps to Atrium CMDB and transform external data using various rules

With Atrium Integrator, you can schedule and perform bulk data transfers. You can also use Atrium Integrator for initial data loading, incremental data transfers, and data synchronization. For example, you can use Atrium Integrator to synchronize IT data from a discovery application with BMC Atrium CMDB, where it can be reconciled with data from other sources to your production dataset.

During data transfers, Atrium Integrator identifies the records to be transferred and performs some or all of the following tasks, depending on how you have configured your integration:

Reads records

Creates new records

Updates records

Deletes records

Modifies data (such as concatenating fields)

verview of Atrium IntegratorThis section describes how Atrium Integrator integrates with the BMC Atrium Core components to form a solution. This architecture is shown in Figure 1-1. Users Guide

Calbro Services user story

CFigure 1-1: BMC Atrium Core architecture

Atrium Integrator transfers data from an external datastore to BMC Atrium CMDB. When the data is in a BMC Atrium CMDB dataset, the Normalization Engine ensures that data from different data providers is consistent. The Reconciliation Engine merges data from multiple import datasets into the BMC Asset dataset. For more information about datasets, see Datasets on page 16.

albro Services user storyThis document uses a fictional company named Calbro Services to explain how Atrium Integrator principles and procedures are used in practice. Although Calbro Services is a fictional company, it is based on research of actual BMC customers. Seeing how Calbro Services completes tasks should prove useful as you implement Atrium Integrator in your own environment.

Calbro Services needs to transfer its existing data about processors, disk drives, printers, and so on to their centralized database in New York. This data resides in multiple databases, flat files, and XML files in various locations across the globe. Calbro Services wants to transfer information from its Chicago, London, Dublin, and Adelaide sites to their New York centralized database. Calbro Services also wants to transfer the personnel records of employees from the Dublin site to the New York site.

This guide provides examples for transferring this data.

BMC Atrium Core

BMC Atrium CMDB

DatabasesComplex XML file

CSV file

Discovery application

Atrium Integrator

Rec

onci

liatio

n E

ngin

e

Nor

ma

lizat

ion

Engi

ne

Import datasets

BMC RemedyAsset Mgmt

Federated data

OtherConsumers

Sandbox dataset

Production dataset

BMC AtriumProduct CatalogChapter 1 Understanding Atrium Integrator 15

16


DatasetsA dataset is a logical group of data in BMC Atrium CMDB. It is a collection of CIs and relationships for a given purpose. A dataset can represent data from a particular source or a snapshot from a particular date. The primary purpose of datasets is to partition data according to the data providers. Each discovery application that you use should store the data it collects in a separate dataset. You can also use datasets for any other logical group of data.

All CIs and relationships in BMC Atrium CMDB reside in a particular dataset, which is specified by the value of their DatasetID attribute.

BMC discovery products and BMC Remedy Asset Management provide the default datasets in BMC Atrium CMDB, as shown in Table 1-1.

The BMC Asset dataset is used as the production dataset and is used by BMC products for reconciled data. The Reconciliation Engine merges data from multiple import datasets in the BMC Asset dataset. Data consumers should use this consolidated view of your data and you should base your business decisions on the data in this dataset.

NOTE Do not use Atrium Integrator to transfer data directly into the BMC Asset dataset. Instead, transfer the data into another dataset and then reconcile it into BMC Asset.

If you use a third-party product to discover products, you should create a different dataset to bring in this data. For information about creating datasets, see the BMC Atrium CMDB 7.6.04 Normalization and Reconciliation Guide.

For more information about configuring datasets, see the BMC Atrium CMDB 7.6.04 Normalization and Reconciliation Guide.

Table 1-1: Default datasets in BMC Atrium CMDB

Data created by Dataset name DatasetID

BMC Atrium CMDB BMC Asset BMC.ASSET

BMC Sample BMC.SAMPLE

BMC Remedy Asset Management BMC.ASSET.SANDBOX BMC.ASSET.SANDBOX

BMC BladeLogic Client Automation BMC Configuration Import BMC.IMPORT.CONFIG

BMC Atrium Discovery and Dependency Mapping

BMC Topology Import BMC.IMPORT.TOPOUsers Guide

Atrium Integrator terminology

A

Otrium Integrator terminologyThe complete process of transferring data from an external source (for example, an XML file) to a BMC Atrium CMDB CI class is referred to as an integration.

The following terms are used in Atrium Integrator to describe the various aspects of an integration:

A transformation is the combination of steps and hops that make an integration between source and target data stores possible. It reads data from the source data store, transforms it according to the rules that you specify, and stores it in the target data store.

A transformation consists of a series of steps. Steps define the input and output data stores as well the clean up or adjustment actions that you might want to perform on the data before adding it to BMC Atrium CMDB.

Steps are connected by hops, which indicate the direction of the data flow.

A job defines the order in which a series of transformations are run so that the dependencies of the individual transformations are met.

A repository is a relational database in which you can store your transformations and jobs. You can also use a repository to store the logs that are generated when executing transformations and jobs.

verview of the data transfer processTo transfer data into BMC Atrium CMDB, follow the process outlined in the following steps.

Figure 1-2: Overview of the data transfer process

Each step represents a procedure. In the section that relates to each procedure, the graphic is repeated, and the related step is highlighted.

Step 1 Configure source and target connection.

You must define connection parameters (such as host name, port number, user name, and password) to your external data store and BMC Atrium CMDB. After you create a connection, you can reuse it for multiple transformations or jobs. For instructions, see Chapter 3, Working with data store connections.

1 Congure source 2 Create and 3 Edit transformation 4 Run job 5 Monitor job & target connection schedule job or job Chapter 1 Understanding Atrium Integrator 17

18


AStep 2 Create a job or transformation.

The Integration Job Builder wizard guides you through the process of creating a job or transformation. After you specify the source and the CIs that you want to import, the wizard makes recommendations on the relationships for the selected CIs. For instructions, see Chapter 4, Creating a job.

You can also create a job in the Pentaho Spoon application. For instructions, see the Spoon User Guide at http://wiki.pentaho.com/display/EAI/Spoon+User+Guide.

Step 3 Edit your transformation or job in Spoon.

You can add intermediate steps for cleaning up or manipulating your data before adding it to BMC Atrium CMDB. Spoon provides support for JavaScript and a wide variety of prebuilt functions. For instructions, see Chapter 5, Editing jobs and transformations.

Step 4 Verify and run your job. If the job completes without any errors, verify that the data has been added to the appropriate BMC Atrium CMDB class. If the job displays error messages, debug the job and run it again. For instructions, see Chapter 6, Running and monitoring a job.

Step 5 Monitor your jobs.

After you create and run your job, you can monitor it. The Atrium Integrator console displays the job run information. For information, see Chapter 6, Running and monitoring a job.

Step 6 Migrate your jobs to a production server

After you create and test your data transfer jobs on a development computer, you can migrate them to a production server. For information, see Chapter 8, Migrating jobs to a production server.

Chapter 2, Scenario for transferring data to BMC Atrium CMDB takes you through the complete data transfer process for a sample scenario.

trium Integrator componentsAtrium Integrator uses the Pentaho Data Integration tool and has the following main components:

Manage Data Stores tool (page 20)

Integration Job Builder wizard (page 20)

Spoon (page 21)

Carte (page 23)Users Guide

Atrium Integrator componentsFigure 1-3 on page 19 shows the Pentaho Data Integration tool components, Spoon and the Pentaho Carte application, in relation to the BMC Atrium Core architecture.

Figure 1-3: Pentaho Data Integration components in relation to BMC Atrium Core

Figure 1-4 on page 20 shows how the Atrium Integrator components work together.

BMC Atrium CoreConsole

Database

Repository

Source data to be tranferred to BMC

Atrium CMDB

Carte server

Pentaho Spoon

CMDB plugin

BMC Remedy Action Request

System

BMC AtriumCMDB

BMC Remedy Mid Tier

Atrium IntegratorconsoleChapter 1 Understanding Atrium Integrator 19

20


M

In

AFigure 1-4: Atrium Integrator components

anage Data Stores toolThe Manage Data Stores tools helps you define connection parameters (such as host name, port number, user name and password) to your external data store and BMC Atrium CMDB.

tegration Job Builder wizardThe Integration Job Builder wizard helps you create a job for transferring your data from an external data store to BMC Atrium CMDB. You can specify the source and target details, specify the CI types and relationships to transfer, and define your preferences for deltas, deletes, reject files, and logging.

trium Integrator consoleThe left panel of the Atrium Integrator console displays a list of jobs available in the Spoon repository.

Atrium Integratorconsole

Database, CSV, XML

Input

RepositoryStores the job

Carte serverRuns the job

Pentaho Spoon(Optional)

Edit a job to add complex steps

CMDB plugin

BMC Atrium CMDBOutput

Manage Data Stores tool

Create a data store connection

Integration Job Builder wizard

Createa job

Job Scheduler

Schedule the job

Job MonitoringMonitor the

job

JobUsers Guide

Atrium Integrator components

SpThe History tab on the right panel displays the job run information for the selected job. You can also display jobs with a specific status or jobs that executed within a range of dates. The Integration Job Details tab displays the date, source and target types, and description of a job.

The Atrium Integrator console provides access to the Manage Data Stores tool and Integration Job Builder wizard. You can start and stop a job, schedule a job, and monitor a job.

For more information about the tasks that you can perform from the Atrium Integrator console, see the following sections:

Working with data store connections on page 53

Creating a job on page 61

Running and monitoring a job on page 105

oon After you build your job, you can edit it in the Spoon application. Spoon has a drag-and-drop graphical user interface that makes it easy for you to edit your transformations and clean up your data before putting it into BMC Atrium CMDB.Chapter 1 Understanding Atrium Integrator 21

22


MeFigure 1-5: Spoon application

Menu bar

The menu bar provides access to common actions such as creating a new transformation or job, editing it, connecting to a repository, and running or debugging the job or transformation.

Navigation panel

The navigation panel on the left contains a View tab and Design tab.

The View tab maintains a history of the different types of steps that were added to the active transformation or job. For a new transformation or job, this tab displays the steps that a transformation must include to run successfully.

The Design tab provides an organized list of transformation steps or job entries used to build transformations and jobs.

Active transformation or jobNavigation panel stepsnu bar CanvasToolbar Transformation stepHopUsers Guide

Performance considerations

C

PYou can perform a search in either tab by typing a phrase in the search field and pressing the Enter key. The steps containing the search phrase are displayed.

Click the icon to expand all steps and the icon to collapse the steps.

Toolbar

The toolbar provides buttons for common actions such as creating a new file, opening a saved file, and saving a file. It also provides buttons for quick access to common actions specific to the active transformation or job, such as Run, Preview, and Debug.

Canvas

The canvas is the main design area for building transformations and jobs.

Active transformation or job

The canvas displays a number of tabbed views that represent the open transformations and jobs. In Figure 1-5 on page 22, the DiskDrive transformation is the active transformation.

arteCarte is a simple web server that you can use to execute transformations and jobs remotely.

erformance considerationsPerformance considerations for Atrium Integrator depend on your network, BMC Remedy Action Request System (BMC Remedy AR System), the BMC Remedy AR System server database, and the external data store load. Predicting the effect of a specific change on Atrium Integrator performance is difficult, but configuration considerations can influence performance.

Although it is easy to add field mappings or extra transformations for each field, remember that each item you add is compared against every record in your database. Seemingly minor additions could have a major impact if your database contains many records. For example, if you have 1200 records in your database and a change adds an additional half-second to the run time for each record, the data transfer might take an additional 10 minutes to run.

Best practices

Following are some best practices that can improve the performance of Atrium Integrator:

Create index entries on:

The BMC_BaseElement class for keys that are used as primary keys

Relationship keys for relationship data exchangesChapter 1 Understanding Atrium Integrator 23

24


P

A External data stores for exchanges with the External Data to CMDB data direction and for relationship data exchanges

Provide minimum and maximum values for the Fast Thread and List Thread options in the BMC Remedy AR System Administration Console. For more information about the Fast Thread and List Thread options and how to specify the number of threads, see the BMC Remedy Action Request System 7.6.04 Configuration Guide.

Launch multiple copies of a step. For optimum performance, you can launch 20 copies of a step.

Distribute a step to multiple processing flows when you want to split the transformation flow to multiple processing paths.

When possible, run job and transformation steps in parallel to improve throughput. If dependencies exist, however, you cannot runs steps in parallel.

Limit the columns that you map. The more columns you map, the slower the transformation runs.

Use JavaScript and lookup steps sparingly as they can significantly increase the processing time.

reparing to transfer dataThis section illustrates the high-level steps that you perform to prepare for transferring data.

Step 1 Create a new source dataset to which you can migrate your source data to. Datasets help in categorizing data by providers. You can then reconcile your dataset with BMC.ASSET.

Step 2 Create index entries on the BMC_BaseElement class in the Class Manager application to improve the performance of Atrium Integrator.

For instructions, see the BMC Atrium CMDB 7.6.04 Administrator's Guide.

ccessing the Atrium Integrator consoleThe Atrium Integrator console is the main user interface for Atrium Integrator. You can access the other Atrium Integrator components from the console.

To access the Atrium Integrator console

1 In a browser, enter the URL designated by an administrator. For example:

http://midTier:port/arsys

midTier is the name of the web server where the BMC Remedy Mid Tier is installed.Users Guide

Accessing the Atrium Integrator console port is the port number of the web server where the BMC Remedy Mid Tier is installed, which is required only if the web server is not using the default port (80 if using Microsoft IIS or 8080 if using Apache Tomcat).

2 In the login page, specify the following details:

In the User Name field, type your user name.

In the Password field, type your password.

In the Authentication field, type the authentication string (if one was provided by an administrator)

3 Click Login.

4 In the AR System Home page, choose BMC Atrium Core > Atrium Core Console.

If you access multiple servers from the AR System Home page, you would choose BMC Atrium Core > serverName > Atrium Core Console.

The Application Launcher bar appears on the left side of the console.

5 From the Application Launcher bar, choose Integration Engines > Integrator.

Figure 1-6: Atrium Integrator link from the Application Launcher

The Atrium Integrator console appears.Chapter 1 Understanding Atrium Integrator 25

26

Atrium Integrator 7.6.04Users Guide

Chapter

2 Scenario for transferring data to BMC Atrium CMDB This tutorial describes a sample BMC Atrium CMDB scenario in which the Calbro administrator, Allen Allbrook, prepares his CMDB for Atrium Integrator, creates and runs an Atrium Integrator job, verifies its success, and schedules it to run repeatedly.

Through this example, you can see how the components of Atrium Integrator work together to help you migrate data from an external database to BMC Atrium CMDB.


Source data organization at Calbro Services (page 28) Preparing to transfer Calbro Services data (page 30) Transferring Calbro data to BMC Atrium CMDB (page 31) Opening the job and transformations in Spoon (page 40) Editing the job in Spoon (page 45) Running the job (page 48) Verifying that the transferred data is in BMC Atrium CMDB (page 49) Monitoring the job (page 50)Chapter 2 Scenario for transferring data to BMC Atrium CMDB 27

28


S

M

Mource data organization at Calbro ServicesCalbro Services has an external database that stores information about all the hardware components in its environment. The external database has separate tables for computers, processors, disk drives, memory, and so on.

The organization of the database tables for computers and disk drives is shown in Figure 2-1.

Figure 2-1: Organization of the computer and disk drive database tables

apping source data to BMC Atrium CMDBThe records in the Computer table correspond to instances of the BMC_ComputerSystem class in BMC Atrium CMDB. The records in the Disk Drive table correspond to instances of the BMC_DiskDrive class in BMC Atrium CMDB.

apping relationship classesMuch of the value of BMC Atrium CMDB comes from the ability to store information about the relationships between configuration items (CIs), not just information about the CIs themselves.

Each record in the Disk Drive table contains the name of its corresponding computer in the AssociatedComputer column. This relationship associates a specific instance of a disk drive in the external database with a specific instance of a computer. For example, in Figure 2-1 on page 28, disk 1520 in the Disk Drive table is associated with computer vm2-w4-dev01 in the Computer table.

Because each disk drive is associated with a computer, you can select a relationship that associates a particular instance of BMC_DiskDrive with a particular instance of BMC_ComputerSystem. In this case, the AssociatedComputer attribute in the BMC_DiskDrive class and the HostName attribute in the BMC_ComputerSystem class contain the data necessary to create the relationship.

Name SerialNumber AssociatedComputerDisk 1520 23541 vm2-w4-dev01Disk 1523 24761 vm2-w3-dev02Disk 1560 24645 vm2-w4-dev03Disk 1534 24671 vm2-w5-dev06Disk 1530 26541 vm2-w7-dev10

Computer table

HostName SerialNumber Manufacturervm2-w4-dev01 MX2435 Dellvm2-w3-dev02 VL3421 HPvm2-w4-dev03 DW2313 Dellvm2-w5-dev06 MX2400 Dell vm2-w7-dev10 MX550 HP

Disk Drive tableUsers Guide

Source data organization at Calbro ServicesEach relationship class in BMC Atrium CMDB defines one CI class as the source member of the relationship and another CI class as the destination member of the relationship. In this case, BMC_ComputerSystem is the source (primary) member and BMC_DiskDrive is the destination (secondary) member of the BMC_HostedSystemComponents relationship class. For more information about relationship classes, see the BMC Atrium Core 7.6.04 Concepts and Planning Guide.

NOTE The transformations that bring data from the external data store into the CI classes (in this case, BMC_DiskDrive and BMC_ComputerSystem) must finish before the transformation for the relationship class can run, because that transformation needs the instance IDs of the related CIs for their relationship instance. The wizard schedules the transformations in this order automatically.

The relationship between computer systems and disk drives at Calbro Services is stored within the source tables, as shown in Figure 2-1 on page 28. Figure 2-2 on page 29 shows how data from the external database is transferred into BMC Atrium CMDB to create CIs, and then how a relationship class instance is created based on attributes in the CI classes.

Figure 2-2: Creating relationships based on attributes in both CI classes

For each BMC_DiskDrive instance, a match between its AssociatedComputer value and the Name value in a BMC_ComputerSystem instance causes the creation of a BMC_HostedSystemComponents relationship between the two CIs.

Disk Drive table

Name SerialNumber AssociatedComputerDisk 1520 23541 vm2-w4-dev01Disk 1523 24761 vm2-w3-dev02Disk 1560 24645 vm2-w4-dev03Disk 1534 24671 vm2-w5-dev06Disk 1530 26541 vm2-w7-dev10

Computer table

HostName SerialNumber Manufacturer vm2-w4-dev01 MX2435 Dellvm2-w3-dev02 VL3421 HPvm2-w4-dev03 DW2313 Dellvm2-w5-dev06 MX2400 Dell vm2-w7-dev10 MX550 HP

BMC_HostedSystemComponentsSource.InstanceId Destination.InstanceId

1F8FEF67A 1F6ABC21F1F8FBE71C 1B3CFA89D1E6A2C5AF 1E8AFB71E1C4E8A2FF 1A2CAC48F1A2B2C5CD 1F5AFE19A

Disk 1520 23541 vm2-w4-dev01 1F6ABC21F Disk 1523 24761 vm2-w3-dev02 1B3CFA89D Disk 1560 24645 vm2-w4-dev03 1E8AFB71E Disk 1534 24671 vm2-w5-dev06 1A2CAC48F Disk 1530 26541 vm2-w7-dev10 1F5AFE19A

vm2-w4-dev01 Dell MX2435 F8FEF67Avm2-w3-dev02 HP VL3421 1F8FBE71Cvm2-w4-dev03 Dell DW2313 1E6A2L5AFvm2-w5-dev06 Dell MX2400 1C4E8A2FFvm2-w7-dev10 HP MX550 1A2B2C5CD

Externaldatastore

BMC AtriumCMDB

RelationshipClass

Transformation

Transformation

Transformation

BMC_DiskDrive

Name IntegrateId* ParentIntegrateId** InstanceId

BMC_ComputerSystem

Name Manufacturer IntegrateId* InstanceId

*IntegrateId = CalbroIntegrationId**ParentIntegrateId = CalbroParentIntegrationIdChapter 2 Scenario for transferring data to BMC Atrium CMDB 29

30


P

CThe instance IDs of these member CIs are stored in the relationship instance as Source.InstanceId for the BMC_ComputerSystem instance and Destination.InstanceId for the BMC_DiskDrive instance.

reparing to transfer Calbro Services dataAllen Allbrook prepares to transfer the Calbro Services computer system and disk drive data to BMC Atrium CMDB by:

Creating a dataset for the transferred data

Creating connections to the source and destination databases

Adding an attribute to the BMC_DiskDrive CI class

reating a dataset for the Calbro dataAs BMC recommends, Allen Allbrook creates a dataset, CALBRO.IMPORT, in BMC Atrium CMDB. A separate dataset helps partition data according to data providers.

To create a dataset

1 Use the direct access URL to open the BMC Remedy AR System Server midtier and log in with your user name and password.

2 On the AR System Home page, choose BMC Atrium Core > Atrium Core Console.

3 In the BMC Atrium Core Console, choose Application Launcher > Reconciliation.

4 In the Reconciliation console, click Create Dataset .

5 In the Dataset Editor, specify the Name (Calbro.Import) and ID (CALBRO.IMPORT) for the dataset.

6 In the Accessibility field, select Writable.

7 Click Save.

The CALBRO.IMPORT dataset is created in BMC Atrium CMDB.Users Guide

Transferring Calbro data to BMC Atrium CMDB

C

A

Treating a database connectionNow Allen creates a data store connection to communicate with the external database, which is the source of the data. Allen then creates a connection to communicate with the BMC Atrium CMDB server, which is the destination for the data.

To create a source database connection

1 In the BMC Atrium Core Console, choose Application Launcher > Integration Engines > Integrator.

2 In the Atrium Integrator console, click Manage Data Store Connections .

3 Click New Data Store .

4 In the New Data Store section on the right side of the Manage Data Stores window, select the Data Store Type as Database.

5 Type Calbro Source Tables in the Name field.

6 Specify the remaining information for your source database.

7 To verify your source database connection parameters, click Test Connection.

8 Click Save.

To create a target database connection


2 In the New Data Store section on the right side of the Manage Data Stores window, select CMDB as the Data Store Type.

3 In the Data Store Name field, type Calbro Connection to CMDB.

4 Specify the remaining information for the target database.

5 To ensure that you can connect to BMC Atrium CMDB, click Test Connection.

6 Click Save.

dding an attribute to the BMC_DiskDrive classAllen creates the ExternalParentIntegrationId attribute in the BMC_DiskDrive CI class using the Class Manager. For more information about creating attributes, see the BMC Atrium CMDB 7.6.03 Administrator's Guide.

ransferring Calbro data to BMC Atrium CMDBAfter preparing the data, Allen Allbrook transfers the data by:

Creating a data transfer job through the Integration Job Builder wizard

Editing the job to map an additional column to a target attribute

Running the job Chapter 2 Scenario for transferring data to BMC Atrium CMDB 31

32


CAfter the transfer is completed, Allen Allbrook:

Verifies that the data is in BMC Atrium CMDB

Monitors the data transfer job in the BMC Atrium Integrator console

reating a data transfer jobAllen uses the Integration Job Builder wizard to create a data transfer job. The wizard helps Allen Allbrook create a basic job, which he can then edit in Spoon to tailor it to meet Calbros data transfer requirements.

To create a job

1 In the Atrium Integrator console, click Create Job .

2 Click anywhere in the Overview page.

The General page appears.

Figure 2-3: General page of the Integration Job Builder wizard

3 In the Job Name field, enter Transfer Calbro data.

4 In the Description field, enter Transfer computer system and disk drive information to CMDB.

5 In the Type field of the Specify Data Store Details for Source area, select Database and in the Name field, select Calbro Source Tables.

6 In the Name field of the Specify Data Store Details for Target area, select Calbro Connection to CMDB, and in the Dataset ID, select CALBRO.IMPORT.Users Guide

Transferring Calbro data to BMC Atrium CMDBAs BMC recommends, Allen Allbrook does not use Atrium Integrator to transfer data directly into the BMC Asset dataset. Instead, he transfers the data into the CALBRO.IMPORT dataset and then reconciles it into BMC Asset.

7 Click Next.

The CI Type Selection page appears.

Figure 2-4: CI Type Selection page of the Integration Job Builder wizard

8 In the Select CI Type from area, select CI List.

9 In the Available List of CI Types, type computer.

The search criteria applies as you enter text, and the matching CIs update automatically in the CI Types table.

10 Select computer system and click Add.

Computer system is moved to the Selected CI Types area.

11 Repeat step 9 and step 10 to add disk drive.

12 Click Next.

The CI TypeRelationships page appears.Chapter 2 Scenario for transferring data to BMC Atrium CMDB 33

34

Atrium Integrator 7.6.04Figure 2-5: CI TypeRelationships page of the Integration Job Builder wizard

13 From the Available CI Types of Relationships area, select SYSTEMDEVICE and click Add.

This relationship identifies computer system as the parent CI and disk drive as the child CI.

The step toolbar is updated to reflect the selections that Allen Allbrook made, as shown in Figure 2-5 on page 34.

14 Click Next.

The Computer system Mapping page appears, which displays the target CI class as BMC_ComputerSytem. Here, Allen maps attributes from the BMC_ComputerSystem class to columns from the source table to specify the fields and attributes to be transferred.Users Guide

Transferring Calbro data to BMC Atrium CMDBFigure 2-6: Computer system Mapping page of the Integration Job Builder wizard

15 On the Select Source field, leave the default selection of Table.

16 In the Schema field, select dbo, and in Table, select CalbroComputerSystem.

17 Select a target attribute and corresponding source column as displayed in the following table, and click Map. Chapter 2 Scenario for transferring data to BMC Atrium CMDB 35

36

Atrium Integrator 7.6.04Repeat this step for each row in the table. The names in the Source column are the Computer table database columns in Figure 2-1 on page 28.

Each row is added to the Mapped Columns area.

18 For the HostName row, select the Source Key check box (which indicates that the HostName column uniquely identifies each row of data in the source table).

19 Click the Transformation Options tab.

20 For Delta, leave the default selection of Yes and select the LastModified column.

Note that the default value of Delta is Yes only when your source table has a date/time column.

21 For Response, leave the default selection of No.

22 Click Next.

The Disk drive Mapping page appears, which displays the target CI class as BMC_DiskDrive.

Figure 2-7: Disk drive Mapping page of the Integration Job Builder wizard

23 On the Select Source field, leave the default selection of Table.

24 In the Schema field, select dbo, and in Table, select CalbroDiskDrive.

Target attribute Source Column

Name HostName

SerialNumber SerialNumber

ManufacturerName ManufacturerUsers Guide

Transferring Calbro data to BMC Atrium CMDB25 Select a target attribute and corresponding source column as displayed in the following table, and click Map.

Repeat this step for each row in the table. The names in the Source column are the Computer table database columns in Figure 2-1 on page 28.

26 For the SerialNumber row, select the Source Key check box (which indicates that the SerialNumber column uniquely identifies each row of data in the source table).

27 Click the Transformation Options tab.

28 For Delta, leave the default selection of Yes. Select the source column to be used for delta.

29 For Response, leave the default selection of No.

30 Click Next.

The Relationships Mappings page appears, and lists the Parent CI as Computer system and child CI as Disk drive. On this page, Allen specifies how the two source tables are related to each other.

Figure 2-8: Relationship Mapping page of the Integration Job Builder wizard

Target attribute Source Column

Name Name

SerialNumber SerialNumber

ExternalParentIntegrationId Associated ComputerChapter 2 Scenario for transferring data to BMC Atrium CMDB 37

38

Atrium Integrator 7.6.0431 Leave the default selection of Key Columns of Computer system in table CalbroComputerSystem are mapped to columns of Disk drive in table CalbroDiskDrive. This indicates that relationship information is stored in the computer system and disk drive source tables. For more information, see Mapping relationship classes on page 28.

The Computer system Key Columns table displays the Source key that Allen had selected in step 26 on page 37 (HostName).

32 From the Disk drive Columns area, select AssociatedComputer.

This indicates that for each BMC_DiskDrive instance, a match exists between its AssociatedComputer value and the HostName value in a BMC_ComputerSystem.

33 In the Transformation Options tab, leave the default selection of Yes for Delta and select the LastModified column.

34 Click Next.

The Schedule page appears, where Allen specifies the time at which the job is to run, and the time interval between jobs.

Figure 2-9: Schedule page of the Integration Job Builder wizard

35 In the Start Time field, enter 5:00:00 PM.

36 In the Interval area, type 1 in the Hours field.

Calbro Services wants to update the database with ATM transactions. Allen, therefore, schedules a data exchange at an interval of an hour to populate the database with the information of the ATM transactions.Users Guide

Transferring Calbro data to BMC Atrium CMDB37 Click Next.

The Summary page appears.

Figure 2-10: Summary page

38 In the Summary page, click Finish.

The Generated Transformations dialog box displays the list of transformations generated to transfer the computer system and disk drive records to BMC Atrium CMDB.

Figure 2-11: List of transformations generated by the Integration Job Builder wizardChapter 2 Scenario for transferring data to BMC Atrium CMDB 39

40


OThe following naming convention is used:

Name of job_CI being transferred (for example, Transfer Calbro data_Computer system)

39 Click OK.

The job is listed in the job catalog on the left side of the Atrium Integrator console, and runs as scheduled. If you want to do a test run, select the job from the job catalog and click Start Job .

pening the job and transformations in SpoonAfter creating a simple data transfer job through the Integration Job Builder wizard, Allen Allbrook opens the job in Spoon to edit it.

To open the job in Spoon

1 On the computer where you have the Spoon client installed, click Start > All Programs > BMC Software > Atrium Integrator > BMC Atrium Integrator Spoon.

The Spoon Repository login page appears.

Figure 2-12: Spoon Repository Login

2 Login as follows:

a In the Repository field, leave the default entry of NGIEREPD.

b In the Login field, enter admin.

c In the Password field, enter admin (the default password).

d Click OK.Users Guide

Opening the job and transformations in Spoon3 In the Spoon window, choose Repository > Explore Repository.

4 In the Repository explorer dialog box, expand the Jobs directory, and then expand the directory.

All the jobs in the NGIEREPD repository are displayed.

5 Now expand the Transfer Calbro data directory.

Figure 2-13: Jobs and transformations for Calbro Services

6 Double-click the Transfer Calbro data job.

The job opens.

Figure 2-14: Transfer Calbro data jobChapter 2 Scenario for transferring data to BMC Atrium CMDB 41

42

Atrium Integrator 7.6.047 Double-click the Set variables step.

The Set Variables dialog box shows the delta and response settings that Allen Allbrook specified when creating his job through the Integration Job Builder.

Figure 2-15: Set variables step in the Transfer Calbro data job

8 Click OK and then double-click the Sub_Transfer Calbro data step.

The Executing a job dialog box shows the delta and response arguments. The argument number is specified within the respective transformations.

Figure 2-16: Executing a job dialog box

9 Click OK.Users Guide

Opening the job and transformations in Spoon10 Right-click the Sub_Transfer Calbro data step and select Open job.

The transformations created for the Transfer Calbro data job are displayed.

11 Right-click Transfer Calbro data_Computer system and select Open transformation.

The computer system transformation is displayed. Allen Allbrook makes edits to this transformation in Editing the job in Spoon on page 45.

Figure 2-17: Computer system transformation in SpoonChapter 2 Scenario for transferring data to BMC Atrium CMDB 43

44

Atrium Integrator 7.6.04Table 2-1 describes each step in the Transfer Calbro data_Computer system_Delta transformation.

Table 2-1: Steps in the Transfer Calbro data_Computer system_Delta job transformation (Sheet 1 of 2)

Step name What the step does

Gets the latest time stamp from the NGIEDELTA table. For a delta job, records are transferred to BMC Atrium CMDB only if the Table Source Delta has a later time stamp than the Table Source Time Stamp.

Specifies the argument number for the delta setting. This steps gets the appropriate argument number from the Set variables step as shown in Figure 2-15 on page 42.

Specifies whether delta is set to yes, in which case the LastModified time stamp determines whether to transfer the records on a subsequent run. If delta is set to no, all records are transferred.

Deletes fields that are not required. This step is only for internal processing.

Specifies the source table.

Provides a placeholder step to add a new field by performing simple calculations.

Provides a placeholder step to map a field to a constant value.

Specifies the argument number for the response setting. This steps gets the appropriate argument number from the Set variables step as shown in Figure 2-15 on page 42.

Specifies the BMC Atrium CMDB class, namespace, and Dataset ID to which the data is to be transferred. This step also specifies the source key and input filetarget attribute mappings.

After the records are transferred to BMC Atrium CMDB, the NGIEDELTA table is updated to reflect the time that the latest record was created in the source table.Users Guide

Editing the job in Spoon

Editing the job in SpoonAllen Allbrook wants to make the following edits to the job that he created:

The abbreviation that Calbro Services uses for the name of the marketing department has changed from Mktg to MKTG. Allen Allbrook uses a calculator step to convert the values in the Department source column to uppercase before transferring them to BMC Atrium CMDB.

Calbro Services wants to transfer data from the dbo.ComputerSystem.Department field only if the value is not NULL. Otherwise, they want to keep the value in the target database. Allen uses the Filter rows step to set this up.

Map an additional source field to a target attribute.

Specifies the name of the transformation.

After the data is transferred to BMC Atrium CMDB, updates the NGIEDELTA table with the time stamp of the latest-created record in the source table. On the next delta run, only records that have a time stamp later than this will be transferred.

Specifies the name and path of the file to which errors are written to.

Defines the job flow. If you set Response as Yes, the job updates the specified source field.

For those records that were transferred successfully to BMC Atrium CMDB, the response values in the source table is set to 0.

For those records that were not transferred to BMC Atrium CMDB, the response values in the source table is set to 1.

For those records that were not transferred to BMC Atrium CMDB, the response values in the source table is set to 1.

Table 2-1: Steps in the Transfer Calbro data_Computer system_Delta job transformation (Sheet 2 of 2)

Step name What the step doesChapter 2 Scenario for transferring data to BMC Atrium CMDB 45

46

Atrium Integrator 7.6.04 To change the Department column values to uppercase

1 In the Transfer Calbro data_Computer system_Delta transformation, double-click the Calculator step.

Figure 2-18: Calculator step

2 In the New field column, enter Used By.

3 In the Calculation row, select UpperCase of a String A.

4 In Field A, select the Department column.

The upper case values from the Department column will be written to the Used By column.

5 Click OK.

To add a step to transfer data from the Department field only if the value is not NULL

1 In the navigation panel, click Design.

2 From the Flow menu in the navigation panel, click the Filter rows step and drag it between the IsResponse and CMDBOutput steps. Click Yes to split the hop.

Figure 2-19: Inserting the Filter rows step

3 From the Transform menu in the navigation panel, click the Dummy plugin step and place it over the Filter rows 2 step.

4 Click the Filter rows 2 step, press the CTRL key, and then select the Dummy plugin step.

5 Right-click the Dummy plugin step and select New hop.

6 In the Hop dialog box, ensure that the value of the From step is Filter 2 row, the value of the To step is Dummy plugin, and the Enable hop check box is selected.

This enables you to set a condition and data that does not comply with your condition is transferred over to the Dummy plugin step.

7 Click OK.Users Guide

Editing the job in SpoonIn the dialog box that appears, select Distribute.

A hop connects the Filter rows 2 and Dummy plugin steps.

8 Double-click the Filter rows 2 step.

9 In the Filter rows dialog box, enter the appropriate values.

a For Step name, enter Filter rows.

b For Send true data to step, enter CMDBOutput.

c For Send false data to step, enter Dummy plugin.

d For the condition, specify Used By as IS NOT NULL.

Figure 2-20: Filter rows dialog box

10 Click OK.

To map additional fields to target attributes

1 Double-click the CMDBOutput step.

Figure 2-21: CMDBOutput dialog boxChapter 2 Scenario for transferring data to BMC Atrium CMDB 47

48


R2 In the Table field column in the Update fields table of the CMDBOutput dialog box, select Assigned to.

3 In the Stream field column, select Used By, and in the Update column, select Y.

Allen Allbrook selects these values to map the Used By column to the Assigned to attribute.

4 Click OK.

Allen has completed his edits.

5 Choose File > Save.

unning the jobAfter editing the job in Spoon, Allen Allbrook runs it to verify that it runs correctly.

1 In the Spoon window, click the Sub_Transfer Calbro data tab.

2 Choose File > Save.

3 Click Run .

4 In the Execute a job window, leave the default selection of Local execution.

NOTE Allen Allbrook runs this job locally because Calbro has BMC Atrium Core installed on the same computer as the Spoon client. If the Spoon client is installed on a different computer, Allen would execute the job remotely.

5 Click Launch.

The job runs and displays the logging details (in the Logging tab) in the bottom half of the window.Users Guide

Verifying that the transferred data is in BMC Atrium CMDB

VAFigure 2-22: Job Run window

You can also see the job progress on the Atrium Integrator console.

erifying that the transferred data is in BMC trium CMDB

After the Transfer Calbro data job completes running, Allen Allbrook verifies that the computer system, disk drive, and relationship records have been transferred to BMC Atrium CMDB.

To verify that the records have been transferred to

1 Return to the browser window and open the BMC Atrium Core Console.

2 Click Application Launcher > CMDB Applications > Explorer.

3 In BMC Atrium Explorer, click the Find tab.

4 In the Query list, click Options.

The Edit Query Options dialog box appears.

5 In the Dataset list, select the Calbro.Import dataset and click OK.Chapter 2 Scenario for transferring data to BMC Atrium CMDB 49

50


M6 In the !Quick search of all CIs area, click Search.

The disk drives and computers from the external data store are displayed in the search results.

7 To view the relationship between the disk drives and computers, perform the following steps:

a Click the View tab.

b Click the New View button and select CALBRO.IMPORT.

A new view of the CALBRO.IMPORT dataset appears.

c Drag a CI (for example, Disk 1534) to the relationship panel.

d Right-click the CI and select Expand Parents.

The relationship between Computer vm2-w5-dev06 (parent) and Disk 1534 (child) is displayed.

onitoring the jobAllen Allbrook can monitor the Calbro jobs (whether he ran them from the Atrium Integrator console, or Spoon) in the Atrium Integrator console.

To monitor the data transfer job

1 From the job catalog of the Atrium Integrator console, select the Transfer Calbro data job.

The History tab displays the start and end times for each run of this job, as shown in Figure 2-23 on page 50.

Figure 2-23: History tab of the Atrium Integrator consoleUsers Guide

Monitoring the job2 Click the Integration Job Details tab to view additional details of the selected job.

Figure 2-24: Integration Job Details tab of the Atrium Integrator consoleChapter 2 Scenario for transferring data to BMC Atrium CMDB 51

52


Chapter

3 Working with data store connectionsThis section describes how to connect to your data stores, which is the first step in the data transfer process.


Before you begin (page 54) Supported data types (page 55) Creating a new data store connection (page 55) Editing a data store connection (page 58) Deleting a data store connection (page 59)

1 Congure source 2 Create and 3 Edit transformation 4 Run job 5 Monitor job & target connection schedule job or job Chapter 3 Working with data store connections 53

54


Before you beginUse Table 3-1 to gather and record the required configuration information, which you will need when you create a data store connection.

Table 3-1: Required configuration information

Type of information Value

BMC Atrium CMDB

BMC Remedy AR System server name

Host name

Port

RPC Program Number

User ID

Password

CSV or Excel files

Path to directory where the file is saved

Database

Host name

Database type

Database name

Port

Instance name (only for Microsoft SQL Server)

User ID

PasswordUsers Guide

Supported data types

S

Cupported data typesTable 3-2 shows the supported external data store types and indicates whether you must define specific connection parameters when using that type.

reating a new data store connection1 In the BMC Atrium Console, choose Application Launcher > Integration Engines

> Integrator.

The Atrium Integrator console appears.

2 Click Manage Data Store Connections .

The Manage Data Stores window appears, with a list of defined data sources.

Figure 3-1: Manage Data Stores window


The New Data Store section appears on the right side of the Manage Data Stores window.

Table 3-2: Supported data store types

Type Requires specific connection parameters

BMC Atrium CMDB Yes

Comma separated value (CSV) flat file

No

XML No

Databases IBM Informix

Microsoft SQL Server My SQL Oracle

Sybase

YesChapter 3 Working with data store connections 55

56

Atrium Integrator 7.6.04Figure 3-2: New Data Store section of the Manage Data Stores window

4 Select the Data Store Type.

The fields below the Data Store Type change depending on the data store you selected.

5 To create a connection to BMC Atrium CMDB, complete the following steps. To create a connection to a CSV or XML file, skip to step 6 on page 56. To create a connection to a database, skip to step 7 on page 57.

a Type a name for the connection.

b In the AR Server Name field, type the name of your BMC Remedy AR System server.

c (optional) Type the port number.

d (optional) In the RPC Program Number field, type the RPC port if you use one.

NOTE You cannot specify a private RPC port for data transfers into BMC Atrium CMDB. You must use the ports defined by BMC Atrium CMDB. For more information about the RPC ports defined by BMC Atrium CMDB, see RPC Ports in BMC Atrium CMDB (page 58).

e Type the user ID and password to log in to BMC Atrium CMDB.

6 To create a connection to a CSV or XML file, complete the following steps:Users Guide

Creating a new data store connectionFigure 3-3: Creating a connection to a CSV or XML file


b Specify the path to the folder that contains the source file. Note that the source files must be on the same computer on which you have installed the BMC Remedy Mid Tier.

7 To create a connection to a database, complete the following steps:

Figure 3-4: Creating a connection to a database


b Enter the host name.

c Specify the database type.

d Enter the name of the database you want to connect to.

The default port for the specified database is displayed.Chapter 3 Working with data store connections 57

58


R

Ee (optional) For a SQL Server database, type the instance name.

f Type the user ID and password to log in to the database.

8 Click Test Connection to verify the connection parameters.

9 Click Save.

The data store connection is created and displayed in the Data Stores section on the left side of the Manage Data Stores window. Each connection has an icon attached to it depending on the data store type, as described in Table 3-3 on page 58.

Table 3-3: Icons associated with data stores

Clicking on a data store provides the connection parameter details for that source.

PC Ports in BMC Atrium CMDBBMC Atrium CMDB has assigned the following RPC ports for Atrium Integrator:

diting a data store connectionAll data store connections are displayed in the Data Stores section of the Manage Data Stores window.

1 In the Manage Data Stores window, select the data store for which you want to edit the connection information.

Connection details for the selected data store are displayed on the right side of the window.

Icon Associated data store type

CMDB

CSV file

XML file

Database

#define CMDB_RPC_PROGRAM_NUM_STANDARD 390696#define CMDB_RPC_PROGRAM_NUM_ADMIN 390697#define CMDB_RPC_PROGRAM_NUM_PRIVATE_MIN 390698#define CMDB_RPC_PROGRAM_NUM_PRIVATE_MAX 390699Users Guide

Deleting a data store connection

DFigure 3-5: Connection details in the Manage Data Stores window

2 Make the necessary changes. Note that you cannot edit the data store type.

3 Click Test Connection to verify the connection parameters.

4 Click Save.

The data store connection is saved. Any new jobs that you create will be based on the edited connection, but jobs defined using the previous connection are not updated.

eleting a data store connectionAll data store connections are displayed in the Data Stores section of the Manage Data Stores window.

1 In the Manage Data Stores window, select the data store for which you want to delete the connection.

2 Click Delete Data Store .

The data store connection is deleted. Jobs that were based on the deleted connection are not affected.Chapter 3 Working with data store connections 59

60


Chapter

4 Creating a jobYou can create a job in the Atrium Integrator console by using the Integration Job Builder wizard, or in the Spoon application.

Atrium Integrator provides an easy-to-use wizard for creating a simple data transfer job for importing data into BMC Atrium CMDB. For complex data manipulations, you can first create a simple data transfer job using the wizard, and then refine the generated job and transformations in Spoon.

To import and export data from inputs like LDAP, BMC Remedy AR System forms, or ITSM forms, you can create a job in Spoon using the samples provided by BMC.


Creating a simple job through the Integration Job Builder wizard (page 62) Creating a complex job in Spoon (page 81)

1 Congure source 2 Create and 3 Edit transformation 4 Run job 5 Monitor job & target connection schedule job or job Chapter 4 Creating a job 61

62


CJ

Hwreating a simple job through the Integration ob Builder wizard

You can use the Integration Job Builder wizard in the Atrium Integrator console to create a simple job for transferring data from XML files, CSV files, or databases (IBM DB2, IBM Informix, Microsoft SQL Server, My SQL, Oracle, and Sybase) to BMC Atrium CMDB.

Using the wizard has the following benefits:

You need to specify only the business names for the information types to be transferred to BMC Atrium CMDB. The wizard automatically selects the Common Data Model (CDM) classes and relationships based on the information entered.

The wizard has built-in templates that specify typical integrations based on BMC experience in populating CMDB.

The wizard adheres to best practices for populating data, such as auto populating categorizations and name fields for relationships.

When multiple CI and relationship classes are selected, data transfers are sequentially ordered.

Processing of delta records is simplified.

igh-level steps for creating a job through the Integration Job Builder izard

This section describes the high-level steps for creating a job to transfer data from an external data store to BMC Atrium CMDB using the Integration Job Builder wizard.

Best practice

BMC recommends that you use the Integration Job Builder wizard to automatically generate a job and transformations from best practice templates. This will improve your productivity by providing a starting point for developing and simplifying the transformation of data into BMC Atrium CMDB.

4 Map target attributes 5 Dene relationship mapping 6 Schedule job 7 View job summary to source columns

1 Specify source and target details 2 Select CI types to transfer 3 Select relationships for the CI types to transfer Users Guide

Creating a simple job through the Integration Job Builder wizardStep 1 Specify source and target details.

You must specify the job name and description, external data store, and the CMDB class and DatasetID to which you want to transfer data. For more information, see Specifying source and target details on page 64.

Step 2 Select CI types to transfer.

Select the CI types that you want to transfer from the external data store. You can either select CIs from a list, or select CIs based on a template. For more information, see Selecting CI types to transfer on page 65.

Step 3 Select the relationships to transfer for the CI types.

Based on the CI types that you want to transfer, the Integration Job Builder wizard displays the relationships between the CI types. Select the relationships that you want to transfer. For more information, see Selecting relationships to transfer for the CI types on page 68.

Step 4 Map target attributes to source columns.

Map the target attributes of the CI to the columns in the external data store. For more information, see Mapping target attributes to source columns on page 69.

Step 5 Define the relationship mapping for the CI types to be transferred.

Specify whether the source has a:

Direct association between parent and child classes

This option creates a mapping for a relationship class based on attributes in the CI classes (parent-child) that are members of this relationship.

Separate table to define relationships

This option creates a mapping for a relationship class based on relationship data stored in the external data store.

For more information, see Defining relationship mapping for the CI types to transfer on page 74.

6 Schedule the job to run at a specific time or timed interval. For more information, see Creating a job schedule on page 79.

Step 7 View the job summary.

Verify the job name, and the CI types and relationships that you are transferring. For more information, see Viewing the job summary on page 80.Chapter 4 Creating a job 63

64


Creating a job through the Integration Job Builder wizardAtrium Integrator provides a wizard to simplify the process of creating a job to transfer data into BMC Atrium CMDB. This topic presents the steps for each wizard page in a separate procedure. Follow the procedures sequentially, as indicated in the graphic.

Specifying source and target details

To specify source and target details

1 In the Atrium Integrator console, click Create Job .

2 In the Overview page, click anywhere on the screen.

The General page appears.

Figure 4-1: General page of the Integration Job Builder wizard

3 In the General page, enter the name and description of the job.


1 Specify source and target details 2 Select CI types to transfer 3 Select relationships for the CI types to transfer Users Guide

Creating a simple job through the Integration Job Builder wizard4 In the Specify Data Store Details for Source area, specify the type and name of the external data store.

If you do not have a data store connection to your source data, click Data Store to create a new connection. For more information, see Creating a new data store connection on page 55.

5 In the Specify Data Store Details for Target area, select the name of the data store and DatasetID of the BMC Atrium CMDB class to which you are transferring data.

If you do not have a data store connection to BMC Atrium CMDB, click Data Store to create a new connection. For more information, see Creating a new data store connection on page 55.

NOTE Do not use Atrium Integrator to transfer data directly into the BMC Asset dataset. Instead, transfer the data into another dataset and then reconcile it into BMC Asset.

6 Click Next. The Next button is enabled only after the Job Name, Source and Target Name, and DatasetID fields have valid entries.

The CI Type Selection page appears.

Selecting CI types to transfer

You can select CI types grouped together in a template, or select the CI types for which you want to transfer data from a CI list. To select CI types from a template, see To select CI types to transfer from a templates list on page 65. To select independent CI types, see To select CI types to transfer from a CI list on page 67.

To select CI types to transfer from a templates list

The Integration Job Builder wizard offers a desktop, server, and virtual machine template. Each available template groups together the appropriate CIs and relationships. For example, the virtual machine template groups all the CIs that make up that virtual machine. If you select this template, the wizard automatically moves all related CIs to the Selected CI Types area.


1 Specify source and target details 2 Select CI types to transfer 3 Select relationships for

Date post:	14-Oct-2015
Category:	Documents
Upload:	guayadeque1
View:	190 times
Download:	18 times

Atrium Integrator 7.6.04 User´s Guide

Documents