CCMDB 711 Int Adapter Taddm Ibmbook

Tivoli Change and Configuration Management Database

Version 7 Release 1.1
Integration Adapter for Tivoli Application Dependency Discovery Manager

Implementation Guide
Tivoli Change and Configuration Management Database
®

Version 7 Release 1.1
Integration Adapter for Tivoli Application Dependency Discovery Manager

Implementation Guide
Note
Before using this information and the product it supports, read the information in “Notices” on page 59.
Contents
About this publication . . . . . . . . v Installing the data schema for your CCMDB
Intended audience . . . . . . . . . . . . v actual CI data . . . . . . . . . . . . 26
Related information . . . . . . . . . . . . v Creating a mapping for your TADDM-to-CCMDB
IBM support . . . . . . . . . . . . . . v CI type data . . . . . . . . . . . . . 28
Conventions used in this publication . . . . . . vi [Optional] Modifying the mapping expressions 30
Creating a mapping for your TADDM-to-CCMDB
Chapter 1. Overview of the integration actual CI data . . . . . . . . . . . . 30
[Optional] Modifying your mapping expressions 32
adapter and Integration Composer . . . 1 Loading the class qualifiers into the target CI
Software required by the integration adapter . . . 1 type data schema . . . . . . . . . . . 32
Integration adapter files . . . . . . . . . . 2 Loading the class qualifiers into the target actual
About Integration Composer . . . . . . . . . 3 CI data schema . . . . . . . . . . . . 33
Integration Composer components . . . . . . 3 Verify your CI classifications. . . . . . . . . 33
Integration Composer file structure . . . . . . 4 Creating a top-level CI class and class structure
identifier . . . . . . . . . . . . . . 34
Chapter 2. Data collection and migration 7 Import your data . . . . . . . . . . . . 35
Configuration items and CI data . . . . . . . . 7 Executing your mapping for CI types. . . . . 35
End-to-end data collection and migration process . . 8 Activating CI types . . . . . . . . . . . 35
Executing your mapping for actual CIs . . . . 36
Chapter 3. Installing the integration Viewing log file information . . . . . . . . . 36
adapter . . . . . . . . . . . . . . 11
Installation checklist . . . . . . . . . . . 11 Chapter 4. Tips for effective mappings 37
Prepare to install . . . . . . . . . . . . 13 Modifying language properties . . . . . . . . 37
Verifying the appropriate level of depth for Mapping data for units of measurement . . . . . 38
actual CI data imports . . . . . . . . . . 14 Mapping data for sites and organizations . . . . 38
Modifying the timeout value . . . . . . . 15 Mapping key properties . . . . . . . . . . 38
[SSL users only] Copying the jssecacerts.cert file 15 Mapping data for scan dates. . . . . . . . . 38
Determining your connection parameters . . . 16
Install the integration adapter for TADDM . . . . 16 Chapter 5. Integration adapter
Copying the database and qualifier scripts to the mappings for TADDM . . . . . . . . 41
Integration Composer server or CCMDB database
server . . . . . . . . . . . . . . . 16
Installing the data schema for your TADDM CI
Appendix A. Advanced users’ checklist
type data . . . . . . . . . . . . . . 17 for installing the integration adapter . . 47
Installing the data schema for your TADDM
actual CI data . . . . . . . . . . . . 17 Appendix B. Executing a mapping . . . 53
Copying the schema and mapping files to the Using values specified in a file . . . . . . . . 53
Integration Composer server. . . . . . . . 18 Using values specified on the command line . . . 56
Defining a data source connection for your
TADDM CI type data . . . . . . . . . . 19 Notices . . . . . . . . . . . . . . 59
Defining a data source connection for your Trademarks . . . . . . . . . . . . . . 61
TADDM actual CI data . . . . . . . . . 21
Installing the data schema for CCMDB CI type
data . . . . . . . . . . . . . . . . 22
© Copyright IBM Corp. 2007, 2008 iii

iv Integration Adapter for TADDM: Implementation Guide
About this publication
This section describes the purpose of integration adapters and this implementation
guide. It also provides information about who this guide is for, as well as about
other IBM® Corporation resources that are available to you, such as related
documentation and support.
Implementation guides like this one explain how to set up an IBM Tivoli®
integration adapter for a particular discovery tool. IBM Tivoli integration adapters
use IBM Tivoli Integration Composer (formerly Maximo Fusion) to import
information technology data collected by discovery tools into a target database.
Intended audience
This implementation guide is for the system administrator, network administrator,
or other professional who is responsible for using Integration Composer to import
data that has already been collected by the discovery tool into a target database.
The user of this document should understand the concepts and tasks presented in
the IBM Tivoli Integration Composer Administrator Guide. This book assumes
knowledge of that guide.
Related information
For more information about Integration Composer, refer to the documentation
described in this section:
Document Description
IBM Tivoli Integration Composer Describes how to use Integration Composer to map data
Administrator Guide from an external source and import the data into a
target database
Planning and Installing IBM Tivoli Describes how to install and configure Integration
Change and Configuration Composer on Microsoft® Windows® and UNIX-based
Management Database 7.1.1 operating systems
Integration Composer Help Provides step-by-step procedures for Integration
Composer
IBM support
IBM Software Support provides assistance with product defects.
Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. For information about the types of maintenance contracts available, see
“Enhanced Support” in the Software Support Handbook at http://
techsupport.services.ibm.com/guides/services.html.
Complete the following steps to contact IBM Software Support with a problem:
1. Define the problem, gather background information, and determine the severity
of the problem. For help, see “Contacting IBM” in the Software Support
Handbook at http://techsupport.services.ibm.com/guides/beforecontacting.html.
© Copyright IBM Corp. 2007, 2008 v

2. Gather diagnostic information.
3. Submit your problem to IBM Software Support in one of the following ways:
a. Online: Click Submit and track problems on the IBM Software Support site
at http://www-306.ibm.com/software/support/probsub.html.
b. By telephone: For the telephone number to call in your country, go to the
“IBM Contacts” page of the Software Support Handbook at
http://techsupport.services.ibm.com/guides/contacts.html.
If you submit a problem that is a software defect or for missing or
inaccurate documentation, IBM Software Support creates an Authorized
Program Analysis Report (APAR). The APAR describes the problem in
detail.
Whenever possible, IBM Software Support provides a workaround that you
can implement until the APAR is resolved and a fix is delivered. IBM
publishes resolved APARs daily on the Software Support Web site so that
other users who experience the same problem can benefit from the same
resolution.
Conventions used in this publication

This publication uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip and Operating system considerations)
v Keywords and parameters in text
Italic
v Citations (examples: titles of publications, diskettes, and CDs)
v Words defined in text (example: a nonswitched line is called a
point-to-point line)
v Emphasis of words and letters (words as words example: ″Use the word
that to introduce a restrictive clause″; letters as letters example: ″The
LUN address must start with the letter L″)
v New terms in text (except in a definition list): a view is a frame in a
workspace that contains data.
v Variables and values you must provide: ... where myname represents....
Monospace
v Examples and code examples
v File names, programming keywords, and other elements that are difficult
to distinguish from surrounding text
v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options
Directory names, paths, and ″folders″
vi Integration Adapter for TADDM: Implementation Guide

This book uses Windows conventions for specifying directory names and directory
paths. UNIX® users should replace each backslash (\) with a forward slash (/) in
any Windows directory paths that include backward slashes. UNIX users should
treat any references to a Windows folder as the equivalent of directory in UNIX.
About this publication vii

viii Integration Adapter for TADDM: Implementation Guide
Chapter 1. Overview of the integration adapter and Integration
Composer
The integration adapter for IBM Tivoli Application Dependency Discovery
Manager (TADDM) consists of a set of software files that you install into IBM
Tivoli Integration Composer. Integration Composer (formerly Maximo Fusion) is
the integration tool that you use to import information technology (IT) data from
TADDM into a target database.
To gather the IT data, the TADDM discovery tool scans computers and other
devices connected to a network and records information about their installed
hardware and software. Integration Composer, with the integration adapter for
TADDM installed, transforms the collected TADDM data and imports it into the
target database. In this case, the target database is the Maximo database in the
Change and Configuration Management Database (CCMDB) product.
Before importing the TADDM data instances, you must first import the Common
Data Model (CDM) definition, which is the core structure of the TADDM data. To
import any kind of TADDM data into the Maximo database, you use Integration
Composer to create some mappings that convert the data from its source form to
the form required by the Maximo database.
A mapping is a set of expressions that tells Integration Composer how to create

data in the target using data from a source. The integration adapter for TADDM
includes two mapping files to use when creating these mappings, one for CI type
data and one for actual CI data. The CI type mapping will bring the CDM
definition into the Maximo database, while the actual CI mapping will bring in the
data instances. The integration adapter, once installed, does this data-mapping part
of the transforming task for you.
Software required by the integration adapter

Several corequisites are required by the integration adapter for TADDM. All the
corequisite software described in this section is provided with IBM Tivoli Change
and Configuration Management Database. To ensure that all the corequisites are
compatible with one another when you run them, use only the software versions
supplied with CCMDB.
The integration adapter for TADDM runs with the following software:
CCMDB IBM Tivoli Change and Configuration Management Database (CCMDB) 7.1.1, which
includes the Maximo database, is required and must be installed before you can use
Integration Composer.
Integration Composer IBM Tivoli Integration Composer 7.1.1. Integration Composer must be installed before you
can use the integration adapter for TADDM.
For installation instructions and information about the minimum hardware and software
requirements for Integration Composer, see the book Planning and Installing IBM Tivoli
Change and Configuration Management Database 7.1.1.
© Copyright IBM Corp. 2007, 2008 1

Discovery tool IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.1, and its associated
database, is required. (This database contains the source data to be transformed and then
imported into the target Maximo database in CCMDB.)
Integration adapter files

The integration adapter for TADDM comprises several components, or files, that
are provided to support the importing of two types of discovered data: CI type
data and actual CI data. CI is an abbreviation for configuration item. A configuration
item is anything in an IT environment subject to configuration management, or
change control—a computer, a printer, a router.
TADDM discovers CIs in the IT environment and stores the information in its
database. In order to import that data (the actual CI data), and the data used to
classify it (the CI type data), into the Maximo database, the TADDM adapter
provides a different set of files for each of the data types.
The media for IBM Tivoli Integration Adapter for Tivoli Application Dependency
Discovery Manager contains these two sets of files:
v The following integration adapter files are related to importing CI type data:
createTADDM71CITypeDataSchema.db2
createTADDM71CITypeDataSchema.ora
createTADDM71CITypeDataSchema.sqs
These database scripts define the structure that organizes and classifies
the CI type source data for IBM DB2, Oracle, and SQL Server databases,
respectively.
qualifierCCMDB71Classification.db2
qualifierCCMDB71Classification.ora
qualifierCCMDB71Classification.sqs
These qualifier scripts modify the way Integration Composer handles CI
type target data when it performs a data import to IBM DB2, Oracle,
and SQL Server databases, respectively.
CCMDB71Classification.schm
This schema file defines the structure that organizes and classifies the CI
type target data.
TADDM71CITypeToCCMDB71Classification.fsn
This mapping file provides predefined expressions that you can use to
transform CI type data from the source formats to the target formats.
v The following integration adapter files are related to importing actual CI data:
createTADDM71ActualCIDataSchema.db2
createTADDM71ActualCIDataSchema.ora
createTADDM71ActualCIDataSchema.sqs
These database scripts define the structure that organizes and classifies
the actual CI source data for IBM DB2, Oracle, and SQL Server
databases, respectively.
qualifierCCMDB71ActualCI.db2
qualifierCCMDB71ActualCI.ora
qualifierCCMDB71ActualCI.sqs
These qualifier scripts modify the way Integration Composer handles
2 Integration Adapter for TADDM: Implementation Guide

actual CI target data when it performs a data import to IBM DB2,
Oracle, and SQL Server databases, respectively.
CCMDB71ActualCI.schm
This schema file defines the structure that organizes and classifies the
actual CI target data.
TADDM71ActualCIToCCMDB71ActualCI.fsn
This mapping file provides predefined expressions that you can use to
transform actual CI data from the source formats to the target formats.
The Integration Adapter for Tivoli Application Dependency Discovery Manager:

Implementation Guide is provided in the following Adobe® Systems Portable
Document Format (PDF) file:
ccmdb_711_int_adapter_taddm_ibmbook.pdf
About Integration Composer

Integration Composer is separately installed software that is required by the
integration adapter. To use the integration adapter, first you have to install and
understand the basics about Integration Composer.
The sections that follow describe the Integration Composer components and file
structure. For more detailed information, see the book IBM Tivoli Integration
Composer Administrator Guide.
Integration Composer components

Integration Composer includes the application itself (the user interface), a
command line interface, an engine for processing mapping expressions, several
connection drivers, and a repository that is a subset of the Maximo database where
your information technology data is imported.
A short description of the Integration Composer components follows:
Integration Composer The Integration Composer user interface lets you define data sources, browse the source data,
user interface define data schemas, and create mappings to transform and migrate data.
Integration Composer The Integration Composer command line interface lets you start Integration Composer and
command line execute mappings that transform your source data and import it from the source to the
interface target (Maximo) database.
Integration Composer The Integration Composer engine processes mapping expressions that transform data from the
engine source data and integrate it into a target database.
Chapter 1. Overview of the integration adapter and Integration Composer 3

Connection methods IBM Configuration Discovery and Tracking API: Integration Composer includes the IBM
Configuration Discovery and Tracking API to establish connections to the source data. Use
this connection method only when connecting to the source data for integration adapters
like TADDM that use configuration item data (CI types and actual CIs).
JDBC drivers: Integration Composer uses a JDBC driver to establish connections to the
target (Maximo) database. Integration Composer includes the following JDBC drivers for
this purpose. Use the driver that is appropriate for your target database:
v IBM DB2® JDBC Driver
v i-net OPTA JDBC Driver for Microsoft SQL Server 7/2000/2005
v Oracle JDBC Thin driver. This driver supports Oracle 10g and earlier versions (including
8.0, 8i, and 9i).
Integration Composer The Integration Composer repository in the Maximo database contains the following
repository Integration Composer data:
v Metadata for data schemas delivered with Integration Composer. This metadata defines
the structure of the data.
v Metadata for data schemas that you create in Integration Composer.
v Data source definitions that provide data connection parameters.
v Mappings that define how to transform data instances and migrate them from a source to
a target.
v The time stamp of the most recent scan for root objects in the source data of the
Integration Composer repository, if such a last-scan time stamp exists.
Integration Composer file structure

During Integration Composer installation, if the default installation path is
accepted, the installation program installs the application in the Integration
Composer (Windows) or Integration_Composer (UNIX) directory, in a
predetermined file structure.
The installation program creates the following file structure for Integration
Composer on Windows operating systems (UNIX is similar):
Integration Composer
bin
data
dataschema
mappings
properties
provider
etc
genrules
help
lib
log
Uninstall_Integration_Composer
Figure 1. Integration Composer file structure
If you select a different location when you install Integration Composer, the
installation program creates the same file structure in the location that you specify.

The Integration Composer folders store the following data:
Folder Description
bin Stores the following batch files:
v commandLine.bat (Windows), commandline.sh (UNIX) - file that
executes an Integration Composer mapping from a command
line.
v init.bat (Windows), init.sh (UNIX) - file used to define and
initialize the Integration Composer environment
v startFusion.bat (Windows), startfusion.sh (UNIX) - file that
launches Integration Composer.
data Stores the following folders:
v dataschema - stores data schemas that users export from
Integration Composer or that users copy to this folder from other
sources, such as an IBM Tivoli integration adapter.
v mappings - stores mappings that users export from Integration
Composer or that users copy to this folder from other sources,
such as an IBM Tivoli integration adapter.
v properties - stores specialized application properties files. The
provider subfolder also includes specialized application
properties files.
etc Stores files used by the Tivoli Application Dependency Discovery
Manager Software Development Kit. Do not modify any files in
this folder.
genrules Stores Java™ source files that Integration Composer creates when
you run 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 JDBC drivers and application program interfaces (APIs) that
Integration Composer uses, including files from TADDM. Do not
modify any files in this subdirectory.
log Stores Integration Composer log files.
Uninstall_Integration Stores the files that remove Integration Composer from your
_Composer computer. Do not modify any files in this folder.
Chapter 1. Overview of the integration adapter and Integration Composer 5

Chapter 2. Data collection and migration
The integration adapter for Tivoli Application Dependency Discovery Manager
facilitates data migration. Data migration is the transfer of data to a different
database server or data model. For our purposes, data migration refers to the
importing, and subsequent transformation, of data from a data source—the
TADDM database—to a target—the Maximo database.
In this case the data is configuration item (CI) data retrieved from an IT
environment. This section explains the concepts related to configuration items and
CI data, and provides an overview of the end-to-end data collection and importing
process. This data migration process involves the use of multiple software tools,
including the integration adapter for TADDM and Integration Composer. In
addition, Change and Configuration Management Database (CCMDB) applications
are required for some steps in the data migration process.
Configuration items and CI data

A configuration item (CI) is any component of an IT environment meant to be under
the control of configuration management and therefore subject to change control. A
discovery tool is used to collect and save configuration data from these CIs.
Authorized and actual configuration items
CCMDB maintains data about two kinds of configuration items:

v Authorized configuration items are manageable objects that conform to specified
rules and relationships assigned to them. As such, these conforming
configuration items are considered to be “authorized” for deployment. Although
authorized, they may or may not actually exist in your IT environment.
Typically, authorized configuration items are either in plan to be deployed or are
believed (but not actually verified) to be deployed.
v Actual configuration items are objects that truly are deployed in the enterprise,
and their deployment can be verified by using discovery tools such as the one
applicable to this integration adapter.
Actual CI data
Two types of database information are associated with authorized CIs and actual
CIs. They are authorized CI data and actual CI data, respectively. For now, we are
only concerned with actual CI data, because we only want to migrate, or import,
CI data that actually exists into the IT environment.
Actual configuration item data, or actual CI data, is data collected directly from
components that actually exist in your enterprise’s IT environment, and can
therefore be ″discovered.″ To gather this data, discovery tools are used to scan the
computers, network devices, and other information technology objects deployed in
your enterprise and record information about the hardware and software installed
on them. You can then import this collected information into the target database.
The import of the actual CI data can occur only after it has been classified using CI
type data.

CI type data
Configuration item type data, or CI type data, is data that classifies the actual CI data.
Such classification allows your enterprise to specify what type of actual CI data it
wants to import and manage in the database.
The integration adapter imports the Common Data Model (CDM) definition, the
core structure of the TADDM data, from TADDM into the Maximo database in
CCMDB. The CI type mapping brings the CDM definition into the Maximo
database, while the actual CI mapping brings in the data instances.
The order in which you import the data is important. You have to import CI type
data into the target database before you import any actual CI data. Checklists are
provided to assist with both of these tasks. If you are importing both CI type data
and actual CI data, be sure to follow the checklist steps in the order presented.
End-to-end data collection and migration process

Recall that the integration adapter for TADDM aids in transforming data that
TADDM discovers in an IT environment, so that the data can be migrated or
imported from the TADDM database into another—target—database using
Integration Composer. This section lists the end-to-end steps required to import
that discovered data into a target database using Integration Composer. In
particular, this discovered data is configuration item (CI) data that represents some
or all of the hardware or software found in your IT environment that is subject to
change control.
Performing the complete end-to-end discovery and importing of such data involves
the use of multiple software tools. In addition to Integration Composer and the
integration adapter for TADDM, these software tools include TADDM itself (for
discovery), as well as CCMDB. Table 1 lists the high-level steps and which tools
you use to do them. Although all the basic steps for collecting and importing data
are listed here, you might have to refer to CCMDB documentation for steps not
performed using Integration Composer. These references are cited in Table 1:
Table 1. End-to-end data collection and migration process.
Product or component to
Steps use Additional information
1. Using a discovery tool, collect TADDM discovery tool Use settings in the discovery tool to specify the types of configuration items to
data about your IT search for. The data resides in the discovery tool database and includes CI type
infrastructure. data.
2. Install Integration Composer Integration Composer For information about how to install Integration Composer, see the book
7.1.1. Planning and Installing IBM Tivoli Change and Configuration Management Database
7.1.1. Note that you must install IBM Java SDK 5.0 Service Release 5 before you
install Integration Composer.
3. Verify that Integration Integration Composer Verify that the level of depth specified in the fusion.properties file is correct for
Composer is configured your business needs. For details about how to do this task, refer to “Verifying
properly for TADDM. the appropriate level of depth for actual CI data imports” on page 14.
4. If you are using SSL Integration Composer To enable Secure Sockets Layer (SSL) connections between Integration Composer
certification, copy the and TADDM, you must copy the jssecacerts.cert file from the TADDM server to
jssecacerts.cert file to the the server where Integration Composer is installed. For details about how to do
Integration Composer this task, refer to “[SSL users only] Copying the jssecacerts.cert file” on page 15.
installation directory.
5. Obtain connection parameters Maximo database, When you prepare to import CI type and actual CI data, you must define
for the TADDM server and TADDM database connection parameters to the TADDM server and the Maximo database. You
Maximo database. might use the default values established when you installed the Maximo
database or other values defined specifically for your organization. If you do not
know these values, contact your database administrator. For details about how
to determine this information, refer to “Determining your connection
parameters” on page 16.

Table 1. End-to-end data collection and migration process. (continued)
Product or component to
Steps use Additional information
6. Install the integration adapter Integration Composer For details on how to do this task, refer to Chapter 3, “Installing the integration
for TADDM. (with TADDM adapter) adapter,” on page 11
7. In the Classifications Classifications This will ensure there is a top-level classification and a CI class structure ID for
application, check to see if a application and all the classes from TADDM.
top-level classification has Organizations application
been created for configuration in CCMDB For details on how to do this task, refer to “Creating a top-level CI class and
items; if not, create one. In the class structure identifier” on page 34.
Organizations application,
create a CI class structure Important: If you do not create the classification and identifier described in
identifier. “Creating a top-level CI class and class structure identifier” on page 34, the
process of importing CI type or actual CI data will stop (without warning or
error messages).
8. Import the CI type data. Integration Composer For details on how to do this task, refer to “Executing your mapping for CI
(with TADDM adapter) types” on page 35.
9. In the CI Types application, CI Types application in Important: You will not be able to import actual CI data, as described in the
change the status of the CI CCMDB next step, if you do not go into the CI Types application and change the status
types that you want to migrate of the types that you want to import to active.
to active.
For details on how to make the CI types active, see “Activating CI types” on
page 35 or refer to the online help for the CI Types application in CCMDB.
10. Import the actual CI data. Integration Composer For details on how to do this task, refer to “Executing your mapping for actual
(with TADDM adapter) CIs” on page 36.
Chapter 2. Data collection and migration 9

Chapter 3. Installing the integration adapter
This section explains how to install the integration adapter—which consists of two
sets of schema and mapping files. The process for importing your data is also
noted.
Because CI type data is the data used to classify the actual CI data, you must do
the CI type data tasks first when you install the integration adapter for TADDM.
You can execute your mappings (again, CI types first) anytime after installing the
adapter. For your convenience, instructions are provided here on how to do so.
Should you need more information about importing data or fixing any mapping
errors, refer to the book IBM Tivoli Integration Composer Administrator Guide.
Installation checklist
This section provides a checklist that summarizes how to install and use the
integration adapter when importing CI type and actual CI data.
When installing the integration adapter, be sure to use the checklist in Table 2. It
gives you the “big picture” of the overall migration process for CIs. And more
importantly, it directs you to the appropriate book instructions. The book
instructions provide detailed substeps to follow in order to successfully accomplish
each step in the checklist.
Note: If you already have experience using CCMDB, Integration Composer, and
the TADDM adapter, you might prefer using the Appendix A, “Advanced users’
checklist for installing the integration adapter,” on page 47. Instead of linking to
the detailed instructions presented within this chapter, the advanced users’
checklist just provides the crucial information you need when installing the
integration adapter for TADDM and importing TADDM data into the Maximo
database in CCMDB.
Table 2. Checklist for installing the integration adapter
1. Prepare to install Review the ″Before getting started″ steps in “Prepare
to install” on page 13
h a. From the Integration Composer server, verify the See “Verifying the appropriate level of depth for actual
appropriate level of depth for actual CI data imports. CI data imports” on page 14.
h b. From the Integration Composer server, modify the See “Modifying the timeout value” on page 15.
timeout value.
h c. [SSL users only] From the Integration Composer server, See “[SSL users only] Copying the jssecacerts.cert file”
copy the jssecacerts.cert file from the TADDMserver. on page 15.
h d. Determine your TADDM server and Maximo database See “Determining your connection parameters” on
connection parameters. page 16.

Table 2. Checklist for installing the integration adapter (continued)
2. Install the integration adapter for TADDM
h a. Copy the database scripts and qualifier scripts for both See “Copying the database and qualifier scripts to the
CI types and actual CIs to a location where you can Integration Composer server or CCMDB database
run them with a database query tool. server” on page 16.
Typically this location would be the Integration

Composer server or the CCMDB database server. You
only need to copy the scripts appropriate for your
Maximo database type (all the .db2, .ora, or .sqs files
listed in “Integration adapter files” on page 2).
h b. On the CCMDB database server, install the data See “Installing the data schema for your TADDM CI
schema for the source CI type data using a database type data” on page 17.
script.
h c. On the CCMDB database server, install the data See “Installing the data schema for your TADDM
schema for the source actual CI data using a database actual CI data” on page 17.
script.
h d. Copy the schema files and mapping files for both CI See “Copying the schema and mapping files to the
types and actual CIs to the Integration Composer Integration Composer server” on page 18.
server.
Copy the all the .schm and .fsn files listed in

“Integration adapter files” on page 2).
h e. From the Integration Composer user interface, define a See “Defining a data source connection for your
data source connection for the source CI type data. TADDM CI type data” on page 19.
h f. From the Integration Composer user interface, define a See “Defining a data source connection for your
data source connection for the source actual CI data. TADDM actual CI data” on page 21.
h g. From the Integration Composer user interface, install See “Installing the data schema for CCMDB CI type
the data schema for the target CI type data. data” on page 22.
h h. From the Integration Composer user interface, install See “Installing the data schema for your CCMDB
the data schema for the target actual CI data. actual CI data” on page 26.
h i. From the Integration Composer user interface, create a See “Creating a mapping for your TADDM-to-CCMDB
mapping for CI type data. CI type data” on page 28.
h j. [Optional] From the Integration Composer user See “[Optional] Modifying the mapping expressions”
interface, modify mapping expressions. on page 30.
h k. From the Integration Composer user interface, create a See “Creating a mapping for your TADDM-to-CCMDB
mapping for actual CI data. actual CI data” on page 30.

h l. [Optional] From the Integration Composer user See “[Optional] Modifying your mapping expressions”
interface, modify mapping expressions. on page 32.
h m. On the CCMDB database server, load the class See “Loading the class qualifiers into the target CI
qualifiers to the target CI type data schema. type data schema” on page 32.
h n. On the CCMDB database server, load the class See “Loading the class qualifiers into the target actual
qualifiers to the target actual CI data schema. CI data schema” on page 33.
3. Verify your CI classifications The following step is part of the Maximo installation
procedure. It is noted here for your convenience.
h a. From the Maximo Console user interface, classify your See “Creating a top-level CI class and class structure
CIs. identifier” on page 34.
4. Import your data The following are repeatable steps that you can
perform in the production environment after the
Integration Adapter for TADDM is installed. They are
noted here for your convenience.
h a. From the command line, execute the mapping for CI See “Executing your mapping for CI types” on page
types. 35.
You must execute this mapping first, and the mapping

must be successful, before you proceed with the actual
CI mapping in step 4.c.
h b. From the Maximo Console user interface, check that CI See “Activating CI types” on page 35.
types were activated.
h c. From the command line, execute the mapping for See “Executing your mapping for actual CIs” on page
actual CIs. 36.
Note that executing the mapping for CI types (step 10)

must be completed and successful before executing the
mapping for actual CIs.
Prepare to install
The sections that follow describe the necessary preparation tasks to do before you
begin your integration adapter installation. Do not omit any of the required tasks.
Omitting these tasks could result in your integration adapter not working properly.
Before getting started:

1. Make sure that you are using version 7.1.1 of both IBM Tivoli Integration
Composer and CCMDB. For information about how to install Integration
Composer, see the book Planning and Installing IBM Tivoli Change and
Configuration Management Database 7.1.1. Note that you must install IBM Java
SDK 5.0 Service Release 5 before you install Integration Composer.
2. If you currently have any data in your target (Maximo) database, back up that
database.
Chapter 3. Installing the integration adapter 13

3. If Integration Composer is running, close all open windows and sign out of the
application.
Verifying the appropriate level of depth for actual CI data

imports
The level of depth describes a property associated with the CI (configuration item)
trees in your data source for actual CIs. It indicates to Integration Composer the
number of class relationships to be traversed and then migrated to the target,
when importing actual CI source data. This verification task is to ensure that the
level of depth for the CI trees you intend to import is appropriate for your needs.
The value for the level of depth is preset to 3, the default, but you can change it by
editing the fusion.properties file. This Integration Composer properties file is
located as follows:
installation_dir\data\properties\fusion.properties
where installation_dir is Integration Composer on Windows operating systems and

Integration_Composer (with underscore) on UNIX-based operating systems.
By subtracting 1 from the depth level currently specified in your fusion.properties

file, you can calculate the number of relationships that will be traversed in your CI
trees during data importing, if no further change is made:
Depth Level Specified – 1 = Number of relationships traversed
For example, if your depth level is currently set to the default, 3, the following
three classes will be imported:
Depth level Class

1 Computer System
2 Operating System
3 Software
In the example, with a depth level of 3, two levels of relationships are traversed:
one between Computer System and Operating System classes, and another
between Operating System and Software classes.
To check the current value for the level of depth:
Look at the mxe.db.queryDepthLevel property in the fusion.properties file

(installation_dir\data\properties\fusion.properties):
// Number of levels to be recursively traversed for a query.
// Default is 3
mxe.db.queryDepthLevel=3
To change the current value for the level of depth, do the following steps:
application.
2. Edit the file installation_dir\data\properties\fusion.properties.
3. Modify the value of the mxe.db.queryDepthLevel property. (Note that
increasing the default value of 3 could reduce system performance.)
4. Save the file.

Modifying the timeout value
Timeout value describes a wait-time property in the Integration Composer
fusion.properties file. The property indicates the maximum number of seconds that
the IBM Configuration Discovery and Tracking API or a JDBC driver will wait for
a response to a data request. Unlike a JDBC driver, however, the API uses minutes
instead of seconds as the unit of measurement for the wait time. This task is to
ensure that the default timeout value for API users is not too long.
Integration Composer presets the value for the timeout to 1200. You can change
this value by editing the fusion.properties file, which is located as follows:
installation_dir\data\properties\fusion.properties
where installation_dir is Integration Composer on Windows operating systems and

Integration_Composer (with underscore) on UNIX-based operating systems.
The default timeout value of 1200 is interpreted as seconds by a JDBC driver,

which equates to a 20-minute wait time. But, as interpreted in minutes by the IBM
Configuration Discovery and Tracking API, 1200 equates to a 1200-minute wait
time, or 20 hours. You will be using both the API and a JDBC driver to connect to
sources and targets, respectively. So you might want to change the timeout value
from 1200 to another number that works better for both connection methods. For
example, if you change the timeout value to 180, you will have a 3-hour timeout
for API connections and a 3-minute timeout for JDBC driver connections.
Note: If you change the timeout value in the properties file while Integration
Composer is running, that change will not take effect until you restart Integration
Composer. That is why you might prefer to have one timeout value that works for
both API and JDBC driver connections.
To modify the fusion.properties file and change the timeout value:

application.
2. Edit the file installation_dir\data\properties\fusion.properties.
3. Change the value of the mxe.db.queryTimeoutSeconds property to 180, or to
another timeout value of your choice.
4. Save the file.
5. Restart Integration Composer to activate your property change.
[SSL users only] Copying the jssecacerts.cert file

In order to enable Secure Sockets Layer (SSL) connections between Integration
Composer and TADDM, you must copy the jssecacerts.cert file from the TADDM
server to the server where Integration Composer is installed.
If you are using SSL, copy the certificate file, jssecacerts.cert, from the TADDM
server, by following these steps:
1. From the server where Integration Composer is installed, point a Web browser
to the TADDM server at port 9430. For example: http://hostname:9430.
2. Make sure the status of all the TADDM components is green, which means
“started.”
3. Click Show SSL Options.
4. Click Download Trust Store.

5. Save the file jssecacerts.cert in the etc folder in the Integration Composer
Determining your connection parameters

This section explains how to determine what parameters to use when setting up
connection information for Integration Composer.
During the integration adapter installation process, you must define database
connections for the target Maximo database and for the source TADDM server in
Integration Composer. The following tables list the default values used for the
Maximo database (in CCMDB) and TADDM connection parameters when you
install CCMDB and TADDM. If you do not use the default values, you must
substitute the values that you do use when you define connection parameters for
your source and target.
Obtain the values appropriate for your installations before you attempt to set up
this adapter. You will need them when you supply connection parameters to
Integration Composer—a required step when you define data schemas and
mappings.
Table 3. Connection parameters for the Maximo database.
Parameter DB2 default Oracle default SQL Server default Comments
Database host name Host name for the Maximo database server.
Database port 50000 1521 1433 Port number for the Maximo database server.
Database name maxdb71 maxdb71 maxdb71 Name of the Maximo database server.
Database instance ctginst1
Database user maximo maximo maximo Maximo database user ID.
Database password Maximo database user password. No value is
assigned on installation. Check with your database
administrator to obtain this value.
Table 4. Connection parameters for the TADDM server.

Parameter DB2 default Oracle default SQL Server default Comments
Host name Host name for the TADDM server (not the
database).
Port 9530 9530 9530 Port for the TADDM server. If using SSL, the
default value is 9531.
User Name administrator administrator Default administrator account automatically created
by TADDM.
User Password collation collation collation Password for the TADDM user ID.
Install the integration adapter for TADDM

The sections that follow describe how to install the integration adapter for
TADDM. Do the tasks in the order presented.
Copying the database and qualifier scripts to the Integration

Composer server or CCMDB database server
As part of the integration adapter setup process, you need to copy the
adapter-provided database and qualifier scripts to a location where you can run
them with a database query tool. Typically this location would be the Integration
Composer server or the CCMDB database server. You only need to copy the
database and qualifier scripts that are appropriate for the type of Maximo database
you have (IBM DB2, Oracle, or SQL Server).

To copy the adapter scripts:
1. Copy the appropriate database scripts for CI types and actual CIs to a location of
your choice—somewhere you can run them with a database query tool. Later,
you will have to run these scripts from whatever directory you place them in.
The database scripts for CI types are:
v createTADDM71CITypeDataSchema.db2 (for source data)
v createTADDM71CITypeDataSchema.ora (for source data)
v createTADDM71CITypeDataSchema.sqs (for source data)
The database scripts for actual CIs are:
v createTADDM71ActualCIDataSchema.db2 (for source data)
v createTADDM71ActualCIDataSchema.ora (for source data)
v createTADDM71ActualCIDataSchema.sqs (for source data)
2. Copy the appropriate qualifier scripts for CI types and actual CIs to a location of
your choice—somewhere you can run them with a database query tool. Later,
you will have to run these scripts from whatever directory you place them in.
The qualifier scripts for CI types are:
v qualifierCCMDB71Classification.db2
v qualifierCCMDB71Classification.ora
v qualifierCCMDB71Classification.sqs
The qualifier scripts for actual CIs are:
v qualifierCCMDB71ActualCI.db2
v qualifierCCMDB71ActualCI.ora
v qualifierCCMDB71ActualCI.sqs
Installing the data schema for your TADDM CI type data

Before you can use the integration adapter to create a mapping and migrate data,
you need to install the source data schema for CI type data in the Integration
Composer repository in the Maximo database.
To install the CI type data schema for the TADDM data source, use whichever one
of the following database scripts is appropriate for your Maximo database type.
(These are the database scripts that you copied in “Copying the database and
qualifier scripts to the Integration Composer server or CCMDB database server” on
page 16.)
v createTADDM71CITypeDataSchema.db2
v createTADDM71CITypeDataSchema.ora
v createTADDM71CITypeDataSchema.sqs
To install the data schema, complete the following steps:

1. Using the appropriate database query tool, execute the database script for your
source data.
2. Check for database script errors and resolve any errors. For error information,
refer to the log files located in the log folder in your Windows or UNIX
Installing the data schema for your TADDM actual CI data

you need to install the source data schema for actual CI data in the Integration

To install the actual CI data schema for the TADDM data source, use whichever
one of the following database scripts is appropriate for your Maximo database
type. (These are the database scripts that you copied in “Copying the database and
qualifier scripts to the Integration Composer server or CCMDB database server” on
page 16.)
v createTADDM71ActualCIDataSchema.db2
v createTADDM71ActualCIDataSchema.ora
v createTADDM71ActualCIDataSchema.sqs
To install the data schema, complete the following steps.

1. Using an appropriate database query tool, execute the database script for your
source data.
Copying the schema and mapping files to the Integration

Composer server
As part of the integration adapter setup process, you need to copy the
adapter-provided schema and mapping files to the appropriate Integration
Composer installation directories on the Integration Composer server.
To copy the adapter files to the Integration Composer installation directories:

1. Copy the schema files for CI types and actual CIs to installation_dir\data\
dataschema (where installation_dir is the directory where Integration Composer
was installed).
The schema file for CI types is:
v CCMDB71Classification.schm (for target data)
The schema file for actual CIs is:
v CCMDB71ActualCI.schm (for target data)
Note: You can put the schema (.schm) files in another location; however, when
you import it into Integration Composer, you will have to browse to that
location and select the file. By default, Integration Composer automatically
looks for the .schm files in the dataschema folder.
2. Copy the mapping file for actual CIs to installation_dir\data\mappings (where
installation_dir is the directory where Integration Composer was installed).
The mapping file for CI types is:
v TADDM71CITypeToCCMDB71Classification.fsn
The mapping file for actual CIs is:
v TADDM71ActualCIToCCMDB71ActualCI.fsn
Note: You can put these files in another location; however, when you import
the files into Integration Composer, by default, Integration Composer looks for
them in the mappings folder. If you put the files in a different location, you
will have to browse to that location and select the files.

Defining a data source connection for your TADDM CI type
data
This section explains the task of defining how Integration Composer connects to a
data source. Follow the steps in this section if you installed your data schema
using a database script, as described previously.
Integration Composer uses an API or JDBC driver to connect to data sources. Use
the IBM Configuration Discovery and Tracking API when connecting to the source
data for TADDM. After you define the connection parameters, Integration
Composer saves them in its repository and displays them whenever you attempt to
connect to that data source.
To define a data source connection, complete the following steps:

1. Sign in to Integration Composer using a valid user ID and password. The IBM
Tivoli Integration Composer window is displayed.
2. Select Define New Data Source. The Data Schema page is displayed in the
Define a New Data Source window. The Data Schema page lists data schemas
that were installed with Integration Composer plus any data schemas that you
created using database scripts or the data schema feature in Integration
Composer.
3. Select the TADDM CI Type data schema and click Next. The Data Source page
is displayed.
4. In the Data Source field, type a name for the data source. The name must have
at least two characters and is case sensitive. For example, type
TADDM-71x-CI-Types. Then click Next. The connection information fields are
displayed.
5. In the Connection Method drop-down list, select a connection method. If you
are connecting to a TADDM data source, you must select the Configuration
Discovery and Tracking API for your connection method.
6. Type in the connection parameters, as required. The connection method that
you selected in step 5 determines the fields that Integration Composer displays.
For information about default values for these fields, refer to “Determining
your connection parameters” on page 16. For example, your settings might look
something like this:
Connection Method: IBM Configuration Discovery and Tracking API
Host Name: taddm_host.tiv.austin.ibm.com

Host Port: 9530
Use SSL:
Trusted Location:
User Name: administrator
Password: ********
The following table lists all the fields that Integration Composer can display.
You may see fewer fields, depending on your connection method.
Table 5. Connection information fields
Field Description
Host Name Host name for the data source.
For the Configuration Discovery and Tracking API, this field

represents the host name of the server on which the IBM
Configuration Discovery and Tracking Server is installed.

Table 5. Connection information fields (continued)
Field Description
Host Port Port for the data source.
Host SID Session identifier for the host (that is, the database instance name).
Database Database name for the data source.
User Name Database user name for the data source.

represents the user identifier to access IBM Configuration Discovery
and Tracking.
Password Database password for the data source.

represents the password associated with the user login account.
Table Owner Data schema name or database schema owner.
Trusted Location Fully qualified path of the SSL certificate file to use to connect to a
server such as the Configuration Discovery and Tracking server. For
example, on Windows operating systems:
c:\Integration Composer\...\jssecacerts.cert
Use SSL Check box that specifies whether the connection is an SSL (Secure
Socket Layer) connection. If you select this check box, you must
enter a value in the Trusted Location field.
URL URL address to access a database instance.
7. Optional: If appropriate, click Test Connection to test the connection to the

data source. Integration Composer displays a Test Connection dialog box. The
text in the dialog box indicates whether the test was successful. To respond to
the dialog box, select one of the following options:
v If Integration Composer establishes a connection, it displays a confirmation
message. Click OK. Integration Composer closes the Test Connection dialog
box. Go to step 8.
v If Integration Composer cannot establish a connection, it displays an
explanatory message. Click OK. Integration Composer closes the Test
Connection dialog box. Review the values for the connection parameters and
retry the connection.
Note: Test Connection verifies only the host name and port, without invoking
underlying Integration Composer processes. Upon finishing, it is still possible
to receive save errors that are unrelated to this connection information. (JDBC
drivers that do not comply with JDBC 2.0 probably do not support this
feature.)
8. On the Connection Information page, click Finish. Integration Composer
displays a Save dialog box.
9. Click OK. Integration Composer returns you to the IBM Tivoli Integration
Composer window.
Note: If Integration Composer does not save the data source successfully, it
displays one or more error messages. Click OK. Integration Composer closes
the error message dialog box. Resolve any errors and try defining the data
source again. For error information, refer to the log files located in the log
folder in your Windows or UNIX installation directory.

Note that in an Integration Composer session, if you connect to one of the defined
data sources, Integration Composer keeps the data source connection open
throughout the session unless you complete one of the following steps:
v Run a mapping for the data source.
v Use the Close Data Source Connection option in the Data Source menu in the
IBM Tivoli Integration Composer window to close the connection.
v Delete the open data source.
Defining a data source connection for your TADDM actual CI

data
This section explains the task of defining how Integration Composer connects to a
data source. Follow the steps in this section if you installed your data schema
using a database script, as described previously.
To define a data source connection, complete the following steps:

1. Sign in to Integration Composer using a valid user ID and password. The IBM
Tivoli Integration Composer window is displayed.
2. Select Define New Data Source. The Data Schema page is displayed in the
Define a New Data Source window. The Data Schema page lists data schemas
that were installed with Integration Composer plus any data schemas that you
created using database scripts or the data schema feature in Integration
Composer.
3. Select the TADDM 7.1 Actual CI data schema and click Next. The Data Source
page is displayed.
4. In the Data Source field, type a name for the data source. The name must have
at least two characters and is case sensitive. For example, type
TADDM-71x-Actual-CIs. Then click Next. The connection information fields are
displayed.
5. In the Connection Method drop-down list, select a connection method. If you
are connecting to a TADDM data source, you must select the Configuration
Discovery and Tracking API for your connection method.
you selected in step 5 determines the fields that Integration Composer displays.
For information about default values for these fields, refer to “Determining
your connection parameters” on page 16. For example, your settings might look
something like this:
Connection Method: IBM Configuration Discovery and Tracking API
Host Name: taddm_host.tiv.austin.ibm.com

Host Port: 9530
Use SSL:
Trusted Location:
User Name: administrator
Password: ********
Table 5 on page 19 lists all the fields that Integration Composer can display. You
may see fewer fields, depending on your connection method.

box. Go to step 8.
Connection dialog box. Review the values for the connection parameters and
retry the connection.
feature.)
8. On the Connection Information page, click Finish. Integration Composer
displays a Save dialog box.
9. Click OK. Integration Composer returns you to the IBM Tivoli Integration
Composer window.
Note: If Integration Composer does not save the data source successfully, it
displays one or more error messages. Click OK. Integration Composer closes
the error message dialog box. Resolve any errors and try defining the data
source again. For error information, refer to the log files located in the log
folder in your Windows or UNIX installation directory.
Note that in an Integration Composer session, if you connect to one of the defined
data sources, Integration Composer keeps the data source connection open
throughout the session unless you complete one of the following steps:
v Run a mapping for the data source.
v Use the Close Data Source Connection option in the Data Source menu in the
IBM Tivoli Integration Composer window to close the connection.
v Delete the open data source.
Installing the data schema for CCMDB CI type data

you need to install the data schema for target CI type data in the Integration
Important: If at any time after installing a target data schema you change your
Maximo database definition (for example, you change the length of an attribute),
re-open the target data schema in Integration Composer and synchronize it with
the Maximo database definition. If Integration Composer finds any discrepancies
between the two, you will be presented with a Data Schema Analysis window that
gives you the opportunity to synchronize them (by clicking Fix Errors). Otherwise,
the target data schema defined in Integration Composer and the Maximo database
might no longer match.
To install the data schema, use the CI type data file that the integration adapter
provides, CCMDB71Classification.schm.

1. If you are not already signed in, sign in to Integration Composer using a valid
user ID and password. The IBM Tivoli Integration Composer window is
displayed.

2. From the IBM Tivoli Integration Composer window, select Define New Data
Schema. Integration Composer displays the Data Schema field on the Define
a New Data Schema window.
Note: To review or change previous selections, click Back. To cancel this

procedure and return to the main Integration Composer window, click Cancel.
3. In the Data Schema field, type CCMDB71Classification as the name of the new
data schema (data schema names are case sensitive).
Note: You can type a different name for the new data schema. However, if
you do, you will have to change the name CCMDB71Classification in the
qualifier script (that you run in “Loading the class qualifiers into the target CI
type data schema” on page 32) in order to match the alternative name that
you typed here.
4. Click Next. The Data Source field is displayed.
5. In the Data Source field, type the name you want to use to identify the data
source. The name must have at least two characters and is case sensitive. For
example, type CCMDB71x-Classification. Then click Next. The connection
information fields are displayed.
6. In the Connection Method drop-down list, select one of the available JDBC
drivers as the connection method to your target Oracle, SQL, or DB2 database
(the Maximo database).
you selected in step 6 determines the fields that Integration Composer
displays. For information about default values for these fields, refer to
“Determining your connection parameters” on page 16. For example, your
settings might look something like this:
Connection Method: Oracle JDBC Thin Driver
Host Name: maximo_host.tiv.austin.ibm.com

Host Port: 1521
Host SID: maximo
User Name: maximo
Password: ********
Table Owner: maximo
The following table lists all the fields that Integration Composer can display.
Table 6. Connection information fields
Field Description
Host Name Host name for the data source.
For the Configuration Discovery and Tracking API, the host name of
the server on which the IBM Configuration Discovery and Tracking
Server is installed.
Host Port Port for the data source.
Host SID Session identifier for the host (that is, the database instance name).
Database Database name for the data source.
User Name Database user name for the data source.
For the Configuration Discovery and Tracking API, the user

identifier to access IBM Configuration Discovery and Tracking.

Table 6. Connection information fields (continued)
Field Description
Password Database password for the data source.
For the Configuration Discovery and Tracking API, , the password

associated with the user login account.
Table Owner Data schema name or database schema owner.
Trusted Location Fully qualified path of the SSL certificate file to use to connect to a
server such as the Configuration Discovery and Tracking server. For
example, on Windows operating systems:
c:\Integration Composer\...\jssecacerts.cert
Use SSL Check box that specifies whether the connection is an SSL (Secure
Socket Layer) connection. If you select this check box, you must
enter a value in the Trusted Location field.
URL URL address to access a database instance.

box. Go to step 9.
Connection dialog box. Review the values for the connection parameters
and retry the connection.
feature.)
9. On the Connection Information page, click Finish. The Data Schema window
is displayed. Integration Composer displays the root class in red because it
has no properties associated with the class.
Note: The display properties that you set for your computer can affect colors.
The color displayed on your computer can vary.
From this window, you can import a data schema file provided with this
integration adapter.
10. To import the data schema file provided with the integration adapter, from the
Select Action menu in the title bar of the Data Schema window, select Import
Data Schema. The Import Data Schema dialog box is displayed. The Import
Data Schema dialog box lists the data schemas that you copied to the
dataschema folder.
11. In the Import Data Schema dialog box, select the data schema file that you
want to import.. For CI type target data, select:
CCMDB71Classification.schm
Integration Composer populates the File name field with the selected file
name.

12. Click Open. Integration Composer imports the data schema file. If
discrepancies exist between the data source and the data schema, the Data
Schema Analysis window is displayed.
This window lists discrepancies between the data schema and the
corresponding data source. Integration Composer displays errors that it can
correct with a green check.
You can use this window to correct the following discrepancies:
v Case of a table name in the database does not match that of a table
associated with a class in the data schema.
v Case of a column name in the database does not match that of a table
column associated with a class table in the data schema.
v Length of a table column in the database does not match length of the same
column in the data schema.
v Data type of a table column in the database does not match the type of the
same column in the data schema.
13. Review the errors in the Data Schema Analysis window and select one of the
following options:
v To repair the errors, click Fix Errors. Integration Composer repairs the
errors and opens the Data Schema window. Go to step 14.
Note: You cannot clear the check boxes. You can either fix all errors
indicated or fix no errors.
v To expand all nodes in the tree to display information about inconsistencies
between the data schema and the data source, click Expand All.
v To view statistics for table and column errors, click Statistics.
v To close the dialog box without repairing the errors, click Close. A Data
Schema Analysis warning window is displayed. In the Data Schema
Analysis warning window, select one of the following options:
– To make the data schema match the source database, complete the
following steps:
a. In the Data Schema Analysis warning window, click Yes. Integration
Composer repairs the errors, closes the warning window, closes the
Data Schema Analysis window, and displays an Import dialog box
indicating that the import is finished.
b. In the Import dialog box, click OK. The Data Schema window is
displayed. Go to step 14.
– To close the window without changing the data schema, click No.
Integration Composer imports the data schema as is and displays the
Data Schema window. Go to step 14.
– To cancel the action, click Cancel. Integration Composer closes the
warning window and displays the Data Schema Analysis window. Go to
step 12. Review the options in this window and select the appropriate
action.
14. After you import the data schema file, you can modify the data schema. For
more information about working with data schemas, see the book IBM Tivoli
Integration Composer Administrator Guide or see the Integration Composer help.
15. After you finish working with the data schema, select Save from the Select
Action menu. Integration Composer saves the data schema.
16. Select Close from the Select Action menu to close the data schema.
Integration Composer closes the data schema and displays the IBM Tivoli
Integration Composer window.

Installing the data schema for your CCMDB actual CI data
you need to install the data schema for target actual CI data in the Integration
To install the data schema, use the actual CI data file that the integration adapter
provides, CCMDB71ActualCI.schm.

1. If you are not already signed in, sign in to Integration Composer using a valid
user ID and password. The IBM Tivoli Integration Composer window is
displayed.
2. From the IBM Tivoli Integration Composer window, select Define New Data
Schema. Integration Composer displays the Data Schema field on the Define
a New Data Schema window.
Note: To review or change previous selections, click Back. To cancel this

procedure and return to the main Integration Composer window, click Cancel.
3. In the Data Schema field, type CCMDB71ActualCI as the name of the new data
schema (data schema names are case sensitive).
Note: You can type a different name for the new data schema. However, if
you do, you will have to change the name CCMDB71ActualCI in the qualifier
script (that you run in “Loading the class qualifiers into the target CI type
data schema” on page 32) in order to match the alternative name that you
typed here.
4. Click Next. The Data Source field is displayed.
5. In the Data Source field, type the name you want to use to identify the data
source. The name must have at least two characters and is case sensitive. For
example, type CCMDB71x-ActualCI. Then click Next. The connection
information fields are displayed.
6. In the Connection Method drop-down list, select one of the available JDBC
drivers as the connection method to your target Oracle, SQL, or DB2 database
(the Maximo database).
you selected in step 6 determines the fields that Integration Composer
displays. For information about default values for these fields, refer to
“Determining your connection parameters” on page 16. For example, your
settings might look something like this:
Connection Method: Oracle JDBC Thin Driver
Host Name: maximo_host.tiv.austin.ibm.com

Host Port: 1521
Host SID: maximo
User Name: maximo
Password: ********
Table Owner: maximo
Table 6 on page 23 lists all the fields that Integration Composer can display.

box. Go to step 9.
Connection dialog box. Review the values for the connection parameters
and retry the connection.
feature.)
9. On the Connection Information page, click Finish. The Data Schema window
is displayed. Integration Composer displays the root class in red because it
has no properties associated with the class.
Note: The display properties that you set for your computer can affect colors.
The color displayed on your computer can vary.
From this window, you can import a data schema file provided with this
integration adapter.
10. To import the data schema file provided with the integration adapter, from the
Select Action menu in the title bar of the Data Schema window, select Import
Data Schema. The Import Data Schema dialog box is displayed. The Import
Data Schema dialog box lists the data schemas that you copied to the
dataschema folder.
11. In the Import Data Schema dialog box, select the data schema file that you
want to import. For actual CI target data, select:
CCMDB71ActualCI.schm
Integration Composer populates the File name field with the selected file
name.
12. Click Open. Integration Composer imports the data schema file. If
discrepancies exist between the data source and the data schema, the Data
Schema Analysis window is displayed.
This window lists discrepancies between the data schema and the
corresponding data source. Integration Composer displays errors that it can
correct with a green check.
You can use this window to correct the following discrepancies:
v Case of a table name in the database does not match that of a table
associated with a class in the data schema.
v Case of a column name in the database does not match that of a table
column associated with a class table in the data schema.
v Length of a table column in the database does not match length of the same
column in the data schema.
v Data type of a table column in the database does not match the type of the
same column in the data schema.
13. Review the errors in the Data Schema Analysis window and select one of the
following options:
v To repair the errors, click Fix Errors. Integration Composer repairs the
errors and opens the Data Schema window. Go to step 14 on page 28.

Note: You cannot clear the check boxes. You can either fix all errors
indicated or fix no errors.
v To expand all nodes in the tree to display information about inconsistencies
between the data schema and the data source, click Expand All.
v To view statistics for table and column errors, click Statistics.
v To close the dialog box without repairing the errors, click Close. A Data
Schema Analysis warning window is displayed. In the Data Schema
Analysis warning window, select one of the following options:
– To make the data schema match the source database, complete the
following steps:
a. In the Data Schema Analysis warning window, click Yes. Integration
Composer repairs the errors, closes the warning window, closes the
Data Schema Analysis window, and displays an Import dialog box
indicating that the import is finished.
b. In the Import dialog box, click OK. The Data Schema window is
displayed. Go to step 14.
– To close the window without changing the data schema, click No.
Integration Composer imports the data schema as is and displays the
Data Schema window. Go to step 14.
– To cancel the action, click Cancel. Integration Composer closes the
warning window and displays the Data Schema Analysis window. Go to
step 12 on page 27. Review the options in this window and select the
appropriate action.
14. After you import the data schema file, you can modify the data schema. For
more information about working with data schemas, see the book IBM Tivoli
Integration Composer Administrator Guide or see the Integration Composer help.
15. After you finish working with the data schema, select Save from the Select
Action menu. Integration Composer saves the data schema.
16. Select Close from the Select Action menu to close the data schema.
Integration Composer closes the data schema and displays the IBM Tivoli
Integration Composer window.
Creating a mapping for your TADDM-to-CCMDB CI type data

Before you can migrate CI type data, you must create a new adapter mapping for
the data you want to migrate and then import the appropriate mapping file
(TADDM71CITypeToCCMDB71Classification.fsn) into the mapping that you create.
Attention: If you import a mapping into a mapping that contains expressions, the
imported mapping has the following effect on the original mapping:
v If an expression exists in both mappings, Integration Composer replaces the
existing expression with the imported expression.
v Integration Composer adds any new expressions in the imported mapping to the
original mapping.
Before creating your mapping, make sure you have installed the data schemas for
both your source and target CI type data, in accordance with the instructions in
Table 2 on page 11.
To create a mapping, complete the following steps:

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

2. Select Create New Mapping. The New Mapping window is displayed.
3. From the Source drop-down list of available data sources, select the TADDM
data source.
4. From the Target drop-down list of available data sources, select the CCMDB
target data source.
5. In the Mapping Name field, type a new mapping name; for example, type
TADDM-2-CCMDB-4-CI-Types. Mapping names can be no longer than 255
characters and are case sensitive (that is, CI-Types is not the same as
ci-types).
6. Click OK, and select one of the following options:
v If Integration Composer opens the Mapping window, go to step 7.
v If Integration Composer opens the connection information fields in the
Open Source Data Source window, use the following procedure to complete
the connection information:
a. In the Open Source Data Source window, accept the defaults established
during the last connection to the data source or update the fields.
b. Enter the password for accessing your source data. (Database users enter
a database password, Configuration Discovery and Tracking API users
enter a password associated with the user login account).
c. Click Finish to establish the connection to the source.
d. 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.
e. Enter the (database or user login account) password for accessing your
target data.
f. Click Finish to establish the connection to the target.
Integration Composer opens the Mapping window.
7. From the Select Action menu in the Integration Composer Mapping window,
select Import. The Import Mapping dialog box is displayed.
Note: When you select Import from the Select Action menu, by default,
Integration Composer points to the mappings folder. If you store 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.
8. In the Import Mapping dialog box, select the mapping file for CI type data,
TADDM71CITypeToCCMDB71Classification.fsn. Integration Composer
populates the File name field with the selected file name.
9. Click Open. Integration Composer imports the mapping file.
Note: If errors occur when you import the mapping, Integration Composer
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:
v Click No to cancel the import action without importing the mapping.
Integration Composer closes the dialog box and does not import the
mapping.
v Click Yes to continue to import the mapping. Integration Composer imports
the mapping and displays errors in red. Resolve the errors before saving the
mapping.
If appropriate, you can modify the mapping. Note that if you install
Integration Composer using a language other than English, you must change
the langcode property in any adapter mappings that you create to the

appropriate language for your installation. For more information about
performing this task, refer to “Modifying language properties” on page 37.
For more information about how to work with mappings, see the book IBM
Tivoli Integration Composer Administrator Guide.
10. After you finish the mapping, select one of the following options:
v To save the mapping with the existing name, select Save from the Select
Action menu.
v To save the mapping with a new name, select Save As from the Select
Action menu. Integration Composer opens a Save Mapping As window. In
the Mapping Name field in this window, type a new name for the mapping
and click OK. Integration Composer saves your changes with the new
mapping name.
For example, if you open mapping A and save it as B, Integration
Composer saves your changes as mapping B and keeps mapping B open for
editing. Mapping A remains in its original form.
11. To close the Mapping window, select Close from the Select Action menu. A
Close Mapping dialog box is displayed.
12. In the Close Mapping dialog box, click Yes. Integration Composer closes the
Mapping window and displays the IBM Tivoli Integration Composer window.
13. Sign out of Integration Composer.
[Optional] Modifying the mapping expressions

If appropriate, you can modify your mapping expressions to suit your business
needs.
For instructions about how to modify mapping expressions, see the book IBM
If you install Integration Composer using a language other than English, you must
change the langcode property in any adapter mappings that you create to the
appropriate language for your installation (for instructions, see “Modifying
language properties” on page 37).
Creating a mapping for your TADDM-to-CCMDB actual CI data

Before you can migrate actual CI data, you must create a new adapter mapping for
the data you want to migrate and then import the appropriate mapping file
(TADDM71ActualCIToCCMDB71ActualCI.fsn) into the mapping that you create.
Before creating your mapping, make sure you have installed the data schemas for
both your source and target actual CI data, in accordance with the instructions in
Table 2 on page 11.
To create a mapping, complete the following steps:

1. Sign in to the Integration Composer application using a valid user ID and
password. Integration Composer displays the IBM Tivoli Integration
Composer window.
2. Select Create New Mapping. The New Mapping window is displayed.
3. From the Source drop-down list of available data sources, select the TADDM
data source.
4. From the Target drop-down list of available data sources, select the CCMDB
target data source.

5. In the Mapping Name field, type a new mapping name; for example, type
TADDM-2-CCMDB-4-Actual-CIs. Mapping names can be no longer than 255
characters and are case sensitive (that is, Actual-CIs is not the same as
actual-cis).
6. Click OK, and select one of the following options:
v If Integration Composer opens the Mapping window, go to step 7.
v If Integration Composer opens the connection information fields in the
Open Source Data Source window, use the following procedure to complete
the connection information:
a. In the Open Source Data Source window, accept the defaults established
during the last connection to the data source or update the fields.
b. Enter the password for accessing your source data. (Database users enter
a database password, Configuration Discovery and Tracking API users
enter a password associated with the user login account).
c. Click Finish to establish the connection to the source.
d. 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.
e. Enter the (database or user login account) password for accessing your
target data.
f. Click Finish to establish the connection to the target.
Integration Composer opens the Mapping window.
7. From the Select Action menu in the Integration Composer Mapping window,
select Import. The Import Mapping dialog box is displayed.
Note: When you select Import from the Select Action menu, by default,
Integration Composer points to the mappings folder. If you store 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.
8. In the Import Mapping dialog box, select the mapping file for actual CI data,
TADDM71ActualCIToCCMDB71ActualCI.fsn. Integration Composer populates
the File name field with the selected file name.
9. Click Open. Integration Composer imports the mapping file.
Note: If errors occur when you import the mapping, Integration Composer
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:
v Click No to cancel the import action without importing the mapping.
Integration Composer closes the dialog box and does not import the
mapping.
v Click Yes to continue to import the mapping. Integration Composer imports
the mapping and displays errors in red. Resolve the errors before saving the
mapping.
If appropriate, you can modify the mapping. Note that if you install
Integration Composer using a language other than English, you must change
the langcode property in any adapter mappings that you create to the
appropriate language for your installation. For more information about
performing this task, refer to “Modifying language properties” on page 37.
For more information about how to work with mappings, see the book IBM
10. After you finish the mapping, select one of the following options:

v To save the mapping with the existing name, select Save from the Select
Action menu.
v To save the mapping with a new name, select Save As from the Select
Action menu. Integration Composer opens a Save Mapping As window. In
the Mapping Name field in this window, type a new name for the mapping
and click OK. Integration Composer saves your changes with the new
mapping name.
For example, if you open mapping A and save it as B, Integration
Composer saves your changes as mapping B and keeps mapping B open for
editing. Mapping A remains in its original form.
11. To close the Mapping window, select Close from the Select Action menu. A
Close Mapping dialog box is displayed.
12. In the Close Mapping dialog box, click Yes. Integration Composer closes the
Mapping window and displays the IBM Tivoli Integration Composer window.
[Optional] Modifying your mapping expressions

If appropriate, you can modify your mapping expressions to suit your business
needs.
For instructions about how to modify mapping expressions, see the book IBM
If you install Integration Composer using a language other than English, you must
change the langcode property in any adapter mappings that you create to the
appropriate language for your installation (for instructions, see “Modifying
language properties” on page 37).
Loading the class qualifiers into the target CI type data

schema
After you create a mapping, load the class qualifiers into the target CI type data
schema using a qualifier script.
The class qualifiers in the qualifier scripts allow Integration Composer to delete
certain class records, in addition to merely inserting and updating them, when
executing a mapping. Specifically, the qualifier scripts add a delete_insert qualifier
on the some of the classes in the Classification schema. The delete_insert qualifier
informs Integration Composer which classes it should delete instances from if they
are not found during a mapping execution. So, whenever the following are true:
v An instance in CCMDB was inserted on a prior run but on a subsequent run it
no longer exists in TADDM
v The class in question has this qualifier
then the corresponding instance in CCMDB is deleted. Thus, by loading the class
qualifiers, you are modifying the way Integration Composer handles data when it
performs a data import.
Important: If you import a data schema, change it, and export it to another file,
and then reimport the file to a data schema with a different name, you must also
rerun the qualifier script. Before you run the qualifier script, you must change the
name in the script to the name of your new data schema. In other words, each
time that you create a new data schema, you must run a qualifier script for that
data schema before you can use it to execute a mapping.

To perform this task, use whichever one of the following qualifier scripts is
appropriate for your Maximo database type. (These are the qualifier scripts that
you copied in “Copying the database and qualifier scripts to the Integration
Composer server or CCMDB database server” on page 16.)
v qualifierCCMDB71Classification.db2
v qualifierCCMDB71Classification.ora
v qualifierCCMDB71Classification.sqs
To load the class qualifiers into the data schema, complete the following steps:
1. Sign out of Integration Composer, if you have not already done so.
2. Optional: If you named the new data schema something other than
CCMDB71Classification in step 3 on page 23, change the name
CCMDB71Classification in the qualifier script to match the alternative name that
you provided.
3. Using an appropriate database query tool, run the qualifier script for your
target data.
Loading the class qualifiers into the target actual CI data

schema
After you create a mapping, you can load the class qualifiers into the target actual
CI data schema using a qualifier script.
To perform this task, use whichever one of the following qualifier scripts is
appropriate for your Maximo database type. (These are the qualifier scripts that
you copied in “Copying the database and qualifier scripts to the Integration
Composer server or CCMDB database server” on page 16.)
v qualifierCCMDB71ActualCI.db2
v qualifierCCMDB71ActualCI.ora
v qualifierCCMDB71ActualCI.sqs
To load the class qualifiers into the data schema, complete the following steps:
1. Sign out of Integration Composer, if you have not already done so.
2. Optional: If you named the new data schema something other than
CCMDB71ActualCI in step 3 on page 26, change the name CCMDB71ActualCI in the
qualifier script to match the alternative name that you provided.
3. Using an appropriate database query tool, run the qualifier script for your
target data.
Verify your CI classifications

The section that follows describes part of the Maximo installation procedure. The
task is noted here so that you can verify that it was completed. If you did not
create the classification and identifier as described below, the process of importing
CI type or actual CI data will fail. So be sure to verify that the task was completed,
or if not, do it now.

Creating a top-level CI class and class structure identifier
To enable the mappings in this integration adapter work correctly, a classification
must be created for the top-level (root) CI class, and a CI class structure identifier
must be created as well.To do so, you need to work with the Classifications and
Organizations applications, which are part of the Maximo Console user interface
for CCMDB 7.1.1.
To ensure that there is a top-level CI classification and a class structure

identifier for the top-level CI class, do the following steps:
1. Create a top-level CI classification, as follows:
a. Sign in to the Maximo Console user interface, select Go To >
Administration > Classifications.
b. On the Classifications application toolbar, click the New Classification icon.
c. In the Classification field, type a classification. If the classification does not
already exist, you receive the message: XXX is not a valid
classification. Would you like to add it? Click Yes.
d. In the field to the right of the Classification field, enter a description for the
new classification.
e. [Optional] Select an organization and a site. If you want to make this
classification available for every organization and site, leave the
Organization and Site fields blank.
f. In the Use With table window, click New Row.
g. To specify that you want to use the classification with configuration items,
in the Use With Object field, click Select Value and select CI.
h. Select the Top-Level? checkbox, which specifies that this is a top-level (root)
object.
i. Click Save Classification.
2. Make sure that a class structure identifier is defined for the top-level CI class,
as follows:
a. Select Go To > Administration > Organizations.
b. From the Select Action menu in the Organizations application, select System
Settings.
c. In the IT Options table window in the Systems Settings dialog box, check
that the CI Top-Level Class field displays the top-level class for CIs and
that a corresponding class structure identifier is displayed in the CI Class
Structure ID field
d. If there is no top-level class, in the CI Top-Level Class field, click the Detail
Menu and select Classify. If necessary, you can select Clear Classification
to clear the value displayed and then select Classify.
e. In the Classify dialog box, select the top-level asset class for CIs by clicking
the blue square to the left of the classification name. The application closes
the Classify dialog box and populates the CI Top-Level Class field.
Note: In the CI Class Structure ID field, you can use the Detail Menu to
navigate to the Classifications application to view additional information
about the class. You can also select a classification and return that value to
the CI Class Structure ID field. The application updates the CI Top-Level
Class field with the appropriate class.
f. Click OK to save the settings and close the dialog box.

The class structure ID that is displayed is an actual value stored in the database. If
the classifications structure changes such that the CI Top-Level Class no longer
exists at the same place in the hierarchy, the CI Class Structure ID field will
remain populated, but the CI Top-Level Class field will be blank or show the
wrong class. Consequently, if the classification is moved within the classification
structure, or deleted and re-added, you must repeat this procedure to update the
class structure ID.
Important: If you do not create the classification and identifier described in this
section, the subsequent import process will stop without warning. No error
messages are provided.
Import your data

The sections that follow describe repeatable tasks that you can perform in the
production environment after the integration adapter for TADDM is installed. They
are noted in this book for your convenience.
Executing your mapping for CI types

When you create a mapping, you define a set of expressions that specify how to
transform instances from the TADDM data source to the target Maximo database
in CCMDB. To transform the TADDM data and import it into the Maximo
database, you must execute the mapping. This section describes how to execute
your mapping for CI types from the Integration Composer command line interface.
To execute the mapping, you can run a script that provides all the parameter
values inside the file, or you can enter a detailed command that provides all the
required parameter values directly on the command line. For this task, the detailed
command is used. The commandLine command runs the script unedited, and you
supply all the values in the command rather than in the script.
To execute your mapping for CI types, do the following steps:

1. Close Integration Composer, if running.
2. Go to the bin subdirectory in your Integration Composer installation directory,
installation_dir\bin.
3. Enter the following command. Type the parameter values in the same order as
they appear in the example. UNIX users must specify ./commandLine.sh
instead of commandLine as the command name. To view the full syntax and
parameter descriptions for this command, see “Using values specified on the
command line” on page 56.
commandLine TADDM-2-CCMDB-4-CI-Types maximo your_maximo_password
administrator your_user_password maximo your_maximo_password
See Appendix B, “Executing a mapping,” on page 53 for more information about

all the options for, and ways to use, the commandLine command.
Activating CI types
Because CI types must be set up in CCMDB before you can import actual CI data,
check the CI Types application in CCMDB to verify that CI types have been
activated appropriately.
To verify active status or activate a CI type:

1. Sign in to the Maximo Console user interface, and select Go To >
Administration > CI Types.

2. Find SYS.COMPUTERSYSTEM.
3. If the CI Type Status for SYS.COMPUTERSYSTEM is not ACTIVE, click the status
change icon to activate it. When the task completes, the message line will
indicate status changed to ACTIVE for the CI type.
Note: The instructions provided above were the latest available at publication
time. To ensure you have the most current information possible, refer to the online
help for the CI Types application in CCMDB.
Executing your mapping for actual CIs

This section describes how to execute your mapping for actual CIs from the
Integration Composer command line interface.
To execute your mapping for actual CIs, do the following steps:

1. Close Integration Composer, if running.
2. Go to the bin subdirectory in your Integration Composer installation directory,
installation_dir\bin.
3. Enter the following command. Type the parameter values in the same order as
they appear in the example. UNIX users must specify ./commandLine.sh
instead of commandLine as the command name. To view the full syntax and
parameter descriptions for this command, see “Using values specified on the
command line” on page 56.
commandLine TADDM-2-CCMDB-4-Actual-CIs maximo your_maximo_password
administrator your_user_password maximo your_maximo_password
See Appendix B, “Executing a mapping,” on page 53 for more information about

all the options for, and ways to use, the commandLine command.
Viewing log file information

A log file is available for viewing information about mapping results and any
errors that are generated when you run a mapping.
Integration Composer maintains information about mapping results and

compilation errors in the fusion.log file in the log subdirectory in the installation
directory. Whenever Integration Composer executes a mapping, the application
provides information about mapping executions and data transactions as well as
errors in the file. The fusion.log file is stored in the following location (where
installation_dir is the directory where Integration Composer was installed):
installation_dir\log
For more information about setting up Integration Composer logs, refer to the IBM

Chapter 4. Tips for effective mappings
This section offers useful information for special mapping expressions and
suggestions for creating effective mappings in Integration Composer.
Modifying language properties

Because the default language is English, if you install Integration Composer in a
language other than English, you must modify language properties in mappings.
The default value for the langcode properties in the mappings included with this
adapter is English. You must change the langcode property in any adapter
mappings that you create to the appropriate language for your installation. You
effect this change by making a modification to the actual CI or CI type mapping
after you import the mapping into Integration Composer.
If you use a language other than English, you must change the following
properties:
Table 7. The langcode properties in CI type and actual CI mappings.
Mapping Class.property
CI type Classstructure.Langcode
Relation.Langcode
actual CI Actual CI.Langcode
Actual Target CI.Langcode
CMP.Langcode
You must replace the ″EN″ value in the langcode properties with the appropriate
literal value for your installation, for example ″FR″ (including the quotation marks)
for French. The following values are available:
Table 8. The values for langcode properties.
Language Code Language
DE German
ES Spanish
FR French
IT Italian
JA Japanese
KO Korean
NL Dutch
PT Portuguese
SV Swedish
ZH Simplified Chinese
ZHT Traditional Chinese

Mapping data for units of measurement
If your data source (TADDM) uses one unit of measurement and your target
(Maximo database) uses another, you have to create a mapping expression that
compensates for that difference.
Suppose that the value for a property in the source is expressed in kilobytes (KB),
but target values are in megabytes (MB). You need to modify your mapping so that
Integration Composer performs the appropriate calculation to correctly convert the
value from KB to MB. Similarly, when RAM is expressed in kilobytes in the source
and megabytes in the target, you must define an expression in your mapping to
convert KB to MB. In this case, define:
‘RAM.Size(bytes)’/1024
When you execute your mapping, for each instance created in the target,
Integration Composer takes the value from the Size(bytes) property of the class
RAM in the source, divides this value by 1024, and inserts the result into the
appropriate property and class in the target.
For detailed, illustrated steps on how to perform this task, see the book IBM Tivoli
Integration Composer: Administrator Guide.
Mapping data for sites and organizations

The system maintains information based on sites and organizations. Most
discovery tools do not provide scanned data about sites and organizations. If you
want to differentiate computers, network devices, and other information
technology objects by sites or organizations, you specifically must set these values
in your Integration Composer mapping.
To include site or organization data, you can insert literal values for Siteid and
Orgid in the target. Site and organization data is not a requirement, but you can
specify a value for them so that the data is available in the actual CI application
and is also available for the Reconciliation module. Because Integration Composer
does not validate this data, be sure to specify a valid value.
Mapping key properties

When you create a mapping, if a class has only a Generated Key or a Foreign Key,
select one or more properties as Alternate Keys for the class to ensure uniqueness.
Mapping data for scan dates

During its processing of an actual CI mapping, Integration Composer transfers
only the data that has changed since the last scan date. (Note that a CI type
mapping does not store scan dates.)
When Integration Composer processes an actual CI mapping for the first time, it
copies the time stamp of the last scan date for each top-level object in the TADDM
data source into the Integration Composer repository. On subsequent mapping
runs, Integration Composer compares the last scan date in the Integration
Composer repository with the scan date from the TADDM data source and
performs one of the following actions:

v If the last scan in the TADDM data source is the same or earlier than the one in
the Integration Composer repository, Integration Composer skips the TADDM
instance.
v If the last scan in the TADDM data source is the later than the one in the
Integration Composer repository, Integration Composer processes the
expressions for the TADDM instance and updates the last scan date in the
repository.
When Integration Composer performs this operation, it ensures that it transfers

only the data that has changed since the last scan date.
Chapter 4. Tips for effective mappings 39

Chapter 5. Integration adapter mappings for TADDM
Configuration item types
The following table lists the mapping expressions for configuration item (CI) types,
as defined in the integration adapter for IBM Tivoli Application Dependency
Discovery Manager.
Table 9. Mapping table for CI types
CI types IBM Tivoli Application Dependency Discovery Manager
Class name Property <Class Name>.<Property Name>
Key Name
Classification PK Classificationid Class.Classname
GV Classificationuid
Description
Orgid
Siteid
Classstructure PK,GV Classstructureid
AK, FK Classificationid
AK Orgid
AK Parent classstructureid of Class.Parent. If Class.Parent is null then it is set as the classstructureid of
CICLASS
AK Siteid
GV Classstructureuid
Description Class.Classname
Genassetdesc 0
Haschildren Class.Haschildren
Hasld 0
Langcode ″EN″
Type
Useclassindesc 0
Ancestor PK Ancestor case 0:classstructureid of Class.Classname
case 1: classstructureid of CICLASS
case 2:classstructureid of Ancestor.Ancestor
PK,FK Classificationid
PK,FK Classstructureid
Ancestorclassid case 0: Class.Classname
case 1: classificationid of CICLASS
case 2: Ancestor.Ancestor
GV Classancestorid
Hierarchylevels case 0: 0
case 1: Class.Hierarchylevel
case 2: Ancestor.Hierarchylevel
Orgid
Siteid
CIType PK,FK Classstructureid
GV Cdmcitypesid
Createdate
Toplevelci Class.Istoplevel
Iscollection 0
Isfunction 0

Table 9. Mapping table for CI types (continued)
Relation PK,FK Relationnum
Classstructureid classstructureid of Class.Classname
Comprelation
Description
Hasld 0
Imported 1
Langcode ″EN″
Linear 0
GV Relationid
Type UNIDIRECTIONAL from synonymdomain table in maximo
RelationRule PK,FK Relationnum
PK Sourceclass classstructureid of Relation.Sourceclass
PK Targetclass classstructureid of Relation.Targetclass
Cardinality Relation.Cardinality
Containment Relation.Iscontainment
Imported 1
Propagatechange Relation.Propagatechange
GV Relationrulesid
Revrelationship Relation.Reverserelationship
Swapped Relation.Swapped
Specification PK,REF Assetattrid
PK,FK Classstructureid
Applydownhier 0
Assetattributeid
Attrdescprefix
GV Classspecid
Cs01
Cs02
Cs03
Cs04
Cs05
Domainid
Inheritedfrom
Linkedtoattribute
Linkedtosection
Lookupname
Measureunitid
Orgid
Section
Siteid
Tableattribute
AssetAttribute PK Assetattrid Attribute.Attributename
GV Assetattributeid
Attrdescprefix
Datatype Attribute.Type
Description Attribute.Attributename
Domainid
Measureunitid
Orgid

Table 9. Mapping table for CI types (continued)
Siteid
Actual configuration items
The following table lists the mapping expressions for actual CIs, as defined in the
integration adapter for IBM Tivoli Application Dependency Discovery Manager.
Note: The expression <CCMDB 7.1 Actual Target CI.Actciid>, which appears in
multiple places in this table, means that a value from the target data source is used
in the mapping.
Table 10. Mapping table for actual CIs
Actual CIs IBM Tivoli Application Dependency Discovery Manager
Class Name Property <Class Name>.<Property Name>
Key Name
Actual CI PK, GV Actciid

AK Actcinum Actual CI.Label + ″~″ + <CCMDB 7.1 Actual CI.Actciid>
or Actual CI.DisplayName + ″~″ + <CCMDB 7.1 Actual CI.Actciid>
or ″UNAVAILABLE″ + ″~″ + <CCMDB 7.1 Actual CI.Actciid>
AK Classstructureid Actual CI.Classstructureid
AK Guid Actual CI.Guid
Changeby Actual CI.LastModifiedBy
Changedate Actual CI.LastModifiedTime
Description Actual CI.Description
Hasld
Langcode ″EN″
Lastscandt Actual CI.LastModifiedTime
CI Attribute PK, GV Actcispecid

FK, AK Actcinum
FK, AK Classstructureid
AK Assetattrid Source CI Attribute.AttributeName
Alnvalue Source CI Attribute.Value
Changeby Actual CI.LastModifiedBy
Changedate Actual CI.LastModifiedTime
Classspecid Source CI Attribute.ClassSpecId
Displaysequence
Linkedtoattribute
Linkedtosection
Mandatory
Measureunitid Source CI Attribute.MeasureUnitId
Numvalue Source CI Attribute.Value
Refobjectid <CCMDB 7.1 Actual CI.Actciid>
Refobjectname ″ACTCI″
Section
Tablevalue
CI Relationship PK, GV Actcirelationid

FK, AK Sourceci
Chapter 5. Integration adapter mappings for TADDM 43

Table 10. Mapping table for actual CIs (continued)
Ref, AK Targetci
AK Relationnum CI Relationship.Classification
Ancestorci Actual CI.Label + ″~″ + <CCMDB 7.1 Actual CI.Actciid>
or Actual CI.AncestorLabel + ″~″ + <CCMDB 7.1 Actual CI.Actciid>
or Actual CI.AncestorDisplayName + ″~″ + <CCMDB 7.1 Actual CI.Actciid>
Changeby CI Relationship.LastModifiedBy
Changedate CI Relationship.LastModifiedTime
Targetguid CI Relationship.Targetguid
Swapped 0
Actual Target PK, GV Actciid

CI
AK Actcinum Actual Target CI.Label + ″~″ + <CCMDB 7.1 Actual Target CI.Actciid>
or Actual Target CI.DisplayName + ″~″ + <CCMDB 7.1 Actual Target CI.Actciid>
or ″UNAVAILABLE″ + ″~″ + <CCMDB 7.1 Actual Target CI.Actciid>
AK Guid Actual Target CI.Guid
Changeby Actual Target CI.LastModifiedBy
Changedate Actual Target CI.LastModifiedTime
Classstructureid Actual Target CI.Classstructureid
Description Actual Target CI.Description
Hasld
Langcode ″EN″
Lastscandt Actual Target CI.LastModifiedTime
OMP PK, GV Ompcirlnid

Relationship
FK, AK Ciguid
Ref, AK Ompguid
Changeby Source CI MSS.LastModifiedBy
Changedate Source CI MSS.LastModifiedTime
Cisourcetoken Source CI MSS.SourceToken
OMP PK, GV Ompid

AK Ompguid Source CI MSS.MSSGuid
Changeby Source CI MSS.LastModifiedBy
Changedate Source CI MSS.LastModifiedTime
Description Source CI MSS.Description
or Source CI MSS.DisplayName
Displaylabel Source CI MSS.DisplayName
Hasld
Hostname Source CI MSS.HostName
Langcode ″EN″
Manufacturer Source CI MSS.ManufacturerName
Name Source CI MSS.MSSName
Productname Source CI MSS.ProductName
Version Source CI MSS.ProductVersion

Table 10. Mapping table for actual CIs (continued)
Reverse CI PK, GV Actcirelationid
Relationship
Ref, AK Sourceci
FK, AK Targetci
AK Relationnum Reverse CI Relationship.Classification
Ancestorci Actual CI.Label + ″~″ + <CCMDB 7.1 Actual CI.Actciid>
or Actual CI.AncestorLabel + ″~″ + <CCMDB 7.1 Actual CI.Actciid>
or Actual CI.AncestorDisplayName + ″~″ + <CCMDB 7.1 Actual CI.Actciid>
Changeby Reverse CI Relationship.LastModifiedBy
Changedate Reverse CI Relationship.LastModifiedTime
Sourceguid Reverse CI Relationship.Sourceguid
Swapped 1
Actual Source PK, GV Actciid

CI
AK Actcinum Actual Source CI.Label + ″~″ + <CCMDB 7.1 Actual Target CI.Actciid>
or Actual Source CI.DisplayName + ″~″ + <CCMDB 7.1 Actual Target CI.Actciid>
or ″UNAVAILABLE″ + ″~″ + <CCMDB 7.1 Actual Target CI.Actciid>
AK Guid Actual Source CI.Guid
Changeby Actual Source CI.LastModifiedBy
Changedate Actual Source CI.LastModifiedTime
Classstructureid Actual Source CI.Classstructureid
Description Actual Source CI.Description
Hasld
Langcode ″EN″
Lastscandt Actual Source CI.LastModifiedTime
Chapter 5. Integration adapter mappings for TADDM 45

Appendix A. Advanced users’ checklist for installing the
integration adapter
This section provides a checklist for advanced users who are already very familiar
with how to install and use the integration adapter and therefore do not require all
the details provided in Chapter 3.
Follow the steps in the checklist in Table 11. Minimal instructions are provided on
the right to assist you. If you need the full installation details, refer to “Installation
checklist” on page 11. It includes links on the right that take you to detailed
instructions.
Table 11. Checklist for installing the integration adapter
1. Prepare to install Before you start:
1. Install IBM Java SDK 5.0 Service Release 5 and Integration
Composer, as described in Planning and Installing IBM Tivoli
Change and Configuration Management Database 7.1.1
2. Use version 7.1.1 of Integration Composer and CCMDB.
3. If necessary, back up your target (Maximo) database.
4. If open, close Integration Composer.
h a. From the Integration Composer server, Check or modify the value of themxe.db.queryDepthLevel property
verify the appropriate level of depth for in installation_dir\data\properties\fusion.properties. Default is 3.
actual CI data imports.
h b. From the Integration Composer server, Check or modify the value of themxe.db.queryTimeoutSeconds
modify the timeout value. property in installation_dir\data\properties\fusion.properties.
Default is 1200 for JDBC users; 180 is preferred for API users.
h c. [SSL users only] From the Integration 1. From the Integration Composer server, point a Web browser to
Composer server, copy the jssecacerts.cert the TADDM server at port 9430. For example:
file from the TADDMserver. http://hostname:9430
2. Make sure the status of all the TADDM components is green,
which means “started.”
3. Click Show SSL Options
4. Click Download Trust Store.
5. Save the file jssecacerts.cert in the Integration Composer etc
folder.
h d. Note your TADDM server and Maximo Have on hand your connection parameters for the TADDM server
database connection parameters. (host name, port, user name, user password) and the Maximo
database (database host name, port, name, instance, user, password).
2. Install the integration adapter for TADDM

h a. Copy the database scripts and qualifier Typically this location would be the Integration Composer server or
scripts for both CI types and actual CIs to the CCMDB database server. You only need to copy the scripts
a location where you can run them with a appropriate for your Maximo database type (all the .db2, .ora, or .sqs
database query tool. files listed in “Integration adapter files” on page 2).
h b. On the CCMDB database server, install Using the appropriate database utility, run the
the data schema for the source CI type createTADDM71CITypeDataSchema.* script (either .db2, .ora, or .sqs)
data using a database script. for your Maximo database type.
h c. On the CCMDB database server, install Using the appropriate database utility, run the
the data schema for the source actual CI createTADDM71ActualCIDataSchema.* script (either .db2, .ora, or
data using a database script. .sqs) for your Maximo database type.
h d. Copy the schema files and mapping files You only need to copy the scripts appropriate for your Maximo
for both CI types and actual CIs to the database type (all the .db2, .ora, or .sqs files listed in “Integration
Integration Composer server. adapter files” on page 2).
h e. From the Integration Composer user When defining the new data source, on the Data Schema page,
interface, define a data source connection select the TADDM CI Type data schema.
for the source CI type data.
In the Data Source field, type TADDM-71x-CI-Types.
Your connection settings might look something like this:

Connection Method:
IBM Configuration Discovery and Tracking API
Host Name:
myhostname.tiv.austin.ibm.com
Host Port:
9530
User Name:
administrator
Password:
********
h f. From the Integration Composer user When defining the new data source, on the Data Schema page,
interface, define a data source connection select the TADDM 7.1 Actual CI data schema.
for the source actual CI data.
In the Data Source field, type TADDM-71x-Actual-CIs.

Connection Method:
IBM Configuration Discovery and Tracking API
Host Name:
myhostname.tiv.austin.ibm.com
Host Port:
9530
User Name:
administrator
Password:
********

h g. From the Integration Composer user In the Data Schema field, type CCMDB71Classification.
interface, install the data schema for the
target CI type data. In the Data Source field, type CCMDB71x-Classification
In the Import Data Schema dialog box, select:

CCMDB71Classification.schm.

Connection Method:
Oracle JDBC Thin Driver
Host Name:
maximo_host.tiv.austin.ibm.com
Host Port:
1521
Host SID:
maximo
User Name:
maximo
Password:
********
Table Owner:
maximo
h h. From the Integration Composer user In the Data Schema field, type CCMDB71ActualCI.
interface, install the data schema for the
target actual CI data. In the Data Source field, type CCMDB71x-ActualCI.
In the Import Data Schema dialog box, select:

CCMDB71ActualCI.schm.

Connection Method:
Oracle JDBC Thin Driver
Host Name:
maximo_host.tiv.austin.ibm.com
Host Port:
1521
Host SID:
maximo
User Name:
maximo
Password:
********
Table Owner:
maximo
h i. From the Integration Composer user In the Mapping Name field, type TADDM-2-CCMDB-4-CI-Types.
interface, create a mapping for CI type
data. In the Import Mapping dialog box, select the mapping file for CI
type data, TADDM71CITypeToCCMDB71Classification.fsn.
h j. [Optional] From the Integration For instructions about how to modify mapping expressions, see the
Composer user interface, modify book IBM Tivoli Integration Composer Administrator Guide.
mapping expressions.
If you install Integration Composer using a language other than
English, change the langcode property in any adapter mappings that
you create. That is, replace the ″EN″ value in the langcode properties
with the appropriate literal value for your installation, for example
″FR″ (including the quotation marks) for French.
Appendix A. Advanced users’ checklist for installing the integration adapter 49

h k. From the Integration Composer user In the Mapping Name field, type TADDM-2-CCMDB-4-Actual-CIs.
interface, create a mapping for actual CI
data. In the Import Mapping dialog box, select the mapping file for CI
type data, TADDM71ActualCIToCCMDB71ActualCI.fsn.
h l. [Optional] From the Integration For instructions about how to modify mapping expressions, see the
Composer user interface, modify book IBM Tivoli Integration Composer Administrator Guide.
mapping expressions.
If you install Integration Composer using a language other than
English, change the langcode property in any adapter mappings that
you create. That is, replace the ″EN″ value in the langcode properties
with the appropriate literal value for your installation, for example
″FR″ (including the quotation marks) for French.
h m. On the CCMDB database server, load the Using the appropriate database utility, run the
class qualifiers to the target CI type data qualifierCCMDB71Classification.* script (either .db2, .ora, or .sqs) for
schema. your Maximo database type.
h n. On the CCMDB database server, load the Using the appropriate database utility, run the
class qualifiers to the target actual CI qualifierCCMDB71ActualCI.* script (either .db2, .ora, or .sqs) for
data schema. your Maximo database type.
3. Verify your CI classifications The following step is part of the Maximo installation procedure. It is
noted here for your convenience.
h a. From the Maximo Console user interface, From the Maximo Console user interface:
classify your CIs. 1. Create a top-level CI classification. Select Go To >
Administration > Classifications.
2. Define a class structure identifier for the top-level CI class. Select
Go To > Administration > Organizations.
4. Import your data The following are repeatable steps that you can perform in the
production environment after the Integration Adapter for TADDM is
installed. They are noted here for your convenience.
h a. From the command line, execute the Syntax:

mapping for CI types.
commandLine [-delete] mappingName repositoryUser repositoryPwd
You must execute this mapping first, and sourceUser sourcePwd targetUser targetPwd
the mapping must be successful, before
you proceed with the actual CI mapping Sample command:
in step 4.c.
commandLine TADDM-2-CCMDB-4-CI-Types maximo maximopw
administrator collation maximo maximopw
On UNIX-based operating systems, specify ./commandLine.sh

instead of commandLine as the command name.

h b. From the Maximo Console user interface, From the Maximo Console user interface:
check that CI types were activated. 1. Select Go To > Administration > CI Types.
2. Find SYS.COMPUTERSYSTEM.
3. If the CI Type Status for SYS.COMPUTERSYSTEM is not ACTIVE, click
the status change icon to activate it.
When the task completes, the message line will indicate status
changed to ACTIVE for the CI type.
h c. From the command line, execute the Syntax:

mapping for actual CIs.
commandLine [-delete] mappingName repositoryUser repositoryPwd
Note that executing the mapping for CI sourceUser sourcePwd targetUser targetPwd
types (step 10) must be completed and
successful before executing the mapping Sample command:
for actual CIs.
commandLine TADDM-2-CCMDB-4-Actual-CIs maximo maximopw
administrator collation maximo maximopw
On UNIX-based operating systems, specify ./commandLine.sh

instead of commandLine as the command name.
Appendix A. Advanced users’ checklist for installing the integration adapter 51

Appendix B. Executing a mapping
When you create a mapping, you define a set of expressions that specify how to
transform instances from a source to a target. To transform the source data and
import it from the source location into the target (Maximo) database, you must
execute the mapping.
For productivity and other reasons, you execute your mapping from the
Integration Composer command line interface. Executing a mapping runs a script.
On Microsoft Windows operating systems it runs commandLine.bat; on
UNIX-based operating systems it runs commandLine.sh. Either file is located in the
bin subdirectory of the Integration Composer installation directory.
To execute the mapping, you can run a script that provides all the parameter
values inside the file, or you can enter a detailed command that provides all the
required parameter values directly on the command line. If you have more than
one mapping to execute, you can edit the file and save separate files for each
mapping that you want to execute.
There are several parameters to consider when executing a mapping:

Delete last scan history option
Setting this parameter is optional. By default, when importing data,
Integration Composer processes only the data that has changed since the
last scan date. However, if you modify a mapping and you want to
implement the change, you might want all data processed. To accomplish
this, you must delete the last scan history. Use the -delete option only if
you want all data processed when you execute the mapping.
Identification parameters
Provide values for some identification parameters that specify mapping
name, repository user name and password, source user name and
password, and target user name and password for mapping execution.
The following sections describe the details for tasks performed on Windows
operating systems (tasks for UNIX-based operating systems are similar but use the
installation_dir/bin/commandLine.sh file instead).
Using values specified in a file

One way to execute a mapping is to run the commandLine command using a
modified commandLine.bat file. Before you execute the mapping, you provide all
the necessary parameter values inside the file.
File parameters
The file commandLine.bat is in the bin subdirectory in the Integration Composer

installation directory. You can edit the command file parameters and create
different files for different mappings.
There are two sections of the file that you can edit for mapping execution:
v Delete last scan history option
This section implements the -delete option:

REM =======================================
REM CHECK FOR DELETE LAST SCAN HISTORY FLAG
REM =======================================
set DELETE=
if not {%1} == {-delete} goto setMappingParams
set DELETE=%1
shift
You can edit this section as follows to delete the last scan history during
mapping execution:
Example 1
REM =======================================
REM CHECK FOR DELETE LAST SCAN HISTORY FLAG
REM =======================================
set DELETE=
if not {%1} == {-delete} goto setMappingParams
set DELETE=-delete
shift
v Identification parameters
This section implements the following identification parameters:
set MAPPINGNAME=%1
set REPOSITORYUSER=%2
set REPOSITORYPWD=%3
set SOURCEUSER=%4
set SOURCEPWD=%5
set TARGETUSER=%6
set TARGETPWD=%7
The identification parameters are defined as follows:
mappingName
The name of the predefined mapping; for example, TADDM-2-CCMDB-4-CI-
Types.
repositoryUser
The login user name for the Integration Composer repository; for
example, maximo.
repositoryPwd
The login password for the Integration Composer repository; for
example, maximopw.
sourceUser
The login user name for the TADDM data source; for example,
administrator.
sourcePwd
The login password for the TADDM data source; for example,
collation.
targetUser
The login user name for the target database; for example, maximo.
targetPwd
The login password for the target database; for example, maximopw.
You can edit this section as follows to specify values for the various
identification parameters to use during mapping execution:
Example 2
set MAPPINGNAME=TADDM-2-CCMDB-4-CI-Types
set REPOSITORYUSER=maximo
set REPOSITORYPWD=********
set SOURCEUSER=administrator
set SOURCEPWD=********
set TARGETUSER=maximo
set TARGETPWD=********
If any parameter value contains spaces, enclose the value in quotation marks, as
follows:
set MAPPINGNAME="TADDM 2 CCMDB 4 CI Types"
If any parameter value represents a database null, enter two single–quotation
marks without a space in between. For example, if you do not have a password
for a database, enter two single–quotation marks for this parameter value, as
follows:
set TARGETPWD=’’
To edit and run the file, complete the following steps:

1. Edit the file
a. Open any text editor, such as Microsoft Notepad.
b. Navigate to the installation_dir\bin directory and open the commandLine.bat
file.
c. (Optional.) To delete the last scan history before executing the mapping, add
the -delete option to the file, as shown previously in Example 1.
Attention: When using the -delete option, be sure to remove your entry
after running the file, so that the last scan history is not inadvertently
deleted the next time you run the file. Alternatively, you can run the file by
specifying the -delete option and your identification parameters on the
command line, rather than by modifying the file itself. See the ″Using
values specified on the command line″ section for details on this alternative.
d. To configure the file for unattended mapping execution, modify the
identification parameters by substituting appropriate values, as shown
previously in Example 2.
e. Save the modified file and close the editor.
2. Execute the mapping
a. If Integration Composer is open, close the application.
b. Open a command prompt.
c. Navigate to the bin subdirectory in your Integration Composer installation
directory, installation_dir\bin.
d. Enter the appropriate command:
Windows: commandLine
UNIX: ./commandLine.sh
The output displays on your screen.

e. Press Enter to close the task.
Using a scheduling program
You can use a scheduling program, such as Windows scheduler, to execute

mappings. If you use a Windows scheduler, comment out the line containing the
pause command:
:exit
@echo Integration Composer has finished
pause
becomes:
:exit
@echo Integration Composer has finished
REM pause
Appendix B. Executing a mapping 55

Using values specified on the command line
Another way to execute a mapping is to issue the commandLine command by
providing all the necessary parameter values directly on the command line itself.
The commandLine command runs the unedited script, and you supply all the
values in the command rather than in the file.
To execute a mapping by typing values directly on the command line, use the
commandLine command as described below.
Syntax:
commandLine [-delete] mappingName repositoryUser repositoryPwd sourceUser

sourcePwd targetUser targetPwd
Parameters:
-delete
[Optional.] Specify -delete if you want the mapping last-scan history to be
deleted prior to executing the mapping.
mappingName
The name of the predefined mapping; for example, type
TADDM-2-CCMDB-4-CI-Types.
repositoryUser
The login user name for the Integration Composer repository; for example,
type maximo.
repositoryPwd
The login password for the Integration Composer repository; for example,
type maximopw.
sourceUser
The login user name for the TADDM data source; for example,
administrator.
sourcePwd
The login password for the TADDM data source; for example, collation.
targetUser
The login user name for the target database; for example, type maximo.
targetPwd
The login password for the target database; for example, type maximopw.
Usage:
v Close Integration Composer before issuing the command.
v UNIX users must specify ./commandLine.sh instead of commandLine as the
command name.
v Issue the command from the bin subdirectory in your Integration Composer
installation directory, installation_dir\bin.
v Always type the parameter values for your command in the same order as they
appear in the command syntax.
Examples:

This command example (on Windows) uses the -delete option to remove the last
scan history, and uses the parameter values illustrated in the preceding
″Parameters″ section:
commandLine -delete TADDM-2-CCMDB-4-CI-Types maximo maximopw administrator

collation maximo maximopw
To retain the last scan history, omit the -delete option:
commandLine TADDM-2-CCMDB-4-CI-Types maximo maximopw administrator

collation maximo maximopw
On UNIX-based operating systems, specify ./commandLine.sh instead of

commandLine as the command name.
Appendix B. Executing a mapping 57

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 Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.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 Corporation

Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 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 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 Corporation
Software Interoperability Coordinator, Department 49XA
3605 Highway 52 N
Rochester, MN 55901
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 information 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.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
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.
All IBM prices shown are IBM’s suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
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.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating

platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs.
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights
reserved.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
For trademark attribution, visit the IBM Terms of Use Web site
(http://www.ibm.com/legal/us/)
The following terms are trademarks of International Business Machines

Corporation in the United States, other countries, or both:
IBM, the IBM logo, DB2, Tivoli, and the Tivoli logo are trademarks or registered
trademarks of International Business Machines Corporation in the United States,
other countries, or both.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
and/or other countries.
Microsoft, Windows, the Windows logo, and Internet Explorer are trademarks of
Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and other countries.
Other company, product, and service names may be trademarks or service marks
of others.
Notices 61

Printed in USA

CCMDB 711 Int Adapter Taddm Ibmbook

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CCMDB 711 Int Adapter Taddm Ibmbook

Hochgeladen von

Copyright:

Verfügbare Formate

Tivoli Change and Configuration Management Database

Integration Adapter for Tivoli Application Dependency Discovery Manager

Integration Adapter for Tivoli Application Dependency Discovery Manager

© Copyright IBM Corp. 2007, 2008 iii

© Copyright IBM Corp. 2007, 2008 v

Conventions used in this publication

Directory names, paths, and ″folders″

vi Integration Adapter for TADDM: Implementation Guide

About this publication vii

A mapping is a set of expressions that tells Integration Composer how to create

Software required by the integration adapter

© Copyright IBM Corp. 2007, 2008 1

Integration adapter files

2 Integration Adapter for TADDM: Implementation Guide

The Integration Adapter for Tivoli Application Dependency Discovery Manager:

About Integration Composer

Integration Composer components

A short description of the Integration Composer components follows:

Chapter 1. Overview of the integration adapter and Integration Composer 3

Integration Composer file structure

Figure 1. Integration Composer file structure

4 Integration Adapter for TADDM: Implementation Guide

Chapter 1. Overview of the integration adapter and Integration Composer 5

Configuration items and CI data

Authorized and actual configuration items

CCMDB maintains data about two kinds of configuration items:

© Copyright IBM Corp. 2007, 2008 7

End-to-end data collection and migration process

8 Integration Adapter for TADDM: Implementation Guide

Chapter 2. Data collection and migration 9

© Copyright IBM Corp. 2007, 2008 11

Typically this location would be the Integration

Copy the all the .schm and .fsn files listed in

12 Integration Adapter for TADDM: Implementation Guide

You must execute this mapping first, and the mapping

Note that executing the mapping for CI types (step 10)

Before getting started:

Chapter 3. Installing the integration adapter 13

Verifying the appropriate level of depth for actual CI data

where installation_dir is Integration Composer on Windows operating systems and

By subtracting 1 from the depth level currently specified in your fusion.properties

Depth Level Specified – 1 = Number of relationships traversed

Depth level Class

To check the current value for the level of depth:

Look at the mxe.db.queryDepthLevel property in the fusion.properties file

14 Integration Adapter for TADDM: Implementation Guide

where installation_dir is Integration Composer on Windows operating systems and

The default timeout value of 1200 is interpreted as seconds by a JDBC driver,

To modify the fusion.properties file and change the timeout value:

[SSL users only] Copying the jssecacerts.cert file

Chapter 3. Installing the integration adapter 15

Determining your connection parameters

Table 4. Connection parameters for the TADDM server.

Install the integration adapter for TADDM

Copying the database and qualifier scripts to the Integration

16 Integration Adapter for TADDM: Implementation Guide

Installing the data schema for your TADDM CI type data

To install the data schema, complete the following steps:

Installing the data schema for your TADDM actual CI data

Chapter 3. Installing the integration adapter 17

To install the data schema, complete the following steps.

Copying the schema and mapping files to the Integration