Troubleshooting

Follow these steps to diagnose and correct problems that you experience with OMEGAMON® Data Provider. For example, expected data not arriving at a destination analytics platform.

Procedure

  1. Examine the messages from the components involved in OMEGAMON Data Provider.

    Check that each component reports the expected messages.

    To get more detailed messages, you can adjust the logging level of some components. For example, you can set the logging levels of OMEGAMON Data Broker and OMEGAMON Data Connect.

  2. Check for common issues.
    Tip:
    • If possible, before introducing SSL/TLS (security protocols), test that your configuration works without SSL/TLS. For example, in a sandbox environment that is entirely inside a secure intranet.
    • Check that you are using the correct character encoding for each configuration member. For details, see Configuration.
    • As a rudimentary test that OMEGAMON Data Connect is receiving the expected data from OMEGAMON Data Broker, temporarily enable the STDOUT output of OMEGAMON Data Connect.
  3. Finally, if you cannot resolve the problem, gather diagnostic information, and then contact IBM Software Support.