Filter
Top Products
5. If you see the messages, the adapter is receiving events and processing them.
Run the wtdumprl command on the event server and verify that the messages
are actually showing up in the reception log. If not, the events were not
received by event server or there is a problem with the event server reception
process. Check the adapter configuration file to verify that ServerLocation and
ServerPort are properly defined. If the event class appears in any filter entry in
the configuration file, it is not sent to event server. The administrator who
started the adapter must have the required roles if you are running the TME
version of the adapter. For a TME adapter, running the odstat command can
offer some clues as to what failed.
6. If the reception log has a PARSING_FAILED error, the BAROC definition of
the class does not match the event that is being received from the adapter.
Usually the error messages pinpoint the problem.
7. If the previous steps do not indicate any problem and you do not see the new
events in the IBM Tivoli Enterprise Console product, there might be a problem
with the event group filters. Make sure the class filters match the classes in the
BAROC files.
8. Change all /dev/null entries in the .err file to the file name you want. Stop and
restart the adapter, send an event through, and then look in the trace file to see
what processing was done on the event.
110 IBM Tivoli Enterprise Console: Adapters Guide