alt2cmdb integration guide v1.5 - bmc software · 1. download and store the tar file, asams.tar, to...

ALT2CMDB

Integration Guide

Version 1.5

ALT2CMDB Integration Guide 2

Contents

1. Introduction ................................................................................................3 1.1 Preface ............................................................................................................................................3 1.2 Scope ...............................................................................................................................................3 1.3 Key Features & Benefits ...............................................................................................................3 1.4 Required Products .........................................................................................................................3 1.5 Supported Platforms .....................................................................................................................3

2. Overview .....................................................................................................4 2.1 Importing Data from Altiris Service & Asset Management Suite .............................................4 2.2 Reconciling the Imported Data.....................................................................................................4

3. Installation..................................................................................................5 3.1 Prerequisites...................................................................................................................................5

3.1.1 Installation on Microsoft Windows..........................................................................................5 3.1.2 Installation on Sun Solaris .......................................................................................................6

3.2 Configuration.................................................................................................................................7 3.2.1 Data Exchange Vendor Configuration .....................................................................................7 3.2.2 Data Exchange Scheduling ......................................................................................................7 3.2.3 Activating Data Exchange .......................................................................................................9 3.2.4 Activating Reconciliation Job................................................................................................10

3.3 Uninstalling ALT2CMDB ...........................................................................................................12 3.3.1 Removing EIE Data Exchange Definitions............................................................................12 3.3.2 Removing Reconciliation Rules.............................................................................................12 3.3.3 Removing CMDB CDM Extensions......................................................................................13 3.3.4 Removing Integration Application Property ..........................................................................13

Appendix A: Atrium CMDB Data Mappings ....................................................14

Appendix B: Relationship Data Mappings......................................................18

Appendix C: Data Module Extensions ............................................................20

Appendix D: Identification Rules for Reconciliation......................................21


1. Introduction

1.1 Preface

ALT2CMDB is a separately distributed add-on for BMC® Atrium CMDB (Atrium CMDB) that

provides integration between Altiris® Service & Asset Management Suite™ and Atrium CMDB.

This document describes how to install and configure ALT2CMDB.

1.2 Scope

With increasing demand for organizations to have a single source of reference for their IT

infrastructure, customers using different asset databases need a method to integrate with the Atrium

CMDB. ALT2CMDB addresses Altiris Service & Asset Management Suite to BMC Atrium CMDB

integration.

1.3 Key Features & Benefits

• Centralized IT asset tracking through Atrium CMDB

• Automated import and reconciliation process

• Easy to install the integration with out-of-box configuration

• Easy to customize the import and reconciliation rules

1.4 Required Products

ALT2CMDB requires the following products to be installed and configured:

• BMC® Remedy® Action Request System (AR System) version 7.0

• BMC® Atrium CMDB (CMDB) version 2.0

• BMC® Remedy® Enterprise Integration Engine (EIE) version 7.0

• BMC® Remedy® Link for SQL Server version 7.0

• Altiris® Service & Asset Management Suite™ version 6.0

1.5 Supported Platforms

ALT2CMDB supports the specified BMC products on the following platforms:

• Microsoft Windows using Oracle database

• Microsoft Windows using Microsoft SQL Server database

• Sun Solaris using Oracle database

ALT2CMDB supports Altiris products on the following platforms:

• Microsoft Windows using Microsoft SQL Server database

Detailed BMC Remedy product requirements and supported platforms can be found at:

http://supportweb.remedy.com/Rem/IssuesAndSolutions/CompatibilityMatrix/index.jsp.


2. Overview

ALT2CMDB is a two-step process - importing the data from Altiris Service & Asset Management

Suite and reconciling it in to the production dataset. Figure 1 displays a high-level architecture

outlining the basic dataflow in ALT2CMDB.

Figure 1: ALT2CMDB Architecture

2.1 Importing Data from Altiris Service & Asset Management Suite

Altiris Service & Asset Management Suite supports Microsoft SQL Server. ALT2CMDB utilizes

BMC Remedy Link for SQL Server and BMC Remedy Enterprise Integration Engine to transfer

data from the Altiris Service & Asset Management Suite database tables.

The Altiris Service & Asset Management Suite asset data is imported into a separate dataset,

OTL.ASAMS.IMPORT. See Appendix A for a complete list of data mappings. During the initial

data exchange, records are created for all IT assets found in Altiris Service & Asset Management

Suite. Subsequent data exchanges will update the existing records and create records for newly

found assets.

If an existing record in OTL.ASAMS.IMPORT dataset, no longer exists in the Altiris Service &

Asset Management Suite database, it will be marked as deleted, by setting the MarkAsDeleted

attribute to Yes.

The standard configuration item (CI) classes do not include some optional Altiris Service & Asset

Management Suite specific attributes. This integration includes additional attributes to extend the

CMDB Common Data Model (CDM). See Appendix C for more details.

After importing all asset data, their associations are transferred, using various relationship mapping

definitions. See Appendix B for a complete list of relationship data mappings. By default, these data

exchanges are configured inactive.

2.2 Reconciling the Imported Data

The imported asset data in OTL.ASAMS.IMPORT dataset is reconciled with BMC.ASSET dataset.

See Appendix D for the list of identification rules used for reconciliation.

BMC Remedy Asset Management Application is one of the BMC IT Service Management (ITSM)

products, which utilizes the Atrium CMDB, and acts as a presentation layer and workflow engine to

manage the asset data in BMC.ASSET dataset.

If you wish to do reconciliation with different datasets, you can add new reconciliation rules. Refer

to BMC Atrium CMDB Install and Configuration Guide for details.

The default reconciliation job is configured inactive.


3. Installation

ALT2CMDB can be downloaded as a Microsoft Windows self-extracting executable or UNIX tar

file.

3.1 Prerequisites

1. Before you begin the installation, make sure all products listed under the section Required

Products are installed and configured correctly, and that the platforms being used are

Supported Platforms.

2. BMC Remedy Link for SQL Server must be installed and licensed.

3. ALT2CMDB will occupy one fixed AR System user license.

4. The EIE should have been configured with user IDs to access the AR System and Altiris

Service & Asset Management Suite.

Note: It is recommended that you take a full offline database backup of the AR System, before

installing ALT2CMDB.

3.1.1 Installation on Microsoft Windows

If the AR System is running on Microsoft Windows, follow the steps below to install ALT2CMDB.

1. Download and extract the contents in the self-extracting file, ASAMS.exe, to a temporary folder

(C:\Temp\ASAMS).

2. Copy the CMDB Extension Loader binary (cmdbExtLoader.exe) to the ASAMS_SqlServer

folder under the temporary folder. Figure 2 shows the directory structure after extracting the

files and copying the CMDB extension loader binary.

Contact BMC Software to obtain a copy of CMDB Extension Loader binaries, if you don’t

have them.

Figure 2: Install Directory Structure


3. Double click on cmdbExtLoader.exe, which will start the installation process.

4. Click Next on the Welcome message, and click I Agree for the software license agreement.

5. Enter the AR System server connection information, and Click Next.

6. Enter the administrator login information for the AR System server, and Click Next.

7. The installation process will start importing the CMDB CDM extensions, reconciliation rules,

and EIE data exchange and mappings. Loading the CDM extensions may take some time, as it

applies all new attribute to subclasses. Once completed, look for SUCCESS messages in the

package load summary.

3.1.2 Installation on Sun Solaris

If the AR System is running on Sun Solaris, follow the steps below to install ALT2CMDB.

1. Download and store the tar file, ASAMS.tar, to a temporary directory (/tmp/ASAMS).

2. Open a shell window, change the directory to the temporary directory, and extract the tar file

using:

# tar xvf ASAMS.tar

3. Copy the CMDB Extension Loader binary (cmdbExtLoader) and required libraries (common)

to the ASAMS_SqlServer directory under the temporary directory.

Contact BMC Software to obtain a copy of CMDB Extension Loader binaries, if you don’t

have them.

4. Execute the CMDB extension loader, which will start the installation process:

# ./cmdbExtLoader

5. Accept the license agreement.

6. Enter the AR System server connection information.

7. Enter the administrator login information for the AR System server.

8. The installation process will start importing the Atrium CMDB CDM extensions, reconciliation

rules, and EIE data exchange and mappings. Loading the CDM extensions may take some time,

as it applies all new attribute to subclasses. Once completed, look for SUCCESS messages in

the package load summary.


3.2 Configuration

3.2.1 Data Exchange Vendor Configuration

In order to query the asset data in the Altiris Service & Asset Management Suite database, the EIE

data exchange requires a valid Altiris Service & Asset Management Suite database user account.

Follow the steps below to configure the login details of the Altiris Service & Asset Management

Suite database.

1. From Remedy User, open the EIE Console and select Vendor Configuration in the left pane.

2. Click on the SQL Server database tab, and highlight all Altiris Service & Asset Management

Suite to CMDB data exchanges. These data exchanges will start with ASAMS. They can be

multi-selected using the Ctrl key. Figure 3 shows this selection.

Figure 3: Vendor Configuration Console

3. Enter the Altiris Service & Asset Management Suite database login details, select the Rows

Selected for Apply option and click on the Apply button.

3.2.2 Data Exchange Scheduling

To automate the data exchange between Altiris Service & Asset Management Suite and Atrium

CMDB, EIE data exchange needs a suitable schedule. By default, the main data exchange,

Computers, is scheduled everyday at 1 a.m. All other assets are triggered one after the other, as

described in Table 1 on the next page. It is recommended that you leave these triggered data

exchanges in the same order. You may want to modify the main data exchange to co-ordinate with

other operations in your organization.


Table 1: Default Data Exchange Schedule

Data Exchange For Execution Method On Completion Trigger Data Exchange For

Computers Scheduled

at 1 a.m.

Virtual Machines

Virtual Machines To be triggered Printers

Printers To be triggered Network Devices

Network Devices To be triggered Monitors

Monitors To be triggered Scanners

Scanners To be triggered Peripherals

Peripherals To be triggered Locations

Assets

Locations To be triggered Cost Centers

Asset-Location Relationships

Cost Centers To be triggered Users

Asset-Cost Center Relationships

Users To be triggered Items

Asset-User Relationships

Assets To be triggered Computer-Computer Relationships

Computer-Component Relationships

Items To be triggered

All Relationships To be triggered

To modify the schedule time for the main data exchange,

1. Open the EIE Console from Remedy User, and select Data Exchanges on the left pane.

2. Highlight the data exchange for Computers (ASAMS-SqlServer-Computers-to-CMDB), and

click on the Schedule tab, as shown in Figure 4.

Figure 4: Data Exchange Console


3. Add, Remove or modify (…) the Time, and click on Save button.

Note: If you don’t want to wait until the next scheduling cycle for initial testing, you can change the

execution to occur in a regular time interval, by selecting Interval, and entering appropriate time

interval in the Minutes field.

3.2.3 Activating Data Exchange

All Altiris Service & Asset Management Suite to Atrium CMDB data exchanges are shipped

inactive state. You have to activate them after you have configured the login details. Once activated,

they will transfer asset data from Altiris Service & Asset Management Suite database to the import

dataset (OTL.ASAMS.IMPORT). It will not start overriding any production dataset.

To activate Altiris Service & Asset Management Suite data exchanges,

1. Open the EIE Console from Remedy User, and select Data Exchanges on the left pane.

2. Double click on the data exchange for Computers (ASAMS-SqlServer-Computers-to-CMDB).

This will open the data exchange definition window, as shown in Figure 5 below.

3. Click on the Instance Name drop down menu and select the EIE instance to be used for the

ASAMS data exchange.

4. Change Active radio button to Yes.

5. Click on the Save button, found in the upper right corner.

6. Repeat these steps for each Altiris Service & Asset Management Suite data exchange. Refer

Appendix A & Appendix B lists their full names.

Figure 5: Data Exchange Definition


The data exchange will start depending on your schedule, and it will create asset records in

OTL.ASAMS.IMPORT dataset. Also it will update the debug logs under the directory:

<EIE install directory>/<server>/service/debug/

Example: C:\Program Files\Remedy\Apps\EIE\server\service\debug\ ASAMS-SqlServer-

Computers-to-CMDB.dbg

You can turn the debug off, if you are satisfied with the data exchange. To turn the debug off, click

on the Debug tag for each Altiris Service & Asset Management Suite data exchange, and select No

for Enable Debug Logging.

3.2.4 Activating Reconciliation Job

The asset data imported into the OTL.ASAMS.IMPORT dataset has to be reconciled with the

production asset data, BMC.ASSET, before it can be used by other BMC ITSM products. By

default, the reconciliation rule (ASAMS Identification and Merge Activity) is shipped inactive. It is

recommended that you review the reconciliation rules (Appendix D) and check whether they are

suitable for your production asset dataset, before activating the reconciliation job.

This reconciliation job needs to run after all asset data has been transferred by the EIE Data

Exchanges. There is a default schedule included in this reconciliation job to run at 5 a.m. everyday.

To change the schedule and activate the reconciliation job,

1. Open the CMDB Console from Remedy User, and select Reconciliation Manager from the

tabs across the top.

2. By default, all jobs are displayed. Select Jobs for Show, if it does not show the jobs. Highlight

the ASAMS Identity and Merge Activity, as shown in Figure 6, and click on View in the top

selection.

Figure 6: Reconciliation Manager


3. Modify the schedule, if required, activate the job by selecting Active as Job Status, as shown

below, and click on Save.

Figure 7: Reconciliation Job Activation

The reconciliation job will start running as per the schedule. You can force it to run immediately by

selecting Job History on the left pane from the Reconciliation Manager, selecting the Job

(ASAMS Identification and Merge Activity), and clicking on the Start Job.

Look for any errors in the execution, and check the final Success status. Also verify the reconciled

data in BMC.ASSET dataset.


3.3 Uninstalling ALT2CMDB

You might want to uninstall this integration to reinstall it or upgrade it to a later version. You must

uninstall the integration, before attempting to reinstall.

3.3.1 Removing EIE Data Exchange Definitions

Follow these steps to delete all EIE data exchange definitions for ALT2CMDB:

1. Open Remedy User and connect to the AR System server as administrator.

2. Select File → Open → Object List (Ctrl-O), and select the form EIE:CMDBDataMapping

and click on Search button. This will open the search form.

3. Empty the contents of the form (Ctrl-E), type %ASAMS% for Data Mapping Name, and click

on Search button in the upper right corner. This will list all data mappings with the string

ASAMS in their name.

4. Multi-select all Altiris Service & Asset Management Suite related data mappings (starts

ASAMS), using Ctrl key, and select Actions → Delete (Ctrl-D). This will delete the definitions.

5. Repeat these steps by selecting the following forms from the Object List in step 2:

EIE:CMDBRelationshipData

EIE:CMDBRelMapping

EIE:Data

EIE:DataExchange

EIE:DataExgLookup

EIE:Trigger_DE

EIE:VendorParamLookup

3.3.2 Removing Reconciliation Rules

Follow these steps to delete reconciliation rules for ALT2CMDB:

1. Open the CMDB Console from Remedy User, and select Reconciliation Manager from the

tabs across the top.

2. By default, all jobs are displayed. Select Jobs for Show, if it does not show the jobs. Highlight

the ASAMS Identity and Merge Activity, as shown in Figure 6, and click on Delete in the top

selection.

3. Select Identification Groups for Show, highlight ASAMS Identification Group, and click on

Delete in the top selection.

4. Select Precedence Groups for Show, multi-select ASAMS Import Precedence Group &

ASAMS Default Precedence Group, and click on Delete in the top selection.

5. Select Datasets for Show, highlight ASAMS Import, and click on Delete.

6. Select Dataset Merge Precedence Sets for Show, highlight ASAMS Precedence Set, and click

on Delete in the top selection.


3.3.3 Removing Atrium CMDB CDM Extensions

Follow these steps to delete Atrium CMDB CDM extensions for ALT2CMDB:

1. Open the CMDB Console from Remedy User, and select Class Manager from the tabs across

the top.

2. Highlight the BMC_BaseElement class (listed in the 3rd

column), and click on View button.

This will open the class information dialog.

3. Click on Attributes tab, multi-select all attributes which start with ASAMS, using the Ctrl key,

and click on Remove button. This will create a new entry for each attribute in Delete Pending

status. Appendix D lists all attributes added for this integration.

4. Click on Save button. This will create a new entry for BMC_BaseElement in the Class

Manager Console with Change Pending status. Wait for this entry to disappear from the

console. This may take some time, as it deletes them from all subclasses. You may want to click

on the Refresh button to see the latest status.

5. Repeat these steps for following classes and remove the Altiris Service & Asset Management

Suite attributes, listed in Appendix D:

BMC_ComputerSystem

BMC_Printer

BMC_Organization

BMC_Person

3.3.4 Removing Integration Application Property

Follow these steps to delete the Application Property for ALT2CMDB:

1. Select File → Open → Object List (Ctrl-O) from the Remedy User, and select the form

SHARE:Application_Property and click on Search button. This will open the search form.

2. Empty the contents of the form (Ctrl-E), and click on Search button in the upper right corner.

This will list all application properties found in the AR System server.

3. Select the line which has a Property Value CDM Extensions and Reconciliation Rules for

Altiris Service & Asset Management Suite, and it’s associated Version line, using Ctrl key. The

associated version will have the same Application ID as the Name property. Select Actions → Delete (Ctrl-D).

4. Repeat the step 4 for the property:

EIE Mapping Rules for Altiris Service & Asset Management Suite


Appendix A: Atrium CMDB Data Mappings

Altiris Service & Asset Management Suite BMC Atrium CMDB

Table / View Column Attribute Class

Submitter = ASAMS DatasetId = OTL.ASAMS.IMPORT

Type = Computer

Guid (PK) ASAMS_ID

Name HostName

Domain Domain

OS Name ASAMS_OS_NAME

OS Version ASAMS_OS_VERSION

IP Address ASAMS_IP_ADDRESS

MAC Address ASAMS_MAC_ADDRESS

System Type ASAMS_SYSTEM_TYPE

Name Name

vComputer

and

OTL_COMPUTER

(all except virtual machines)

BMC_ComputerSystem EIE Data Exchange Name:

ASAMS-SqlServer-Computers-to-CMDB


Type = Virtual Machine

Guid (PK) ASAMS_ID

Name HostName

Domain Domain

OS Name ASAMS_OS_NAME

OS Version ASAMS_OS_VERSION



System Type ASAMS_SYSTEM_TYPE

Name Name

vComputer

and

OTL_COMPUTER

(only virtual machines)

BMC_VirtualSystem EIE Data Exchange Name:

ASAMS-SqlServer-VirtualMachines-to-CMDB





Type = Printer

_ResourceGuid (PK) ASAMS_ID

Name HostName

ServerName ASAMS_SERVER_NAME

Color ASAMS_COLOR

DoubleSided ASAMS_DOUBLE_SIDED

Speed AveragePagesPerMinute

MaxResolution ASAMS_MAX_RESOLUTION

Printer.Name Name

Inv_ID_Network_Printer

BMC_Printer EIE Data Exchange Name:

ASAMS-SqlServer-Printers-to-CMDB


Type = Network Device

_ItemGuid (PK) ASAMS_ID

Host Name HostName

Domain Domain



Category Category

Device Class ASAMS_DEVICE_CLASS

Device Type ASAMS_DEVICE_TYPE

Name Name

vNetworkDevice

and

OTL_NETWORK_DEVICE

BMC_ComputerSystem EIE Data Exchange Name:

ASAMS-SqlServer-NetworkDevices-to-CMDB


Type = Network Device


Name Name

vMonitor

BMC_Monitor EIE Data Exchange Name:

ASAMS-SqlServer-Monitors-to-CMDB





Type = Scanner


Manufacturer + Model Name

vScanner

BMC_HardwareSystemComponent EIE Data Exchange Name:

ASAMS-SqlServer-Scanners-to-CMDB


Type = Peripheral


Manufacturer + Model Name

vPeripheral

BMC_HardwareSystemComponent EIE Data Exchange Name:

ASAMS-SqlServer-Peripherals-to-CMDB

Asset Tag ASAMS_ASSET_TAG

Asset Type ASAMS_ASSET_TYPE

Status ASAMS_ASSET_STATUS

Manufacturer ManufacturerName

Model Model

Serial Number SerialNumber

System Number ASAMS_SYSTEM_NUMBER

Barcode ASAMS_BARCODE

Last Barcode Scan ASAMS_BARCODE_SCAN_DATE

vAsset

and

OTL_ASSET

(for all asset types above)

BMC_BaseElement EIE Data Exchange Name:

ASAMS-SqlServer-Assets-to-CMDB


Type = Location


Address Address

City City

State StateOrProvince

Country Country

Zip PostalCode

Name Name

vLocation

BMC_PhysicalLocation EIE Data Exchange Name:

ASAMS-SqlServer-Locations-to-CMDB





Type = Cost Center

ResourceGuid (PK) ASAMS_ID

Cost Center Code ASAMS_COST_CENTER_CODE

Name Name

vCostCenter

and

OTL_COST_CENTER

BMC_Organization EIE Data Exchange Name:

ASAMS-SqlServer-CostCenters-to-CMDB


Type = User

Guid (PK) ASAMS_ID

Personal Title ASAMS_PERSONAL_TITLE

Given Name FirstName

Initials MiddleName

Surname LastName

Display Name PersonAdditionalDetails

Office Location ASAMS_OFFICE_LOCATION

Office Telephone OfficePhone

Email Email

Job Title Title

Department Department

Home Telephone ASAMS_HOME_TELEPHONE

Mobile MobilePhone

Pager PagerPhoneNumber

Facsmile Fax

Name Name

vUser

and

OTL_USER

BMC_Person EIE Data Exchange Name:

ASAMS-SqlServer-Computers-to-CMDB


Appendix B: Relationship Data Mappings


Relationship Class Relationship Definition Relationship Attributes Class Attributes

Relationship Mapping Type: Vendor Source.InstanceId (Key) Class1.InstanceId

Vendor Table: ResourceAssociation Desination.InstanceId (Key) Class2.InstanceId

Vendor Query: ResourceAssociationType = Associated Asset Source.ClassId Class1.ClassId

Desination.ClassId Class2.ClassId

Source.DatasetId Class1.DatasetId

Desination.DatasetId Class2.DatasetId

Name Associated Computer

BMC_MemberOfCollection

For many-to-many relationships

between computers (computers, virtual

machines and printers).

EIE Data Exchange Name: ASAMS-SqlServer-Computer-

Computer-Relationships-to-CMDB

Class 1: BMC_ComputerSystem Class 1 Key: ASAMS_ID Vendor Key: ParentResourceGuid

Class 2: BMC_BaseElement Class 2 Key: ASAMS_ID Vendor Key: ChildResourceGuid Class 2 Query: Type = Computer, Virtual Machine or Printer



Vendor Query: ResourceAssociationType = Associated Asset Source.ClassId Class1.ClassId




Name Associated Component

BMC_HostedSystemComponent

For many-to-many relationships

between computers and components.

EIE Data Exchange Name: ASAMS-SqlServer-Computer-

Component-Relationships-to-CMDB

Class 1: BMC_ComputerSystem Class 1 Key: ASAMS_ID Vendor Key: ParentResourceGuid

Class 2: BMC_HarwareSystemComponent Class 2 Key: ASAMS_ID Vendor Key: ChildResourceGuid



Vendor Query: ResourceAssociationType = Location Source.ClassId Class1.ClassId




Name Asset Location

BMC_ElementLocation

For one-to-one relationships between

assets and locations.

EIE Data Exchange Name: ASAMS-SqlServer-Asset-Location-

Relationships-to-CMDB

Class 1: BMC_BaseElement Class 1 Key: ASAMS_ID Vendor Key: ParentResourceGuid

Class 2: BMC_PhysicalLocation Class 2 Key: ASAMS_ID Vendor Key: ChildResourceGuid



Relationship Class Relationship Definition Relationship Attributes Class Attributes



Vendor Query: ResourceAssociationType = Cost Center Source.ClassId Class1.ClassId




Name Asset Cost Center

BMC_ElementLocation


assets and cost centers.

EIE Data Exchange Name: ASAMS-SqlServer-Asset-CostCenter-



Class 2: BMC_Organization Class 2 Key: ASAMS_ID Vendor Key: ChildResourceGuid



Vendor Query: ResourceAssociationType = Owners Source.ClassId Class1.ClassId




Name Asset Owner

BMC_ElementLocation


assets and owners.

EIE Data Exchange Name: ASAMS-SqlServer-Asset-CostCenter-



Class 2: BMC_Person Class 2 Key: ASAMS_ID Vendor Key: ChildResourceGuid


Appendix C: Data Module Extensions

Class Attribute Date Type

ASAMS_ID Character(256)

ASAMS_CREATED_DATE Date/Time

ASAMS_CREATED_BY Character(256)

ASAMS_MODIFIED_DATE Date/Time

ASAMS_MODIFIED_BY Character(256)

ASAMS_ASSET_TAG Character(256)

ASAMS_ASSET_TYPE Character(256)

ASAMS_ASSET_STATUS Character(256)

ASAMS_SYSTEM_NUMBER Character(256)

ASAMS_BARCODE Character(256)

BMC_BaseElement

ASAMS_BARCODE_SCAN_DATE Date/Time

ASAMS_OS_NAME Character(256)

ASAMS_OS_VERSION Character(256)

ASAMS_IP_ADDRESS Character(256)

ASAMS_MAC_ADDRESS Character(256)

ASAMS_SYSTEM_TYPE Character(256)

ASAMS_DEVICE_CLASS Character(256)

BMC_ComputerSystem

ASAMS_DEVICE_TYPE Character(256)

ASAMS_SERVER_NAME Character(256)

ASAMS_COLOR Character(256)

ASAMS_DOUBLE_SIDED Character(256)

BMC_Printer

ASAMS_MAX_RESOLUTION Character(256)

BMC_Oraganization ASAMS_COST_CENTER_CODE Character(256)

ASAMS_PERSONAL_TITLE Character(256)

ASAMS_OFFICE_LOCATION Character(256)

BMC_Person

ASAMS_HOME_TELEPHONE Character(256)


Appendix D: Identification Rules for Reconciliation

Order Class Rules

1 BMC_ComputerSystem ‘HostName != $\NULL$ AND ‘HostName’ = $HostName$ 2 BMC_BaseElement ‘SerialNumber’ != $\NULL$ AND

‘SerialNumber’ = $SerialNumber$ 3 BMC_BaseElement ‘Name’ = $Name$

BMC and BMC Software 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.

BMC® Remedy® Asset Management Application, BMC® Atrium CMBD, BMC® Remedy® Action Request

System®, BMC® Remedy® Link for SQL Server and BMC® Remedy® Enterprise Integration Engine are

registered trademarks or trademarks of BMC Software, Inc.

Microsoft® and Microsoft Management Service are registered trademarks or trademarks of Microsoft Corporation.

Altiris and Altiris Service & Asset Management Suite are registered trademarks or trademarks of Altiris, Inc.

All other trademarks are the property of their respective owners.

Copyright (c) 2007 BMC Software, Inc.

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the

following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following

disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the

following disclaimer in the documentation and/or other materials provided with the distribution.

• Neither the name of the BMC Software, Inc. nor the names of its contributors may be used to endorse or

promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS

"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT

LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR

A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE BMC SOFTWARE, INC. OR

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

alt2cmdb integration guide v1.5 - bmc software · 1. download and store the tar file, asams.tar, to...

Documents