Tivoli Business Systems Manager V2.1 End-to-end Business Impact Management

80 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management

3.2 The databases

IBM Tivoli Business Systems Manager comes with pre-populated databases.

Detailed installation procedure is given in 6.3, “Database server installation” on

page 176. The following databases are provided:

Objects The primary IBM Tivoli Business Systems Manager

database that stores most of the management data. As

the name implies, it stores IBM Tivoli Business Systems

Manager objects information, attributes, and links.

ASIRuleSvc Rule database that contains a mirror image of selective

IBM Tivoli Business Systems Manager objects for rule

processing. This database offloads some heavy rule

processing from the main object database, as most of the

rules are not concerned with state changes.

Meta Metadata database that contains the most information

about IBM Tivoli Business Systems Manager database

objects structure, attributes, and methods. Some of the

tables here are provided as views in the object database.

RODM, RODMLoad Temporary loading database for SNA network objects

from RODM.

OPCLoad Temporary loading database for Tivoli Workload

Scheduler (used to be called Tivoli OPC) data.

WebServer Database for the help and reporting system resources.

ObjectEvents Contains the processing queues of IBM Tivoli Business

Systems Manager. Each queue isrepresented in three

tables: Pending<qtype>, LastProcessed<qtype>, and

Processed<qtype>.

ObjectQueues Not used.

3.3 Object implementation

IBM Tivoli Business Systems Manager uses an object-oriented data structure. It

implements the objects in Microsoft SQL Server relational database. Typically, an

object in IBM Tivoli Business Systems Manager has:

򐂰 Class definition and attributes

򐂰 Methods that can be invoked

򐂰 Links to other objects

Our discussion provides some information about object implementation.

Chapter 3. Database structure 81

3.3.1 Important information sources

Tables that show important information about IBM Tivoli Business Systems

Manager object structure typically reside in the Meta database, but they can be

accessed through views in the Object database. Those are:

obj_class Primary table that contains an object’s class definition.

link_type Primary table that describes existing link types.

isa_table Inheritance structure table.

obj_link_table Lists all possible links between object types.

link_chain Generated containment structure table.

isa_chain_table Generated inheritance structure paths.

method_table Lists the available methods for a specific class.

Extensions to these core information tables address required new functions.

These additional informational tables are not related directly to the object

implementation, but provide good information about the IBM Tivoli Business

Systems Manager object classes:

򐂰 Tables provided with the IBM Tivoli Business Systems Manager agent listener

implementation:

GEM_LookupCID Provides a master list of all Gxxx classes that are

dynamically created and mapped to the

triplet (the

information about Manufacturer, Product, and

Version). The triplet is the key matching attribute for

the TEC integration as discussed in Chapter 7, “TEC

components integration” on page 209.

GEMIDLookup Provides the field key lookup for TEC-related objects,

such as IP Address, TMR, and host name, so that

finding an object does not require searching through

multiple tables with dynamically created names

Gxxxcname_C and Gxxxcname_A.

GEM_DMtoCID Provides a mapping for the ‘old’ Tivoli Distributed

Monitoring Version 3.6 objects implementation.

Multiple DM profiles can be mapped to a single IBM

Tivoli Business Systems Manager class, therefore this

table is necessary.

򐂰 Tables provided with the Common Listener implementation:

CL_AutoPlacement Mapping of instrumentation to enterprise

CL_LinkRules Rules for creating a link based on the cid and other

attributes

CL_Options Common Listener global options

CL_Registration All known registered connectors