Sending events

Common problems that can occur when events are sent to the event server.

My adapter is not sending all the events to the event server.
Cause
There is either a communication problem between the adapter and the event server, or there is a problem internal to the adapter code.
Remedy
Send events to a file instead of directly to the event server. Then, verify the event delivery, as follows:
  1. Set the TestMode keyword to YES in the adapter configuration file.
  2. Specify the file to receive the events with the ServerLocation keyword.
  3. Restart the adapter.
  4. Review the file that is specified by the ServerLocation keyword and check to see whether all the events appear there.
If all events appear in the file, then there is a communication problem with the event server. If the events are missing from the file, then there is problem internal to the adapter. Check the adapter code.
After you test the adapter, reset the TestMode keyword so that events are sent to the event server and no longer directed to a file.
I am using the posteifmsg command to send events, but they are not arriving at the event server
Cause
The events are being sent to the cache on the adapter or gateway because of one of the following situations:
  • The -S option expects that a portmapper, or similar program, is running at the receiving machine. For Windows systems, there is no portmapper daemon.
  • A non-valid port, host name, or event server was specified.
Remedy
Resolve the non-valid name or port issues.
Multi-byte characters in an event that is generated by posteifmsg are garbled
For locales that use multibyte characters: A message in an event that is generated by posteifmsg is garbled. The garbled message can be seen in the event list, the debug log of the Probe for Tivoli EIF, and the cache file of the posteifmsg utility.
Cause
The posteifmsg utility fails to convert local DBCS message, such as Japanese, to UTF-8 encoded characters if the TISDIR environment variable is not set.
Remedy
Set the TISDIR environment variable to the path to the codeset directory before you run the posteifmsg utility. This directory is included in the EIF SDK for Tivoli Netcool/OMNIbus.
To set this environment variable:
  1. Run the following command:
    # export TISDIR=/path_to_extracted_eif-sdk_package/codeset
  2. Then, run the following command:
    # posteifmsg -f /path_to_configuration_file -r CRITICAL -m "DBCS included message" CLASS SOURCE
posteifmsg processes do not complete
If a cache file is shared by multiple posteifmsg processes, some posteifmsg processes do not complete. Instead, the processes hang.
Cause
Multiple instances of the posteifmsg utility cannot share a single cache file.
Remedy
Specify unique configuration files for each instance of posteifmsg. You can specify a cache file in configuration file for each instance of posteifmsg.
Alternatively, use the nco_postmsg utility, which can share a single cache file across multiple instances. If you use this solution, ensure that you specify a unique log file for each instance of nco_postmsg by using the -messagelog command-line option.