EMA can be used for both the purposes - either serialize the OMM messages into JSON, and also to directly display/visualize the data. As mentioned earlier, the application has to ensure that they are not slowing down the event callback loop by taking too much time decoding/writing messages to file etc. Doing so will risk getting disconnected from the ADS.
To serialize the message as JSON, application has to walk the field list and create its own JSON message. The part where this message may be written to disk can be quite time consuming, so use some sort of buffered writer.
Hello @ashwathguru.s, The key parameter which an EMA application should be aware of is to not slow down the event processing. Its not clear if you intend to display the message on the dashboard or publish the messages on a MQ type bus; which will be displayed on the dashboard.
Dashboard type of applications do not have a high update rate requirements. It might be easier to use the Websocket API along with a conflated feed to do this. You can also use the new RDP library to get websocket data with other programming languages. Here is an example of dashboard written using Dash framework which shows streaming and fundamental data. If you are using TREP, then you only have access to the streaming data.