IBM Tivoli Netcool/OMNIbus, Version 7.4

Directory structure

The directory structure of the Event Integration Facility after you extract the compressed EIF files.

The following table describes the file and directory structure of the Event Integration Facility. In this directory structure, interp can be one of the following directory names, which map to the supported operating systems.

Table 1. Event Integration Facility directory structure
Directory or file name Header
bin/interp Contains, for each supported operating system that is represented by interp, the 32-bit version of the posteifmsg command that is used to send EIF events.
bin64/interp Contains, for each supported operating system that is represented by interp, the 64-bit version of the posteifmsg command that is used to send EIF events.
codeset Contains the code pages.
contrib/interp Contains compiled sample 32-bit C programs for each supported operating system that is represented by interp. The sample receivers are eifrcv1, eifrcv2, eifrcv3, and eifrcv4. The sample senders are eifsend1 and eifsend2.
contrib64/interp Contains compiled sample 64-bit C programs for each supported operating system that is represented by interp. The sample receivers are eifrcv1, eifrcv2, eifrcv3, and eifrcv4. The sample senders are eifsend1 and eifsend2.
default_sm Contains the default empty rule set for the Tivoli Enterprise Console® State Correlation Engine. You can add rules, which are also called state machines, as is required by your environment.
include Contains header files for building adapters. These files have a .h file extension. These files are common across all operating systems.
jars Contains all the JAR files that are necessary to use the Java™ based EIF API. These files are evd.jar and log.jar.
javadoc Contains the Javadoc for the Java based EIF API.
lib/interp Contains the 32-bit static library for each supported operating system that is represented by interp. The library name is libeif.a.
lib64/interp Contains the 64-bit static library for each supported operating system that is represented by interp. The library name is libeif.a.
misc Contains a sample eif.conf file that you can use to define your own configuration files, and various readme files that explain how to use the EIF and the purpose and usage of the sample files that are provided. In particular, the readme.tips file has useful information about using the EIF.
samples Contains the following sample adapter source code:
  • Sample C-based receivers, which are as follows:
    • eifrcv1.c
    • eifrcv2.c
    • eifrcv3.c
    • eifrcv4.c
  • Sample C-based senders, which are as follows:
    • eifsend1.c
    • eifsend2.c
  • A sample C-based long running adapter that is called sampleAdapter.c.
  • A sample Java based long running adapter that is called SampleAdapter.java
Tip: For more information about the purpose and usage of each sample file, see the misc/readme.samples file.
EIF.version A file that shows the current build version of Event Integration Facility.


Feedback