Chapter 8. IBM Tivoli Monitoring integration 261
transport.class.name =
com.tivoli.commonlistener.transport.mqe.client.ClientTransportMQe
transport.local.ip.address = 9.3.4.59
transport.request.address = 9.3.4.59.DM.QM+DM.Q
transport.request.port = 6969
transport.response.address = 9.3.4.59.DM.QM+DM.Q
transport.response.port = 6969
transport.mqe.local.queue.store = file
transport.mqe.remote.queue.store = file
transport.mqe.usefiller = false
transport.mqe.fileregistry = com.ibm.mqe.registry.MQeFileSession
transport.mqe.maxchannels = 1
transport.server.mqe.address = ServerQM+ServerQ
transport.server.mqe.port = 8082
transport.server.ip.address = 9.3.4.53
heartbeat.send_events_to_tbsm = false
heartbeat.send_events_to_tec = false
heartbeat.send_events_to_notice = true
heartbeat.tec_server = not-configured
tbsma.jre_root = c:Java13jre
We will show some of the recommended trace parameters in 8.4, “Tracing an
event to the Common Listener” on page 268.
8.3 Using the TBSM adapter
The discussion consists of the following:
? 8.3.1, “Discovery process” on page 261
? 8.3.2, “Event forwarding to Tivoli Business Systems Manager” on page 264
8.3.1 Discovery process
Once the IBM Tivoli Business Systems Manager adapter is installed onto the
gateway, you can run a discovery. This sends a listing and locations of endpoints
that are attached to the gateway to the IBM Tivoli Business Systems Manager
Common Listener. This information is entered into the IBM Tivoli Business
Systems Manager database.
262 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
There are two ways to carry out a discovery:
? Bulk discovery
The wdmdiscovery command can be issued from the Tivoli desktop to carry
out a bulk discovery. The adapter sends details of all systems it has in its
cache to the IBM Tivoli Business Systems Manager Common Listener. The
bulk discovery process creates new instances of resources, deletes old ones,
and updates those that already exist. Bulk Discovery is an intensive process
and should be used judiciously to minimize performance degradation,
especially if you are dealing with many endpoints on a gateway.
? Delta discovery
The same wdmdiscovery command can be issued from the Tivoli desktop to
carry out a delta discovery. The adapter sends details of all changes since the
last discovery to the IBM Tivoli Business Systems Manager Common
Listener. The delta creates, deletes, and updates resources one at a time.
This is the primary method to discover new resources, as it has less impact
on performance. If a large number of resources is being created, updated, or
deleted, bulk discovery should be used instead of delta.
In our environment, the discovery is performed as shown in Example 8-4.
Example 8-4 The wdmdiscovery command
c:> wdmdiscovery -m all -b
Processing ManagedNode ibmtiv9...
If you have a problem issuing the discovery, it usually will be a time-out problem
caused by incorrect port settings or a network problem. (By default the adapter
will allow 300 seconds for the Common Listener to respond.) We can enable a
trace and look at the IBM Tivoli Business Systems Manager log files to diagnose
the problem. More on this later in 8.4, “Tracing an event to the Common Listener”
on page 268.
After successfully running the wdmdiscovery command, we can run the
wdmmngcache command, as shown in Example 8-5, to check whether the
registration completed sucessfully.
Example 8-5 The wdmmngcache command
C:>wdmmngcache -m all -l -v
Processing ManagedNode ibmtiv9...
Endpoint | HB status | TBSM status
ibmtiv8 HBOff Discovered
ibmtiv9 HBOff Discovered
Chapter 8. IBM Tivoli Monitoring integration 263
This shows that the discovery of the endpoint with IBM Tivoli Business Systems
Manager was successful. If an endpoint status does not show the TBSM status
as Discovered, it will be ignored by the Common Listener whenever an event is
send to IBM Tivoli Business Systems Manager from this endpoint because there
is no registered object to associate this change of state with. Also, on the
gateway’s $DBDIRdmml directory, you will see a directory
<ip-address>.DM.QM created by the wdmdiscovery process.
If we open the IBM Tivoli Business Systems Manager console we can see the
discovered endpoints as shown in Figure 8-5.
Figure 8-5 IBM Tivoli Business Systems Manager console window
IBM Tivoli Business Systems Manager automatically populates the new
resources on a successful discovery. The object hierarchy for the IBM Tivoli
Monitoring is located as follows:
Enterprise - IP Network - Network Subnet - Network Segment - Computer -
resource
This hierarchy is based on the IP address of the endpoint. The mapping of the
enterprise is performed from the table CL_AutoPlacement. Our content in this
table is shown in Figure 8-6.
264 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
Figure 8-6 Instrumentation mapping to enterprise
In this example we have created an enterprise called Chuy Inc. To display the
desired view we can drill down the menu and see that the discovered endpoints
are on Network Segment: 9.0.0.0:Segment 1. Systems Manager resource view
gave the listing of the two endpoints that were discovered by the IBM Tivoli
Business Systems Manager Adapter, as shown in Figure 8-5 on page 263.
Our next step is to set up IBM Tivoli Monitoring to send an event to IBM Tivoli
Business Systems Manager.
8.3.2 Event forwarding to Tivoli Business Systems Manager
IBM Tivoli Monitoring 5.1.1 events on the endpoints can be forwarded to IBM
Tivoli Business Systems Manager using the IBM Tivoli Monitoring 5.1.1 IBM
Tivoli Business Systems Manager Adapter. Two kinds of events can be sent to
IBM Tivoli Business Systems Manager: heartbeat events and IBM Tivoli
Monitoring 5.1.1 events. The option to forward IBM Tivoli Monitoring 5.1.1 events
to IBM Tivoli Business Systems Manager is configured in the IBM Tivoli
Monitoring 5.1.1 profile before distributing the profile to the endpoints.
In our example we have created a new IBM Tivoli Monitoring Profile:
ITM511Profile within an ITM511 dataless profile manager. To enable the events
to be sent to IBM Tivoli Business Systems Manager we select Edit -> Properties
from within the IBM Tivoli Monitoring Profile window, as shown in Figure 8-7 on
page 265.
Chapter 8. IBM Tivoli Monitoring integration 265
Figure 8-7 Profile Properties window
Select the Send TBSM check box and click OK. We can now create an arbitrary
monitor. In our example, we monitor CPU utilization and the Processor activity.
We must designate in the individual resource model that we want these events to
be forwarded to IBM Tivoli Business Systems Manager. From the IBM Tivoli
Monitoring Profile window select the resource model that you wish to send to IBM
Tivoli Business Systems Manager and click Edit. The Edit Resource Model
window appears. Select a threshold from the list and click Indications. From
here you can see whether this event will be sent to IBM Tivoli Business Systems
Manager as well as TEC. This is shown in Figure 8-8 on page 266.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.