Receive IBM Tivoli Event Integration Facility Events
You can configure Meridian to receive events sent using the Tivoli Event Integration Facility.
These EIF events are translated into OpenNMS events using preconfigured rules.
The resulting UEI are anchored in the
uei.opennms.org/vendor/IBM/EIF/ namespace, with the name of the EIF event class appended.
A sample event configuration for the
OMEGAMON_BASE class is included with OpenNMS.
Once Meridian starts and the Karaf shell is accessible, you can install the EIF Adapter feature and configure it to listen on a specific interface and port.
|By default the EIF Adapter listens on TCP port 1828 on all interfaces.|
[root@localhost /root]# $ ssh -p 8101 admin@localhost ... opennms> feature:install eif-adapter opennms> config:edit org.opennms.features.eifadapter opennms> config:property-set interface 0.0.0.0 opennms> config:property-set port 1828 opennms> config:update
You can check the routes status with the
camel:* commands and/or inspect the log with
log:tail for any obvious errors.
The feature has a debug level logging that can be used to debug operations.
Features installed through the Karaf shell persist only as long as the
You should now be able to configure your EIF forwarders to send to this destination, and their events will be translated into OpenNMS events and written to the event bus.
If events are not reaching OpenNMS, check whether the event source (EIF forwarder) is correctly configured.
Check your event destination configuration. In particular review the
PORT parameters. Also check that your situations are configured to forward to that EIF destination.
If those appear to be correct verify that the EIF forwarder can communicate with OpenNMS over the configured port (default 1828).
Review the OSGi log with
log:tail or the