IBM Maximo Product Extensionpublib.boulder.ibm.com/tividd/td/ITMProdE/621_mpe_itsm...IBM Maximo...

Release 6

Implementation GuideIT Asset Initialization for ITSM

IBM Maximo Product Extension

Second Edition (January 2007)This edition applies to Release 6.2.1 of the IBM Maximo Product Extension for IT Asset Initialization for ITSM 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 Contract with IBM Corp.

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: IT Asset Initialization Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1IBM Maximo Integration Composer Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Asset Discovery Tools Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Integration Composer Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Integration Composer File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6IT Asset Initialization Product Extension Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7IT Asset Initialization Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Chapter 2: Installing the IT Asset Initialization Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Adding the Mapping File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Adding and Configuring the maximoassets.properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Adding and Configuring the assetinit.properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Adding Data Schema Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Chapter 3: Creating IT Asset Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Creating Data Source Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Creating a Connection to the Deployed Assets Source Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Creating a Connection to the Maximo IT Assets Target Data Source . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Creating the Deployed Assets to IT Assets Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Mapping Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Viewing Mapping Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

Executing the IT Asset Initialization Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21Executing a Mapping Using the Integration Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21Executing a Mapping from a Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Chapter 4: Deployed Assets to IT Assets Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

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

Contents

iv IBM Maximo Product Extension: Implementation Guide

© Copyright IBM Corp. 2007 v

About This Guide

This section explains how this guide can help you to use the Information Technology and Service Management (ITSM) IT Asset Initialization product extension for IBM® Maximo®. It also provides information about other IBM Corporation resources available to you, such as additional documentation and support.

Audience

Use this guide if you have installed ITSM Release 4 for Maximo. This guide is for the system administrator or other professional who is responsible for creating IT asset records in Maximo from deployed asset data collected by an asset discovery tool.

Related Documentation

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

Document Description

IBM Maximo Finance Manager�s Guide

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

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

! Application server! IBM Maximo! Actuate®

IBM Maximo Multisite Administrator�s Guide

Describes how to configure IBM Maximo for a Multisite implementation.

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

IBM Maximo Reconciliation 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.

Related Documentation

vi IBM Maximo Product Extension: Implementation Guide

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

IBM Maximo Report Administration and Development Guide

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

IBM Maximo System Administrator�s Guide

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

IBM Maximo User�s Guide Provides an overview of the 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 Administrator�s Guide

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

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

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 Adapter Implementation Guide

Describes how to install and configure adapters purchased for the Integration Composer. IBM Corporation provides adapter implementation guides for the following products:

! Altiris® Inventory Solution®

! Centennial Discovery®

! HP Configuration Management (CM) Inventory Manager

! IBM Tivoli® Configuration Manager

! Maximo MainControl® i.collect�

! Maximo Discovery®

! Microsoft SMS


http://support.mro.com

Support

viii IBM Maximo Product Extension: Implementation Guide

© Copyright IBM Corp. 2007 1-1

IT Asset Initialization for Information Technology and Service Management (ITSM) is an IBM Maximo Product Extension that lets you use deployed asset data in Maximo to create IT asset records in IBM Maximo. Deployed asset data is information you collect from computers, printers, and network devices in your enterprise.

Using deployed asset data to create IT asset records efficiently lets you create IT asset records when you first implement IT asset management in Maximo. To collect deployed asset data, you can use IBM Tivoli Configuration Manager or another asset discovery tool, such as Altiris Inventory Solution. Asset discovery tools scan systems and networks to collect information about hardware and software.

After you collect data about deployed assets, you use the IBM Maximo Integration Composer (formerly Maximo Fusion) to import the data into Maximo. You can then view the information in the Computers, Printers, and Network Devices applications in the Deployed Assets module in Maximo.

With this product extension, you also use the Integration Composer to create IT asset records from the deployed asset data that you collected and imported into Maximo. You should use this product extension only if you have installed ITSM Release 4 for Maximo. To facilitate data migration, this product extension provides a mapping for creating IT asset records. When you use this mapping to create asset records, it creates software as spare parts. The spare parts records are associated with a parent IT asset record.

Use this IT Asset Initialization product extension only to create new assets. Do not use the processes described in this guide to update existing assets.

IT Asset Initialization Overview 1

IBM Maximo Integration Composer Overview

1-2 IBM Maximo Product Extension: Implementation Guide


The IBM Maximo Integration Composer is an integration tool that lets you import data from an external source into Maximo. You can use the Integration Composer to transform data collected by asset discovery tools and integrate the data into Maximo, creating a central repository for enterprise IT asset management, reporting, and decision support.

Asset Discovery Tools Supported

The Integration Composer supports the following asset discovery tools:

! Altiris Inventory Solution

! Centennial Discovery

! HP Configuration Management (CM) Inventory Manager(formerly, Hewlett Packard Inventory Manager using Radia®)

! IBM Tivoli Configuration Manager

! Maximo Discovery

! Microsoft SMS

! Maximo MainControl i.collect

To facilitate data migration, IBM Corporation offers optional IBM Maximo integration adapters to transform and import data that these asset discovery tools collect.

You can use the Create Data Schema feature in the Integration Composer to create data schemas that let you integrate data from other asset discovery tools. The structure of your database might limit your ability to use this feature.

Integration Composer Components

The Integration Composer integration tool 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 user interface 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 the source data source and integrate it into a target data source.


IT Asset Initialization Overview 1-3

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 Microsoft 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. The repository contains data schemas for the following products:

! Altiris Inventory Solution! Centennial Discovery! HP Configuration Management (CM) Inventory Manager! IBM Tivoli Configuration Manager! Maximo Deployed Assets! Maximo Discovery! Microsoft SMS! Maximo MainControl i.collect

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

! Data source definitions that provide database connection parameters.

! Mappings that define how to transform data and migrate it 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.



Integration Composer File Structure

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

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

Integration Composer File Structure

e

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

If you select a different location for the Integration Composer, the installer 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 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.

Folder Description

Software Requirements


Software Requirements

The IT Asset Initialization for ITSM product extension requires the following software:

! IBM Maximo 6.2.1 or later with the ITSM product extension applied.

! 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 UNIX or the IBM Maximo Integration Composer Installation Guide for Microsoft Windows.

! An asset discovery tool that collects data about hardware and software on systems and networks, for example, IBM Tivoli Configuration Manager.

IT Asset Initialization Product Extension Components

The IT Asset Initialization product extension contains the following components:

Component Description

maximoassets.properties File that defines the hierarchical structure and class names for the Maximo Assets 6.x data schema. It also associates class structure identifiers to the defined classes.

assetinit.properties File that defines global values for asset initialization properties.

createMaximoAssets6xDataSchema.db2 DB2 database script that loads the Maximo Assets 6.x data schema into the Integration Composer repository.

createMaximoAssets6xDataSchema.ora Oracle database script that loads the Maximo Assets 6.x data schema into the Integration Composer repository.

createMaximoAssets6xDataSchema.sqs SQL database script that loads the Maximo Assets 6.x data schema into the Integration Composer repository.

createSourceDPADataSchema.db2 DB2 database script that loads the Source�Maximo Deployed Assets data schema into the Integration Composer repository.

createSourceDpaDataSchema.ora Oracle database script that loads the Source�Maximo Deployed Assets data schema into the Integration Composer repository.

createSourceDpaDataSchema.sqs Microsoft SQL Server database script that loads the Source�Maximo Deployed Assets data schema into the Integration Composer repository.

SourceDPAtoAssetsWithITSME6x.fsn Mapping file that contains predefined expressions you can use to create IT asset records from deployed asset data.

621_mpe_itsm_it_asset_init.pdf IBM Maximo IT Asset Initialization for ITSM Implementation Guide in Adobe® Systems� Portable Document Format (PDF).

Prerequisites


Prerequisites

Before you can use the IT Asset Initialization product extension, you must perform the following tasks:

1 Install the ITSM product extension for Maximo.

1 Set up UNSPSC or customer-defined classifications in Maximo. Use the Maximo Classifications application to create classifications, or load classifications from an external source. For more information about creating classifications, refer to Maximo Online Help or the IBM Maximo User�s Guide.

2 Set up item records in Maximo. Use the Maximo Item Master application to create item records that have classifications, or load items from an external source. For more information about creating items, refer to Maximo Online Help or the IBM Maximo User�s Guide.

3 Set up standard software naming conventions in Maximo. Use the MEA Interface for Deployed Asset Conversion Data, or use the Software Conversion and Software Suite Setup applications in the Maximo Deployed Assets Administration module. For more information about using these applications, refer to Maximo Online Help or the IBM Maximo User�s Guide.

4 Using an asset discovery tool, scan your network and create a database of hardware and software information.

5 Install and configure the Integration Composer. For more information about installing the Integration Composer, refer to the IBM Maximo Integration Composer Installation Guide for Windows or the IBM Maximo Integration Composer Installation Guide for UNIX.

6 Use the Integration Composer to import deployed asset data into Maximo. For more information about importing deployed asset data into Maximo, refer to the IBM Maximo Integration Composer System Administrator�s Guide. If you purchased an IBM Maximo integration adapter for a specific asset discovery tool, you can find information about using the adapter to import data in the IBM Maximo Integration Adapter Implementation Guide for the specific discovery tool.

7 In Maximo, review the records the Integration Composer added to the Software Conversion and Software Suite Setup applications. For information about reviewing these records, refer to Maximo Online Help or the IBM Maximo System Administrator�s Guide.

After you complete the preceding steps, you can set up the IT Asset Initialization product extension in the Integration Composer and use the Integration Composer to create IT asset records in Maximo.

IT Asset Initialization Checklists



The following checklists provide an overview of how to install and use the IT Asset Initialization product extension. You will find detailed instructions in subsequent chapters of this guide.

Install IT Asset Initialization Components

[ ] 1 Copy the following components, which are included in the IT Asset Initialization product extension, to the appropriate location in the Integration Composer installation directory:

! createMaximoAssets6xDataSchema.db2! createMaximoAssets6xDataSchema.ora! createMaximoAssets6xDataSchema.sqs! createSourceDPADataSchema.db2! createSourceDpaDataSchema.ora! createSourceDpaDataSchema.sqs! maximoassets.properties file! assetinit.properties file! IT Asset Initialization mapping for Spare Parts

(SourceDPAtoAssetsWithITSME6x.fsn)

[ ] 2 Use the appropriate utility to execute either the DB2, Oracle, or SQL database scripts, which add the Source�Maximo Deployed Assets and Maximo Assets 6.x data schemas to the Integration Composer repository in the Maximo database.

[ ] 3 Configure the maximoassets.properties file with your enterprise�s asset classifications.

[ ] 4 Configure the assetinit.properties files.

Use the Integration Composer to Create IT Asset Records

[ ] 1 Sign in to the Integration Composer and set up data source connections for both the deployed assets source data source and the Maximo IT assets target data source.

[ ] 2 In the Integration Composer, perform the following tasks:

! Create a new mapping for deployed assets to IT assets.

! Import the IT Asset Initialization mapping for Spare Parts (SourceDPAtoAssetsWithITSME6x.fsn).

! Save the mapping.

[ ] 3 In the deployed assets to Maximo IT assets mapping that you create, modify mapping expressions for the following properties:

! itemnum! classstructureid! status! asset specification properties! software (applies only if you use the IT Asset and Service

Management Product Extension)



[ ] 4 Execute the deployed assets to Maximo IT assets mapping to create IT asset records.

If you execute mappings as a stand-alone process from a command line, you must update your batch file with the new mapping information before you execute the mapping. The batch file is in the following location:

<installDir>\bin\commandLine.bat


IBM Corporation provides the following components for the IT Asset Initialization product extension:

! SourceDPAtoAssetsWithITSME6x.fsn! maximoassets.properties! assetinit.properties! createMaximoAssets6xDataSchema.db2 (for IBM DB2 databases)! createMaximoAssets6xDataSchema.ora (for Oracle databases)! createMaximoAssets6xDataSchema.sqs (for Microsoft SQL Server

databases)! createSourceDPADataSchema.db2 (for IBM DB2 databases)! createSourceDpaDataSchema.ora (for Oracle databases)! createSourceDpaDataSchema.sqs (for Microsoft SQL Server

databases)

This chapter describes how to install the components in the Maximo database and in the Integration Composer.

Before You Begin

Before you install the components, perform the following steps:

1 Verify that you have installed Maximo 6.2.1 or later and have applied the ITSM product extension.

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

3 Copy the files provided with the IT Asset Initialization product extension to a convenient directory, for example C:\temp.

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

Installing the IT Asset Initialization Components 2

Adding the Mapping File


Adding the Mapping File

The IT Asset Initialization product extension provides a mapping file (SourceDPAtoAssetsWithITSME6x.fsn) with predefined expressions that tell the Integration Composer how to create IT asset records from deployed asset data.

The following procedure explains how to add the mapping file to the Integration Composer directory. After you add the file to the Integration Composer, you can import it into the Deployed Assets to Maximo IT Assets mapping. For more information about importing the mapping, see Chapter 3, "Creating IT Asset Records," on page 3-1.

To add the mapping files to the Integration Composer, perform the following procedure:

! From the temporary location where you saved the IT Asset Initialization components, copy the SourceDPAtoAssetsWithITSME6x.fsn file to the following location:

<installDir>\data\mappings

NOTE You can put the file in a different location. However, when you import a file into a mapping, the Integration Composer selects the mappings folder as a default location. If you copy the .fsn file to a different location, you must browse to that location and select the desired file.

Adding and Configuring the maximoassets.properties File

Installing the IT Asset Initialization Components 2-3


The IT Asset Initialization product extension provides a provider properties file (maximoassets.properties) for Maximo assets, as illustrated in the following figure. The Integration Composer uses this file to define the hierarchical structure and class names for the Maximo Assets 6.x data schema. The properties file also associates Maximo class structure IDs to the defined classes.

Maximo Assets Properties File

The maximoassets.properties file specifies a hierarchy with three levels of classes and the following class names:

For each class below the root class, the properties file lists the class structure IDs associated with the class. For example, Computer has the following class structure IDs: 1221, 1210, 1223.

# root class nameroot.classname=IT Asset

# level 1 classes names level1.classnames=Computer,Network Device,Network Printer

# level2.[level 1 class name no space].classnames - level 2 classes names (if exist)level2.Computer.classnames=Disk,Software,Operating System,Network Card,Display,Printerlevel2.NetworkDevice.classnames=Network Device Card

# [class name no space].classstructureids - the class structure ids for every classComputer.classstructureids=1221,1210,1223NetworkDevice.classstructureids=1035NetworkPrinter.classstructureids=1050Disk.classstructureids=1240Display.classstructureids=1218NetworkCard.classstructureids=1243OperatingSystem.classstructureids=1229Printer.classstructureids=1234Software.classstructureids=1216,1229,1231,1232NetworkDeviceCard.classstructureids=1002

Class Level Class Name(s)

root class IT Asset

level 1 class Computer, Network Device, Network Printer

level 2 class For Computers:

Disk, Software, Operating System, Network Card, Display, Printer

For Network Devices:

Network Device Card



Configuring the Provider To configure the provider, complete the following steps:

1 Copy the maximoassets.properties file to the provider folder in the Integration Composer installation directory.

2 Configure the file to add the class names and class structure IDs used in your enterprise.

The following rules apply to class names:

! You must make each class name unique.

! You cannot use null values for a class name.

! You must specify at least one classstructureid for each class name specified.

To add and configure the maximoassets.properties file, complete the following steps:

1 Copy the maximoassets.properties file from the temporary location where you stored the IT Asset Initialization components to the following location:

<installDir>\data\properties\provider

2 Open the maximoassets.properties file you copied to the provider directory in a text editor, such as Notepad.

3 For the root.classname property, type the name of your root class, as shown in the following example:

root.classname=IT Asset

where

IT Asset is the root class name.

4 For the level1.classnames property, type the name of the level 1 classes that you will use, as shown in the following example:

level1.classnames=Computer,Network Device,Network Printer

where

Computer, Network Device, and Network Printer are class names for level 1 classes.

5 For each level 1 property that will consist of level 2 classes, type the names of the level 2 classes that you will use, as shown in the following example:

level2.Computer.classnames=Disk,Software,Operating System,Network Card,Display,Printer

where

Disk, Software, Operating System, Network Card, Display, and Printer are class names for level 2 classes.

Adding and Configuring the assetinit.properties File


6 For each class that you added in steps 4 and 5, enter a classstructureid, as shown in the following example.

Computer.classstructureids=1221,1210,1223

NetworkDevice.classstructureids=1035

NetworkPrinter.classstructureids=1050

Disk.classstructureids=1240

7 After you enter all classes and classstructureid�s, save the properties file and close it. Configuration of the properties file is complete.

Adding and Configuring the assetinit.properties File

The IT Asset Initialization product extension provides a properties file (assetinit.properties) for asset initialization, as illustrated in the following figure. The Integration Composer uses this file to define values for properties that are used in many places in the mapping.

assetinit.properties File

The assetinit.properties file includes four properties:

To add and configure the assetinit.properties file, complete the following steps:

1 Copy the assetinit.properties file from the temporary location where you stored the IT Asset Initialization components to the following location:

<installDir>\data\properties

2 Open the assetinit.properties file you copied to the properties directory in a text editor, such as Notepad.

Property Description

assetinit_orgid Organization for the Maximo assets.

assetinit_siteid Site for the target Maximo assets.

assetinit_langcode Language for the target Maximo assets.

assetinit_itemset Set ID for the item set you create in the SETS table. All items migrated from deployed assets belong to this item set.

assetinit_orgid=EAGLENAassetinit_siteid=MCLEANassetinit_langcode=ENassetinit_itemset=SET1

Adding Data Schema Files


3 For each property, type the appropriate value, as shown in the following example:

assetinit_orgid=EAGLENA

where

EAGLENA is the organization ID.

4 After you enter all values, save the file and close it. Configuration of the assetinit.properties file is complete.


Before you can use the Integration Composer to create IT asset records, you must add the Source�Deployed Assets and the Maximo Assets 6.x data schemas to the Integration Composer repository in the Maximo database.

The IT Asset Initialization product extension provides scripts to let you add these data schemas. It includes the following scripts for IBM DB2, Oracle and Microsoft SQL Server databases:

IBM DB2

! createMaximoAssets6xDataSchema.db2! createSourceDPADataSchema.db2

Oracle

! createMaximoAssets6xDataSchema.ora! createSourceDpaDataSchema.ora

Microsoft SQL Server

! createMaximoAssets6xDataSchema.sqs! createSourceDpaDataSchema.sqs

Adding the Data Schemas To add the data schemas to the Integration Composer repository, complete the following steps:

1 If no database folder exists in the data folder in the Integration Composer installation directory, create a database folder in the following location:

<installDir>\data\database

2 Based on the type of database you use, copy the appropriate database scripts to the following location:

<installDir>\data\database

3 Using an appropriate database query tool, execute either the DB2, Oracle, or SQL database scripts.

4 Check for database script errors and resolve any errors.



5 If you have no errors, you now can define a data source for the deployed assets source database and the Maximo IT assets target database. You then can browse the data schemas, or you can create a new mapping and import the IT Asset Initialization mapping into the Integration Composer.

For information about browsing data schemas, refer to the IBM Maximo Integration Composer System Administrator�s Guide.

Chapter 3, �Creating IT Asset Records,� explains how to create data source connections and how to import the IT Asset Initialization mappings into the Integration Composer.


This chapter explains how to use the Integration Composer to create IT asset records in Maximo from deployed asset data in the Maximo deployed assets database tables. It explains how to define connections to your source and target databases, create a mapping, and execute the mapping to create IT asset records. It also explains how to modify expressions in the mapping.

Creating Data Source Connections

The Integration Composer uses JDBC drivers to connect to source and to target databases. Before you can import the mapping for asset initialization into the Integration Composer, you must define connections to the following locations:

! Deployed assets, which is your source data source! Maximo assets, which is your target data source.

To define the connections, use the Integration Composer application to define a data source for both the source and the target.

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.

Creating IT Asset Records 3



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

! Delete the open data source.

Creating a Connection to the Deployed Assets Source Data Source

To define a data source for the Maximo deployed assets source database, complete the following steps:

1 Sign in to the Integration Composer application.

2 In the IBM Maximo Integration Composer window, select Define New Data Source.

The Integration Composer displays the Data Schema page in the Define a New Data Source window. This page lists 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


Creating IT Asset Records 3-3

3 On the Data Schema page, select Source�Maximo Deployed Assets for the source data schema, and then 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, enter Deployed Assets Source and then 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 connection parameters for the driver as required.

The Integration Composer displays fields on this page based on the type of driver selected. The following table describes 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. Go to step 8.

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, 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 Host name for the Deployed Assets Source data source.

Host Port Port for the Deployed Assets Source data source.

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

Database Database name for the Deployed Assets Source data source.

User Name Database user name for the Deployed Assets Source data source.

Password Database password for the Deployed Assets Source data source.

Table Owner

Database schema name or database schema owner.

URL URL address to access a database instance.



Creating a Connection to the Maximo IT Assets Target Data Source

To define a data source for the Maximo IT assets target database, complete the following steps:

1 Sign in to the Integration Composer application.

2 In the IBM Maximo Integration Composer window, select Define New Data Source.

The Integration Composer displays the Data Schema page in the Define a New Data Source window. This page lists 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 Maximo Assets 6.x for the target data schema, and then 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, enter Maximo IT Assets Target 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 connection 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. Go to step 8.

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, 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 Host name for the Maximo IT Assets Target data source.

Host Port Port for the Maximo IT Assets Target data source.

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

Database Database name for the Maximo IT Assets Target data source.

User Name Database user name for the Maximo IT Assets Target data source.

Password Database password for the Maximo IT Assets Target data source.

Table Owner

Database schema name or database schema owner.

URL URL address to access a database instance.

Creating the Deployed Assets to IT Assets Mapping



Before you import deployed asset data into Maximo IT assets, you use the Integration Composer to create a deployed-assets-to-IT-assets mapping. The mapping is a set of Java programming expressions that tell the Integration Composer how to create IT asset records in Maximo using the deployed asset data.

After you create the mapping, you import the mapping provided in this IT Asset Initialization product extension. The extension�s mapping provides expressions that specify how to transform the data for a property when the Integration Composer imports the data from the deployed assets tables into IT assets. When you execute the mapping, the Integration Composer transforms the collected data and imports it into Maximo.

Mapping Overview To set up the deployed assets to Maximo IT assets mapping, perform the following tasks. Detailed instructions for these tasks are on page 3-9.

1 Create a new mapping. To create an Integration Composer mapping for IT asset initialization, you specify the following parameters:

! Source data source: Deployed Assets Source! Target data source: Maximo IT Assets Target! Mapping name: Deployed Assets to Maximo IT Assets

2 Import the IT Asset Initialization mapping (SourceDPAtoAssetsWithITSME6x.fsn) into the new mapping.

WARNING If you import a mapping into a mapping that contains expressions, 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.

3 Modify the mapping expressions for the following properties:

! itemnum property

The expressions for itemnum properties that the mapping for the IT Asset Initialization product extension provides do not include item numbers customized for your enterprise. You must define item numbers for computers and software classes.

To define item numbers, modify the itemnum property expressions so that the item numbers in the expressions match item numbers you use in your enterprise. Item numbers that you specify in the expression must be valid item numbers in Maximo.



! classstructureid property

The Integration Composer associates class structure IDs to your IT assets according to the item number(s) specified in the expression for the itemnum property. Consequently, you must modify the expression for the classstructureid property to include these items.

Make sure that each class structure ID you enter is also included in the maximoassets.properties file.

! status property

By default, the Integration Composer creates new IT asset records with a status of �NOT READY.� If you want to create IT asset records with a different status, you must modify the status property in your mapping. The status specified in the expression must be a valid LOCASSETSTATUS as defined in the Maximo SYNONYMDOMAIN table. For more information about SYNONYMDOMAINs, refer to the IBM Maximo System Administrator�s Guide.

! asset specification properties

You must map some properties, such as disk size, memory size, and processor speed, to system specification attributes. The mapping table in Chapter 4, �Deployed Assets to IT Assets Mapping�, on page 4-1 flags these properties with an asterisk.

! software items (spare parts) properties

You must modify the itemnum property for software items to include the appropriate item numbers for your software items. In addition, because the Integration Composer calculates the quantity of software items based on the item number specified in the expression for the itemnum property, you must modify the expression for the quantity property to include the same item number.

For more information about working with mappings and using the Mapping window features, refer to the IBM Maximo Integration Composer System Administrator�s Guide.

Mapping Procedure

To set up the IT asset initialization mapping, complete the following steps:

Create a New Mapping 1 Using a valid user ID and password, sign in to the Integration Composer. The Integration Composer displays the IBM Maximo Integration Composer window.

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 Deployed Assets Source.

4 From the Target drop-down list of existing and available data sources, select Maximo IT Assets Target.

5 In the Mapping Name field, enter Deployed Assets to Maximo IT Assets as the mapping name. Mapping names are case sensitive; for example, DEPLOYED ASSETS TO MAXIMO IT ASSETS is not the same as Deployed Assets to Maximo IT Assets.

6 Click OK.

If data sources are open for the source and target databases, the Integration Composer displays the Mapping window.

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

! If the Integration Composer displays the Connection Information page in the Open <source or target> Data Source window, complete the following steps to complete the connection information:

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

b Click Finish. The Integration Composer displays the Connection Information page in the Open Target Data Source window.

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

d Click Finish to establish the target�s connection. The Integration Composer displays the Deployed Assets Source and the Maximo IT Assets Target in the Mapping window.



Import the IT Asset Initialization 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:

SourceDPAtoAssetsWithITSME6x.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 in a different location, you can use the browse features in this window to locate the file. The .fsn extension identifies Integration Composer files.

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.



10 Click Open. The Integration Composer imports the mapping and displays it as shown in the following figure.

Deployed Assets to Maximo IT Assets Mapping

NOTE If any errors result from importing the mapping, the Integration Composer stops the import and displays a dialog box that lists the errors and asks 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. If errors exist, the Integration Composer displays errors in red. Resolve the errors before saving the mapping. You must resolve the errors before you can execute the mapping.

11 From the Select Action menu in the Mapping window, select Insert Only.

Because you use this product only to create new assets, you must select the Insert Only option so that Integration Composer only creates new assets when it imports data into Maximo and does not update existing assets.

NOTE The Insert Only feature works only on sources that contain a last scan date.



Review and Edit the Mapping

12 Review the mapping to verify that the expressions in the mapping will create IT asset records that meet your business requirements.

Because some property expressions must include values specific to your enterprise, you must evaluate them closely. Review the following properties:

! itemnum! classstructureid! status! asset specification properties! software items (spare parts) properties

Modify the itemnum Property

13 To modify the itemnum property for each class, complete the following steps:

a In the tree view in the Target pane, select the class whose itemnum you want to modify.

b In the table view in the Target pane, scroll to the itemnum property, as shown in the following figure.

itemnum Property in the Maximo IT Assets Target

c In the itemnum property row, double-click the cell in the Expression column. The Integration Composer displays the selected expression in the Expression Builder dialog box, as shown in the following example.



Sample Expression for itemnum Property in the Expression Builder Dialog Box

d For each asset class, specify the appropriate itemnum. For example, in the preceding figure, the expression specifies DT66 for DESKTOP, Network PC, Standalone PC, or PC.

NOTE Item numbers that you specify in the expression must be valid item numbers in Maximo.

TIP You can copy the item number specifications in the itemnum property and paste them into the classstructureid expression in step 14 on page 3-14. The itemnum expressions to copy are illustrated in bold text in the figure.

e After you modify the itemnum expression, click OK. The Integration Composer saves the modified expression and closes the Expression Builder dialog box.

Modify the classstructureid Property

14 To modify the classstructureid property, complete the following steps:

a In the tree view in the Target pane, select the class whose classstructureid you want to modify.

b In the table view in the Target pane, scroll to the classstructureid property, as shown in the following example.

{String itemnum = 'Deployed Asset.Systemrole';if(!isNull(itemnum)){ if(itemnum.equalsIgnoreCase("DESKTOP") || itemnum.equalsIgnoreCase("Network PC") || itemnum.equalsIgnoreCase("Standalone PC") || itemnum.equalsIgnoreCase("PC")) { itemnum = "DT66"; } else if(itemnum.equalsIgnoreCase("Network Portable") || itemnum.equalsIgnoreCase("Standalone Portable") || itemnum.equalsIgnoreCase("NOTEBOOK")){ itemnum = "D900"; } else if (itemnum.equalsIgnoreCase("LAPTOP")){ itemnum = "D600"; } else if(itemnum.equalsIgnoreCase("Server") || itemnum.equalsIgnoreCase("Windows 2003 Server") || itemnum.equalsIgnoreCase("PowerEdge 500C Server")){ itemnum = "S900"; } else if (itemnum.equalsIgnoreCase("Unix Server") ){ itemnum = "S700"; } else { skipCurrentInstance(); }}else skipCurrentInstance();

return(itemnum);}



classstructureid Property in the Maximo IT Assets Target

c In the classstructureid property row, double-click the cell in the Expression column. The Integration Composer displays the selected expression in the Expression Builder dialog box, as shown in the following example.

Sample Expression for classstructureid Property in the Expression Builder Dialog Box

{String itemnum = 'Deployed Asset.Systemrole';String classstructureid = null;

if(!isNull(itemnum)){ if(itemnum.equalsIgnoreCase("DESKTOP") || itemnum.equalsIgnoreCase("Network PC") || itemnum.equalsIgnoreCase("Standalone PC") || itemnum.equalsIgnoreCase("PC")) { itemnum = "DT66"; } else if(itemnum.equalsIgnoreCase("Network Portable") || itemnum.equalsIgnoreCase("Standalone Portable") || itemnum.equalsIgnoreCase("NOTEBOOK")){ itemnum = "D900"; } else if (itemnum.equalsIgnoreCase("LAPTOP")){ itemnum = "D600"; } else if(itemnum.equalsIgnoreCase("Server") || itemnum.equalsIgnoreCase("Windows 2003 Server") || itemnum.equalsIgnoreCase("PowerEdge 500C Server")){ itemnum = "S900"; } else if (itemnum.equalsIgnoreCase("Unix Server") ){ itemnum = "S700"; } else { itemnum = null; skipCurrentInstance(); }

if (!isNull(itemnum)) { String sql = "select classstructureid from " + getTargetTableOwner() + ".item where itemnum = '" + itemnum + "'"; classstructureid = executeTargetSQL(sql,null);

if(isNull(classstructureid)) { skipCurrentInstance(); } }}else skipCurrentInstance();

return(classstructureid);}



d For each asset class, specify the appropriate itemnum for the classstructureid. For example, in the preceding figure, the expression specifies DT66 for DESKTOP, Network PC, Standalone PC, or PC.

e After you modify the classstructureid expression, click OK. The Integration Composer saves the modified expression and closes the Expression Builder dialog box.

Modify the status Property 15 To modify the status property, complete the following steps:

a In the tree view in the Target pane, select the class whose status you want to change.

b In the table view in the Target pane, scroll to the status property, as shown in the following example.

status Property in the Maximo IT Assets Target

c In the status property row, double-click the cell in the Expression column. The Integration Composer displays a data entry field for the expression.

d In the Expression field, type the appropriate string literal for your status (including quotation marks), for example �OPERATING�.

NOTE The status specified in the expression must be a valid LOCASSETSTATUS in the Maximo SYNONYMDOMAIN table. For more information about SYNONYMDOMAINs, refer to the IBM Maximo System Administrator�s Guide.

e To ensure that the Integration Composer saves the last entry, press Enter after you type the expression.

Modify Asset Specification Properties

16 To modify the asset specification property, complete the following steps:

a In the tree view in the Target pane in the lower half of the window, select the class whose asset specification you want to change.

b In the table view in the Target pane, scroll to the asset specification properties, as shown in the following example. Asset specification properties are flagged with an asterisk (*) in Chapter 4, �Deployed Assets to IT Assets Mapping�, on page 4-1.



Asset Specification Property in the Maximo IT Assets Target

c In the asset specification property row, double-click the cell in the Expression column. The Integration Composer displays a data entry field for the expression.

d In the Expression field, type the expression you want to use for the asset specification property using the following format:

�<class>.<property>�

e To ensure that the Integration Composer saves the last entry, press Enter after you type the expression.

NOTE For more information about asset specifications, refer to the IBM Maximo User�s Guide and the IBM Maximo System Administrator�s Guide.

Modify Software Item (Spare Parts) Properties

17 To modify software item properties, complete the following steps:

a In the tree view in the Target pane in the lower half of the window, select Spare Parts.

b In the table view in the Target pane, scroll to the itemnum property, as shown in the following example.

Software Item Property in the Maximo IT Assets Target



c In the itemnum property row, double-click the cell in the Expression column. The Integration Composer displays the selected expression in the Expression Builder dialog box, as shown in the following example.

Sample Expression for Spare Parts itemnum Property in the Expression Builder Dialog Box

d For each software item, specify the appropriate itemnum. For example, in the preceding figure, the expression specifies WINDOWS95 and other versions of Microsoft software.

NOTE Item numbers that you specify in the expression must be valid item numbers in Maximo.

TIP You can copy the item number specifications in the itemnum property and paste them into the quantity expression in step h on page 3-19. The itemnum expressions to copy are illustrated in bold text in the figure.

e After you modify the itemnum expression, click OK. The Integration Composer saves the modified expression and closes the Expression Builder dialog box.

f Scroll to the quantity property in the table view and select the row.

g In the quantity property row, double-click the cell in the Expression column. The Integration Composer displays the selected expression in the Expression Builder dialog box, as shown in the following example.

{String itemnum = 'Software.Softwarename';if(!isNull(itemnum)){

if((itemnum.indexOf("Windows 95") > -1)) { itemnum = "WINDOWS95"; } else if ((itemnum.indexOf("Windows 98") > -1)) { itemnum = "WINDOWS98"; } else if ((itemnum.indexOf("Windows 2000") > -1)) { itemnum = "WINDOWS2000"; } else if (itemnum.equalsIgnoreCase("Windows XP Workstation")) { itemnum = "WINDOWSXP"; } else if ((itemnum.equalsIgnoreCase("Microsoft Office 2003")) || (itemnum.equalsIgnoreCase("Microsoft Office XP")) || (itemnum.equalsIgnoreCase("Office 2000 Premium")) || (itemnum.equalsIgnoreCase("Microsoft Office 2000"))) { itemnum = "MSOFFICE"; } else { skipCurrentInstance(); }}else skipCurrentInstance();

return(itemnum);}



Sample Expression for Spare Parts quantity Property in the Expression Builder Dialog Box

h For each software item, specify the appropriate itemnum. For example, in the preceding figure, the expression specifies WINDOWS95 and other versions of Microsoft software.

i After you modify the quantity expression, click OK. The Integration Composer saves the modified expression and closes the Expression Builder dialog box.

18 If appropriate, you can make other changes to the mapping.

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

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

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

{String itemnum = 'Software.Softwarename';if(!isNull(itemnum)){ if((itemnum.indexOf("Windows 95") > -1)) { itemnum = "WINDOWS95"; } else if ((itemnum.indexOf("Windows 98") > -1)) { itemnum = "WINDOWS98"; } else if ((itemnum.indexOf("Windows 2000") > -1)) { itemnum = "WINDOWS2000"; } else if (itemnum.equalsIgnoreCase("Windows XP Workstation")) { itemnum = "WINDOWSXP"; } else if ((itemnum.equalsIgnoreCase("Microsoft Office 2003")) || (itemnum.equalsIgnoreCase("Microsoft Office XP")) || (itemnum.equalsIgnoreCase("Office 2000 Premium")) || (itemnum.equalsIgnoreCase("Microsoft Office 2000"))) { itemnum = "MSOFFICE"; } else { skipCurrentInstance(); }}else skipCurrentInstance();

int quantity = 0;int j = 'Deployed Asset.Nodeid'; String assetnum = "C-" + Integer.toString(j); String orgid = getProperty("assetinit.properties", "assetinit_orgid");String siteid = getProperty("assetinit.properties", "assetinit_siteid");

...



Viewing Mapping Errors

From the Integration Composer Mapping window�s Select Action menu, you can select Show Errors to view any errors in the open mapping. The Show Errors function displays Java parsing errors but not compilation errors.

The Integration Composer generates compilation errors only when it executes a mapping. To view compilation errors, you must view the Integration Composer's log files. For information about log files, refer to the �logging.properties File� section in Appendix B of the IBM Maximo Integration Composer System Administrator�s Guide.

To view Java parsing errors in a mapping, complete the following steps:

1 From the Select Action menu on the Integration Composer Mapping window, select Show Errors. The Integration Composer opens an Errors dialog box that displays any errors in your mapping.

2 After you view the errors, click OK to close the dialog box.

Executing the IT Asset Initialization Mapping



When you create the Deployed Assets to Maximo IT Assets mapping, you define a set of expressions that specify how to transform deployed asset data to Maximo IT assets. To transform the data and create IT assets in Maximo, you execute the mapping.

You can use the Integration Composer application to execute a mapping, or you can execute a mapping from a command line. For performance reasons, it is usually more efficient to execute a mapping as a stand-alone process from a command line. For more information about executing a mapping from a command line, refer to �Executing a Mapping from a Command Line� on page 3-23.

As the Integration Composer executes a mapping, it builds a file for each class in the mapping. After the Integration Composer processes a top-level asset, including its children, it commits the data for that asset to the database.

If you stop and then restart mapping execution, the Integration Composer begins where it left off and moves only assets that it did not previously commit to the database.

When the Integration Composer imports data into Maximo, it adds records and it updates records. It does not delete asset records.

Executing a Mapping Using the Integration Composer

To execute a mapping using the Integration Composer application, complete the following steps:

1 In the IBM Maximo Integration Composer window, select Execute Mapping. The Integration Composer displays the Execute Mapping window, as shown in the following figure.

Execute Mapping Window



The Execute Mapping window displays a table that lists the mappings currently available in the Integration Composer. The table contains the following information about each mapping:

2 In the list of mappings, verify that the Integration Composer has selected the Ready check box for the Deployed Assets to Maximo IT Assets mapping and then select one of the following options:

! If the Integration Composer has not selected the Ready field, click Cancel. Review the mapping and correct the appropriate expressions and then re-attempt this procedure.

For more information about mapping expressions, refer to the IBM Maximo Integration Composer System Administrator�s Guide.

! If the Integration Composer has selected the Ready field, the mapping has no syntax errors and is ready to execute. Go to step 3.

3 To select the mapping to execute, click the Deployed Assets to Maximo IT Assets mapping. The Integration Composer displays the mapping name in the Mapping Name field.

4 In the Execute Mapping dialog box, click OK. The Integration Composer displays the Open Source Data Source window.

5 On the Connection Information page in the Open Source Data Source window, accept the settings established for the last connection to the data source or update the fields. You must enter a password.

6 In the Open Source Data Source window, click Finish. The Integration Composer displays the Open Target Data Source window.

7 In the Open Target Data Source window, click Finish. The Integration Composer displays the Mapping Execution Progress dialog box as it builds a Java source file, as shown in the following figure.

Column Description

Mapping Name Name of the mapping.

Date Date when someone last saved the mapping.

Source Name of the source data source for the mapping.

Target Name of the target data source for the mapping.

Ready Check box that specifies whether the mapping is ready to execute; that is, the mapping has no errors.

Insert Only Indicates that when importing data into the target data source, Integration Composer only creates new assets. It does not update existing assets.



Mapping Execution Progress Window

NOTE If appropriate, to cancel a mapping execution, in the Mapping Execution Progress dialog box, click Cancel.

If the mapping execution is successful, the Integration Composer displays a confirmation message.

If the Integration Composer finds errors, it displays an error message dialog box.

8 Select one of the following options:

! If the mapping is successful and the Integration Composer displays a confirmation message, click OK. The Integration Composer displays the IBM Maximo Integration Composer window.

! If the Integration Composer found errors and the Integration Composer displays an error message dialog box, click OK. Review the Integration Composer log files to determine the cause of the errors. For information about how to review log files, see the IBM Maximo Integration Composer System Administrator�s Guide.

Executing a Mapping from a Command Line

After you create and save a mapping, to optimize performance, execute a mapping from a command line. It is especially useful if you execute a mapping often.

To run the mapping without supervision, you can enter a command line or use a batch file. At the command line, enter the appropriate execution instruction and desired parameters.

The commandLine.bat file is in the bin folder in the Integration Composer installation directory. You can edit the command file parameters and create different files for different mappings. To set up a new command file, you can edit the following parameter arguments in the file:

@echo off@echo Fusion will now start.@echo offset MAPPINGNAME=%1



set REPOSITORYUSER=%2set REPOSITORYPWD=%3set SOURCEUSER=%4set SOURCEPWD=%5set TARGETUSER=%6set TARGETPWD=%7

Example

@echo off@echo Fusion will now start.@echo offset MAPPINGNAME="Deployed Assets to Maximo IT Assets"set REPOSITORYUSER=maximoset REPOSITORYPWD=********set SOURCEUSER=saset SOURCEPWD=********set TARGETUSER=maximoset TARGETPWD=********

If any parameter arguments contain spaces, enclose the parameter argument in quotation marks.

If any parameter arguments represent a database null, enter single quotation marks without a space in between. For example, if you do not have a password for your database, enter single quotation marks for this parameter argument, as shown in the following example:

set TARGETPWD=��

If you set the parameters specified in the preceding example, you can execute the mapping with the command:

commandline.bat

If you do not want to set the parameters shown in the preceding example, you can use a command similar to the following command to execute the mapping:

commandLine.bat �Deployed Assets to Maximo IT Assets� maximo maximo sa sa maximo maximo

To edit a commandLine.bat file, complete the following steps:

1 Open any text editor, such as MS Notepad.

2 Select File > Open.

3 In the <installDir>\bin> directory, select commandLine.bat as the file name and click Open.

4 To configure the batch file to perform the unattended Mapping execution, establish the following arguments in the file, substituting the appropriate data, as illustrated in the example on page 3-24:

@echo off@echo Fusion will now start.@echo offset MAPPINGNAME=%1set REPOSITORYUSER=%2set REPOSITORYPWD=%3



set SOURCEUSER=%4set SOURCEPWD=%5set TARGETUSER=%6set TARGETPWD=%7

5 To save the modified file, select File > Save.

6 To exit the text editor, select File > Exit.

7 From the task bar, select Start > Run. Your computer displays a Run dialog box.

8 In the Open field, enter <installDir>\bin\commandLine.bat.

9 Click OK. Your computer executes the batch file.

10 After the word Done appears, press Ctrl+c to terminate the batch job.

11 Type Y.

TIP Another method for running an unattended mapping is to use the Windows NT® Schedule Service. If you use the Windows scheduler, comment out the line containing the �pause� command.

Example

:exit@echo Fusion has finishedpause

becomes

:exit@echo Fusion has finishedREM pause


The following table lists mapping expressions for the IT Asset Initialization product extension for ITSM (SourceDPAtoAssetsWithITSME6x.fsn). This mapping creates software as spare parts records.

Deployed Assets to IT Assets Mapping 4

Maximo Assets 6.x Source�Maximo Deployed Assets

Class NameProperty

<Class Name>.<Property Name>Key Name

Key: PK=Primary Key AK=Alternate Key FK=Foreign Key GV=Generated Value

ITAsset PK assetnum "C�" + 'Deployed Asset.Nodeid'

PK moved 0

PK orgid assetinit_orgid property in assetinit.properties

PK siteid assetinit_siteid property in assetinit.properties

GV assetid

GV assetuid

Computer PK,FK assetid

PK,FK assetnum

PK,FK assetuid

PK,FK moved

PK,FK orgid

PK,FK siteid

ancestor

assettag 'Deployed Asset.Assettag'

assettype "IT"

autowogen 0

binnum

budgetcost 0

calnum

changeby "FSN"

GV changedate

children 0

classstructureid 'Deployed Asset.Systemrole', 'item.classstructureid'

conditioncode

description "NODE NAME:" + 'Deployed Asset.Nodename' + ";" + 'Deployed Asset.Description'

disabled 0

eq1


Computer

(continued)

eq10

eq11

eq12

eq2

eq23

eq24

eq3

eq4

eq5

eq6

eq7

eq8

eq9

externalrefid

failurecode

glaccount

groupname

hasld 0

installdate

invcost 0

isrunning 1

itemnum 'Deployed Asset.Systemrole'

itemsetid

itemtype

langcode assetinit_langcode property in assetinit.properties

location

mainthierchy 0

manufacturer

ownersysid

parent

priority

purchaseprice 0

replacecost 0

rotsuspacct

sendersysid

serialnum 'Deployed Asset.Serialnumber'

shiftnum

sourcesysid

status "NOT READY"


Class NameProperty



Deployed Assets to IT Assets Mapping 4-3

* indicates the property is an asset specification.

Computer

(continued)

statusdate

toolcontrolaccount

toolrate

totalcost 0

totdowntime 0

totunchargedcost 0

unchargedcost 0

usage

vendor

warrantyexpdate

ytdcost 0

*disksize 'Physical Disk.Totalspace'

*disksize_muid 'Physical Disk.Sizeunit'

*prospeed 'Processor.Maxspeed'

*prospeed_muid 'Processor.Speedunit'

*ramsize 'Computer.Ramsize'

*ramsize_muid 'Computer.Ramunit'

*mindisk

*mindisk_muid "GBYTE"

Spare Parts PK,FK assetnum

PK itemnum 'Software.Softwarename'

PK,FK orgid

PK,FK siteid

description

hasid 0

itemsetid assetinit_itemsetid property in assetinit.properties

langcode assetinit_langcode property in assetinit.properties

quantity

issuedqty Increments the target quantity by one.

GV sparepartid


Class NameProperty



© 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 Product Extension: 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 Product Extension: Implementation Guide

IBM Maximo Product Extensionpublib.boulder.ibm.com/tividd/td/ITMProdE/621_mpe_itsm...IBM Maximo...

Documents

Transcript of IBM Maximo Product Extensionpublib.boulder.ibm.com/tividd/td/ITMProdE/621_mpe_itsm...IBM Maximo...