226 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
Event Enabler: ibmtiv9
Connection Status: Connected
Enabled for connection at startup.
Port: Default Port
RetryTime: Default
Done.
By default the TCP/IP port 4030 is used for event enablement to agent listener
communication. You can see from Example 7-4 on page 225 that when the agent
listener starts, it will connect to an event enabler running on ibmtiv9. You can
change any of the default parameters, such as the TCP/IP port, by using the
gemeeconfig command.
7.3 IBM Tivoli Monitoring modules integration
IBM Tivoli Monitoring modules, which are based on IBM Tivoli Monitoring version
5.1.1, replace most of the Tivoli Manager for products. Although they are based
on IBM Tivoli Monitoring, the interface to IBM Tivoli Business Systems Manager
uses TEC instead of common listener as discussed in Chapter 8, “IBM Tivoli
Monitoring integration” on page 249.
This section demonstrates the integration of IBM Tivoli Monitoring for Databases:
DB2 with IBM Tivoli Business Systems Manager. These steps set up the
integration:
1. Define IBM Tivoli Monitoring for Databases resources to Tivoli Business
Systems Manager. This includes defining the object types, icons, operational
tasks, and other necessary attributes. Use the installation program in the
TBSM subdirectory of the
IBM Tivoli Monitoring for Databases
CD-ROM. Run
install.bat on the Tivoli Business Systems Manager database server. The
installation will copy the uninstallation program and start the initialization
script called <component>_init_tbsm.sh, where component indicates the
component to be installed.
2. Event enablement is already installed on our system so the next step is to
modify the rulebase to forward DB2 events to it. To do this we use the
Configure Event Server task. If you have installed event enablement on this
event server, this task recognizes it and compiles the rule base that forwards
events to IBM Tivoli Business Systems Manager. You can see the addition of
a new rule db2_to_TBSM.rls in Example 7-5.
Example 7-5 Excerpt of db2_to_TBSM.rls
/* COPYRIGHT: Licensed material - Property of IBM */
/* 5648-A46 (C) Copyright IBM Corp. 2002 */
Chapter 7. TEC components integration 227
/* All Rights Reserved */
/* US Government Users Restricted Rights - */
/* Use, duplication or disclosure restricted */
/* by GSA ADP Schedule Contract with IBM Corp. */
/* */
/***************************************************************/
rule:
forward_DB2_event_to_tbsm:
(
event: _event of_class within ['DB2_Event']
where [ ],
reception_action: send_to_TBSM:
(
exec_program(_event,
'scripts/DB2_send_to_TBSM.sh', '', [],
'YES'),
commit_set
)
).
rule:
forward_DB2_Clearing_Event_to_tbsm:
(
event: _event of_class within ['TMW_Clearing']
where [
application_class: _application_class within [ 'DB2InstanceManager',
'DB2PartitionManager', 'DB2PartitionGroupManager', 'DB2DatabaseManager',
'DB2Gateway' ],
eventname: _eventname
],
reception_action: send_to_TBSM:
(
exec_program(_event,
'scripts/DB2_send_to_TBSM.sh',
'"%s"',
[ _eventname ],
'YES'),
commit_set
)
).
This rule invokes a script called DB2_send_to_TBSM.sh as shown in
Example 7-6, which in turn formats and sends the event to the event
enablement engine within TEC. It uses the ihstttec exit, which is the generic
event exit.
228 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
Example 7-6 DB2_send_to_TBSM.sh
#!/bin/sh
if [ "$1" != "" ]; then
EVENT_CLASS=$1
fi
# The following will happen with clearing events
if [ "$application_version" = "" -o "$application_version" = "N/A" -o
"$application_version" = "n/a" ]; then
application_version="7.x"
fi
TMP=`wtemp`
LOGDIR=${TMP}/DB2
if [ ! -d $LOGDIR ]; then
mkdir $LOGDIR
fi
LOG=${LOGDIR}/trace_itmDB2_send_to_TBSM.log
exec 2>$LOG
set -x
SOFTCOMP_NAME="DB2"
FILEPREFIX="itmDB2"
$TEC_BIN_DIR/../../TDS/EventService/ihstttec -b
"$application_class;$application_version" -i "$application_label" -p
"$EVENT_CLASS" -s "$severity" -t "EXCEPTION" -4 oid="$application_oid" -q
"$origin" -m "$msg"
grep
"$application_class;$application_oid;$application_version;$application_label;$o
rigin" ${TMP}/${FILEPREFIX}_DISCOVERED_to_tbsm.file >/dev/null
if [ $? != 0 ]; then
echo
"$application_class;$application_oid;$application_version;$application_label;$o
rigin" >>${TMP}/${FILEPREFIX}_DISCOVERED_to_tbsm.file
fi
3. Before we can obtain the status of any of the objects reflected in the TBSM
console, we have to run discovery. After you define the object types, you must
define the specific objects. You can do this with the ECC_TBSM_Discovery
task. This task searches a managed node for objects and sends a
DISCOVER event to IBM Tivoli Business Systems Manager for each object.
The shutdown of a DB2 database that has been monitored would be reflected in
the IBM Tivoli Business Systems Manager console as shown in Figure 7-10 on
page 229.
Chapter 7. TEC components integration 229
Figure 7-10 TBSM console: All Resources - Descendents window
This shows that the database down state has propagated up the Business
System View.
For your reference, Table 7-1 shows the TEC setup tasks and the IBM Tivoli
Business Systems Manager discovery tasks for other IBM Tivoli Monitoring
modules.
Table 7-1 IBM Tivoli Monitoring tasks
Module TEC setup task TBSM disovery task
Databases: DB2 DB2ManagerAdminTasks
ECC_Configure_TEC_Classes
DB2ManagerAdminTasks
ECC_TBSM_Discovery
Databases: Oracle ITMOracle Tasks
ConfigureTECOracle
ITMOracle Tasks
OracleTBSMDiscovery
Databases: Informix® IBM Informix Server Tasks
Configure_TEC
IBM Infomric Server Task.
TBSM_Discovery
Business Integration:
WebSphere MQ
Configure Event Server menu from
Monitoring for WebSphere MQ icon
MQS TBSM
QMgr:Discover_Queue_Managers
MQS TBSM Queue: Discover_Queues
MQS_TBSM_Channel:Discover_Cha
nnels
Business Integration:
WebSphere MQ
Integrator
MQSI Event Tasks: Configure Event
Server
MQSI Utility Task:
MQSI TBSM Discover
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.