This article explains how to leverage EMA Java to write a Non-Interactive Provider in Scala language to publish real-time level 1 and level 2 data and to perform connection and publishing data recovery.
This article explains how to leverage EMA Java to write a Consumer application in Scala language to get real time market data and to request interest of fields and request multiple items using a single request.
This article shows how to implement EMA Java Consumer and Provider applications with Kotlin, a new first-class programming language on JVM world.
Theis article is intended for anyone who is interested in using Thomson Reuters Enterprise Platform (TREP) as a messaging medium for internal business workflows i.e. publishing his own data services using custom fields to TREP.
The article explains how to leverage Elektron Message API to write a Non-Interactive Provider application that publishes Symbol List.
The EMA Java API is implemented on top of SLF4J API as a facade for logging utility. It allows developers integrate EMA Java application with their prefer Logging framework by replacing the Logging library and configurations files without touching the application source code.
In this article we take the basic EMA Java Consumer App example provided in the dev kit and enhance it to be able to provide web service capabilities - in this case RESTful ones.
This article describes how downstream applications discover the health of Elektron Real Time Infrastructure, through the consumption of SPS (Service Provider Status) messages provided by the Elektron Real Time CHE (Collection Head End).
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?