3. If the endpoint has logged into a Tivoli Management Framework gateway
successfully, create and distribute the ACP profile (see the IBM Tivoli Enterprise
Console User’s Guide for details). Check the lcfd.log file if there are further
problems; you can also turn on tracing at the Tivoli Management Framework
gateway and look in $DBDIR/gatelog for further debugging information.
4. If events do not arrive at the event server but are not incorrectly parsed, check
to see if the events are caching on the endpoint instead. If so, either the lcfd
process cannot communicate to the Tivoli Management Framework gateway or
the event server, or the lcfd process itself is down. Verify that all
communications among the event server, Tivoli Management Framework
gateway, and endpoint are working.
5. Source the endpoint environment, then use the endpoint wpostemsg command
from the system the adapter is running on to see if the event arrives at the
event server. See the IBM Tivoli Enterprise Console Reference Manual for more
information.
Non-TME Adapters
Use the postemsg command from the system on which the adapter is running to
see if the event arrives at the event server. The postemsg command works in
environments where Tivoli software is not installed. Thus, this standalone
command displays error messages in English only, because the command does not
have access to the message catalogs for the language support packs. See the IBM
Tivoli Enterprise Console Reference Manual for more information.
22 IBM Tivoli Enterprise Console: Adapters Guide