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

read the information in “Notices” on page 59.Note Before using this information and the product it supports. .

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

iv Integration Adapter for TADDM: Implementation Guide .

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

html.ibm. Online: Click Submit and track problems on the IBM Software Support site at http://www-306. IBM Software Support creates an Authorized Program Analysis Report (APAR). where myname represents. multicolumn lists. items inside list boxes. 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.html. 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″. The APAR describes the problem in detail.. By telephone: For the telephone number to call in your country. Whenever possible.com/guides/contacts.. menu names. 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. IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered.. 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. diskettes. list boxes.services. tabs. radio buttons.ibm. 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.. folders. b. If you submit a problem that is a software defect or for missing or inaccurate documentation. programming keywords. 3. v Variables and values you must provide: . Submit your problem to IBM Software Support in one of the following ways: a. containers. menu choices. property sheets). paths. and ″folders″ vi Integration Adapter for TADDM: Implementation Guide . icons. go to the “IBM Contacts” page of the Software Support Handbook at http://techsupport..com/software/support/probsub. labels (such as Tip and Operating system considerations) v Keywords and parameters in text Italic v Citations (examples: titles of publications. fields. push buttons. Gather diagnostic information.2. spin buttons. Monospace v Examples and code examples v File names.

About this publication vii . 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.This book uses Windows conventions for specifying directory names and directory paths.

viii Integration Adapter for TADDM: Implementation Guide .

To import any kind of TADDM data into the Maximo database. The CI type mapping will bring the CDM definition into the Maximo database. In this case. © Copyright IBM Corp. For installation instructions and information about the minimum hardware and software requirements for Integration Composer. use only the software versions supplied with CCMDB. while the actual CI mapping will bring in the data instances. which includes the Maximo database. The integration adapter for TADDM runs with the following software: CCMDB IBM Tivoli Change and Configuration Management Database (CCMDB) 7. you use Integration Composer to create some mappings that convert the data from its source form to the form required by the Maximo database. the target database is the Maximo database in the Change and Configuration Management Database (CCMDB) product. Software required by the integration adapter Several corequisites are required by the integration adapter for TADDM. transforms the collected TADDM data and imports it into the target database. the TADDM discovery tool scans computers and other devices connected to a network and records information about their installed hardware and software. 2007.1. Integration Composer IBM Tivoli Integration Composer 7. Integration Composer. All the corequisite software described in this section is provided with IBM Tivoli Change and Configuration Management Database. The integration adapter for TADDM includes two mapping files to use when creating these mappings. To gather the IT data. Integration Composer must be installed before you can use the integration adapter for TADDM. To ensure that all the corequisites are compatible with one another when you run them.Chapter 1. which is the core structure of the TADDM data. once installed. does this data-mapping part of the transforming task for you. A mapping is a set of expressions that tells Integration Composer how to create data in the target using data from a source.1.1. Before importing the TADDM data instances. The integration adapter. you must first import the Common Data Model (CDM) definition. is required and must be installed before you can use 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.1. 2008 1 . see the book Planning and Installing IBM Tivoli Change and Configuration Management Database 7. one for CI type data and one for actual CI data.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. with the integration adapter for TADDM installed.1.

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

Overview of the integration adapter and Integration Composer 3 . and create mappings to transform and migrate data.pdf About Integration Composer Integration Composer is separately installed software that is required by the integration adapter. browse the source data. and a repository that is a subset of the Maximo database where your information technology data is imported. Integration Composer engine The Integration Composer engine processes mapping expressions that transform data from the source data and integrate it into a target database. Oracle. For more detailed information. CCMDB71ActualCI. Integration Composer components Integration Composer includes the application itself (the user interface). TADDM71ActualCIToCCMDB71ActualCI. define data schemas. and SQL Server databases. an engine for processing mapping expressions.fsn This mapping file provides predefined expressions that you can use to transform actual CI data from the source formats to the target formats. To use the integration adapter.schm This schema file defines the structure that organizes and classifies the actual CI target data. first you have to install and understand the basics about Integration Composer. several connection drivers. respectively. 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. A short description of the Integration Composer components follows: Integration Composer user interface The Integration Composer user interface lets you define data sources. The sections that follow describe the Integration Composer components and file structure. Integration Composer command line interface The Integration Composer command line interface lets you start Integration Composer and execute mappings that transform your source data and import it from the source to the target (Maximo) database. Chapter 1. see the book IBM Tivoli Integration Composer Administrator Guide. a command line interface.actual CI target data when it performs a data import to IBM DB2.

v Mappings that define how to transform data instances and migrate them from a source to a target. 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). the installation program creates the same file structure in the location that you specify. JDBC drivers: Integration Composer uses a JDBC driver to establish connections to the target (Maximo) database. if the default installation path is accepted. in a predetermined file structure. 8i. This metadata defines the structure of the data. Integration Composer file structure If you select a different location when you install Integration Composer. v Data source definitions that provide data connection parameters. Integration Composer file structure During Integration Composer installation. v The time stamp of the most recent scan for root objects in the source data of the Integration Composer repository. This driver supports Oracle 10g and earlier versions (including 8.0. v Metadata for data schemas that you create in Integration Composer. and 9i). 4 Integration Adapter for TADDM: Implementation Guide .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. Integration Composer repository The Integration Composer repository in the Maximo database contains the following Integration Composer data: v Metadata for data schemas delivered with Integration Composer. the installation program installs the application in the Integration Composer (Windows) or Integration_Composer (UNIX) directory. if such a last-scan time stamp exists. Integration Composer includes the following JDBC drivers for this purpose. 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. 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.

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

6 Integration Adapter for TADDM: Implementation Guide .

The import of the actual CI data can occur only after it has been classified using CI type data. and other information technology objects deployed in your enterprise and record information about the hardware and software installed on them. Typically. v Actual configuration items are objects that truly are deployed in the enterprise. or actual CI data. Data collection and migration The integration adapter for Tivoli Application Dependency Discovery Manager facilitates data migration. 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. and their deployment can be verified by using discovery tools such as the one applicable to this integration adapter. You can then import this collected information into the target database. and can therefore be ″discovered. we are only concerned with actual CI data. This section explains the concepts related to configuration items and CI data.Chapter 2. As such. discovery tools are used to scan the computers. In addition. respectively. of data from a data source—the TADDM database—to a target—the Maximo database. Data migration is the transfer of data to a different database server or data model. authorized configuration items are either in plan to be deployed or are believed (but not actually verified) to be deployed.″ To gather this data. Change and Configuration Management Database (CCMDB) applications are required for some steps in the data migration process. and subsequent transformation. data migration refers to the importing. 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. including the integration adapter for TADDM and Integration Composer. For now. They are authorized CI data and actual CI data. because we only want to migrate. they may or may not actually exist in your IT environment. 2008 7 . © Copyright IBM Corp. Although authorized. or import. network devices. 2007. Actual configuration item data. and provides an overview of the end-to-end data collection and importing process. these conforming configuration items are considered to be “authorized” for deployment. A discovery tool is used to collect and save configuration data from these CIs. In this case the data is configuration item (CI) data retrieved from an IT environment. CI data that actually exists into the IT environment. For our purposes. Actual CI data Two types of database information are associated with authorized CIs and actual CIs. is data collected directly from components that actually exist in your enterprise’s IT environment. This data migration process involves the use of multiple software tools.

so that the data can be migrated or imported from the TADDM database into another—target—database using Integration Composer. For information about how to install Integration Composer. Performing the complete end-to-end discovery and importing of such data involves the use of multiple software tools. This section lists the end-to-end steps required to import that discovered data into a target database using Integration Composer. In particular. The integration adapter imports the Common Data Model (CDM) definition. Integration Composer 5.0 Service Release 5 before you install Integration Composer. You have to import CI type data into the target database before you import any actual CI data. When you prepare to import CI type and actual CI data. be sure to follow the checklist steps in the order presented. as well as CCMDB. If you do not know these values.1.CI type data Configuration item type data. you must define connection parameters to the TADDM server and the Maximo database. while the actual CI mapping brings in the data instances. Steps 1. In addition to Integration Composer and the integration adapter for TADDM. To enable Secure Sockets Layer (SSL) connections between Integration Composer and TADDM. you must copy the jssecacerts. The order in which you import the data is important. refer to “[SSL users only] Copying the jssecacerts. Maximo database. from TADDM into the Maximo database in CCMDB. these software tools include TADDM itself (for discovery).properties file is correct for your business needs. The data resides in the discovery tool database and includes CI type data. copy the jssecacerts. If you are using SSL certification. contact your database administrator. see the book Planning and Installing IBM Tivoli Change and Configuration Management Database 7. TADDM database 8 Integration Adapter for TADDM: Implementation Guide . Although all the basic steps for collecting and importing data are listed here. Such classification allows your enterprise to specify what type of actual CI data it wants to import and manage in the database. These references are cited in Table 1: Table 1. Obtain connection parameters for the TADDM server and Maximo database.1.cert file from the TADDM server to the server where Integration Composer is installed. Product or component to use Additional information TADDM discovery tool Use settings in the discovery tool to specify the types of configuration items to search for. For details about how to do this task. Verify that the level of depth specified in the fusion.cert file to the Integration Composer installation directory. collect data about your IT infrastructure. refer to “Verifying the appropriate level of depth for actual CI data imports” on page 14. Integration Composer 4. You might use the default values established when you installed the Maximo database or other values defined specifically for your organization. For details about how to do this task.1. Install Integration Composer 7. you might have to refer to CCMDB documentation for steps not performed using Integration Composer. 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. refer to “Determining your connection parameters” on page 16. Table 1 lists the high-level steps and which tools you use to do them. the core structure of the TADDM data. Integration Composer 3. Checklists are provided to assist with both of these tasks. 2. The CI type mapping brings the CDM definition into the Maximo database. Using a discovery tool.cert file” on page 15. is data that classifies the actual CI data. End-to-end data collection and migration process. 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. Note that you must install IBM Java SDK 5. If you are importing both CI type data and actual CI data. For details about how to determine this information.1. Verify that Integration Composer is configured properly for TADDM. or CI type data.

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

10 Integration Adapter for TADDM: Implementation Guide .

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

See “Copying the schema and mapping files to the Integration Composer server” on page 18. See “Installing the data schema for CCMDB CI type data” on page 22. create a mapping for CI type data. Copy the schema files and mapping files for both CI types and actual CIs to the Integration Composer server.db2. You only need to copy the scripts appropriate for your Maximo database type (all the . Install the integration adapter for TADDM h a. On the CCMDB database server. h i. See “Installing the data schema for your TADDM actual CI data” on page 17. From the Integration Composer user interface.schm and . 12 Integration Adapter for TADDM: Implementation Guide . h b. h c. h f. See “Defining a data source connection for your TADDM CI type data” on page 19. From the Integration Composer user interface. 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. From the Integration Composer user interface. See “Creating a mapping for your TADDM-to-CCMDB CI type data” on page 28.fsn files listed in “Integration adapter files” on page 2). or . install the data schema for the target CI type data. . install the data schema for the target actual CI data. See “Installing the data schema for your CCMDB actual CI data” on page 26. See “[Optional] Modifying the mapping expressions” on page 30. From the Integration Composer user interface. define a data source connection for the source CI type data.Table 2. h e. create a mapping for actual CI data. On the CCMDB database server. h h. h d. From the Integration Composer user interface. h j. [Optional] From the Integration Composer user interface. modify mapping expressions. h g. See “Defining a data source connection for your TADDM actual CI data” on page 21. server” on page 16. h k. Checklist for installing the integration adapter (continued) 2. install the data schema for the source CI type data using a database script.sqs files listed in “Integration adapter files” on page 2).ora. define a data source connection for the source actual CI data. Typically this location would be the Integration Composer server or the CCMDB database server. See “Creating a mapping for your TADDM-to-CCMDB actual CI data” on page 30. See “Installing the data schema for your TADDM CI type data” on page 17. install the data schema for the source actual CI data using a database script. Copy the all the . From the Integration Composer user interface.

Prepare to install The sections that follow describe the necessary preparation tasks to do before you begin your integration adapter installation. Before getting started: 1. Note that executing the mapping for CI types (step 10) must be completed and successful before executing the mapping for actual CIs. See “Executing your mapping for actual CIs” on page 36. See “Loading the class qualifiers into the target CI type data schema” on page 32. load the class qualifiers to the target actual CI data schema. and the mapping must be successful. h c. 3.Table 2. see the book Planning and Installing IBM Tivoli Change and Configuration Management Database 7.1. before you proceed with the actual CI mapping in step 4. types were activated. execute the mapping for actual CIs. For information about how to install Integration Composer. Verify your CI classifications The following step is part of the Maximo installation procedure. Do not omit any of the required tasks. From the command line. It is noted here for your convenience. See “[Optional] Modifying your mapping expressions” on page 32. See “Creating a top-level CI class and class structure identifier” on page 34. h m.1 of both IBM Tivoli Integration Composer and CCMDB. From the Maximo Console user interface.1. If you currently have any data in your target (Maximo) database. h b. Omitting these tasks could result in your integration adapter not working properly. Make sure that you are using version 7. [Optional] From the Integration Composer user interface. On the CCMDB database server. h n. On the CCMDB database server. From the command line. 2. Checklist for installing the integration adapter (continued) h l. modify mapping expressions. Import your data The following are repeatable steps that you can perform in the production environment after the Integration Adapter for TADDM is installed. 4.0 Service Release 5 before you install Integration Composer. They are noted here for your convenience. classify your CIs. Note that you must install IBM Java SDK 5.c. You must execute this mapping first. load the class qualifiers to the target CI type data schema. h a. From the Maximo Console user interface. Chapter 3.1. check that CI See “Activating CI types” on page 35. See “Executing your mapping for CI types” on page 35. back up that database. execute the mapping for CI types. h a. Installing the integration adapter 13 . See “Loading the class qualifiers into the target actual CI data schema” on page 33.

if no further change is made: Depth Level Specified – 1 = Number of relationships traversed For example.properties. if your depth level is currently set to the default. and another between Operating System and Software classes. If Integration Composer is running. By subtracting 1 from the depth level currently specified in your fusion.queryDepthLevel=3 To change the current value for the level of depth. (Note that increasing the default value of 3 could reduce system performance.properties file (installation_dir\data\properties\fusion.properties): // Number of levels to be recursively traversed for a query.properties where installation_dir is Integration Composer on Windows operating systems and Integration_Composer (with underscore) on UNIX-based operating systems. do the following steps: 1. when importing actual CI source data.db.3.properties file. This verification task is to ensure that the level of depth for the CI trees you intend to import is appropriate for your needs. close all open windows and sign out of the application.) 4.db. but you can change it by editing the fusion. you can calculate the number of relationships that will be traversed in your CI trees during data importing. 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. The value for the level of depth is preset to 3. 14 Integration Adapter for TADDM: Implementation Guide . two levels of relationships are traversed: one between Computer System and Operating System classes. 2.db.queryDepthLevel property in the fusion. 3. // Default is 3 mxe. with a depth level of 3. close all open windows and sign out of the application. the following three classes will be imported: Depth level 1 2 3 Class Computer System Operating System Software In the example. the default.queryDepthLevel property. Edit the file installation_dir\data\properties\fusion. To check the current value for the level of depth: Look at the mxe. Modify the value of the mxe.properties file. If Integration Composer is running. 3. This Integration Composer properties file is located as follows: installation_dir\data\properties\fusion. Save the file. It indicates to Integration Composer the number of class relationships to be traversed and then migrated to the target.

properties. the API uses minutes instead of seconds as the unit of measurement for the wait time. Integration Composer presets the value for the timeout to 1200. Save the file. respectively. or 20 hours.” 3. 2.cert file from the TADDM server to the server where Integration Composer is installed.properties file and change the timeout value: 1.Modifying the timeout value Timeout value describes a wait-time property in the Integration Composer fusion. For example. copy the certificate file. from the TADDM server. Installing the integration adapter 15 . jssecacerts. which is located as follows: installation_dir\data\properties\fusion. The default timeout value of 1200 is interpreted as seconds by a JDBC driver. 4. which equates to a 20-minute wait time. That is why you might prefer to have one timeout value that works for both API and JDBC driver connections. Chapter 3. Note: If you change the timeout value in the properties file while Integration Composer is running.cert. as interpreted in minutes by the IBM Configuration Discovery and Tracking API. Click Download Trust Store. [SSL users only] Copying the jssecacerts. But. if you change the timeout value to 180.db.cert file In order to enable Secure Sockets Layer (SSL) connections between Integration Composer and TADDM. Change the value of the mxe. You will be using both the API and a JDBC driver to connect to sources and targets. close all open windows and sign out of the application. To modify the fusion. 1200 equates to a 1200-minute wait time. From the server where Integration Composer is installed. point a Web browser to the TADDM server at port 9430. If you are using SSL. Unlike a JDBC driver. however. If Integration Composer is running.queryTimeoutSeconds property to 180. So you might want to change the timeout value from 1200 to another number that works better for both connection methods. 3. which means “started. Make sure the status of all the TADDM components is green. 2. Edit the file 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 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. This task is to ensure that the default timeout value for API users is not too long. For example: http://hostname:9430. or to another timeout value of your choice. Restart Integration Composer to activate your property change. Click Show SSL Options. that change will not take effect until you restart Integration Composer. you must copy the jssecacerts. you will have a 3-hour timeout for API connections and a 3-minute timeout for JDBC driver connections. 5. You can change this value by editing the fusion.properties file. 4. by following these steps: 1.properties file.

Install the integration adapter for TADDM The sections that follow describe how to install the integration adapter for TADDM. No value is assigned on installation. Name of the Maximo database server. Table 3. 16 Integration Adapter for TADDM: Implementation Guide . Oracle. Obtain the values appropriate for your installations before you attempt to set up this adapter. Do the tasks in the order presented. If using SSL. Connection parameters for the TADDM server. Connection parameters for the Maximo database. you must substitute the values that you do use when you define connection parameters for your source and target. Port for the TADDM server. You will need them when you supply connection parameters to Integration Composer—a required step when you define data schemas and mappings. Password for the TADDM user ID. 1521 maxdb71 1433 maxdb71 DB2 default Oracle default SQL Server default Comments Host name for the Maximo database server. Parameter Database host name Database port Database name Database instance Database user Database password 50000 maxdb71 ctginst1 maximo maximo maximo Maximo database user ID. During the integration adapter installation process. the default value is 9531. Typically this location would be the Integration Composer server or the CCMDB database server. Default administrator account automatically created by TADDM. The following tables list the default values used for the Maximo database (in CCMDB) and TADDM connection parameters when you install CCMDB and TADDM. Table 4. Determining your connection parameters This section explains how to determine what parameters to use when setting up connection information for Integration Composer. you must define database connections for the target Maximo database and for the source TADDM server in Integration Composer.cert in the etc folder in the Integration Composer installation directory. Check with your database administrator to obtain this value. Maximo database user password. Save the file jssecacerts.5. or SQL Server). Parameter Host name Port User Name User Password 9530 administrator collation 9530 administrator collation collation 9530 DB2 default Oracle default SQL Server default Comments Host name for the TADDM server (not the database). you need to copy the adapter-provided database and qualifier scripts to a location where you can run them with a database query tool. You only need to copy the database and qualifier scripts that are appropriate for the type of Maximo database you have (IBM DB2. Copying the database and qualifier scripts to the Integration Composer server or CCMDB database server As part of the integration adapter setup process. Port number for the Maximo database server. If you do not use the default values.

ora (for source data) v createTADDM71CITypeDataSchema. To install the CI type data schema for the TADDM data source.sqs (for source data) The database scripts for actual CIs are: v createTADDM71ActualCIDataSchema. Installing the integration adapter 17 . Chapter 3.sqs To install the data schema. Later.db2 (for source data) v createTADDM71ActualCIDataSchema.ora v qualifierCCMDB71ActualCI.ora (for source data) v createTADDM71ActualCIDataSchema.db2 v createTADDM71CITypeDataSchema.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. 2. complete the following steps: 1. Installing the data schema for your TADDM actual CI data Before you can use the integration adapter to create a mapping and migrate data.db2 v qualifierCCMDB71Classification. Later.To copy the adapter scripts: 1. For error information. The qualifier scripts for CI types are: v qualifierCCMDB71Classification. execute the database script for your source data. you will have to run these scripts from whatever directory you place them in.sqs The qualifier scripts for actual CIs are: v qualifierCCMDB71ActualCI.ora v qualifierCCMDB71Classification.db2 v qualifierCCMDB71ActualCI. you need to install the source data schema for actual CI data in the Integration Composer repository in the Maximo database. Check for database script errors and resolve any errors. use whichever one of the following database scripts is appropriate for your Maximo database type.sqs (for source data) 2. The database scripts for CI types are: v createTADDM71CITypeDataSchema. refer to the log files located in the log folder in your Windows or UNIX installation directory.ora v createTADDM71CITypeDataSchema. you need to install the source data schema for CI type data in the Integration Composer repository in the Maximo database. 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. 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.db2 (for source data) v createTADDM71CITypeDataSchema. Using the appropriate database query tool. you will have to run these scripts from whatever directory you place them in.) v createTADDM71CITypeDataSchema. (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.

For error information. however. Integration Composer automatically looks for the . Check for database script errors and resolve any errors. 18 Integration Adapter for TADDM: Implementation Guide . (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. The mapping file for CI types is: v TADDM71CITypeToCCMDB71Classification. you will have to browse to that location and select the files. when you import it into Integration Composer. by default. To copy the adapter files to the Integration Composer installation directories: 1.schm) files in another location.schm (for target data) Note: You can put the schema (.schm files in the dataschema folder. Copying the schema and mapping files to the Integration Composer server As part of the integration adapter setup process. Copy the mapping file for actual CIs to installation_dir\data\mappings (where installation_dir is the directory where Integration Composer was installed). use whichever one of the following database scripts is appropriate for your Maximo database type. complete the following steps. 1.fsn Note: You can put these files in another location. 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).) v createTADDM71ActualCIDataSchema.db2 v createTADDM71ActualCIDataSchema. you will have to browse to that location and select the file. when you import the files into Integration Composer. refer to the log files located in the log folder in your Windows or UNIX installation directory. execute the database script for your source data.fsn The mapping file for actual CIs is: v TADDM71ActualCIToCCMDB71ActualCI.To install the actual CI data schema for the TADDM data source. however. By default. Using an appropriate database query tool. 2.sqs To install the data schema. If you put the files in a different location.schm (for target data) The schema file for actual CIs is: v CCMDB71ActualCI. 2. Integration Composer looks for them in the mappings folder. you need to copy the adapter-provided schema and mapping files to the appropriate Integration Composer installation directories on the Integration Composer server. The schema file for CI types is: v CCMDB71Classification.ora v createTADDM71ActualCIDataSchema.

The name must have at least two characters and is case sensitive. For information about default values for these fields. your settings might look something like this: Connection Method: Host Name: Host Port: Use SSL: Trusted Location: User Name: Password: IBM Configuration Discovery and Tracking API taddm_host. In the Connection Method drop-down list. 5.com 9530 administrator ******** The following table lists all the fields that Integration Composer can display. 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.tiv. Type in the connection parameters. After you define the connection parameters. type TADDM-71x-CI-Types. you must select the Configuration Discovery and Tracking API for your connection method. To define a data source connection. refer to “Determining your connection parameters” on page 16. The Data Schema page is displayed in the Define a New Data Source window. The IBM Tivoli Integration Composer window is displayed. complete the following steps: 1. The connection information fields are displayed. as required.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. select a connection method. Installing the integration adapter 19 . Table 5. Sign in to Integration Composer using a valid user ID and password. 2. If you are connecting to a TADDM data source. Integration Composer saves them in its repository and displays them whenever you attempt to connect to that data source. Then click Next. In the Data Source field. Follow the steps in this section if you installed your data schema using a database script. type a name for the data source. Connection information fields Field Host Name Description Host name for the data source. Chapter 3. 3. as described previously. The connection method that you selected in step 5 determines the fields that Integration Composer displays. 6.austin. You may see fewer fields. depending on your connection method. 4. Select Define New Data Source. Use the IBM Configuration Discovery and Tracking API when connecting to the source data for TADDM. For example.ibm. Select the TADDM CI Type data schema and click Next. Integration Composer uses an API or JDBC driver to connect to data sources. For example. 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. The Data Source page is displayed.

9. click Test Connection to test the connection to the data source. Password Database password for the data source. Integration Composer closes the error message dialog box. The text in the dialog box indicates whether the test was successful. Click OK.0 probably do not support this feature. without invoking underlying Integration Composer processes. v If Integration Composer cannot establish a connection. the database instance name). Integration Composer closes the Test Connection dialog box. Table Owner Trusted Location Data schema name or database schema owner.. Note: Test Connection verifies only the host name and port. Click OK. refer to the log files located in the log folder in your Windows or UNIX installation directory. Integration Composer displays a Save dialog box. you must enter a value in the Trusted Location field. Go to step 8. 20 Integration Adapter for TADDM: Implementation Guide . Upon finishing. Database user name for the data source. Integration Composer closes the Test Connection dialog box. click Finish. on Windows operating systems: c:\Integration Composer\. Connection information fields (continued) Field Host Port Host SID Database User Name Description Port for the data source. Fully qualified path of the SSL certificate file to use to connect to a server such as the Configuration Discovery and Tracking server. (JDBC drivers that do not comply with JDBC 2. it displays a confirmation message. URL address to access a database instance. this field represents the user identifier to access IBM Configuration Discovery and Tracking. On the Connection Information page. Session identifier for the host (that is.\jssecacerts. If you select this check box.) 8. To respond to the dialog box. For example. Integration Composer displays a Test Connection dialog box. For the Configuration Discovery and Tracking API. Click OK. this field represents the password associated with the user login account. Database name for the data source.Table 5. Note: If Integration Composer does not save the data source successfully.cert Use SSL Check box that specifies whether the connection is an SSL (Secure Socket Layer) connection. select one of the following options: v If Integration Composer establishes a connection. it displays an explanatory message. Review the values for the connection parameters and retry the connection. For error information. For the Configuration Discovery and Tracking API. URL 7. Optional: If appropriate. it displays one or more error messages. Resolve any errors and try defining the data source again.. Click OK. Integration Composer returns you to the IBM Tivoli Integration Composer window. it is still possible to receive save errors that are unrelated to this connection information.

ibm. The Data Source page is displayed. depending on your connection method. select a connection method. Select the TADDM 7. 3.1 Actual CI data schema and click Next. For example. Then click Next. as required. Optional: If appropriate. Follow the steps in this section if you installed your data schema using a database script. The Data Schema page is displayed in the Define a New Data Source window.tiv. type TADDM-71x-Actual-CIs. The name must have at least two characters and is case sensitive. Integration Composer displays a Test Connection dialog box. For example. complete the following steps: 1. click Test Connection to test the connection to the data source. 6.austin. 5. v Delete the open data source. you must select the Configuration Discovery and Tracking API for your connection method. v Use the Close Data Source Connection option in the Data Source menu in the IBM Tivoli Integration Composer window to close the connection. You may see fewer fields. The connection information fields are displayed. 4. The IBM Tivoli Integration Composer window is displayed. Type in the connection parameters. select one of the following options: Chapter 3. To define a data source connection. type a name for the data source. 7. Installing the integration adapter 21 . 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. Sign in to Integration Composer using a valid user ID and password. 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. If you are connecting to a TADDM data source. The connection method that you selected in step 5 determines the fields that Integration Composer displays. For information about default values for these fields. your settings might look something like this: Connection Method: Host Name: Host Port: Use SSL: Trusted Location: User Name: Password: IBM Configuration Discovery and Tracking API taddm_host. In the Connection Method drop-down list. refer to “Determining your connection parameters” on page 16. Select Define New Data Source. 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.Note that in an Integration Composer session. To respond to the dialog box. The text in the dialog box indicates whether the test was successful.com 9530 administrator ******** Table 5 on page 19 lists all the fields that Integration Composer can display. 2. In the Data Source field. as described previously. if you connect to one of the defined data sources.

refer to the log files located in the log folder in your Windows or UNIX installation directory. Integration Composer closes the Test Connection dialog box. Integration Composer closes the Test Connection dialog box. re-open the target data schema in Integration Composer and synchronize it with the Maximo database definition. click Finish. if you connect to one of the defined data sources. Integration Composer displays a Save dialog box.v If Integration Composer establishes a connection. use the CI type data file that the integration adapter provides. For error information. you need to install the data schema for target CI type data in the Integration Composer repository in the Maximo database. Note: If Integration Composer does not save the data source successfully. you will be presented with a Data Schema Analysis window that gives you the opportunity to synchronize them (by clicking Fix Errors). Note: Test Connection verifies only the host name and port. Integration Composer closes the error message dialog box. sign in to Integration Composer using a valid user ID and password. it is still possible to receive save errors that are unrelated to this connection information. complete the following steps: 1. Important: If at any time after installing a target data schema you change your Maximo database definition (for example. Integration Composer returns you to the IBM Tivoli Integration Composer window. If Integration Composer finds any discrepancies between the two. v If Integration Composer cannot establish a connection. 22 Integration Adapter for TADDM: Implementation Guide . Resolve any errors and try defining the data source again. it displays one or more error messages.) 8. the target data schema defined in Integration Composer and the Maximo database might no longer match. Otherwise. without invoking underlying Integration Composer processes.0 probably do not support this feature. v Delete the open data source.schm. v Use the Close Data Source Connection option in the Data Source menu in the IBM Tivoli Integration Composer window to close the connection. To install the data schema. CCMDB71Classification. you change the length of an attribute). it displays an explanatory message. If you are not already signed in. it displays a confirmation message. (JDBC drivers that do not comply with JDBC 2. Upon finishing. Go to step 8. Click OK. 9. Installing the data schema for CCMDB CI type data Before you can use the integration adapter to create a mapping and migrate data. Note that in an Integration Composer session. Click OK. Click OK. Click OK. Review the values for the connection parameters and retry the connection. To install the data schema. On the Connection Information page. 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. The IBM Tivoli Integration Composer window is displayed.

ibm. Note: You can type a different name for the new data schema. Connection information fields Field Host Name Description Host name for the data source. as required. You may see fewer fields. Chapter 3. For the Configuration Discovery and Tracking API. Host Port Host SID Database User Name Port for the data source. the user identifier to access IBM Configuration Discovery and Tracking. click Cancel. select Define New Data Schema. However. For information about default values for these fields. or DB2 database (the Maximo database).2. The connection information fields are displayed. select one of the available JDBC drivers as the connection method to your target Oracle. 5. 3. The connection method that you selected in step 6 determines the fields that Integration Composer displays. From the IBM Tivoli Integration Composer window. Note: To review or change previous selections. The name must have at least two characters and is case sensitive. In the Connection Method drop-down list. your settings might look something like this: Connection Method: Host Name: Host Port: Host SID: User Name: Password: Table Owner: Oracle JDBC Thin Driver maximo_host. The following table lists all the fields that Integration Composer can display. Click Next. 7.austin. SQL. Then click Next. For example. 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. Table 6. For the Configuration Discovery and Tracking API. In the Data Schema field. if you do. In the Data Source field. Installing the integration adapter 23 . 6. the database instance name). depending on your connection method. Type in the connection parameters. To cancel this procedure and return to the main Integration Composer window. type CCMDB71Classification as the name of the new data schema (data schema names are case sensitive). Database name for the data source. refer to “Determining your connection parameters” on page 16. Integration Composer displays the Data Schema field on the Define a New Data Schema window. type CCMDB71x-Classification. Database user name for the data source. For example. The Data Source field is displayed. type the name you want to use to identify the data source.com 1521 maximo maximo ******** maximo 4. click Back. Session identifier for the host (that is. the host name of the server on which the IBM Configuration Discovery and Tracking Server is installed.tiv.

Table 6. Connection information fields (continued) Field Password Description Database password for the data source. For the Configuration Discovery and Tracking API, , the password associated with the user login account. Table Owner Trusted Location Data schema name or database schema owner. 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 address to access a database instance.

URL

8. 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 9. 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.) 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.

24

Integration Adapter for TADDM: Implementation Guide

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.
Chapter 3. Installing the integration adapter

25

Installing the data schema for your CCMDB actual CI data
Before you can use the integration adapter to create a mapping and migrate data, you need to install the data schema for target actual CI data in the Integration Composer repository in the Maximo database. To install the data schema, use the actual CI data file that the integration adapter provides, CCMDB71ActualCI.schm. To install the data schema, complete the following steps: 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). 7. Type in the connection parameters, as required. The connection method that 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: Host Name: Host Port: Host SID: User Name: Password: Table Owner: Oracle JDBC Thin Driver maximo_host.tiv.austin.ibm.com 1521 maximo maximo ******** maximo

Table 6 on page 23 lists all the fields that Integration Composer can display. You may see fewer fields, depending on your connection method. 8. Optional: If appropriate, click Test Connection to test the connection to the data source. Integration Composer displays a Test Connection dialog box. The

26

Integration Adapter for TADDM: Implementation Guide

it displays an explanatory message. Upon finishing. Integration Composer closes the Test Connection dialog box. This window lists discrepancies between the data schema and the corresponding data source. it is still possible to receive save errors that are unrelated to this connection information. v Data type of a table column in the database does not match the type of the same column in the data schema. On the Connection Information page. Integration Composer repairs the errors and opens the Data Schema window. Integration Composer imports the data schema file. 11. From this window. The Import Data Schema dialog box lists the data schemas that you copied to the dataschema folder. select one of the following options: v If Integration Composer establishes a connection. For actual CI target data. you can import a data schema file provided with this integration adapter.schm Integration Composer populates the File name field with the selected file name. (JDBC drivers that do not comply with JDBC 2. Integration Composer closes the Test Connection dialog box. Installing the integration adapter 27 . 12. The color displayed on your computer can vary. The Data Schema window is displayed.text in the dialog box indicates whether the test was successful. from the Select Action menu in the title bar of the Data Schema window. If discrepancies exist between the data source and the data schema. Integration Composer displays the root class in red because it has no properties associated with the class. the Data Schema Analysis window is displayed. it displays a confirmation message. 10. select the data schema file that you want to import. Review the values for the connection parameters and retry the connection. select Import Data Schema. select: CCMDB71ActualCI. v Length of a table column in the database does not match length of the same column 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. To import the data schema file provided with the integration adapter. 13.0 probably do not support this feature. Review the errors in the Data Schema Analysis window and select one of the following options: v To repair the errors. Chapter 3. In the Import Data Schema dialog box. Note: Test Connection verifies only the host name and port. Note: The display properties that you set for your computer can affect colors. without invoking underlying Integration Composer processes. v If Integration Composer cannot establish a connection. The Import Data Schema dialog box is displayed. Click OK. Click Open. Integration Composer displays errors that it can correct with a green check. click Finish. Click OK.) 9. 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. click Fix Errors. Go to step 14 on page 28. Go to step 9. To respond to the dialog box.

A Data Schema Analysis warning window is displayed. Integration Composer imports the data schema as is and displays the Data Schema window. in accordance with the instructions in Table 2 on page 11. In the Data Schema Analysis warning window. Integration Composer replaces the existing expression with the imported expression. click Statistics. – To cancel the action. The Data Schema window is displayed. v To view statistics for table and column errors. Integration Composer closes the warning window and displays the Data Schema Analysis window. v To expand all nodes in the tree to display information about inconsistencies between the data schema and the data source. click Cancel. b. Attention: If you import a mapping into a mapping that contains expressions. In the Import dialog box. – To close the window without changing the data schema. see the book IBM Tivoli Integration Composer Administrator Guide or see the Integration Composer help. v Integration Composer adds any new expressions in the imported mapping to the original mapping.fsn) into the mapping that you create. you can modify the data schema. Integration Composer repairs the errors. closes the warning window. complete the following steps: a. Go to step 14. select Save from the Select Action menu.Note: You cannot clear the check boxes. Go to step 14. Integration Composer saves the data schema. 15. Creating a mapping for your TADDM-to-CCMDB CI type data Before you can migrate CI type data. To create a mapping. Integration Composer closes the data schema and displays the IBM Tivoli Integration Composer window. click No. Select Close from the Select Action menu to close the data schema. Go to step 12 on page 27. make sure you have installed the data schemas for both your source and target CI type data. In the Data Schema Analysis warning window. and displays an Import dialog box indicating that the import is finished. You can either fix all errors indicated or fix no errors. complete the following steps: 1. 14. closes the Data Schema Analysis window. you must create a new adapter mapping for the data you want to migrate and then import the appropriate mapping file (TADDM71CITypeToCCMDB71Classification. For more information about working with data schemas. 28 Integration Adapter for TADDM: Implementation Guide . click Expand All. Before creating your mapping. After you import the data schema file. select one of the following options: – To make the data schema match the source database. click Close. the imported mapping has the following effect on the original mapping: v If an expression exists in both mappings. Integration Composer displays the IBM Tivoli Integration Composer window. click OK. click Yes. Review the options in this window and select the appropriate action. 16. Sign in to the Integration Composer application using a valid user ID and password. After you finish working with the data schema. v To close the dialog box without repairing the errors.

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

see “Modifying language properties” on page 37). Integration Composer saves your changes as mapping B and keeps mapping B open for editing. v To save the mapping with a new name. select the CCMDB target data source. click Yes. 2. Integration Composer saves your changes with the new mapping name. In the Mapping Name field in this window. Integration Composer displays the IBM Tivoli Integration Composer window. 11. you can modify your mapping expressions to suit your business needs. Select Create New Mapping. 10. From the Target drop-down list of available data sources. see the book IBM Tivoli Integration Composer Administrator Guide. To close the Mapping window. complete the following steps: 1. you must create a new adapter mapping for the data you want to migrate and then import the appropriate mapping file (TADDM71ActualCIToCCMDB71ActualCI. After you finish the mapping. in accordance with the instructions in Table 2 on page 11. Before creating your mapping. Integration Composer closes the Mapping window and displays the IBM Tivoli Integration Composer window. make sure you have installed the data schemas for both your source and target actual CI data. select Save As from the Select Action menu. For more information about performing this task. 3. For more information about how to work with mappings.appropriate language for your installation. refer to “Modifying language properties” on page 37. select Close from the Select Action menu. For instructions about how to modify mapping expressions. 4. From the Source drop-down list of available data sources. If you install Integration Composer using a language other than English. 13. select one of the following options: v To save the mapping with the existing name. A Close Mapping dialog box is displayed. For example. you must change the langcode property in any adapter mappings that you create to the appropriate language for your installation (for instructions. if you open mapping A and save it as B. Creating a mapping for your TADDM-to-CCMDB actual CI data Before you can migrate actual CI data. To create a mapping. 12. In the Close Mapping dialog box. The New Mapping window is displayed. select the TADDM data source. [Optional] Modifying the mapping expressions If appropriate. see the book IBM Tivoli Integration Composer Administrator Guide. Mapping A remains in its original form. Sign in to the Integration Composer application using a valid user ID and password.fsn) into the mapping that you create. Integration Composer opens a Save Mapping As window. select Save from the Select Action menu. type a new name for the mapping and click OK. Sign out of Integration Composer. 30 Integration Adapter for TADDM: Implementation Guide .

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

in addition to merely inserting and updating them. you must also rerun the qualifier script.v To save the mapping with the existing name. change it. Thus. and export it to another file. In other words. In the Close Mapping dialog box. The class qualifiers in the qualifier scripts allow Integration Composer to delete certain class records. In the Mapping Name field in this window. and then reimport the file to a data schema with a different name. you must run a qualifier script for that data schema before you can use it to execute a mapping. Important: If you import a data schema. the qualifier scripts add a delete_insert qualifier on the some of the classes in the Classification schema. see the book IBM Tivoli Integration Composer Administrator Guide. Integration Composer opens a Save Mapping As window. you must change the langcode property in any adapter mappings that you create to the appropriate language for your installation (for instructions. you must change the name in the script to the name of your new data schema. A Close Mapping dialog box is displayed. by loading the class qualifiers. see “Modifying language properties” on page 37). if you open mapping A and save it as B. [Optional] Modifying your mapping expressions If appropriate. select Save As from the Select Action menu. 32 Integration Adapter for TADDM: Implementation Guide . Mapping A remains in its original form. load the class qualifiers into the target CI type data schema using a qualifier script. For instructions about how to modify mapping expressions. when executing a mapping. Integration Composer saves your changes as mapping B and keeps mapping B open for editing. So. select Close from the Select Action menu. click Yes. The delete_insert qualifier informs Integration Composer which classes it should delete instances from if they are not found during a mapping execution. Specifically. 12. If you install Integration Composer using a language other than English. type a new name for the mapping and click OK. Before you run the qualifier script. you can modify your mapping expressions to suit your business needs. each time that you create a new data schema. 11. Loading the class qualifiers into the target CI type data schema After you create a mapping. v To save the mapping with a new name. 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. select Save from the Select Action menu. you are modifying the way Integration Composer handles data when it performs a data import. For example. Integration Composer closes the Mapping window and displays the IBM Tivoli Integration Composer window. To close the Mapping window. Integration Composer saves your changes with the new mapping name.

change the name CCMDB71ActualCI in the qualifier script to match the alternative name that you provided. The task is noted here so that you can verify that it was completed. run the qualifier script for your target data. refer to the log files located in the log folder in your Windows or UNIX installation directory.) v qualifierCCMDB71ActualCI. For error information. if you have not already done so. or if not. do it now. (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. 2. Using an appropriate database query tool. To perform this task. 4. complete the following steps: 1. the process of importing CI type or actual CI data will fail.db2 v qualifierCCMDB71ActualCI. If you did not create the classification and identifier as described below. change the name CCMDB71Classification in the qualifier script to match the alternative name that you provided. Using an appropriate database query tool. complete the following steps: 1. run the qualifier script for your target data. 4. Check for database script errors and resolve any errors. Chapter 3. Check for database script errors and resolve any errors. For error information. (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. Optional: If you named the new data schema something other than CCMDB71Classification in step 3 on page 23. Sign out of Integration Composer.sqs To load the class qualifiers into the data schema. you can load the class qualifiers into the target actual CI data schema using a qualifier script. if you have not already done so.ora v qualifierCCMDB71ActualCI. Verify your CI classifications The section that follows describes part of the Maximo installation procedure. 2.sqs To load the class qualifiers into the data schema.) v qualifierCCMDB71Classification.ora v qualifierCCMDB71Classification.db2 v qualifierCCMDB71Classification. 3. use whichever one of the following qualifier scripts is appropriate for your Maximo database type. Sign out of Integration Composer. Loading the class qualifiers into the target actual CI data schema After you create a mapping. refer to the log files located in the log folder in your Windows or UNIX installation directory.To perform this task. Installing the integration adapter 33 . 3. So be sure to verify that the task was completed. use whichever one of the following qualifier scripts is appropriate for your Maximo database type. Optional: If you named the new data schema something other than CCMDB71ActualCI in step 3 on page 26.

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

To execute the mapping. Chapter 3. Sign in to the Maximo Console user interface. and you supply all the values in the command rather than in the script. and ways to use. if the classification is moved within the classification structure. 3. 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. or deleted and re-added.sh instead of commandLine as the command name. No error messages are provided. Executing your mapping for CI types When you create a mapping. you must execute the mapping. commandLine TADDM-2-CCMDB-4-CI-Types maximo your_maximo_password administrator your_user_password maximo your_maximo_password See Appendix B. you define a set of expressions that specify how to transform instances from the TADDM data source to the target Maximo database in CCMDB. you can run a script that provides all the parameter values inside the file. Enter the following command. To execute your mapping for CI types. Go to the bin subdirectory in your Integration Composer installation directory. Close Integration Composer. or you can enter a detailed command that provides all the required parameter values directly on the command line. Important: If you do not create the classification and identifier described in this section. The commandLine command runs the script unedited. To verify active status or activate a CI type: 1. do the following steps: 1. Installing the integration adapter 35 . Type the parameter values in the same order as they appear in the example. 2. see “Using values specified on the command line” on page 56. “Executing a mapping. the commandLine command. To transform the TADDM data and import it into the Maximo database. installation_dir\bin. if running. the subsequent import process will stop without warning. but the CI Top-Level Class field will be blank or show the wrong class. Activating CI types Because CI types must be set up in CCMDB before you can import actual CI data. If the classifications structure changes such that the CI Top-Level Class no longer exists at the same place in the hierarchy.The class structure ID that is displayed is an actual value stored in the database. This section describes how to execute your mapping for CI types from the Integration Composer command line interface. To view the full syntax and parameter descriptions for this command. the detailed command is used. check the CI Types application in CCMDB to verify that CI types have been activated appropriately. They are noted in this book for your convenience. you must repeat this procedure to update the class structure ID. the CI Class Structure ID field will remain populated.” on page 53 for more information about all the options for. For this task. Consequently. and select Go To > Administration > CI Types. UNIX users must specify ./commandLine.

Go to the bin subdirectory in your Integration Composer installation directory. the message line will indicate status changed to ACTIVE for the CI type. click the status change icon to activate it. Whenever Integration Composer executes a mapping. 3. UNIX users must specify . and ways to use.sh instead of commandLine as the command name.COMPUTERSYSTEM is not ACTIVE. 2. 3. if running. installation_dir\bin. The fusion.” on page 53 for more information about all the options for. Integration Composer maintains information about mapping results and compilation errors in the fusion. refer to the online help for the CI Types application in CCMDB. Enter the following command.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. To ensure you have the most current information possible. To view the full syntax and parameter descriptions for this 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. If the CI Type Status for SYS./commandLine. Close Integration Composer. see “Using values specified on the command line” on page 56.2. When the task completes. commandLine TADDM-2-CCMDB-4-Actual-CIs maximo your_maximo_password administrator your_user_password maximo your_maximo_password See Appendix B. Find SYS.log file in the log subdirectory in the installation directory. the application provides information about mapping executions and data transactions as well as errors in the file. do the following steps: 1. the commandLine command. To execute your mapping for actual CIs. 36 Integration Adapter for TADDM: Implementation Guide . Note: The instructions provided above were the latest available at publication time.COMPUTERSYSTEM. refer to the IBM Tivoli Integration Composer Administrator Guide. “Executing a mapping. Type the parameter values in the same order as they appear in the example. Executing your mapping for actual CIs This section describes how to execute your mapping for actual CIs from the Integration Composer command line interface.

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

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. and inserts the result into the appropriate property and class in the target. you have to create a mapping expression that compensates for that difference. and other information technology objects by sites or organizations. you can insert literal values for Siteid and Orgid in the target. be sure to specify a valid value. for each instance created in the target. Integration Composer takes the value from the Size(bytes) property of the class RAM in the source. Similarly. Suppose that the value for a property in the source is expressed in kilobytes (KB). 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: 38 Integration Adapter for TADDM: Implementation Guide . Site and organization data is not a requirement. On subsequent mapping runs. you specifically must set these values in your Integration Composer mapping. Integration Composer transfers only the data that has changed since the last scan date. To include site or organization data. In this case. you must define an expression in your mapping to convert KB to MB. select one or more properties as Alternate Keys for the class to ensure uniqueness. For detailed. Because Integration Composer does not validate this data. 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. but target values are in megabytes (MB). when RAM is expressed in kilobytes in the source and megabytes in the target. (Note that a CI type mapping does not store scan dates. Mapping data for scan dates During its processing of an actual CI mapping. You need to modify your mapping so that Integration Composer performs the appropriate calculation to correctly convert the value from KB to MB. define: ‘RAM. illustrated steps on how to perform this task. If you want to differentiate computers. Mapping key properties When you create a mapping.Size(bytes)’/1024 When you execute your mapping. 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. if a class has only a Generated Key or a Foreign Key.Mapping data for units of measurement If your data source (TADDM) uses one unit of measurement and your target (Maximo database) uses another. network devices. see the book IBM Tivoli Integration Composer: Administrator Guide. divides this value by 1024.) When Integration Composer processes an actual CI mapping for the first time.

v If the last scan in the TADDM data source is the later than the one in the Integration Composer repository. When Integration Composer performs this operation. Tips for effective mappings 39 . Integration Composer skips the TADDM instance. Integration Composer processes the expressions for the TADDM instance and updates the last scan date in the repository. Chapter 4.v If the last scan in the TADDM data source is the same or earlier than the one in the Integration Composer repository. it ensures that it transfers only the data that has changed since the last scan date.

40 Integration Adapter for TADDM: Implementation Guide .

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

Iscontainment 1 Relation.Sourceclass classstructureid of Relation.Attributename Attribute.Table 9.FK PK PK Relationnum Sourceclass Targetclass Cardinality Containment Imported Propagatechange GV Relationrulesid Revrelationship Swapped Specification PK.FK Assetattrid Classstructureid Applydownhier Assetattributeid Attrdescprefix GV Classspecid Cs01 Cs02 Cs03 Cs04 Cs05 Domainid Inheritedfrom Linkedtoattribute Linkedtosection Lookupname Measureunitid Orgid Section Siteid Tableattribute AssetAttribute PK GV Assetattrid Assetattributeid Attrdescprefix Datatype Description Domainid Measureunitid Orgid Attribute.Propagatechange UNIDIRECTIONAL from synonymdomain table in maximo 0 1 ″EN″ 0 classstructureid of Class.Classname IBM Tivoli Application Dependency Discovery Manager <Class Name>.Swapped classstructureid of Relation.Attributename 0 Relation.Targetclass Relation. Mapping table for CI types (continued) CI types Class name Relation PK.FK Property Relationnum Classstructureid Comprelation Description Hasld Imported Langcode Linear GV Relationid Type RelationRule PK.Cardinality Relation.<Property Name> 42 Integration Adapter for TADDM: Implementation Guide .Reverserelationship Relation.Type Attribute.REF PK.

AK FK.LastModifiedBy Actual CI.Value <CCMDB 7.Guid Actual CI.Label + ″~″ + <CCMDB 7. Note: The expression <CCMDB 7. AK AK Actcispecid Actcinum Classstructureid Assetattrid Alnvalue Changeby Changedate Classspecid Displaysequence Linkedtoattribute Linkedtosection Mandatory Measureunitid Numvalue Refobjectid Refobjectname Section Tablevalue Source CI Attribute. GV FK.Classstructureid Actual CI.AttributeName Source CI Attribute.MeasureUnitId Source CI Attribute.Actciid> ″ACTCI″ Source CI Attribute.Actciid> or ″UNAVAILABLE″ + ″~″ + <CCMDB 7.Actciid>. AK Actcirelationid Sourceci Chapter 5.1 Actual Target CI. GV FK.<Property Name> Actual CI PK.1 Actual CI.LastModifiedTime Actual CI. as defined in the integration adapter for IBM Tivoli Application Dependency Discovery Manager.DisplayName + ″~″ + <CCMDB 7. Mapping table for CI types (continued) CI types Class name Property Siteid IBM Tivoli Application Dependency Discovery Manager <Class Name>.Actciid> or Actual CI.Actciid> AK AK Classstructureid Guid Changeby Changedate Description Hasld Langcode Lastscandt Actual CI. GV AK Actciid Actcinum Actual CI.1 Actual CI.1 Actual CI.Table 9. which appears in multiple places in this table.LastModifiedBy Actual CI.<Property Name> Actual configuration items The following table lists the mapping expressions for actual CIs. means that a value from the target data source is used in the mapping.Description ″EN″ Actual CI.Value Actual CI.LastModifiedTime CI Attribute PK. Mapping table for actual CIs Actual CIs Class Name Key Property Name IBM Tivoli Application Dependency Discovery Manager <Class Name>.LastModifiedTime Source CI Attribute. Integration adapter mappings for TADDM 43 .ClassSpecId CI Relationship PK.1 Actual CI. Table 10.

AK Ompcirlnid Ciguid Ompguid Changeby Changedate Cisourcetoken Source CI MSS. AK Ref.Actciid> or ″UNAVAILABLE″ + ″~″ + <CCMDB 7.DisplayName + ″~″ + <CCMDB 7.Actciid> or Actual CI.LastModifiedTime Source CI MSS.Actciid> or ″UNAVAILABLE″ + ″~″ + <CCMDB 7.MSSGuid Source CI MSS. GV FK.AncestorDisplayName + ″~″ + <CCMDB 7.Guid Actual Target CI.1 Actual CI.DisplayName + ″~″ + <CCMDB 7.1 Actual CI.1 Actual Target CI.LastModifiedBy Source CI MSS.MSSName Source CI MSS.Label + ″~″ + <CCMDB 7.Classification Actual CI.Description or Source CI MSS.HostName ″EN″ Source CI MSS.<Property Name> Actual Target CI PK.Actciid> or Actual CI.DisplayName Displaylabel Hasld Hostname Langcode Manufacturer Name Productname Version Source CI MSS.1 Actual Target CI.Label + ″~″ + <CCMDB 7.LastModifiedBy Source CI MSS.ManufacturerName Source CI MSS. GV AK Actciid Actcinum Actual Target CI. GV AK Ompid Ompguid Changeby Changedate Description Source CI MSS. Mapping table for actual CIs (continued) Actual CIs Class Name Ref.SourceToken OMP PK.Actciid> or Actual Target CI.Classstructureid Actual Target CI.Actciid> or Actual CI.DisplayName 44 Integration Adapter for TADDM: Implementation Guide .1 Actual CI.LastModifiedBy CI Relationship.1 Actual CI.Actciid> Changeby Changedate Targetguid Swapped CI Relationship.1 Actual CI.LastModifiedBy Actual Target CI.ProductVersion Source CI MSS.LastModifiedTime OMP Relationship PK.Table 10.Targetguid 0 IBM Tivoli Application Dependency Discovery Manager <Class Name>.ProductName Source CI MSS.1 Actual Target CI.LastModifiedTime Source CI MSS.LastModifiedTime Actual Target CI. AK AK Property Targetci Relationnum Ancestorci CI Relationship.AncestorLabel + ″~″ + <CCMDB 7.Actciid> AK Guid Changeby Changedate Classstructureid Description Hasld Langcode Lastscandt Actual Target CI.LastModifiedTime CI Relationship.Description ″EN″ Actual Target CI.

Classification Actual CI.1 Actual Target CI.Actciid> or ″UNAVAILABLE″ + ″~″ + <CCMDB 7. Mapping table for actual CIs (continued) Actual CIs Class Name Reverse CI Relationship PK.Actciid> AK Guid Changeby Changedate Classstructureid Description Hasld Langcode Lastscandt Actual Source CI.Guid Actual Source CI.1 Actual Target CI. GV AK Actciid Actcinum Actual Source CI.1 Actual CI.DisplayName + ″~″ + <CCMDB 7.1 Actual CI.1 Actual Target CI.AncestorDisplayName + ″~″ + <CCMDB 7.LastModifiedTime Chapter 5.LastModifiedTime Reverse CI Relationship.Actciid> or Actual CI. GV Ref.1 Actual CI.Actciid> or Actual CI. AK FK.AncestorLabel + ″~″ + <CCMDB 7.Actciid> or ″UNAVAILABLE″ + ″~″ + <CCMDB 7.LastModifiedBy Reverse CI Relationship.Classstructureid Actual Source CI.1 Actual CI.Label + ″~″ + <CCMDB 7.Sourceguid 1 IBM Tivoli Application Dependency Discovery Manager <Class Name>.Actciid> Changeby Changedate Sourceguid Swapped Reverse CI Relationship.Description ″EN″ Actual Source CI.Actciid> or Actual Source CI.Label + ″~″ + <CCMDB 7.1 Actual CI.DisplayName + ″~″ + <CCMDB 7. AK AK Property Actcirelationid Sourceci Targetci Relationnum Ancestorci Reverse CI Relationship. Integration adapter mappings for TADDM 45 .<Property Name> Actual Source CI PK.LastModifiedTime Actual Source CI.LastModifiedBy Actual Source CI.Actciid> or Actual CI.Table 10.

46 Integration Adapter for TADDM: Implementation Guide .

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

ibm.ibm. On the CCMDB database server. You only need to copy the scripts appropriate for your Maximo database type (all the . Your connection settings might look something like this: Connection Method: IBM Configuration Discovery and Tracking API Host Name: myhostname. define a data source connection for the source actual CI data. define a data source connection for the source CI type data. select the TADDM 7.com Host Port: 9530 User Name: administrator Password: ******** 48 Integration Adapter for TADDM: Implementation Guide .austin.* script (either . type TADDM-71x-CI-Types. .db2. Checklist for installing the integration adapter (continued) h a.ora. When defining the new data source. Using the appropriate database utility. Copy the database scripts and qualifier scripts for both CI types and actual CIs to a location where you can run them with a database query tool.ora. . From the Integration Composer user interface. h e. In the Data Source field. . Copy the schema files and mapping files for both CI types and actual CIs to the Integration Composer server.db2. h b. install the data schema for the source actual CI data using a database script. Typically this location would be the Integration Composer server or the CCMDB database server.Table 11. Using the appropriate database utility.sqs) for your Maximo database type.ora. On the CCMDB database server. install the data schema for the source CI type data using a database script.db2.com Host Port: 9530 User Name: administrator Password: ******** h f.1 Actual CI data schema.sqs files listed in “Integration adapter files” on page 2). or .tiv. .sqs files listed in “Integration adapter files” on page 2).db2. From the Integration Composer user interface. You only need to copy the scripts appropriate for your Maximo database type (all the .austin. on the Data Schema page. or . h c. or . on the Data Schema page. In the Data Source field. When defining the new data source.sqs) for your Maximo database type. Your connection settings might look something like this: Connection Method: IBM Configuration Discovery and Tracking API Host Name: myhostname.ora. h d. or . type TADDM-71x-Actual-CIs.tiv. run the createTADDM71ActualCIDataSchema.* script (either . run the createTADDM71CITypeDataSchema. select the TADDM CI Type data schema.

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

In the Mapping Name field. It is noted here for your convenience. On the CCMDB database server. 2. If you install Integration Composer using a language other than English. On the CCMDB database server. From the Integration Composer user interface. 4. 50 Integration Adapter for TADDM: Implementation Guide . In the Import Mapping dialog box. execute the mapping for CI types. From the Maximo Console user interface: 1.Table 11.ora.c.* script (either . type TADDM-2-CCMDB-4-Actual-CIs. load the class qualifiers to the target CI type data schema. Using the appropriate database utility.db2. h a./commandLine. modify mapping expressions. h n. see the book IBM Tivoli Integration Composer Administrator Guide. From the command line. before you proceed with the actual CI mapping in step 4.fsn. For instructions about how to modify mapping expressions.sh instead of commandLine as the command name. h m. TADDM71ActualCIToCCMDB71ActualCI.sqs) for your Maximo database type. You must execute this mapping first. From the Maximo Console user interface.db2. select the mapping file for CI type data. 3. run the qualifierCCMDB71ActualCI. . for example ″FR″ (including the quotation marks) for French. Import your data The following are repeatable steps that you can perform in the production environment after the Integration Adapter for TADDM is installed. Select Go To > Administration > Classifications. create a mapping for actual CI data. Select Go To > Administration > Organizations. . That is. Verify your CI classifications The following step is part of the Maximo installation procedure. classify your CIs. Syntax: commandLine [-delete] mappingName repositoryUser repositoryPwd sourceUser sourcePwd targetUser targetPwd Sample command: commandLine TADDM-2-CCMDB-4-CI-Types maximo maximopw administrator collation maximo maximopw On UNIX-based operating systems. change the langcode property in any adapter mappings that you create. and the mapping must be successful. load the class qualifiers to the target actual CI data schema.ora. replace the ″EN″ value in the langcode properties with the appropriate literal value for your installation.* script (either . Create a top-level CI classification. [Optional] From the Integration Composer user interface. or .sqs) for your Maximo database type. run the qualifierCCMDB71Classification. or . Define a class structure identifier for the top-level CI class. h a. They are noted here for your convenience. specify . Using the appropriate database utility. Checklist for installing the integration adapter (continued) h k. h l.

Syntax: commandLine [-delete] mappingName repositoryUser repositoryPwd sourceUser sourcePwd targetUser targetPwd Sample command: commandLine TADDM-2-CCMDB-4-Actual-CIs maximo maximopw administrator collation maximo maximopw On UNIX-based operating systems. From the Maximo Console user interface. 2. h c. specify . click the status change icon to activate it.Table 11./commandLine.sh instead of commandLine as the command name. execute the mapping for actual CIs. check that CI types were activated. Select Go To > Administration > CI Types. the message line will indicate status changed to ACTIVE for the CI type. Advanced users’ checklist for installing the integration adapter 51 .COMPUTERSYSTEM is not ACTIVE. 3. Appendix A. Checklist for installing the integration adapter (continued) h b. When the task completes. From the Maximo Console user interface: 1. From the command line. Note that executing the mapping for CI types (step 10) must be completed and successful before executing the mapping for actual CIs.COMPUTERSYSTEM. If the CI Type Status for SYS. Find SYS.

52 Integration Adapter for TADDM: Implementation Guide .

you must execute the mapping. Executing a mapping When you create a mapping.Appendix B. or you can enter a detailed command that provides all the required parameter values directly on the command line. 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: © Copyright IBM Corp. On Microsoft Windows operating systems it runs commandLine. repository user name and password. For productivity and other reasons. Identification parameters Provide values for some identification parameters that specify mapping name. 2008 53 .bat file. you can run a script that provides all the parameter values inside the file. To transform the source data and import it from the source location into the target (Maximo) database. you execute your mapping from the Integration Composer command line interface. However. when importing data. you must delete the last scan history. If you have more than one mapping to execute. source user name and password. if you modify a mapping and you want to implement the change.sh file instead).bat is in the bin subdirectory in the Integration Composer installation directory. you provide all the necessary parameter values inside the file. Either file is located in the bin subdirectory of the Integration Composer installation directory. You can edit the command file parameters and create different files for different mappings. To execute the mapping. Before you execute the mapping. To accomplish this.sh. on UNIX-based operating systems it runs commandLine. There are several parameters to consider when executing a mapping: Delete last scan history option Setting this parameter is optional. 2007. Executing a mapping runs a script. you might want all data processed. Use the -delete option only if you want all data processed when you execute the mapping.bat. Using values specified in a file One way to execute a mapping is to run the commandLine command using a modified commandLine. By default. and target user name and password for mapping execution. Integration Composer processes only the data that has changed since the last scan date. File parameters The file commandLine. 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. you can edit the file and save separate files for each mapping that you want to execute. you define a set of expressions that specify how to transform instances from a source to a target.

You can edit this section as follows to specify values for the various identification parameters to use during mapping execution: Example 2 set set set set set set set MAPPINGNAME=TADDM-2-CCMDB-4-CI-Types REPOSITORYUSER=maximo REPOSITORYPWD=******** SOURCEUSER=administrator SOURCEPWD=******** TARGETUSER=maximo TARGETPWD=******** If any parameter value contains spaces. repositoryPwd The login password for the Integration Composer repository. for example. maximopw. as follows: 54 Integration Adapter for TADDM: Implementation Guide . for example. maximopw. maximo. targetUser The login user name for the target database. sourcePwd The login password for the TADDM data source. targetPwd The login password for the target database. for example. enclose the value in quotation marks. for example.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 set set set set set set MAPPINGNAME=%1 REPOSITORYUSER=%2 REPOSITORYPWD=%3 SOURCEUSER=%4 SOURCEPWD=%5 TARGETUSER=%6 TARGETPWD=%7 The identification parameters are defined as follows: mappingName The name of the predefined mapping. administrator. collation. TADDM-2-CCMDB-4-CITypes. sourceUser The login user name for the TADDM data source. maximo. for example. for example. for example. repositoryUser The login user name for the Integration Composer repository.

Execute the mapping a. installation_dir\bin. complete the following steps: 1. Executing a mapping 55 . if you do not have a password for a database. Press Enter to close the task. modify the identification parameters by substituting appropriate values. Open a command prompt. add the -delete option to the file. b. d. enter two single–quotation marks without a space in between. See the ″Using values specified on the command line″ section for details on this alternative. Edit the file a. Save the modified file and close the editor. 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.set MAPPINGNAME="TADDM 2 CCMDB 4 CI Types" If any parameter value represents a database null.) To delete the last scan history before executing the mapping. d. to execute mappings. Alternatively. rather than by modifying the file itself. Enter the appropriate command: Windows: UNIX: commandLine . e. Navigate to the installation_dir\bin directory and open the commandLine.sh The output displays on your screen. as shown previously in Example 2. c. such as Microsoft Notepad. such as Windows scheduler. Attention: When using the -delete option. If Integration Composer is open. close the application. so that the last scan history is not inadvertently deleted the next time you run the file. c. If you use a Windows scheduler. Open any text editor. be sure to remove your entry after running the file. (Optional. For example.bat file. you can run the file by specifying the -delete option and your identification parameters on the command line. Navigate to the bin subdirectory in your Integration Composer installation directory. Using a scheduling program You can use a scheduling program. as follows: set TARGETPWD=’’ To edit and run the file. To configure the file for unattended mapping execution./commandLine. 2. b. as shown previously in Example 1. e. enter two single–quotation marks for this parameter value.

for example.sh instead of commandLine as the command name. for example. Usage: v Close Integration Composer before issuing the command. for example. type maximo. for example. targetUser The login user name for the target database. Examples: 56 Integration Adapter for TADDM: Implementation Guide . sourceUser The login user name for the TADDM data source. sourcePwd The login password for the TADDM data source. mappingName The name of the predefined mapping. targetPwd The login password for the target database. The commandLine command runs the unedited script. v UNIX users must specify . Syntax: commandLine [-delete] mappingName repositoryUser repositoryPwd sourceUser sourcePwd targetUser targetPwd Parameters: -delete [Optional. To execute a mapping by typing values directly on the command line.] Specify -delete if you want the mapping last-scan history to be deleted prior to executing the mapping. repositoryPwd The login password for the Integration Composer repository./commandLine. installation_dir\bin. type maximo. use the commandLine command as described below. and you supply all the values in the command rather than in the file. administrator. type maximopw. type TADDM-2-CCMDB-4-CI-Types. for example. collation. v Always type the parameter values for your command in the same order as they appear in the command syntax. repositoryUser The login user name for the Integration Composer repository. type maximopw. for example.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. v Issue the command from the bin subdirectory in your Integration Composer installation directory. for example.

sh instead of commandLine as the command name. specify .This command example (on Windows) uses the -delete option to remove the last scan history. Appendix B. Executing a mapping 57 . 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./commandLine.

58 Integration Adapter for TADDM: Implementation Guide .

NY 10504-1785 U. 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. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. these changes will be incorporated in new editions of the publication. to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. or service may be used. or features discussed in this document in other countries. program. 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. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT.A. or service.S. program. IBM may not offer the products. 2008 59 . or service is not intended to state or imply that only that IBM product. You can send license inquiries. EITHER EXPRESS OR IMPLIED. 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. 2007. Some states do not allow disclaimer of express or implied warranties in certain transactions. to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome. Minato-ku Tokyo 106-0032. The furnishing of this document does not grant you any license to these patents.A. © Copyright IBM Corp. this statement may not apply to you. INCLUDING. This information could include technical inaccuracies or typographical errors.S. program. IBM may have patents or pending patent applications covering subject matter described in this document. However. Changes are periodically made to the information herein. services. in writing. therefore. 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 functionally equivalent product. it is the user’s responsibility to evaluate and verify the operation of any non-IBM product. contact the IBM Intellectual Property Department in your country or send inquiries. BUT NOT LIMITED TO. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Any reference to an IBM product. program. For license inquiries regarding double-byte (DBCS) information. in writing. Consult your local IBM representative for information on the products and services currently available in your area. or service that does not infringe any IBM intellectual property right may be used instead.Notices This information was developed for products and services offered in the U.

All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice.A. compatibility or any other claims related to non-IBM products.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. which illustrate programming techniques on various operating platforms. marketing or distributing application programs conforming to the application programming interface for the operating 60 Integration Adapter for TADDM: Implementation Guide . IBM International Program License Agreement. 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. including in some cases. brands. are current and are subject to change without notice. Any performance data contained herein was determined in a controlled environment. payment of a fee. Users of this document should verify the applicable data for their specific environment. subject to appropriate terms and conditions. and represent goals and objectives only. some measurements may have been estimated through extrapolation. COPYRIGHT LICENSE: This information contains sample application programs in source language. and products. Department 49XA 3605 Highway 52 N Rochester. 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. companies. for the purposes of developing. This information is for planning purposes only. their published announcements or other publicly available sources. the results obtained in other operating environments may vary significantly. using. You may copy. should contact: IBM Corporation Software Interoperability Coordinator. MN 55901 U. The information herein is subject to change before the products described become available. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. the examples include the names of individuals. and distribute these sample programs in any form without payment to IBM.S. Information concerning non-IBM products was obtained from the suppliers of those products. or any equivalent agreement between us. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM has not tested those products and cannot confirm the accuracy of performance. Such information may be available. Actual results may vary. All IBM prices shown are IBM’s suggested retail prices. To illustrate them as completely as possible. Dealer prices may vary. Therefore. This information contains examples of data and reports used in daily business operations. Furthermore. modify.

Trademarks For trademark attribution. and Internet Explorer are trademarks of Microsoft Corporation in the United States.platform for which the sample programs are written. the Windows logo. must include a copyright notice as follows: © (your company name) (year). cannot guarantee or imply reliability. IBM. Notices 61 . Other company. or both: IBM. Sample Programs. visit the IBM Terms of Use Web site (http://www. Windows. _enter the year or years_. and/or other countries. the photographs and color illustrations may not appear. Tivoli. UNIX is a registered trademark of The Open Group in the United States and other countries. Inc. These examples have not been thoroughly tested under all conditions. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems. PostScript. DB2.ibm. Portions of this code are derived from IBM Corp. and the Tivoli logo are trademarks or registered trademarks of International Business Machines Corporation in the United States. or function of these programs. and service names may be trademarks or service marks of others. All rights reserved. the Adobe logo. therefore. Each copy or any portion of these sample programs or any derivative work.com/legal/us/) The following terms are trademarks of International Business Machines Corporation in the United States. serviceability. the IBM logo. product. Microsoft. and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States. or both. or both. Adobe. © Copyright IBM Corp. If you are viewing this information softcopy. other countries. other countries. other countries. in the United States and other countries.

62 Integration Adapter for TADDM: Implementation Guide .

.

Printed in USA .

Sign up to vote on this title
UsefulNot useful