270 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
<id>
<class>OperatingSystem</class>
<instid>os_ibmtiv9</instid>
</id>
<type>TMW_TaskResult@TMW_Processor</type>
<context>[666252843]Processor=0;</context>
<tbsm>
<type>EXCP</type>
<desc>The tasks associated to the event '
TMW_HighProcesses', have been submitted for execution.
(;eventtriggername="TMW_HighProcesses"
;return_codes="[0]";task_libs="
['IBM Tivoli Monitoring Utility
Tasks']";tasks="
['dm_mn_send_notice']")
</desc>
</tbsm>
<tecstatus>
<severity></severity>
</tecstatus>
</event>
We can see here that the ibmtiv9 endpoint fired and invoked a
send_event_to_tbsm() request to the tmnt_tbsm_eng.exe process. This
information was then passed to the IBM Tivoli Business Systems Manager
wrapper process. This data also shows that we sent an information event to IBM
Tivoli Business Systems Manager that shows that a task has been invoked. We
set a task up to send information to the notice board in framework on an alert.
Note that this second event has no severity.
Next we go the the tmnt_tbsm_wrapper. The log file, shown in Example 8-9, is
trace_tmnt_tbsm_wrapper1.log.
Example 8-9 The file trace_tmnt_tbsm_wrapper1.log
<F>1037738265000<F>Tue Nov 19 20:37:45 2002 GMT<F>AMW<F>tbsma-wrapper<F><F>3996
<F>MAX<F>../../src/tbsm_adapter_wrapper/TBSMAWrapper.cpp<F>send_event<F>n/a<F>C
alling Adapter::sendEvent(DM+ibmtiv9-9.3.4.53-1389241399-0000000023, ...). XML
stream<F>None.
<event>
<time>1037738248</time>
<id>
<class>OperatingSystem</class>
<instid>os_ibmtiv9</instid>
</id>
<type>TMW_HighProcesses@TMW_Processor</type>
<context>[666252843]Processor=0;</context>
<tbsm>