Rational Asset Manager and Tivoli Change and Configuration Management Database integration
This chapter covers the integration of IBM Rational Asset Manager and IBM Tivoli Change and Configuration Management Database (CCMDB). Using this integration, you can automatically create assets in Rational Asset Manager from existing configuration items (CIs) in the CCMDB. You can also use Rational Asset Manager as a definitive software library (DSL) for storing software images.
This chapter contains the following topics:
18.1 Rational Asset Manager
Many software development organizations do not have a central place to store their reusable, high-value assets; therefore, they often store an asset as just another version of an artifact among the millions of other versioned artifacts in a software configuration management (SCM) system. Sometimes, they resort to storing the assets on a web server or on a wiki site. Even when companies provide a consistent place to store and search for these assets, the metadata that describes them is typically either inconsistent or nonexistent. Such makeshift arrangements can cause difficulty in finding, assessing, and reusing assets quickly. Rational Asset Manager ends this confusion by providing a central place to store reusable, high-value assets.
Rational Asset Manager also enables you to track versioned artifacts back to the assets that were used to create them. This traceability can help developers more easily maintain existing assets and create new versions, which saves them time, thus saving the company money.
18.2 Definitive Media Library
Definitive Media Library (DML), as defined by ITIL, is one or more locations in which the definitive and approved versions of all software configuration items (CIs) are securely stored. It may also contain associated CIs such as documentation, licences, and software keys
 
Note: In this scenario, we use the DML term within the context of CCMDB and IBM Tivoli Release Process Manager.
The DML is a single logical storage area, even if multiple locations exist. All CIs in the DML are under the control of CCMDB. See Figure 18-1 on page 547 to better understand the DML and interaction with CCMDB.
Figure 18-1 Definitive Media Library
18.3 Scenario overview
Figure 18-2 shows the architectural diagram of the scenario.
Figure 18-2 Scenario architecture
 
Note: For more information about the architecture of this integration, see How to integrate IBM Rational Asset Manager with your IBM Tivoli database, by Ramin Sanaie:
With this integration, you can create assets in Rational Asset Manager from existing configuration items (CIs) in the CCMDB. You can also use Rational Asset Manager as a Definitive Media Library (DML) for storing software images.
Note that this integration is bidirectional. Assets from Rational Asset Manager can be sent to the CCMDB and the CIs from CCDMB can be sent to the Rational Asset Manager. After the implementation, you will have a single repository for software images: the DML. Developers will be able to automatically create assets in Rational Asset Manager from existing CIs in CCMDB and use Rational Asset Manager as a DML for storing software images.
The assets created by Rational Asset Manager from a CCMDB CI, are referred to as remote assets. These remote assets contain a link to the CI in the CCMDB, and, similarly, you can navigate to the asset in Rational Asset Manager from the CI in the CCMDB. The remote asset in Rational Asset Manager is a reference to a remote resource, meaning that the asset is managed in a remote repository. In addition to storing the reference in the remote resource, the Rational Asset Manager repository stores metadata information for the asset, such as attributes and categories.
Similarly when the CCMDB creates new CIs from Rational Asset Manager assets, this information is stored in the CI, indicating that the asset originated in Rational Asset Manager. If the Rational Asset Manager repository is then synchronized with the CCMDB, repository and a remote asset is created from the CCMDB CI, the remote asset and the original asset become related assets: the original asset will have the “publish as” relationship to the remote asset, and the remote asset will have the “publish by” relationship to the original asset.
Remote assets in the Rational Asset Manager repository retain much of the metadata from the CCMDB CI. They are also given the asset type of Configuration Item and the category of CCMDB. These can be used as search filters to search for remote assets faster in the Rational Asset Manager repository.
After the asset is created in CCMDB as CI, it becomes available to the other applications running on Tivoli Process Automation Engine, such as Tivoli Service Request Manager and IBM Tivoli Release Process Manager
18.4 Products involved
To implement this scenario, your environment must have the following products installed:
•IBM Tivoli Change and Configuration Management Database 7.2.0.1
•IIBM Tivoli Release Process Manager 7.1.2
•IBM Tivoli Application Dependency Discovery Manager 7.2.0.1
•IBM Tivoli Integration Composer 7.2.0.1
•IBM Rational Asset Manager 7.2.0
18.5 Benefits
The benefits of this integration are as follows:
•Increased productivity by automated creation of assets in Rational Asset Manager from existing CIs in the CCMDB and automated creation of CIs in CCMDB from Rational Asset Manager assets.
•Access to the linked data (assets linked to the CIs and CIs linked to assets) by various groups in an organization for various perspectives.
•Secure and centralized control of the company software assets from a single place.
18.6 Implementation
In this section, we describe the implementation steps for this scenario.
18.6.1 Downloading and installing the integration module
To integrate CCMDB with Rational Asset Manager, the first thing is to install a module for the products talk to each other. This module is present in the Rational Asset Manager. In this part we will show how to install it in the CCMDB.
1. Log on the Rational Asset Manager (Figure 18-3) with your admin user account.
Figure 18-3 RAM Home window
2. Click Help → Extensions. See Figure 18-4 on page 550.
Figure 18-4 RAM Extensions
3. Select the imram_x.x.zip file (where x.x is the version of Rational Asset Manager that you are using) to download the integration module. See Figure 18-5.
Figure 18-5 The .zip files for integrating with CCMDB
 
Note: Do not extract the .zip file; only download and save it.
4. Install the Integration module in the CCMDB. First, run a backup, in case something goes wrong.
Back up the maxdb71 database and the registry on the CCMDB server as follows:
a. To back up maxdb71 in IBM DB2, run the backup command in a DB2 command window, as shown in Example 18-1.
Example 18-1 Back up maxdb71
CONNECT TO MAXDB71;
QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS;
CONNECT RESET;
BACKUP DATABASE MAXDB71 TO "C:db2backupfolder" WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 WITHOUT PROMPTING;
CONNECT TO MAXDB71;
UNQUIESCE DATABASE;
CONNECT RESET;
 
Note: If your Maximo database is Oracle or SQL Server, review the database documentation for the appropriate command line to use to back up your database
b. To back up the registry, use the following path (see Example 18-2):
C:Program FilesIBMCommonacsiin>backupdb.cmd
Example 18-2 Backup the registry
C:Program FilesIBMCommonacsiin>backupdb.cmd
ACUDB0004I A database backup command was issued, but directory C:Program FilesIBMCommonacsiackupDBs, the default directory where database backup information is stored, does not exist. Deployment Engine will create the directory.
ACUDB0005I The backupdb command completed successfully.
5. Use the Tivoli base services to install the integration module on the CCMDB repository. Open a command line and change to CCMDBInstallationin directory.
6. Run solutionInstallerGU file. See Example 18-3.
Example 18-3 solutionInstallerGU
C:>cd C:ibmSMPin
C:ibmSMPin>solutionInstallerGUI.bat
The base services window opens (Figure 18-6 on page 552).
Perform the following steps to install the Rational Asset Manager IM (imram_x.x.zip) by using the Process Solution Installer (PSI):
a. Select a language and click OK.
Figure 18-6 Language window
The next window opens (Figure 18-7).
Figure 18-7 Introduction window
b. Click Next.
c. On the next window (Figure 18-8), select a PSI installable package by clicking Choose, selecting imram_x.x.zip, and clicking Next.
Figure 18-8 Choose PSI Package
The package is validated (Figure 18-9).
Figure 18-9 Validating Package window
 • If an error occurs, return to step 3 on page 550 and download the file again.
 • If the package is ok, the next window (Figure 18-10 on page 554) opens.
Figure 18-10 Package Validation Results
d. To proceed, accept the terms in the license agreement. See Figure 18-11.
Figure 18-11 Software license agreement
e. Optional: If you want to install the Language Support Feature, besides the Rational Asset Manager Integration Module, select the check box in Figure 18-12.
Figure 18-12 Adding features
f. Enter the required user IDs and passwords, as in Figure 18-13 on page 556.
Figure 18-13 Login information
g. Click Next, and verify that all requirements have been satisfied. See Figure 18-14.
Figure 18-14 Pre-Install Summary
h. When the installation completes successfully, a message is displayed (Figure 18-15). Click Next. In the next window, click Done.
Figure 18-15 Package deployment results
7. Log in to Maximo (http://host_name/maximo) and click Help → System Information.
8. Verify that the Rational Asset Manager integration module is installed. See Figure 18-16.
Figure 18-16 Maximo System Information
The integration package is now installed.
18.6.2 Creating a discovery library adapter (DLA) to import in the TADDM
This section has instructions for manually generating the DLA output file and installing and configuring a discovery library adapter that will create a DLA output file by searching the Rational Asset Manager repository.
 
Note: DLA is discovery library adapter. To propagate information contained in a Rational Asset Manager to a operational management product (OMP) we have to create a DLA output file.
Perform the following steps:
1. Create a DLA output file that uses a search filter to define a set of assets for the DSL:
a. In the Rational Asset Manager web client, click Administration. See Figure 18-17.
Figure 18-17 Administration button
b. Click the name of the community that you want to connect to the CCMDB, for example, RAMCCMDB, as shown in Figure 18-18 on page 559.
Figure 18-18 Rational community
c. Click the community name you have just created.
d. Click the Connections tab (Figure 18-19).
Figure 18-19 Connections tab
e. In the Change and Configuration Management Database section (Figure 18-20), click New Connection.
Figure 18-20 Create a CCMDB connection
f. On the connection properties page, complete the form with the following details of the CCMDB installation:
 • Name: Type a name for the connection, for example RAM-CCMDB.
 • Description: Optionally, type a detailed description of the connection. The description can include spaces and special characters.
 • URL: Enter the fully qualified URL, including the port number, to use when accessing the CCMDB application, for example:
http://ccmdbserver/meaweb/services
 • Login: Type the user ID of a user who is authorized to access the CCMDB.
 • Password: Type the user’s password for accessing CCMDB.
 • Default asset owner: Click Select Owner to choose the Rational Asset Manager user who will own the assets that are created in the Rational Asset Manager repository from the CCMDB CIs.
 • Synchronization schedule: Click Edit to modify how frequently the Rational Asset Manager repository will synchronize with the CCMDB repository. You may choose to synchronize daily or weekly at a specific time or at an interval specified in minutes or hours.
g. Click the Test Connection. If the connection is successful, the following message is displayed (see Figure 18-21 on page 561):
Connection to CCMDB server was successful
 
Note: If an error message is indicated (in a red box), verify the URL you typed.
h. Click OK.
Figure 18-21 CCMDB Connection Properties
2. Click Assets to go to the Search for Assets page. See Figure 18-22.
Figure 18-22 Assets tab
3. Search for the approved assets (Figure 18-23 on page 562). Use the filter at the left side, or type the following text in the search field:
ramSearch:(1fState,approved)
Figure 18-23 Asset State
4. Determine how many assets were displayed, and then copy the entire search shortcut from the text field. The search shortcut is an icon with a magnifying glass in front of a clipboard. See Figure 18-24.
Figure 18-24 View Search Shortcut
5. Return to the Connection Properties page and paste the search shortcut into the Search Text field, under the topic Discovery Library Adapter Generation. See Figure 18-25 on page 563.
Figure 18-25 Synchronization schedule of CCMDB Connection
6. To create an output DLA file to be saved on the file system, click Generate DLA Output, which creates an .xml file.
7. Save the .xml file in the TADDM server.
18.6.3 Loading the DLA output file into the TADDM
A DML requires an operational management product (OMP). To create an OMP in the CCMDB, use the TADDM to propagate information contained in a Rational Asset Manager DLA output file to the CCMDB.
Perform the following steps:
1. Transfer the Rational Asset Manager DLA output file to TADDM server.
2. In the TADDM server, from a command line, navigate to the cmdbdistin folder and run the following command (see Example 18-4):
loadidml -f <dla_output_file> where <dla_output_file> is the full path to and name of the discovery library adapter file
 
Note: To run the loadidml.sh or loadidml.bat command, you must be logged in as the taddm user.
Example 18-4 loadidml -f
taddm2:/opt/IBM/cmdb/dist/bin # su - cmdbuser
cmdbuser@taddm2:~> cd /opt/IBM/cmdb/dist/bin
cmdbuser@taddm2:/opt/IBM/cmdb/dist/bin> ./loadidml.sh -f /opt/IBM/cmdb/ram-to-ccmdb/RAMv7201.ramlnx.2010-06-07T20.34.47.340Z.refresh.xml
Bulk Load Program starting.
Bulk Load Program running.
Bulk Load Program running.
Bulk Load Program running.
Bulk Load Program succeeded. Return code is: 0
0
Bulk Load Program ending.
3. Verify that the DLA output file was loaded. Launch the TADDM application and click Start Product Console. If prompted, enter your user ID and password.
4. Click Edit → MSS, as shown in Figure 18-26.
Figure 18-26 Accessing MSS from TADDM
5. The MSS list contains an entry that matches the DLA output file. The product name in the MSSName entry is Rational Asset Manager. See Figure 18-27 on page 565.
Figure 18-27 MSS list
6. Select the MSS and click List CIs (Configuration Items). See Figure 18-28.
Figure 18-28 MSS list
7. Click OK when the following message is displayed:
This operation can take a long time. Do you want to continue?
8. The Configuration Item List in Figure 18-29 shows the Rational Asset Manager assets.
Figure 18-29 Configuration Item List
18.6.4 Mapping actual CIs from TADDM to CCMDB
Tivoli Integration Composer uses information from the Rational Asset Manager DLA output file to create the OMP in CCMDB. This section describes mapping actual CIs from TADDM to CCMDB by using Tivoli Integration Composer adapter.
To set up the CI type adapter, perform the following steps:
1. Create a TADDM data source:
a. Start the Tivoli Integration Composer application (for example, in the <ITIC_root_dir>in folder, run startFusion.bat (for Windows) or startFusion.sh (for UNIX-based systems). Log on to the Tivoli Integration Composer.
b. Click Define New Data Source. See Figure 18-30.
Figure 18-30 New Data Source on Tivoli Integration Composer
c. Select TADDM72CIType. See Figure 18-31.
Figure 18-31 New Data Source
d. For the data source name, enter TADDM72CIType. See Figure 18-32.
Figure 18-32 Define the Data Source name
e. Enter the following information (see Figure 18-33 on page 568):
 • Select Connection Method: Select IBM Configuration and Tracking API.
 • Host name: Type the host name for the TADDM server (not the database).
 • Port: Type the RMI port for the TADDM server. The default value is 9530. If you are using SSL, the default value is 9531.
 • Trusted Location: Type the fully-qualified path of the SSL certificate file to use to connect to a server, such as the Configuration Discovery (Not required field) and Tracking Server, for example:
c:Integration Composer...jssecacerts.cert
 • User name: Type the user name for a TADDM account with administrator privileges.
 • Password: Type the password for the TADDM use.
Figure 18-33 Data Source connection information
f. Click Test Connection. If the test is successful, the pop-up window shown in Figure 18-34 opens. If an error occurs, check the values you have entered.
Figure 18-34 Test connection
ii. Click OK and then click Finish.
2. Create CI type mappings:
a. Go to Tivoli Integration Composer home.
b. Click Create New Mapping. See Figure 18-35 on page 569.
Figure 18-35 Creating a new Mapping
c. On the next window, select the following values (shown in Figure 18-36):
 • Source: TADDM72CIType
 • Target: CCMDB72citype
 • Mapping Name: taddm-2-ccmdb-ci-types
Figure 18-36 New mapping
d. Complete the Password field and verify that the other required data from TADDM server is correct.
e. Click Test Connection. If the test succeeded, click OK and click Finish. See Figure 18-37 on page 570.
Figure 18-37 Test the connection
f. Fill in the appropriate data for your environment:
 • Connection Method:
DB2: IBM DB2 JDBC Driver
Oracle: Oracle JDBC Thin Driver
SQL server: i-net OPTA JDBC Driver for Microsoft SQL Server 7/2000
 • Host name: Type the host name for the CCMDB database server.
 • Port: Type the port number for the machine. The default values are as follows:
DB2: 50005
Oracle: 1521
SQL server: 1433
 • Database: Type the name of the database: maxdb71.
 • User name: Type the user name for the user who created the Maximo tables in the database.
 • Password: Type the user's password.
 • Table owner: Type the user name for the user who created the Maximo tables in the database.
g. Click Test Connection. See Figure 18-38.
Figure 18-38 Connection Information
h. When you receive a pop-up window indicating that the information is OK, proceed and click Finish.
i. A window showing the relationships opens. If there is no relationship, you must import an .fsn file with the relationships by clicking Select Action → Import and then, selecting the *.fsn file.
j. Make any other changes you want and then click Select Action → Save. If you do not want to make further changes, click Select Action → Close.
3. Execute the CI type mapping:
a. Open a command (cmd) prompt.
b. Change directory (cd) to the integration composerin directory.
c. Run the following command, where <password> is the password for the Maximo database user:
commandline taddm-2-ccmdb-ci-types maximo password administrator collation maximo password
 
Note: The commandline.bat/sh parameters are case-sensitive.
Example 18-5 Run commandline.bat
C:Integration Composer>commandline.bat taddm-2-ccmdb-ci-types maximo PASSWORD administrator collation maximo PASSWORD
Integration Composer will now start.
IBM Tivoli Integration Composer 7.2.0.1 Build 200911031354
08 Jun 2010 11:06:32:953 [INFO] IBM Tivoli Integration Composer 7.2.0.1 Build 200911031354
Mapping: taddm-2-ccmdb-citypes
08 Jun 2010 11:06:32:969 [INFO] ObjectManager created. (This should only happen once.)
Creating data source Fusion...08 Jun 2010 11:06:32:985 [INFO] GlobalContext created. (This should only happen once.)
08 Jun 2010 11:06:32:985 [INFO] ResourceManager created. (This should only happen once.) : 0 resource(s) loaded.
08 Jun 2010 11:06:33:453 [INFO] ResourceManager : Loading resource labels : 577 resource(s) loaded.
08 Jun 2010 11:06:33:485 [INFO] ResourceManager : Loading resource messages : 279 resource(s) loaded .
08 Jun 2010 11:06:33:485 [INFO] IBM Tivoli Integration Composer database version: V7116-173 done
IBM Tivoli Integration Composer database version: V7116-173
Retrieving mapping definition taddm-2-ccmdb-citypes... done
Creating source data source TADDM72CIType... done
Connecting to source data source TADDM72CIType...
08 Jun 2010 11:06:33:953 [INFO] ResourceManager : Loading resource file C:Integration Composerdata
propertiesjdbcinfo.properties : 39 resource(s) loaded.
08 Jun 2010 11:06:34:016 [INFO] DataManager created. (This should only happen once.)
08 Jun 2010 11:06:36:875 [INFO] Collation version: 2.2, build: null, home: C:Integration Composer
Connecting to source data source TADDM72CIType... done
Creating target data source ccmdb72citype... done
Connecting to target data source ccmdb72citype...
Connecting to target data source ccmdb72citype... done
.
.
.
Classification: RELATION.DONATEDTO
Classification: RELATION.ISACTUALLYCAUSEDBY
Classification: RELATION.VIRTUALIZES
Classification: RELATION.MIRRORS
*
Done
08 Jun 2010 18:46:44:750 [INFO]
========================================================
Mapping execution completed
Mapping: taddm-2-ccmdb-ci-types
Execution time: 00:19:26
Classifications created: 0
Records created: 971
Records updated: 12
Records deleted: 0
Errors: 0
NRS GUIDs created: 0
NRS records updated on Alternate Keys: 0
NRS records found as duplicate: 0
NRS records deleted because of duplicate: 0
========================================================
 
Done
Mapping completed successfully.
Integration Composer has finished.
d. Verify your action by viewing the logs: <installdir>logfusion.log
18.6.5 Activating the CI types
Perform the following steps:
1. Log in to the Base Services/CCMDB application (http://host_name/maximo).
2. Click Go To → Administration → CI Types. See Figure 18-39.
Figure 18-39 Accessing the CI Types application
3. Search for the following files:
 – SYS.COMPUTERSYSTEM
 – SYS.OPERATINGSYSTEM
 – APP. DEFINITESOFTWARELIBRARY
 – APP. SOFTWAREIMAGE
4. Click the Change Status icon and then change the status to Active. See Figure 18-40 on page 574.
Figure 18-40 Changing status
5. Click OK and Save.
18.6.6 Setting up the actual CI adapter
Perform the following steps:
1. Create CI type mappings:
a. Go to Tivoli Integration Composer home.
b. Click Create New Mapping. See Figure 18-41.
Figure 18-41 Creating a new mapping
c. In the next window, provide the following values (Figure 18-42):
 • Source: TADDM72CIType
 • Target: CCMDB72citype
 • Name: taddm-2-ccmdb-ci-types
Figure 18-42 Mapping name
d. Complete the Password field and determine whether the other required data from TADDM server is correct. See Figure 18-43.
Figure 18-43 Connection information
e. Click Test Connection. If the test is successful, click OK and click Finish.
f. Enter the appropriate data for your environment:
 • Connection Method:
DB2: IBM DB2 JDBC Driver
Oracle: Oracle JDBC Thin Driver
SQL server: i-net OPTA JDBC Driver for Microsoft SQL Server 7/2000
 • Host name: Type the host name for the CCMDB database server.
 • Port: Type the port number for the machine. The default values are as follows:
DB2: 50005
Oracle: 1521
SQL server: 1433
 • Database: Type the name of the database: maxdb71.
 • User name: Type the user name for the user who created the Maximo tables in the database.
 • Password: Type the user's password.
 • Table owner: Type the user name for the user who created the Maximo tables in the database. See Figure 18-44.
Figure 18-44 Connection information
g. Click Test Connection.
h. At the message indicating success, proceed and click Finish. A window showing the relationships opens.
i. If there is no relationship, import an .fsn file with the relationships by clicking Select Action → Import, and then selecting the *.fsn file.
j. Verify that the column expressions have codes and then click Close. See Figure 18-45 on page 577.
Figure 18-45 Expressions
2. Run the CI type mapping:
a. Open a command (cmd) prompt.
b. Change directory (cd) to the integration composerin directory.
c. Run the following command, where <password> is the password for the Maximo database user (see Example 18-6):
commandline taddm-2-ccmdb-actual-ci maximo password administrator collation maximo password
Example 18-6 Run commandline
C:Integration Composerin>commandline.bat taddm-2-ccmdb-actual-ci maximo smartway administrator collation maximo smartway
Integration Composer will now start.
IBM Tivoli Integration Composer 7.2.0.1 Build 200911031354
08 Jun 2010 19:30:55:078 [INFO] IBM Tivoli Integration Composer 7.2.0.1 Build 200911031354
Mapping: taddm-2-ccmdb-actual-ci
08 Jun 2010 19:30:55:109 [INFO] ObjectManager created. (This should only happen once.)
Creating data source Fusion...08 Jun 2010 19:30:55:172 [INFO] GlobalContext created. (This should only happen once.)
08 Jun 2010 19:30:55:172 [INFO] ResourceManager created. (This should only happen once.) : 0 resource(s) loaded.
08 Jun 2010 19:31:24:297 [INFO] ResourceManager : Loading resource labels : 577 resource(s) loaded.
08 Jun 2010 19:31:25:016 [INFO] ResourceManager : Loading resource messages : 279 resource(s) loaded
.
08 Jun 2010 19:31:25:016 [INFO] IBM Tivoli Integration Composer database version: V7116-173
done
IBM Tivoli Integration Composer database version: V7116-173
Retrieving mapping definition taddm-2-ccmdb-actual-ci... done
Creating source data source taddm72actualci... done
Connecting to source data source taddm72actualci...
08 Jun 2010 19:31:27:313 [INFO] ResourceManager : Loading resource file C:Integration Composerdata
propertiesjdbcinfo.properties : 39 resource(s) loaded.
08 Jun 2010 19:31:28:953 [INFO] DataManager created. (This should only happen once.)
08 Jun 2010 19:31:40:219 [INFO] Collation version: 2.2, build: null, home: C:Integration Composer
08 Jun 2010 19:31:42:828 [INFO] ResourceManager : Loading resource file C:Integration Composerdata
propertiesproviderccmdb.properties : 853 resource(s) loaded.
Connecting to source data source taddm72actualci... done
Creating target data source ccmdb72actualci... done
Connecting to target data source ccmdb72actualci...
Connecting to target data source ccmdb72actualci... done
Retrieving mapping expressions... done
Retrieving mapping deciding classes... done
retrieving mapping expressions 64
finished mapping expressions 1
finished mapping expressions 2
.
.
.
finished compiling 15
done
REMOVELISTENER
08 Jun 2010 19:32:29:500 [INFO]
========================================================
Start mapping execution
Mapping: taddm-2-ccmdb-actual-ci
========================================================
.
.
.
Actual CI: 71155 C0A01C1F7EBD3B02B979031AECA66E77
Actual CI: 71156 CAF8B47F3E353686936E008EC047FF4E
Actual CI: 71157 214725A156F9355AB0FF73B2A80083BF
Actual CI: 71158 D2702D161479375FBAF4CD5B079CC782
Actual CI: 71159 D946CC33E1613CFEB4BBA562697BAD5E
Actual CI: 71160 77973EC44C5E3AAB8C8194676416FF73
.
.
.
3. View the logs if necessary: <installdir>logfusion.log
18.6.7 Verifying that the data has been imported into CCMDB
Next, verify that the data has been imported into CCMDB:
1. In CCMDB, click Go To → IT Infrastructure → Actual Configuration Items. See Figure 18-46.
Figure 18-46 Actual Configuration Items
2. Search for items that should have been imported and confirm that they are present. If you find them, you have successfully imported the data. In the Classification field, type app.softwareimage. Figure 18-47 shows a list with the imported assets from Rational Asset Manager.
Figure 18-47 Imported assets
18.6.8 Creating and configuring the integration module in the CCMDB
At this time, the data from Rational Asset Manager is already in the CCMDB but it is not in the DML. Now, we configure to transfer the assets from the actual configuration items to the DML.
Set up web services in CCMDB
First you must set up web services in CCMDB:
1. Click Go To → Integration → Web Services Library. See Figure 18-48.
Figure 18-48 Web Services Library
2. In the Web Services Library, click Select Action → Create Web Service → Create WS from Object Structure. See Figure 18-49.
Figure 18-49 Create a Web Service from Object Structure
3. Create the following web services, as shown in Figure 18-50.
 – MXAUTHCI
 – MXCLASSIFICATION
 – MXOMP
 
Tip: Use the arrows to find those web services.
Figure 18-50 Web services
4. On the List page, verify that the Web Services were created. If they were, click Select Records, as shown in Figure 18-51.
Figure 18-51 Select Records
5. Select the check box of each web service you created, and then click Select Action menu → Deploy Web Service. See Figure 18-52.
Figure 18-52 Deploy Web Service
Set up the Integration module
Next, set up an Integration module:
1. Click Go To → Integration → Integration Modules. See Figure 18-53.
Figure 18-53 Opening Integration Modules application
2. Search for RAMIM by using the Integration Module page:
a. Click the Logical Management Operations tab and verify that the IMPORTSOFTWAREIMAGE operation is added, as Figure 18-54 shows.
Figure 18-54 IMPORTSOFTWAREIMAGE operation is added
b. Click the Operational Management Products tab.
c. Click the New Row under Operational Management Products for RAMIM to add the OMP.
d. Click the Operational Management Product and filter the product name by Rational. See Figure 18-55.
Figure 18-55 Select the OMP
Before saving, you have to define an endpoint.
Define an endpoint
Perform the following steps to define an endpoint:
1. Click the button next to the End Point field and click Go To End Points. See Figure 18-56.
Figure 18-56 Go To End Points.
2. On the End Points page, click New End Point to create a new endpoint.
3. Enter RAMENDPOINT as name of the endpoint.
4. Click the Handler icon to select the handler.
5. Select RAMHANDLER (com.ibm.ram.ccmdb.im.ram.RAMHandler handler class name). See Figure 18-57.
Figure 18-57 Select RAMHANDLER
6. Enter the URL of the Rational Asset Manager server application. First, locate the URL name as follows:
a. Go to the Rational Asset Manager application.
b. Click Help → Extensions. See Figure 18-58.
Figure 18-58 Extensions page from RAM
c. Look for the repository location under the Eclipse Client Plug-in tab (Figure 18-59).
Figure 18-59 Extensions page
d. Return to the End Points application and type the name you have found. See Figure 18-60.
Figure 18-60 End Points page
7. Type the password for a Rational Asset Manager administrator.
8. Type the user ID for a Rational Asset Manager repository administrator. The window, shown in Figure 18-61 opens.
Figure 18-61 Rational Asset Manager repository administrator
9. Click Save to save the endpoint.
10. Click Return With Value.
11. On the Integration Module page, click Save to save the integration module configuration.
18.6.9 Creating the Definitive Media Library (DML)
Create the DML, as follows, because all the modules responsible for the integration are set:
1. In CCMDB, click Go To → Release > Definitive Media Library. See Figure 18-62.
Figure 18-62 Create the DML
2. Click Create DML.
3. In the Name field, type RAM 72 as the name of the DML configuration.
4. Optional: Type a description for the DML.
5. In the Owner field, click Select Value → maxadmin as owner for the DML. See Figure 18-63.
Figure 18-63 Owner field
6. Under the Details section, in the Classification Path field, click Classify. See Figure 18-64.
Figure 18-64 Details section
7. In the Classify window, select Rational Asset Manager Repository. The classification is from the Rational Asset Manager integration module that was installed in the CCMDB. See Figure 18-65.
Figure 18-65 Classify window
8. In the Scope section, select the Source Code and Binary check boxes. See Figure 18-66.
Figure 18-66 Scope section
9. In the Management Application section, click the arrow next to the name to select the OMP.
10. In the Select OMP window, click Rational Asset Manager OMP to use for this DML. See Figure 18-67.
Figure 18-67 Rational Asset Manager OMP
11. Click Save DML.
12. Click the Software Images tab.
13. Click Select from OMP. See Figure 18-68.
Figure 18-68 Select from OMP
14. Select the Software Images and click OK. See Figure 18-69.
Figure 18-69 List of the imported software images
A list of all the imported software will be created and will be added to the CCMDB. Now the integration is done. All the software images from Rational Asset Manager are there.
15. Click Save DML.
The first part of integration is complete. All data from the Rational Asset Manager is in CCMDB.
18.6.10 Synchronizing the asset from CCMDB with Rational Asset Manager
As explained previously, synchronizing the data from CCMDB to the Rational Asset Manager is possible.
Perform the following steps:
1. Log in to Rational Asset Manager web client.
2. Go to the RAMCCMDB community (Figure 18-70).
Figure 18-70 RAMCCMDB community
3. Go to the Change and Configuration Management Database Connections section (Figure 18-71).
Figure 18-71 Change and Configuration Management Database Connections
4. Click Synchronize. The success message, shown in Figure 18-72, is displayed.
Figure 18-72 Synchronize
5. Click the Assets page.
6. Search for the remote asset. The search returns the CCMDB CIs. The CIs are synchronized from the Tivoli CCMDB to Rational Asset Manager.
7. Go to any remote asset. The remote assets in the Rational Asset Manager repository retain much of the information from the CCMDB CI.
18.7 Summary
Figure 18-73 shows the summary of this integration.
Figure 18-73 Quick summary
 
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.144.84.175