Chapter 3. Database structure 91
The propagation has to be customized for each installation so that:
? Meaningful status is reflected from the workstation. This includes the correct
representation of each alert status in the enterprise.
? Thresholding for objects gives the necessary filter for unwanted events.
? Certain objects that are very important will be given higher priority.
? Certain messages will be emphasized to show their priority.
3.5 Agent listener resources
This section discusses the implementation of the resources from the agent
listener. The discussion is divided into:
? 3.5.1, “Class implementation” on page 91
? 3.5.2, “AMS tables” on page 93
3.5.1 Class implementation
The agent listener objects are implemented in IBM Tivoli Business Systems
Manager by extending its database data structure. A new abstract object is
created as the base class of the GEM objects. These classes are constructed in
the hierarchy shown in Figure 3-6. (This is the inheritance hierarchy.)
Figure 3-6 GEM object classes in TBSM
These components in IBM Tivoli Business Systems Manager are defined with the
class ID of G
xxx
, where xxx are any alphanumeric characters. The class name is
represented as G
xxx
cname. As with the standard IBM Tivoli Business Systems
Manager class discussed in 3.3, “Object implementation” on page 80, agent
GEM Software Component
GMSC
GEM Mainframe
GMMF
Gxxx
Gxxx
Gxxx
Distributed Monitoring
GMDM
Gxxx
Gxxx
Gxxx
GEM AMS object
GMGM
Gxxx
Gxxx
Gxxx
GEM Generic
GMGN
Gxxx
Gxxx
Gxxx
GEM Generic
GMGX
92 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
listener objects are implemented in a set of tables and procedures. Figure 3-7
shows the tables for object class G02H.
Figure 3-7 Tables for CID G02H
Some of the important tables shown in Figure 3-7 are:
G02H_ID This table contains a single number that represents the
highest-instance ID number in the class table. Whenever
an instance is created for a class, the content of this table
must be incremented.
G02Hcname_C The class table that contains the instances of this class.
G02Hcname_S The setting table that contains a single row representing
the class-wide attributes. Some examples in this category
are icon definition, message tables, and propagation
matrix limits.
Chapter 3. Database structure 93
3.5.2 AMS tables
For the GEM-based components, several additional tables define important
information about the classes and instances. These tables can be categorized as
being used for:
? Finding and locating GEM classes and instances
? Placement of object instances
? Automatic creation of Line of Business views
These additional tables are useful for finding and locating these GEM objects:
? GEMLookupCID
This table contains the information about GEM-based classes in IBM Tivoli
Business Systems Manager. These classes are named Gxxxx, with a long
name of Gxxxxcname. Figure 3-8 shows the content of a GEMLookupCID
table.
Figure 3-8 GEMLookupCID
94 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
The Manufacturer, Product, and Version columns contain unique information
that identifies the component. Tasklib contains the name of the Task Library
where a task for this component can be invoked. Comptype indicates the type
of GEM component: gem, os390, gen, or dm.
? GEM_IDlookup
This table shows the argument that matches an event attribute with the GEM
object and its parent. Figure 3-9 shows a sample content of this table.
Figure 3-9 GEM_IDlookup
Some instances can be located from their TCP/IP host names, the
sub-source field, or from their endpoint IDs in the TMR.
? GEM_DMtoCID
This table maps the DM profile to the GEM object class id. When an event
from a DM profile is received as indicated in the sub-source slot, it will be
applied to the GEM object in the specified class. Figure 3-10 on page 95
shows sample content from the GEM_DMtoCID table.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.