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