IBM Maximo Integration Adapter For Tivoli

IBM Maximo IntegrationAdapter Overview1The IBM Maximo Integration Composer (Integration Composer) is anintegration tool that you can use to import information technology (IT) assetdata into IBM Maximo for Asset Management. To gather deployed asset data,an asset discovery tool, such as IBM Tivoli Application Dependency DiscoveryManager (TADDM), scans computers, network devices, and network printersdeployed in an enterprise and records information about the hardware andsoftware installed on those assets. The Integration Composer transforms thecollected data and imports it into Maximo.Before you migrate data from an external data source into Maximo, you usethe Integration Composer to map data from the source format to the targetMaximo format. A mapping is a set of expressions that tells the IntegrationComposer how to create data in Maximo using information from a source. Foreach property that you want to import, you define an expression that specifieshow to transform the data for that property when the Integration Composerimports the data from the source into Maximo.To facilitate data migration, the IBM Maximo Integration Adapter forTADDM provides a set of pre-defined mapping expressions designed totransform data in the TADDM data source to the format required by thedeployed assets tables in the Maximo database. You can import this mappinginto the Integration Composer and with little or no additional programmingexecute a mapping to import TADDM data into Maximo.Maximo Product Versions SupportedIBM MaximoThis integration adapter requires Maximo 6.2.1 or later.IBM Maximo IntegrationComposerTo use the IBM Maximo Integration Adapter for TADDM, you must installIntegration Composer 6.2.1, or later. For information about the minimumhardware and software requirements for the Integration Composer, refer tothe IBM Maximo Integration Composer Installation Guide for Windows orIBM Maximo Integration Composer Installation Guide for UNIX.Asset Discovery Tool SupportedYou can use this IBM Maximo integration adapter with IBM TivoliApplication Dependency Discovery Manager 5.1.1 FP1 and CCMDB 1.1.1 FP1. Copyright IBM Corp. 20071-1

Integration Composer ComponentsIntegration Composer ComponentsThis section provides an overview of the Integration Composer components.For more detailed information, refer to the IBM Maximo Integration ComposerSystem Administrator’s Guide. The Integration Composer includes thefollowing components:Integration Composer applicationIntegration Composer engine! JDBC drivers! Integration Composer repository!!Integration ComposerApplicationThe Integration Composer application has a Windows-based graphical userinterface (GUI) that lets you define data sources, browse data source data,define data schemas, and create mappings to transform and migrate data.Integration ComposerEngineThe Integration Composer engine processes mapping expressions thattransform data from a source data source and integrate it into the targetMaximo data source. You can execute the mapping directly from theIntegration Composer application or as a stand-alone process running from acommand line.NOTEJDBC DriversThe Integration Composer uses JDBC drivers to establish connectionsbetween a source data source and a target data source. IBM Corporationprovides the following JDBC drivers with the Integration Composer:!!!Integration ComposerRepositoryFor performance reasons, it is more efficient to run mappings as astand-alone process executed from a command line.IBM DB2 JDBC driver.i-net OPTA JDBC driver for Microsoft SQL Server 7/2000 and SQLServer 2005.Oracle JDBC Thin driver. This driver supports Oracle 10g and earlierversions (including 8.0, 8i, and 9i).The Integration Composer repository resides in the Maximo database andcontains the following Integration Composer data:!Metadata for read-only data schemas delivered with the IntegrationComposer. This metadata defines the structure of the data.In addition to metadata, the Integration Composer repository stores otherinformation about mapping execution parameters for the data schema.This information includes caching mechanism, inventory hardware lastscan class and property names, software last scan class and propertynames (optional), and so forth. Users cannot modify this information; it isset when data schemas are created in the Integration Composer or whenyou import a data schema into the Integration Composer.1-2!Metadata for data schemas that users create in the Integration Composer.!Data source definitions that provide database connection parameters.IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

Integration Composer File Structure!Mappings that define how to transform data instances and migrate themfrom a source to a target.!If a last scan time stamp exists, the Integration Composer stores the mostrecent last scan time stamp for every source IT asset in the IntegrationComposer repository.Integration Composer File StructureWhen you install the Integration Composer, if you accept the defaultinstallation path, the installation program installs the application in theMaximo Fusion directory.At this location, the installation program sets up the following file structurefor the Integration Composer:Integration Composer File StructureeNOTESome installations might include an icons folder. This folder isobsolete.If you select a different location when you install the Integration Composer,the installation program creates the same file structure in the location thatyou specify.IBM Maximo Integration Adapter Overview1-3

Integration Composer File StructureThe Integration Composer folders store the following data:FolderDescriptionbinStores the following batch files:data1-4!commandLine.bat – batch file that executes anIntegration Composer mapping from acommand line.!init.bat – batch file used to define andinitialize the Integration Composerenvironment.!startFusion.bat – batch file that launches theIntegration Composer.Stores the following folders:!dataschema – stores data schemas that usersexport from the Integration Composer or thatusers copy to this folder from other sources,such as an IBM Maximo integration adapter.!mappings – stores mappings that usersexport from the Integration Composer or thatusers copy to this folder from other sources,such as an IBM Maximo integration adapter.!properties – contains specialized applicationproperties files. The provider sub-folder alsoincludes specialized application propertiesfiles.genrulesStores Java source files that the IntegrationComposer creates when you execute a mapping.Do not modify any files in this folder.helpStores the Integration Composer online help files.Do not modify any files in this folder.libStores third-party Java application programinterfaces (APIs) that the Integration Composeruses, including JDBC drivers.logStores the Integration Composer log files.PowerUpdateClientStores files that PowerUpdate uses to check forupdates to the Integration Composer. Do notmodify any files in this folder.Uninstall IntegrationComposerStores the files that uninstall the IntegrationComposer from your computer. Do not modify anyfiles in this folder.IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

Optional IBM Maximo Integration AdaptersOptional IBM Maximo Integration AdaptersIn addition to this IBM Maximo Integration Adapter for TADDM, IBMCorporation 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 PackardConfiguration 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 SMSContents of the Adapter CD-ROMThe CD-ROM for the IBM Maximo Integration Adapter for TADDM containsthe following files:!TADDM.schm – This data schema file defines the structure fororganizing and classifying data in the IBM Tivoli Application DependencyDiscovery Manager data source.!TADDM11toDPA62.fsn – This mapping file provides predefinedexpressions you can use to transform data from IBM Tivoli ApplicationDependency Discovery Manager formats to Maximo Deployed Assetsformats.!621 mx integ adapter taddm.pdf – The IBM Maximo IntegrationAdapter for IBM Tivoli Application Dependency Discovery ManagerImplementation Guide is provided in Adobe Systems’ Portable DocumentFormat (PDF).IBM Maximo Integration Adapter Overview1-5

TADDM Adapter ChecklistTADDM Adapter ChecklistThe following checklist summarizes how to install and use the IBM MaximoIntegration Adapter for IBM Tivoli Application Dependency DiscoveryManager.Adding TADDM Components to Integration Composer[ ]1 Add adapter componentsto Integration Composer.Copy the following files, which are provided with the IBM MaximoIntegration Adapter for IBM Tivoli Application Dependency DiscoveryManager, to the appropriate location in the Integration Composerinstallation directory:!!TADDM11toDPA62.fsnTADDM.schmFor instructions about how to complete these steps, see "AddingAdapter Components to Integration Composer," on page 2-1.Setting Up the TADDM Adapter in Integration Composer[ ]2 Install the TADDM dataschema.Open the Integration Composer and complete the following tasks toinstall 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 theTADDM Data Schema," on page 2-2.[ ]3 Define a data sourceconnection for the targetMaximo data source.In the Integration Composer, set up a data source connection for thetarget data source, which is Maximo deployed assets.When you create an adapter mapping, you must have a data sourceconnection defined for both the target data source and the source datasource. You defined a data source for the source TADDM data sourcein step 2 when you installed the data schema.For instructions about how to complete these steps, see "Setting Upthe TADDM-to-Maximo Adapter," on page 2-9.[ ]4 Create a TADDM-toMaximo mapping.In the Integration Composer, create a new mapping for TADDM toMaximo deployed assets and import the mapping file provided withthis adapter (TADDM11toDPA62.fsn) into the new mapping youcreate.For instructions about how to complete these steps, see "Setting Upthe TADDM-to-Maximo Adapter," on page 2-13.[ ]5 Modify the mapping asrequired.If appropriate, in the TADDM-to-Maximo mapping you create, modifymapping expressions to suit your business needs.For instructions about how to modify mapping expressions, see theIBM Maximo Integration Composer System Administrator’s Guide.Importing TADDM data into Maximo[ ]6 Import TADDM datainto Maximo.To import TADDM data into Maximo, execute the TADDM-to-Maximomapping.For instructions about how to execute mappings, see the IBM MaximoIntegration Composer System Administrator’s Guide.1-6IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

Setting Up the IntegrationAdapter for TADDM2This chapter explains how to install the components of the IBM MaximoIntegration Adapter for TADDM. It also tells you how to create a mappingthat you can use to import the deployed asset data gathered by TADDM intothe Maximo deployed assets database tables.Before You BeginBefore 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 release6.2.1 or later.3 Copy the files provided with the integration adapter to a convenientdirectory, for example C:\temp.4 If the Integration Composer is running, close all open windows and exitthe application.5 If you have any data in your Maximo database, back up the database.Adding Adapter Components to Integration ComposerBefore you can use the integration adapter, you must copy the following filesto the appropriate folders in the Integration Composer installation directory:!!TADDM11toDPA62.fsnTADDM.schmTo add TADDM adapter components to Integration Composer, complete thefollowing steps:1 From the temporary location where you saved the TADDM integrationadapter components, copy the TADDM11toDPA62.fsn mapping file tothe following location: installDir \data\mappingsNOTE Copyright IBM Corp. 2007You can put the file in a different location; however, when youimport the file into the Integration Composer, by default the2-1

Installing the TADDM Data SchemaIntegration Composer selects the mappings folder. If you put thefile in a different location, you have to browse to that location andselect the file.2 From the temporary location where you saved the TADDM integrationadapter components, copy the TADDM.schm data schema file to thefollowing location: installDir \data\dataschemaAfter you add the file to the Integration Composer installation directory,you can use the Integration Composer application to import it into aTADDM data schema.Installing the TADDM Data SchemaBefore you can use the integration adapter to create a mapping and migrateTADDM data, you must install the TADDM data schema in the IntegrationComposer repository. This section explains how to define a TADDM dataschema in Integration Composer and then import the data schema fileprovided with the integration adapter into it.Defining the Data SchemaWhen you define a data schema, you name the data schema, define a datasource, and specify connection parameters for the data source. After youdefine data source connection parameters, the Integration Composer storesthe connection information and displays those parameters when you attemptto connect to the data source. The only parameter the Integration Composerrequests is the password.After you define a new data schema, the Integration Composer displays theData Schema window. From this window, you can import the TADDM.schmfile 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 aNew Data Schema window, as shown in the following figure.2-2IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

Installing the TADDM Data SchemaDefine a New Data Schema Window – Data Schema PageNOTENaming the Data SchemaIn the Define a New Data Source window, you can click Back toreview or change previous selections. To cancel this procedure andreturn to the IBM Maximo Integration Composer window, clickCancel.2 In the Data Schema field on the Data Schema page, enter the name ofthe data schema, then click Next. The Integration Composer displays theData Source page, as shown in the following figure.Define a New Data Schema Window – Data Source PageDefining the Data Source3 In the Data Source field, enter a name for the data source (the namemust have at least two characters), then click Next. The IntegrationSetting Up the Integration Adapter for TADDM2-3

Installing the TADDM Data SchemaComposer displays the Connection Information page, as shown in thefollowing figure.Define a New Data Schema Window – Connection Information PageSetting Up ConnectionParameters4 On the Connection Information page, in the JDBC Driver field, select adriver.5 Enter the parameters for the driver as required. The fields displayeddepend upon the type of driver selected. The following table lists some ofthe fields the Integration Composer might display.FieldDescriptionHost NameSpecifies the host name for the data source.Host PortSpecifies the port for the data source.Host SIDSession identifier for the host (that is, the databaseinstance name).DatabaseDatabase name for the data source.User NameDatabase user name for the data source.PasswordDatabase password for the data source.TableOwnerSpecifies a data schema name or database schemaowner.URLSpecifies the URL address to access a databaseinstance.6 If appropriate, to test the connection to the data source, click TestConnection. The Integration Composer displays a Test Connection dialogbox. 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:2-4IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

Installing the TADDM Data Schema!If the Integration Composer cannot establish a connection, it displaysan explanatory message. Click OK. The Integration Composer closesthe Test Connection dialog box. Review the values for the connectionparameters and retry the connection.!If the Integration Composer establishes a connection, it displays aconfirmation message. Click OK. The Integration Composer closes theTest Connection dialog box.NOTEThe Test Connection feature lets you test only the connectionwithout invoking any additional Integration Composer processes.JDBC drivers that are not JDBC 2.0 compliant might not supportthis feature.7 On the Connection Information page, click Finish. The IntegrationComposer displays the Data Schema window, as shown in the followingfigure. The Integration Composer displays the root class in red because noproperties are associated with the class.NOTEThe display properties you set for your computer might affectcolors. The color displayed on your computer might vary.Sample Data Schema Window Showing Root ClassImporting the Data Schema8 To import the data schema provided with the TADDM integration adapter,from the Select Action menu in the Data Schema window, select ImportSetting Up the Integration Adapter for TADDM2-5

Installing the TADDM Data SchemaData Schema. The Integration Composer displays the Import DataSchema dialog box, as shown in the following figure.Import Data Schema Dialog BoxThe Import Data Schema dialog box lists the data schemas you copied tothe custom data schemas folder.The dialog box includes the following buttons:ButtonDescriptionNavigates to the folder one level higher than the currentfolder.Creates a new folder in the selected folder.Displays large icons for sub-folders and files in theselected folder.Displays details for sub-folders and files in the selectedfolder.Imports the data schema into the Integration Composer.Cancels the import action.9 In the Import Data Schema dialog box, select the data schema file toimport. The Integration Composer populates the File name field with thefile's name.Fixing Errors2-610 Click Open. The Integration Composer imports the data schema. Ifdiscrepancies exist between the data source and the data schema, theIntegration Composer displays the Data Schema Analysis window, asshown in the following figure.IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide

Installing the TADDM Data SchemaData Schema Analysis WindowThis window lists discrepancies the Integration Composer found betweenthe data schema and the corresponding data source. You can use thiswindow to correct the following discrepancies:!Case of a table name in the database does not match that of a tableassociated with a class in the data schema.!Case of a column name in the database does not match that of a tablecolumn associated with a class table in the data schema.!Length of a table column in the database does not match length of thesame column in the data schema.!Data type of a table column in the database does not match the type ofthe same column in the data schema.The Data Schema Analysis window includes the following buttons:ButtonDesc

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 info rmation, refer to the IBM Maximo Integration Composer System Administrator s Guide. The Integration .