Introduction

This document describes how the Tivoli Process Automation Engine (TPAE) can be configured to use a federated data source.

Assumptions:

This document assumes that DB2 Enterprise Edition Server is being used as a backend database for the TPAE.

Configuration:

Run the following command to enable the federation in a DB2 instance:

DB2 update dbm cfg using FEDERATED YES

Scenario

Assume there is a DB2 database containing information about Computer System, to be federated with the Authorized CI space in the Change and Configuration Management Database (CCMDB). Here is the DB2 table definition:

COMPUTER_OWNER table

Column Name	Column Type	Length
COMPUTER_OWNER_ID	INTEGER
COMPUTER_NAME	VARCHAR	50
OWNER	VARCHAR	50

with the following contents:

COMPUTER_OWNERID	COMPUTER_NAME	OWNER
16	bush.my.com	Dan Quayle
18	bushw.my.com	Dick Chenney
14	carter.my.com	Walter Mondale
17	clinton.my.com	Al Gore
5	coolidge.my.com	Charles Dawes
9	eisenhower.my.com	Richard Nixon
13	ford.my.com	Nelson Rockfeller
7	froosevelt.my.com	John Garner
4	harding.my.com	Calvin Colidge
6	hoover.my.com	Charles Curtis
11	johnson.my.com	Hubert Humphrey
10	kennedy.my.com	Lyndon Johnson
12	nixon.my.com	Spiro Agnew
19	obama.my.com	Joe Biden
15	reagan.my.com	George Bush
2	taft.my.com	James Sherman
1	troosevelt.my.com	Charles Fairbanks
8	truman.my.com	Alben Barkley
3	wilson.my.com	Thomas Marshall

Configuring TPAE

Creating New Database Object

Although the COMPUTER_OWNER table will be federated from an external database, in order to use this table in TPAE, it needs to be defined using the Database Configuration application (under System Configuration -> Platform Configuration).

In the Database Configuration application, click New Object:

Type COMPUTER_OWNER in the Object field, and Computer Owner in the Description:

In the Attributes tab, add the attributes COMPUTER_NAME and OWNER and delete the attribute DESCRIPTION:

Save the new Database Object.

Applying the Database Change

Make a backup of the TPAE database
Go back to the List tab
In the Select Action pull down menu, choose Manage Admin Mode
Click Turn Admin Mode ON

Click the Refresh Status button until the Admin Mode is set to ON:

Close the Turn Admin Mode ON dialog
In the Select Action pull down menu, click Apply Configuration Changes
Select the Do you have a current backup? checkbox
Click the Start Configuring the Database button:

Click the Refresh Status button until the End ConfigDB message is displayed:

Close the Structural Database Configuration dialog.

Creating the Relationship

Select the CI Object:

Click the Relationships tab
Add the new Relationship, specifying the following information:

Relationship: COMPUTER_OWNER
Child Object: COMPUTER_OWNER
Where Clause: computer_name = :cinum

Save the new Relationship
Go back to the List tab

Modifying TPAE GUI to show the federated information

In this step, we'll add the Computer Owner to the TPAE GUI.

Go to Application Designed (under System Configuration -> Platform Configuration).
Select the CI application:

Click the Configuration Item tab
Select the Organization attribute:

Right-click the CI Location attribute and click Copy
Click the section containing the CI Location attribute:

Right click the section and select Paste. A copy of the Organization attribute is put in the section.
Right-click the new Organization field and select Properties
In the Attribute field, type COMPUTER_OWNER.OWNER
Define a value in the Label field:

Save your work in the Application Designer

Configuring Database Nickname

So far, the database still contains a table (created through the Database Configuration application). We'll redefine it as a nickname to the table in another database.

Registering the Federated Database in the TPAE Database Server

If the federated database is in another database instance, the database needs to be registered in the TPAE database server.

Run the following command to register the node:
db2 catalog tcpip node federate remote <remote_db_server> server <remote_db_port>
Run the following command to register the instance:
db2 catalog db <remote_db> at node federate

Creating the Database Nickname

In the DB2 Control Center, expand the options under MAXDB71 and select Tables
The application shows all tables. Right-click the table COMPUTER_OWNER and select Drop
In the left side, under MAXDB71, right-click Nicknames and select Create..
In the Introduction screen, click Next
In the Specify the data source and the wrapper, select DB2.
Click the Create... button in the Wrappers area.
Click OK in the Create Wrapper dialog.
Click Next.
In the Specify the server definition for the data source, click the Create... button
In the Create Server Definitions dialog, click the Discover.. button
Select the federated database and define the Type and Version:
Click Properties...
In the Server Definition Properties dialog, type the User ID and Password:
Click OK to close the Server Definition Properties
Click OK to close the Create Server Definitions
In the Create Nicknames dialog, click Next twice
In the Define Nicknames windows, click Discover...
In the Discover dialog, filter by Schema name
Select the table and click Properties...
In the Nickname schema, select MAXIMO and click OK
Click Finish to close the Create Nicknames dialog.