Event Integration Facility (EIF) events date back to the
days of the Tivoli Enterprise Console. This
event mechanism is robust and reliable, and still used today as a means to
transport event information between ITM (and many other Tivoli products) and
the EIF Probe for Omnibus.
The Netcool Omnibus Event Integration Facility is a software
toolkit or SDK that can be used to send and receive EIF formatted events from
within an application. These EIF based applications
are referred to as adapters. The EIF
toolkit provides many services to the adapter – some of these services include adapter
configuration, event transport, event caching, automatic failover, and encryption
via SSL or FIPS 140-2, to name a few.
You may be saying to yourself about now, well that’s cool,
but with all the monitoring solutions out there and command line capabilities, why
would I need to write my own adaptor? That
is a good question, and while the Omnibus EIF reference says:
The
Event Integration Facility is a toolkit that expands the types of events and
system information that you can monitor. You can use it to develop your own
adapters, tailored to your network environment and to your specific needs.
I have found a useful feature to be receiving events rather
than generating them.
It’s not uncommon to find a company looking to replace both
a legacy monitoring tool, and it’s event management system with IBM Tivoli Monitoring
and Netcool Omnibus. Many times the deployment
of the ITM monitoring solution can be delayed while work is being done to
implement automation and new processes within the new event management system –
Netcool Omnibus. This is usually a
people/process delay not a technical one, but still delays the time to value of
the overall solution.
In some of these cases, use the EIF toolkit to develop an
EIF receiver adapter, to “catch” ITM EIF events and then forward appropriate
events on to the legacy event management system, can allow the ITM deployment
to move forward. Later, as the teams and
processes are ready to begin transitioning the event management system, the
adapter can be updated to forward only certain events to the legacy system and
others to Omnibus, or perhaps to both for a period of time. Ultimately the entire event flow is
transition to Omnibus and the adapter eliminated from the environment.
I’ve used the Event Integration Facility toolkit a number of
times in scenarios similar to this and for other things, and it can be a great
tool to have in your tool belt.
For more information, see the Event Integration Facility Reference
Manual, part of the Omnibus documentation set.
You can also find sample code shipped with the SDK, which is available for
download with your Omnibus license.