621 Mx Integ Adapter Taddm

Release 6

Implementation Guide

IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager

First Edition (January 2007)This edition applies to Release 6 of IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager and to all subsequent releases and modifications until otherwise indicated in new editions.

Third-Party Technology: Certain Maximo products contain technology provided under license from third parties, as noted in the following table:

Open Source: Maximo contains computer software obtained from the public domain, known as "Open Source" ownership of which is attributed as follows: Portions 2002, Steve Souza ([email protected]). Portions 2000-2004, Jason Hunter & Brett McLaughlin. Portions 2004-2005, The Apache Software Foundation (http://www.apache.org/).

Copyright International Business Machines Corporation 2007. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule

IBM Product Third-Party Information

All Products Portions 1996-2003 Visual Mining, Inc. Visual Mining NetCharts Server provided by Visual Mining, Inc.

IBM Maximo Portions 1995-2004 Actuate Corporation.

Portions 2005 BEA Systems, Inc. BEA WebLogic Server provided by BEA Systems, Inc.

Portions 1996-2005, i-net software GmbH. J-Integra for COM v2.4. 2004 Intrinsyc Software International, Inc.

Maximo Discovery MSDE Copyright Microsoft Corporation.

1998-2005 Centennial Software Limited.

IBM Maximo Asset Navigator Portions 1993-2002 Snowbound Software Corporation. RasterMaster Raster imaging technology provided by Snowbound Software Corporation.

IBM Maximo Mobile Portions 2005 DataMirror, Inc.

Portions 2000-2005 Zaval Creative Engineering Group.

IBM Maximo Mobile SE Portions 1996-2005 Syclo, LLC.

NoteBefore using this information and the product it supports, read the information in Notices on page Notices-1.

Copyright IBM Corp. 2007 iii

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vAudience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vRelated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vSupport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1: IBM Maximo Integration Adapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Maximo Product Versions Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Asset Discovery Tool Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Integration Composer Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Integration Composer File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Optional IBM Maximo Integration Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Contents of the Adapter CD-ROM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5TADDM Adapter Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Chapter 2: Setting Up the Integration Adapter for TADDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Adding Adapter Components to Integration Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Installing the TADDM Data Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Setting Up the TADDM-to-Maximo Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Defining a Data Source Connection to Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Creating the TADDM-to-Maximo Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Chapter 3: Creating Effective Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Mapping Data for Sites and Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Mapping Data for Conversion Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Mapping Key Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Mapping Data for Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Mapping Data for Scan Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Chapter 4: Integration Adapter Mapping for TADDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notices-1

Contents

iv IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

Copyright IBM Corp. 2007 v

About This Guide

This guide explains how to set up the IBM Maximo Integration Adapter for IBM Tivoli Application Dependency Discovery Manager (TADDM). IBM Maximo Integration Adapters use IBM Maximo Integration Composer (formerly Maximo Fusion) to import information technology asset data collected by asset discovery tools into the IBM Maximo deployed assets database tables.

The IBM Maximo Integration Adapter for TADDM includes a pre-defined mapping for converting data from the TADDM asset discovery tool into the format required by the Maximo deployed assets tables. This guide explains how to import the mapping in this adapter into the Integration Composer, but it does not explain how to use the Integration Composer. For more information about using the Integration Composer to migrate data into Maximo, refer to the IBM Maximo Integration Composer System Administrators Guide or to Integration Composer Help.

This section explains how this guide can help you to use the IBM Maximo Integration Adapter for TADDM. It also provides information about other IBM Corporation resources available to you, such as additional documentation and support.

Audience

This guide is designed for the system administrator, network administrator, or other professional who is responsible for using the Integration Composer to import data collected by TADDM into Maximo.

Related Documentation

For more information about IBM Maximo for Asset Management, refer to the following documentation:

Document Description

IBM Maximo Finance Managers Guide

Describes how IBM Maximo completes financial transactions and how to set up general ledger accounts.

Related Documentation

vi IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

For more information about IBM Maximo Integration Composer, refer to the following documentation:

IBM Maximo Installation Guide Describes how to install and configure the following software:

! Application server! IBM Maximo! Actuate

IBM Maximo Multisite Administrators Guide

Describes how to configure IBM Maximo for a Multisite implementation.

IBM Maximo Online Help Provides step-by-step procedures for IBM Maximo applications.

IBM Maximo Reconciliation Module Implementation Guide

Describes how to use the IBM Maximo Reconciliation module to reconcile the two types of information that IBM Maximo maintains about information technology (IT) assets: IT asset data and deployed asset data.

IBM Maximo Report Administration and Development Guide

Describes how to use Actuate to design and administer IBM Maximo reports.

IBM Maximo System Administrators Guide

Describes database configuration, security, and other administrative level applications and tasks.

IBM Maximo Users Guide Provides an overview of the IBM Maximo end user applications. It also describes how the IBM Maximo applications interact with each other.

IBM Maximo Workflow Implementation Guide

Provides information about how to use IBM Maximo to plan, design, build, test, implement, and manage Workflow processes.

IBM Maximo Enterprise Adapter (MEA) System Administrator's Guide

Describes how to configure and use the IBM MEA.


IBM Maximo Integration Composer System Administrators Guide

Describes how to use the Integration Composer to map data from an external source and import the data into the Maximo database.


Support

About This Guide vii

Support

IBM Maximo users with a valid Annual Customer Support Plan (ACSP) can obtain product support online at Support Online: support.mro.com.

Support Online includes information about product releases, software patches, and documentation updates. To find the most current version of a document, refer to the Knowledge Base on this site.

IBM Maximo Integration Composer Installation Guide

Describes how to install and configure the Integration Composer. IBM Corporation provides installation guides for the following platforms:

! Microsoft Windows

! UNIX

Integration Composer Help

Provides step-by-step procedures for the Integration Composer.


Support

viii IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

Copyright IBM Corp. 2007 1-1

The IBM Maximo Integration Composer (Integration Composer) is an integration tool that you can use to import information technology (IT) asset data into IBM Maximo for Asset Management. To gather deployed asset data, an asset discovery tool, such as IBM Tivoli Application Dependency Discovery Manager (TADDM), scans computers, network devices, and network printers deployed in an enterprise and records information about the hardware and software installed on those assets. The Integration Composer transforms the collected data and imports it into Maximo.

Before you migrate data from an external data source into Maximo, you use the Integration Composer to map data from the source format to the target Maximo format. A mapping is a set of expressions that tells the Integration Composer how to create data in Maximo using information from a source. For each property that you want to import, you define an expression that specifies how to transform the data for that property when the Integration Composer imports the data from the source into Maximo.

To facilitate data migration, the IBM Maximo Integration Adapter for TADDM provides a set of pre-defined mapping expressions designed to transform data in the TADDM data source to the format required by the deployed assets tables in the Maximo database. You can import this mapping into the Integration Composer and with little or no additional programming execute a mapping to import TADDM data into Maximo.

Maximo Product Versions Supported

IBM Maximo This integration adapter requires Maximo 6.2.1 or later.

IBM Maximo Integration Composer

To use the IBM Maximo Integration Adapter for TADDM, you must install Integration Composer 6.2.1, or later. For information about the minimum hardware and software requirements for the Integration Composer, refer to the IBM Maximo Integration Composer Installation Guide for Windows or IBM Maximo Integration Composer Installation Guide for UNIX.

Asset Discovery Tool Supported

You can use this IBM Maximo integration adapter with IBM Tivoli Application Dependency Discovery Manager 5.1.1 FP1 and CCMDB 1.1.1 FP1.

IBM Maximo Integration Adapter Overview 1

Integration Composer Components

1-2 IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

Integration Composer Components

This section provides an overview of the Integration Composer components. For more detailed information, refer to the IBM Maximo Integration Composer System Administrators Guide. The Integration Composer includes the following components:

! Integration Composer application! Integration Composer engine! JDBC drivers! Integration Composer repository

Integration Composer Application

The Integration Composer application has a Windows-based graphical user interface (GUI) that lets you define data sources, browse data source data, define data schemas, and create mappings to transform and migrate data.

Integration Composer Engine

The Integration Composer engine processes mapping expressions that transform data from a source data source and integrate it into the target Maximo data source. You can execute the mapping directly from the Integration Composer application or as a stand-alone process running from a command line.

NOTE For performance reasons, it is more efficient to run mappings as a stand-alone process executed from a command line.

JDBC Drivers The Integration Composer uses JDBC drivers to establish connections between a source data source and a target data source. IBM Corporation provides the following JDBC drivers with the Integration Composer:

! IBM DB2 JDBC driver.

! i-net OPTA JDBC driver for Microsoft SQL Server 7/2000 and SQL Server 2005.

! Oracle JDBC Thin driver. This driver supports Oracle 10g and earlier versions (including 8.0, 8i, and 9i).

Integration Composer Repository

The Integration Composer repository resides in the Maximo database and contains the following Integration Composer data:

! Metadata for read-only data schemas delivered with the Integration Composer. This metadata defines the structure of the data.

In addition to metadata, the Integration Composer repository stores other information about mapping execution parameters for the data schema. This information includes caching mechanism, inventory hardware last scan class and property names, software last scan class and property names (optional), and so forth. Users cannot modify this information; it is set when data schemas are created in the Integration Composer or when you import a data schema into the Integration Composer.

! Metadata for data schemas that users create in the Integration Composer.

! Data source definitions that provide database connection parameters.

Integration Composer File Structure

IBM Maximo Integration Adapter Overview 1-3

! Mappings that define how to transform data instances and migrate them from a source to a target.

! If a last scan time stamp exists, the Integration Composer stores the most recent last scan time stamp for every source IT asset in the Integration Composer repository.


When you install the Integration Composer, if you accept the default installation path, the installation program installs the application in the Maximo_Fusion directory.

At this location, the installation program sets up the following file structure for the Integration Composer:


e

NOTE Some installations might include an icons folder. This folder is obsolete.

If you select a different location when you install the Integration Composer, the installation program creates the same file structure in the location that you specify.



The Integration Composer folders store the following data:

Folder Description

bin Stores the following batch files:

! commandLine.bat batch file that executes an Integration Composer mapping from a command line.

! init.bat batch file used to define and initialize the Integration Composer environment.

! startFusion.bat batch file that launches the Integration Composer.

data Stores the following folders:

! dataschema stores data schemas that users export from the Integration Composer or that users copy to this folder from other sources, such as an IBM Maximo integration adapter.

! mappings stores mappings that users export from the Integration Composer or that users copy to this folder from other sources, such as an IBM Maximo integration adapter.

! properties contains specialized application properties files. The provider sub-folder also includes specialized application properties files.

genrules Stores Java source files that the Integration Composer creates when you execute a mapping. Do not modify any files in this folder.

help Stores the Integration Composer online help files. Do not modify any files in this folder.

lib Stores third-party Java application program interfaces (APIs) that the Integration Composer uses, including JDBC drivers.

log Stores the Integration Composer log files.

PowerUpdateClient Stores files that PowerUpdate uses to check for updates to the Integration Composer. Do not modify any files in this folder.

Uninstall_Integration_Composer

Stores the files that uninstall the Integration Composer from your computer. Do not modify any files in this folder.

Optional IBM Maximo Integration Adapters

IBM Maximo Integration Adapter Overview 1-5

Optional IBM Maximo Integration Adapters

In addition to this IBM Maximo Integration Adapter for TADDM, IBM Corporation also offers the following optional integration adapters:

! IBM Maximo Integration Adapter for Altiris Inventory Solution

! IBM Maximo Integration Adapter for Centennial Discovery

! IBM Maximo Integration Adapter for HP CM (Hewlett Packard Configuration Management) Inventory Manager(formerly HP Inventory Manager using Radia)

! IBM Maximo Integration Adapter for IBM Tivoli Configuration Manager

! IBM Maximo Integration Adapter for MainControl i.collect

! IBM Maximo Integration Adapter for Maximo Discovery

! IBM Maximo Integration Adapter for Microsoft SMS

Contents of the Adapter CD-ROM

The CD-ROM for the IBM Maximo Integration Adapter for TADDM contains the following files:

! TADDM.schm This data schema file defines the structure for organizing and classifying data in the IBM Tivoli Application Dependency Discovery Manager data source.

! TADDM11toDPA62.fsn This mapping file provides predefined expressions you can use to transform data from IBM Tivoli Application Dependency Discovery Manager formats to Maximo Deployed Assets formats.

! 621_mx_integ_adapter_taddm.pdf The IBM Maximo Integration Adapter for IBM Tivoli Application Dependency Discovery Manager Implementation Guide is provided in Adobe Systems Portable Document Format (PDF).

TADDM Adapter Checklist


TADDM Adapter Checklist

The following checklist summarizes how to install and use the IBM Maximo Integration Adapter for IBM Tivoli Application Dependency Discovery Manager.

Adding TADDM Components to Integration Composer

[ ] 1 Add adapter components to Integration Composer.

Copy the following files, which are provided with the IBM Maximo Integration Adapter for IBM Tivoli Application Dependency Discovery Manager, to the appropriate location in the Integration Composer installation directory:

! TADDM11toDPA62.fsn! TADDM.schm

For instructions about how to complete these steps, see "Adding Adapter Components to Integration Composer," on page 2-1.

Setting Up the TADDM Adapter in Integration Composer

[ ] 2 Install the TADDM data schema.

Open the Integration Composer and complete the following tasks to install the TADDM data schema:

! Create a new data schema for TADDM.! Import the TADDM data schema file (TADDM.schm).! Save the data schema.

For instructions about how to complete these steps, see "Installing the TADDM Data Schema," on page 2-2.

[ ] 3 Define a data source connection for the target Maximo data source.

In the Integration Composer, set up a data source connection for the target data source, which is Maximo deployed assets.

When you create an adapter mapping, you must have a data source connection defined for both the target data source and the source data source. You defined a data source for the source TADDM data source in step 2 when you installed the data schema.

For instructions about how to complete these steps, see "Setting Up the TADDM-to-Maximo Adapter," on page 2-9.

[ ] 4 Create a TADDM-to-Maximo mapping.

In the Integration Composer, create a new mapping for TADDM to Maximo deployed assets and import the mapping file provided with this adapter (TADDM11toDPA62.fsn) into the new mapping you create.

For instructions about how to complete these steps, see "Setting Up the TADDM-to-Maximo Adapter," on page 2-13.

[ ] 5 Modify the mapping as required.

If appropriate, in the TADDM-to-Maximo mapping you create, modify mapping expressions to suit your business needs.

For instructions about how to modify mapping expressions, see the IBM Maximo Integration Composer System Administrators Guide.

Importing TADDM data into Maximo

[ ] 6 Import TADDM data into Maximo.

To import TADDM data into Maximo, execute the TADDM-to-Maximo mapping.

For instructions about how to execute mappings, see the IBM Maximo Integration Composer System Administrators Guide.


This chapter explains how to install the components of the IBM Maximo Integration Adapter for TADDM. It also tells you how to create a mapping that you can use to import the deployed asset data gathered by TADDM into the Maximo deployed assets database tables.

Before You Begin

Before you install the components, complete the following steps:

1 Verify that you have installed Maximo release 6.2.1 or later.

2 Verify that you have installed IBM Maximo Integration Composer release 6.2.1 or later.

3 Copy the files provided with the integration adapter to a convenient directory, for example C:\temp.

4 If the Integration Composer is running, close all open windows and exit the application.

5 If you have any data in your Maximo database, back up the database.

Adding Adapter Components to Integration Composer

Before you can use the integration adapter, you must copy the following files to the appropriate folders in the Integration Composer installation directory:

! TADDM11toDPA62.fsn! TADDM.schm

To add TADDM adapter components to Integration Composer, complete the following steps:

1 From the temporary location where you saved the TADDM integration adapter components, copy the TADDM11toDPA62.fsn mapping file to the following location:

\data\mappings

NOTE You can put the file in a different location; however, when you import the file into the Integration Composer, by default the

Setting Up the Integration Adapter for TADDM 2

Installing the TADDM Data Schema


Integration Composer selects the mappings folder. If you put the file in a different location, you have to browse to that location and select the file.

2 From the temporary location where you saved the TADDM integration adapter components, copy the TADDM.schm data schema file to the following location:

\data\dataschema

After you add the file to the Integration Composer installation directory, you can use the Integration Composer application to import it into a TADDM data schema.


Before you can use the integration adapter to create a mapping and migrate TADDM data, you must install the TADDM data schema in the Integration Composer repository. This section explains how to define a TADDM data schema in Integration Composer and then import the data schema file provided with the integration adapter into it.

Defining the Data Schema When you define a data schema, you name the data schema, define a data source, and specify connection parameters for the data source. After you define data source connection parameters, the Integration Composer stores the connection information and displays those parameters when you attempt to connect to the data source. The only parameter the Integration Composer requests is the password.

After you define a new data schema, the Integration Composer displays the Data Schema window. From this window, you can import the TADDM.schm file provided with this integration adapter.

To define a new data schema, complete the following steps:

1 In the Integration Composer window, choose Define New Data Schema. The Integration Composer displays the Data Schema page of the Define a New Data Schema window, as shown in the following figure.


Setting Up the Integration Adapter for TADDM 2-3

Define a New Data Schema Window Data Schema Page

NOTE In the Define a New Data Source window, you can click Back to review or change previous selections. To cancel this procedure and return to the IBM Maximo Integration Composer window, click Cancel.

Naming the Data Schema 2 In the Data Schema field on the Data Schema page, enter the name of the data schema, then click Next. The Integration Composer displays the Data Source page, as shown in the following figure.

Define a New Data Schema Window Data Source Page

Defining the Data Source 3 In the Data Source field, enter a name for the data source (the name must have at least two characters), then click Next. The Integration



Composer displays the Connection Information page, as shown in the following figure.

Define a New Data Schema Window Connection Information Page

Setting Up Connection Parameters

4 On the Connection Information page, in the JDBC Driver field, select a driver.

5 Enter the parameters for the driver as required. The fields displayed depend upon the type of driver selected. The following table lists some of the fields the Integration Composer might display.

6 If appropriate, to test the connection to the data source, click Test Connection. The Integration Composer displays a Test Connection dialog box. The text in the dialog box depends on whether the test was successful. To respond to the dialog box, select one of the following options:

Field Description

Host Name Specifies the host name for the data source.

Host Port Specifies the port for the data source.

Host SID Session identifier for the host (that is, the database instance name).

Database Database name for the data source.

User Name Database user name for the data source.

Password Database password for the data source.

Table Owner

Specifies a data schema name or database schema owner.

URL Specifies the URL address to access a database instance.



! If the Integration Composer cannot establish a connection, it displays an explanatory message. Click OK. The Integration Composer closes the Test Connection dialog box. Review the values for the connection parameters and retry the connection.

! If the Integration Composer establishes a connection, it displays a confirmation message. Click OK. The Integration Composer closes the Test Connection dialog box.

NOTE The Test Connection feature lets you test only the connection without invoking any additional Integration Composer processes. JDBC drivers that are not JDBC 2.0 compliant might not support this feature.

7 On the Connection Information page, click Finish. The Integration Composer displays the Data Schema window, as shown in the following figure. The Integration Composer displays the root class in red because no properties are associated with the class.

NOTE The display properties you set for your computer might affect colors. The color displayed on your computer might vary.

Sample Data Schema Window Showing Root Class

Importing the Data Schema 8 To import the data schema provided with the TADDM integration adapter, from the Select Action menu in the Data Schema window, select Import



Data Schema. The Integration Composer displays the Import Data Schema dialog box, as shown in the following figure.

Import Data Schema Dialog Box

The Import Data Schema dialog box lists the data schemas you copied to the custom data schemas folder.

The dialog box includes the following buttons:

9 In the Import Data Schema dialog box, select the data schema file to import. The Integration Composer populates the File name field with the file's name.

Fixing Errors 10 Click Open. The Integration Composer imports the data schema. If discrepancies exist between the data source and the data schema, the Integration Composer displays the Data Schema Analysis window, as shown in the following figure.

Button Description

Navigates to the folder one level higher than the current folder.

Creates a new folder in the selected folder.

Displays large icons for sub-folders and files in the selected folder.

Displays details for sub-folders and files in the selected folder.

Imports the data schema into the Integration Composer.

Cancels the import action.



Data Schema Analysis Window

This window lists discrepancies the Integration Composer found between the data schema and the corresponding data source. You can use this window to correct the following discrepancies:

! Case of a table name in the database does not match that of a table associated with a class in the data schema.

! Case of a column name in the database does not match that of a table column associated with a class table in the data schema.

! Length of a table column in the database does not match length of the same column in the data schema.

! Data type of a table column in the database does not match the type of the same column in the data schema.

The Data Schema Analysis window includes the following buttons:

Button Description

Opens a Data Schema Statistics window that displays statistics for table and column errors.

Expands all nodes in the tree to display information about inconsistencies between the data schema and the data source.



11 Review the errors displayed in the Data Schema Analysis window and select one of the following options.

! To repair the errors, click Fix Errors. The Integration Composer repairs the errors and displays the Data Schema window.

! To close the dialog box without repairing the errors, click Close. The Integration Composer displays the following window:

Data Schema Analysis Warning

Select one of the following options:

! To make the data schema match the source database, complete the following steps:

a In the Data Schema Analysis Warning window, click Yes. The Integration Composer repairs the errors, closes the warning window, closes the Data Schema Analysis window, and displays an Import dialog box indicating that the import is finished.

b In the Import dialog box, click OK. The Integration Composer displays the Data Schema window. Go to step 12.

Fixes errors that are selected in the tree hierarchy. The Integration Composer displays errors that it can correct automatically with a green check.

NOTE You cannot clear the check boxes. You can either fix all errors indicated or fix no errors.

Closes the Data Schema Analysis window.

Button Description

Setting Up the TADDM-to-Maximo Adapter


! To leave the data schema as is, click No. The Integration Composer imports the data schema as is and displays the Data Schema window. Go to step 12.

! To cancel the action, click Cancel. The Integration Composer closes the warning window and displays the Data Schema Analysis window. Review the options in this window and select the appropriate action. These options are described in step 10.

12 If appropriate, after you import the data schema file, you can modify the data schema. For more information about working with data schemas, see the IBM Maximo Integration Composer System Administrators Guide or Integration Composer Help.

Saving the Data Schema 13 After you finish working with the data schema, from the Select Action menu, select Save. The Integration Composer saves the data schema.

NOTE If the Integration Composer does not save the data schema successfully, it displays an error message. Click OK. Resolve the errors and try to save the data schema again.

14 If appropriate, to close the data schema, from the Select Action menu, select Close. The Integration Composer closes the data schema and displays the IBM Maximo Integration Composer window.


This section of the guide explains how to create data source definitions to connect the Integration Composer to the Maximo deployed assets database. It also explains how to create a mapping for TADDM to Maximo deployed assets and import the mapping provided with this adapter (TADDM11toDPA62.fsn) into the mapping you create.

Defining a Data Source Connection to Maximo

The Integration Composer uses JDBC drivers to connect to source databases and to the target Maximo database. Before you create an adapter mapping, you must have a data source connection defined for both the target data source (that is, the Maximo deployed assets tables) and the source data source (that is the TADDM data source). You already defined a data source for the source TADDM data source when you defined the TADDM data schema using the instructions in Installing the TADDM Data Schema on page 2-2. You must now define a data source for Maximo deployed assets.

When you define a data source, you perform the following tasks:

! Select a data schema for the data source.

! Name the data source.

! Select a JDBC driver and specify the parameters for connecting to the data source.



After you define data source connection parameters, the Integration Composer stores the connection information and displays those parameters when you attempt to connect to the data source. The only parameter the Integration Composer requests is the password.

In an Integration Composer session, if you connect to a data source, the Integration Composer keeps the data source connection open throughout the session unless you complete one of the following steps:

! Execute a mapping for the data source.

! Close the connection using the Close Data Source Connection option in the Data Source menu in the IBM Maximo Integration Composer window.

! Close a data schema by selecting Close from the Select Action menu on the Data Schema window.

! Delete the open data source.

Define a Data Source To define a data source, complete the following steps:

1 Sign in to the Integration Composer application using a valid user ID and password. Integration Composer displays the IBM Maximo Integration Composer window.

2 In the IBM Maximo Integration Composer window, choose Define New Data Source. The Integration Composer displays the Data Schema page in the Define a New Data Source window. This page displays data schemas delivered with the Integration Composer and any data schemas that you created using the Data Schema functions in the application, as shown in the following figure.

Define a New Data Source Window - Data Schema Page



3 On the Data Schema page, select a data schema, and click Next. The Integration Composer displays the Data Source page, as shown in the following figure.

Define a New Data Source Window - Data Source Page

4 In the Data Source field, type a name for the data source (the name must have at least two characters) and click Next. The Integration Composer displays the Connection Information page, as shown in the following figure.

CAUTION If you enter an existing data source name, the connection parameters that you enter replace the original data source connection parameters.

Define a New Data Source Window - Connection Information Page



5 On the Connection Information page, from the JDBC Driver drop-down list, select a driver.

6 Type the parameters for the driver as required.

The Integration Composer displays fields on this page based on the type of driver selected. The following table lists some of the fields the Integration Composer might display.

7 If appropriate, to test the connection to the data source, click Test Connection and select one of the following options:

! If the Integration Composer cannot establish a connection, it displays an explanatory message. Click OK. The Integration Composer closes the Test Connection dialog box. Review the values for the parameters and retry the connection.

! If the Integration Composer establishes a connection, it displays a confirmation message. Click OK. The Integration Composer closes the Test Connection dialog box.

NOTE The Test Connection feature lets you test only the connection without invoking any additional Integration Composer processes. JDBC drivers that are not JDBC 2.0 compliant might not support this feature.

8 On the Connection Information page, click Finish. The Integration Composer saves the data source and displays a Save dialog box.

9 In the Save dialog box, click OK. The Integration Composer displays the IBM Maximo Integration Composer window.

NOTE If the Integration Composer does not save the data source successfully, it displays one or more error messages. Click OK. The Integration Composer closes the error message dialog box. Resolve the error(s) and try to define the data source again.

Field Description

Host Name Specifies the host name for the data source.

Host Port Specifies the port for the data source.

Host SID Session identifier for the host (that is, the database instance name).

Database Database name for the data source.

User Name Database user name for the data source.

Password Database password for the data source.

Table Owner

Database schema name or database schema owner.

URL URL address to access a database instance.



Creating the TADDM-to-Maximo Mapping

After you set up connections to your data sources, use the following procedure to create a mapping in the Integration Composer and import the TADDM mapping provided in this adapter.

WARNING If you import a mapping into a mapping that contains expressions, you should be aware that importing a mapping has the following effect on the original mapping you are importing into:

!If an expression exists in both mappings, the Integration Composer replaces the existing expression with the imported expression.

!The Integration Composer adds any new expressions in the imported mapping to the original mapping.

!If an expression exists only in the original mapping, it remains unchanged; the Integration Composer does not delete the existing expression.

To import the TADDM mapping into the Integration Composer, complete the following steps:

Sign In to the Integration Composer

1 Sign in to the Integration Composer application using a valid user ID and password. The Integration Composer displays the IBM Maximo Integration Composer window.

Create a New Mapping 2 In the IBM Maximo Integration Composer window, select Create New Mapping. The Integration Composer displays the New Mapping window.

New Mapping Window

3 From the Source drop-down list of existing and available data sources, select the TADDM source data source.

4 From the Target drop-down list of existing and available data sources, select the Maximo deployed assets target data source.

5 In the Mapping Name field, enter a new mapping name (maximum of 255 characters). Mapping names are case sensitive; for example, taddm is not the same as TADDM.

6 Click OK. The Integration Composer displays the Mapping window; or, if no data sources are open for the specified mapping, the Integration



Composer displays a Connection Information page in the Open Data Source window.

7 Select one of the following options:

! If the Integration Composer displays the Mapping window, go to step 8 on page 2-14.

! If the Integration Composer displays the Connection Information page in the Open Data Source window, use the following procedure to complete the connection information:

a On the Connection Information page in the Open Source Data Source window, either accept the defaults established during the last connection to the data source or update the fields.

b Click Finish.

c On the Connection Information page in the Open Target Data Source window, either accept the defaults established during the last connection to the data source or update the fields as necessary.

d Click Finish to establish the connection to the target.

The Integration Composer displays the Mapping window.

Import the TADDM Mapping

8 From the Select Action menu in the Integration Composer Mapping window, select Import. The Integration Composer displays the Import Mapping dialog box, as shown in the following figure.

Import Mapping Dialog Box



The Import Mapping dialog box includes the following buttons:

9 In the Import Mapping dialog box, select the following file:

TADDM11toDPA62.fsn

NOTE When you select Import from the Select Action menu, by default the Integration Composer points to the mappings folder. If you stored the .fsn file to a different location, you can use the browse features in this window to locate the file. The .fsn extension identifies Integration Composer files.

The Integration Composer displays the name of the file selected in the File name field.

10 Click Open. The Integration Composer imports the mapping.

NOTE If any errors result from importing the mapping, the Integration Composer displays a dialog box listing the errors and asking if you want to continue to import the mapping. To respond, select one of the following options:

!To cancel the import action without importing the mapping, click No. The Integration Composer closes the dialog box and does not import the mapping.

!To continue to import the mapping, click Yes. The Integration Composer imports the mapping and displays errors in red. Resolve the errors before saving the mapping.

11 If appropriate, you can modify the mapping. For more information about working with mappings, refer to the IBM Maximo Integration Composer System Administrators Guide.

12 After you finish the mapping, from the Select Action menu, select Save to save the mapping. The Integration Composer saves the mapping.

NOTE To save changes as a new mapping, from the Select Action menu, select Save As. The Integration Composer displays a Save Mapping As window. In the Mapping Name field in this window, type a new name for the mapping and click OK. The Integration

Button Description

Navigates to the folder one level higher than the current folder.

Creates a new folder in the selected folder.

Displays large icons for sub-folders and files in the selected folder.

Displays details for sub-folders and files in the selected folder.

Imports the mapping into the Integration Composer.

Cancels the import action.



Composer saves your changes with the new mapping name. For instance, if you open mapping A and save it as B, the Integration Composer saves your changes as mapping B and keeps mapping B open for editing. Mapping A will still exist in its original form.

13 To close the Mapping window, from the Select Action menu, select Close. The Integration Composer displays a Close Mapping dialog box.

14 In the Close Mapping dialog box, click Yes. The Integration Composer closes the Mapping window and displays the IBM Maximo Integration Composer window.

NOTE For information about how to execute a mapping after you have created it, refer to the IBM Maximo Integration Composer System Administrators Guide.


This chapter offers useful information for special mapping expressions and suggestions for creating effective mappings in the Integration Composer.

Mapping Data for Sites and Organizations

Maximo maintains information based on sites and organizations. Most asset discovery tools do not provide scanned data about sites and organizations. If you want to differentiate computers, network devices, and network printers by sites and/or organizations, you must specifically set these values in your Integration Composer mapping.

If you want to include site and/or organization data, you can insert literal values for Siteid and Orgid in the Deployed Asset target, as shown in the following figure.

Sample Mapping Expression for Siteid

Site and organization data is not a requirement, but you can specify a value for site and organization so that the data is available in the Maximo Deployed Assets applications and is also available for the Maximo Reconciliation module. Because the Integration Composer does not validate this data, be sure to specify a valid value.

The Maximo Deployed Assets module applications have a Site field but not an Organization field. The organization can be determined based on the site. If the Maximo Deployed Assets module applications display site information, the standard Maximo rules govern how Maximo displays site data.

Creating Effective Mappings 3

Mapping Data for Conversion Applications


Mapping Data for Conversion Applications

Because of variable hardware and software naming conventions, data collected by asset discovery tools for display in the Maximo Deployed Assets module is often inconsistent. For example, operating system might sometimes be Fermion 4 and sometimes Fermion IV. In addition, sometimes asset discovery tools include version and release numbers in product names, such as IBM Maximo 4.1 or IBM Maximo 5.2. Your enterprise might want to track only instances of IBM Maximo without specifying a version number.

The Deployed Assets Administration module in Maximo includes the following five conversion applications that let Maximo translate inconsistent names used by asset discovery tools to standard naming conventions.

! Adapter Conversion translates adapter names, both media adapters (such as video and sound cards) and network adapters.

! Manufacturer Conversion translates manufacturer names.

! Operating System Conversion translates operating system names.

! Processor Conversion translates processor (CPU) names.

! Software Conversion translates software application names.

The conversion applications in the Maximo Deployed Assets Administration module let administrators review the names assigned to imported data and, if necessary, set up conversions that translate variations in software, hardware, or manufacturer names to a standard naming convention.

Each record in a conversion application specifies a target name and a variant or a set of variants. A variant is a variation of a name that Maximo translates to the target name each time data is displayed.

Maximo applies deployed asset conversions each time deployed asset data for computers, network devices, and network printers is requested. Maximo displays the translated data in the Deployed Assets module applications and uses the translated data in the reports generated for these applications.

When the Integration Composer imports adapter, manufacturer, processor, operating system, and software application data into Maximo, it checks the data to determine whether the deployed asset name exists as a variant on a conversion record in the Maximo database. If the Integration Composer does not find a variant, it creates a conversion record with a target name and a variant name that are identical to the name of the deployed asset.

To enable the Integration Composer to supply a target name and variant, an Integration Composer mapping must contain expressions for both a target name and a variant name for adapters, manufacturers, processors, operating systems and software applications. The target name must be identical to the variant name, as shown in the following figure:

Mapping Key Properties

Creating Effective Mappings 3-3

Sample Target Name with Identical Variant Name

You cannot have a null value for the target name and variant name properties. If these properties have null values, Maximo does not display deployed asset data for computers, network printers, network devices, adapters, manufacturers, operating systems, processors, or software.

In IBM Maximo integration adapters, the expression defined for both the target name and the variant name searches for a value and if the value is null returns the string UNKNOWN as shown in the following example:

{ String name = 'OS.ManufacturerName'; if ((name != null) && (name.length() > 0)) { if (!"".equalsIgnoreCase(name) && !"unknown".equalsIgnoreCase(name)) { return name; } } return "UNKNOWN";}

Mapping Key Properties

When creating a mapping, if a class has only a Generated Key or a Foreign Key, you must select one or more properties as Alternate Keys for the class.

Mapping Data for Files

This IBM Maximo Integration Adapter does not map source data about files to the Maximo Deployed Assets File class. You can modify mappings to include file data; however, you should be aware that this might affect Integration Composer performance if large numbers of files are present.

Mapping Data for Scan Dates


Mapping Data for Scan Dates

When the Integration Composer executes a mapping for the first time, it copies the last scan date time stamp for each top-level asset in the TADDM data source into the Integration Composer repository. On subsequent mapping executions, the Integration Composer compares the last scan date in the Integration Composer repository with the scan date from the TADDM data source and performs one of the following actions:

! If the dates match, the Integration Composer skips the source instance.

! If the dates differ and the source date is more recent than the date stored in the Integration Composer, the Integration Composer processes the expressions for the source instance and updates the last scan date in the repository.

By doing this, the Integration Composer ensures that it transfers only the data that has changed since the last scan date.

The Integration Composer determines scan dates based on the source-to-target mappings defined for the following Deployed Assets properties:

! Deployed Asset.Hwlastscandate

! Computer.Swlastscandate


The following table lists the mapping expressions defined in this IBM Maximo Integration Adapter for IBM Tivoli Application Dependency Discovery Manager.

Integration Adapter Mapping for TADDM 4

Maximo Deployed Assets IBM Tivoli Application Dependency Discovery Manager

Class NameProperty

.Key Name

Key: X=Primary Key XX=Alternate Key

Deployed Asset XX Assetclass COMPUTER or

NETPRINTER or

NETDEVICE

XX Domainname System.Fqdn or

System.Name or

UNKNOWN

XX Nodename System.Fqdn or

System.Name or

UNKNOWN + System.Contextip

Assettag System.Assettag

Description System.Description

Hwlastscandate System.Lastmodifiedtime

Makemodel System.Model

Manufacturer System.Manufacturer or

UNKNOWN

Orgid

Serialnum System.SerialNumber

Siteid

Sourceid System.Pk

Supportssnmp

Systemrole System.Type

Computer X Nodeid

Biosdate

Biosname

Biospnp

Biosversion


Computer

(continued)

Logonname

Moboassettag

Mobochipset

Mobodescription

Mobomakemodel

Mobomanufacturer

Moboserialnumber

Ramdescription

Ramsize Computer.Memorysize

Ramtotalslots

Ramtype

Ramunit MBYTE or

GBYTE

Ramunusedslots

Smbios

Supportswmi

Swlastscandate

Communication X Nodeid

XX Devicename

XX Devicetype

XX Makemodel

XX Manufacturer

Assettag

Bandwidth

Bandwidthunit

Description

Serialnumber

Display X Nodeid

XX Displaytype

XX Makemodel

XX Manufacturer

XX Serialnumber

Assettag

Colordepth

Description

Displaysize

Maxhorzresolution

Maxvertresolution


Class NameProperty

.Key Name


Integration Adapter Mapping for TADDM 4-3

File X Nodeid

XX Extension

XX Name

XX Path

XX Volume

Author

Description

Filecreatedate

Filesize

Lastaccessdate

Lastaccessedby

Lastchangedate

Owner

Sizeunit

IPX X Nodeid

XX Ipxaddress

XX Networknumber

Path

Frametype

Linkspeed

Maxpascketsize

Image Device X Nodeid

XX Devicetype

XX Makemodel

XX Manufacturer

XX Name

Alias

Assettag

Colordepthbit

Copycapable

Currentram

Description

Faxcapable

Horizontaldpi

Interface

Maxlength

Maxram

Maxwidth


Class NameProperty

.Key Name



Image Device

(continued)

Numberoftrays

Printcapable

Ramunit

Scancapable

Serialnumber

Sizeunit

Verticaldpi

Logical Drive X Nodeid

XX Drivetype

XX Mount

Attachednetname

Availablesize

Compressed

Description

Encrypted

Filesystem

Sizeunit

Totalsize

Volumelabel

Media Adapter X Nodeid

XX Makemodel

XX Manufacturer

XX Mediatype

XX Serialnumber

Assettag

Bustype

Chipset

Description

Memorytype

Ramsize

Ramunit

Network Adapter X Nodeid

XX Adapterytpe

XX Makemodel

XX Manufacturer

XX Netmacaddr1

XX Netmacaddr2

Assettag


Class NameProperty

.Key Name



Network Adapter

(continued)

Bandwidth

Bandwidthunit

Chipset

Description

Firmwareversion

Port

Protocol

Serialnumber

Operating System X Nodeid

XX Build

XX Language Operating System.Locale

XX Manufacturer Operating System.Osname or

UNKNOWN

XX Name Operating System.Osname or

UNKNOWN

XX Servicepack

XX Version Operating System.Osversion

Description Operating System.Description

Licensedorg

Licesneduser

Serialnumber

Physical Disk X Nodeid

XX Disktype

XX Makemodel

XX Manufacturer

XX Serialnumber

XX Systemname

XX Totalspace

Assettag

Description

Diskinterface

Externaldevice

Hotswappable

Removablemedia

Sizeunit

Writecapable


Class NameProperty

.Key Name



Processor X Nodeid

XX Makemodel Computer.Cputype or

UNKNOWN

XX Manufacturer Computer.Cputype or

UNKNOWN

XX Serialnumber

Currspeed

Description (Computer.Cputype or "UNKNOWN") + Computer.Numcpus

Maxspeed Computer.Cpuspeed

Speedunit MHz or

GHz

Software X Nodeid

XX Installpath Case 0Software Installed.Installedlocation

XX Language

XX Manufacturer Case 0Software Installed.Manufacturername or

UNKNOWN

Case 1Software Component.Publisher or

UNKNOWN

Case 2Software Component.Publisher or

UNKNOWN

XX Softwarename Case 0Software Installed.Productname or

UNKNOWN

Case 1Software Component.Name or

UNKNOWN

Case 2Software Patch.Name or

UNKNOWN


Class NameProperty

.Key Name



Software

(continued)

XX Version Case 0Software Installed.Versionstring

Case 1Software Component.Softwareversion

Case 2Software Patch.Version

Description Case 0Software.Installed.Description

Case 1Software Component.Description

Installdate Case 1Software Component.Installeddate

Lastusagedate

Licensedorg

Licenseduser

Productid Case 0Software Installed.Productid

Serialnumber

Suiteid

Type

Usagecount

TCP/IP X Nodeid

XX Gateway UNKNOWN

XX Host System.Name or

System.Fqdn

XX Tcpipaddress TCP IP.Dotnotation

Dhcpserver

Dnsserver1

Dnsserver2

Dnsserver3

Primarywins

Secondarywins

Tcpipdomain System.Fqdn

Tcpipnetmask TCP IP.Netmask

User X Nodeid

XX Firstname

XX Lastname

XX Personnelnumber

Assettag


Class NameProperty

.Key Name



User

(continued)

Building

Department

Facility

Floor

Glaccount

Jobtitle

Room

Workemail

Workphone

Network Device X Nodeid

XX Netmacaddr System.Primaryaddress or

"UNKNOWN"

XX Networkaddress Network Device.Dotnotation or

"UNKNOWN"

Firmwareversion

Osversion

Ramsize

Ramunit

Network Card X Nodeid

XX Netmacaddr

XX Networkaddress

XX Serialnumber

XX Type

Assettag

Bandwidth

Bandwidthunit

Chipset

Description

Firmwareversion

Makemodel

Manufacturer

Ramsize

Ramunit

Network Printer X Nodeid

XX Netmacaddr System.Primarymacaddress

XX Networkaddress Network Device.Dotnotation

Colordepthbit

Currentram


Class NameProperty

.Key Name



Network Printer

(continued)

Horizontaldpi

Maxlength

Maxram

Maxwidth

Numberoftrays

Ramunit

Sizeunit

Verticaldpi


Class NameProperty

.Key Name


Copyright IBM Corp. 2007 Notices-1

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those

Notices-2 IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

AIX, IBM, IBM Corporation, the IBM logo, Tivoli, and WebSphere are registered trademarks of the International Business Machines Corporation in the United States, other countries, or both.

Intel, the Intel logo, and Pentium are registered trademarks of the Intel Corporation in the United States, other countries, or both.

Microsoft, Windows, and Internet Explorer are registered trademarks of Microsoft Corporation in the United States, other countries, or both.

Notices-3

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Sun, Sun Microsystems, the Sun logo, and Solaris are trademarks of Sun Microsystems, Inc.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

Notices-4 IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

IBM Maximo Integration Adapter for Tivoli Application Dependency Discover Manager Implementation GuideContentsAbout This GuideAudienceRelated DocumentationSupport

Chapter 1: IBM Maximo Integration Adapter OverviewMaximo Product Versions SupportedAsset Discovery Tool SupportedIntegration Composer ComponentsIntegration Composer File StructureOptional IBM Maximo Integration AdaptersContents of the Adapter CD-ROMTADDM Adapter Checklist

Chapter 2: Setting Up the Integration Adapter for TADDMBefore You BeginAdding Adapter Components to Integration ComposerInstalling the TADDM Data SchemaSetting Up the TADDM-to-Maximo AdapterDefining a Data Source Connection to MaximoCreating the TADDM-to-Maximo Mapping

Chapter 3: Creating Effective MappingsMapping Data for Sites and OrganizationsMapping Data for Conversion ApplicationsMapping Key PropertiesMapping Data for FilesMapping Data for Scan Dates

Chapter 4: Integration Adapter Mapping for TADDMNotices

Date post:	18-Sep-2015
Category:	Documents
Upload:	komple
View:	38 times
Download:	0 times

621 Mx Integ Adapter Taddm

Documents