ITM: Debugging the Situation Update Forwarder (SUF) - Part 1: Overview
carinb 100000JKNU Visits (8979)
Sending ITM EIF events to an event destination can work either in a uni-directional fashion or a bi-direction fashion.
Uni-directional, meaning sending ITM events to an EIF receiver (typically TEC or Netcool) uses the EIF subcomponent of ITM.
Bi-directional includes going from ITM to the EIF receiver and then from the Event Management Product (such as TEC or Netcool) back to ITM. This uses the SUF (Situation Update Forwarder) component of the ITM product.
Debugging the SUF means breaking down the components that allow for events to be sent back to ITM.
The major area of event handling include
- Netcool Event Management to handle the ITM event and writes the event out to a cache file.
- Persistence Directory Cache File to hand the event to the SUF listening process
- SUF process to read the cache file
- SOAP calls to send the event to the ITM SOAP client
- ITM event matching to match the receiving event to the original sent event.
Each of these areas have debugging capabilities in which you can determine if the event is incoming and outgoing successfully thru that step.
I'll cover what you can look for in each step to determine if the event was handled successfully.
I will be using Netcool for the examples, since that is the most commonly used EIF receiver and installed SUF environment.
I will be breaking down each step into mini-tutorials and providing examples for how to debug.
Here are the Parts of the SUF Debugging Series (5 parts, including the Overview):
- Part 2: Netcool Event Management to handle the ITM event and writes the event out to a cache file.
- Part 3: SUF process to read the cache file
- Part 4: SOAP calls to send the event to the ITM SOAP client
- Part 5: ITM event matching to match the receiving event to the original sent event. (Not yet published)
Subscribe and follow us for all the latest information directly on your social feeds: