The utility is a GUI based application which The utility was provided for troubleshooting purpose. It can be used to decode Market Price and MRN data from the RSSL XML trace file which generated by RFA C++/.NET or Elektron SDK C++ and then displaying the Trace Log in GUI.
The utility was provided for troubleshooting purpose, it can help verify issue such as data integrity and it can also help verify the message that API sends and receives. The utility can decode Market Price and MRN data from RSSL XML trace log generated by RFA C++/.NET or Elektron SDK C++.
Introduce how to implement a custom domain for binary blob
Explore different available options for contributing to Thomson Reuters
The article explains how to leverage Elektron Message API to write a Non-Interactive Provider application that publishes Symbol List.
This article provides sample Cmake command with instruction for a new user to run Cmake GUI generating EMA project file.
This article explains how to encode and decode RMTES String containing non-ASCII text using EMA and RFA C++ /.NET edition.
Article about exception handling in EMA C++.
Elektron Message API is designed as an ease of use API which provides one of the easiest entry points into consuming and publishing real-time data. How to configure it?
For some instruments, suffix of RIC indicates the exchange where it is traded, e.g. HSBA.L (.L = LSE - London Stock Exchange), HBC.N (.N = NYSE - New York Stock Exchange). However, there are some instruments without this suffix. How can an app know on which exchange they are listed?
This article explains streaming Level 2 data and how to process and manage this using EMA C++
This is the second part of the "Simple Chain Objects for EMA" article. In this part I present two Java example applications that demonstrate the different concepts explained in "Simple Chain Objects for EMA - Part 1".
Working with Thomson Reuters real-time data, you probably came across a very specific type of instruments called Chains or Chain Records. If you never heard about these, well… soon or later you will probably have to deal with them.
Using FID 259 to identify your market data records