Testing with the Demo Subscriber

Run your feed handler with the demo subscriber to test that messages are processed correctly.

1. If your publisher is configured for the OpsConsole:
   1. From the OpsConsole, view statistics for messages sent by the custom feed handler, and for messages received by the subscriber.
   2. Compare the results.
      They should be the same, especially for a short run.
2. To look at data to ensure that it arrived correctly for a custom message type:
   1. Define it for RAPCache and RAPStore in the message template.
   2. Ensure that the subscriber has the same template.
   3. Ensure that RAPCache and RAPStore data stores have the same table as in the template to store the data, and that it is defined correctly.
3. From the OpsConsole, start RAPCache and RAPStore, and start your feed handler.
4. Use View Statistics in the Monitor to see how much data is received and loaded.
   • If data is not being loaded at all, examine log files.
   • If data is being loaded but is not what is expected, there is probably a problem with the set field method.
   For example, date formatting or time formatting may be read in one way, but not sent to the subscriber in the way that RAP requires. The feed handler must interpret data in a way that RAP expects.
5. If data does not match what you expect, try either:
   • Running a debugger
   • Writing log statements

• Demo Subscriber
  Demo subscriber demonstrates, along with the demo feed handler, how messages flow through RAP.