This article will help you to get an access token easily in Java using EDPToken. The token is required to access any data from EDP and as a part of the login request before an application can consume real-time data from ERT in Cloud.
This article will guide you launch an Amazon AWS EC2 Instance to run the ERT in Cloud WebSocket Python example from the instance.
Use a Fiddler proxy to capture web request/response.
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.
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 is the second part of "Implementing Elektron API application to work with ATS" article. It guides how to work with ATS using Elektron APIs(EMA, ETA, WebSocket API) to contribute data, delete a RIC and its fields. It also contains troubleshooting which help the developers to solve common problems.
This article guides you in how to work with ATS using Elektron APIs (EMA, ETA, WebSocket API) to contribute data, add or delete a RIC and its fields. It also contains troubleshooting which help the developers to solve the common problems.
Open DACS API and Open DACS Permission Server (ODPS) are two ways for a developer to get a programmatic, application's view into DACS
Video article that demonstrates the “ease of use” of the Thomson Reuters Elektron Message API (EMA).
An example use-case for decoding the DACS locks and example code to do it.
This article is intended as an introduction to the concepts of DACS and OpenDACS for developers who are new to the subject
The purpose of this article is to describe the Item and Connection recovery mechanisms in EMA C++. It also provides guidance for application reponsibility in scenarios that EMA does not perform recovery.
A guide on the use of the infra tools to record data from a Thomson Reuters Enterprise Platform or Elektron realtime feed and how to replay the recorded data for Elektron SDK consumer applications.
A simple MarketPrice object or How to easily get market prices with EMA - Part 2
A simple MarketPrice object or How to easily get market prices with EMA – Part 1
This article explains important concepts that developers need to understand before they start building applications for the Thomson Reuters Enterprise Platform (TREP) or the Elektron Real Time platform
This article discusses the ease of use of the Elektron Message API and introduces a layer of reusable value add objects that would simplify even more Elektron content access with EMA.
This article follows on from the Webinar session Introduction to MiFID II for Developers, with some detail on the coding aspects of handling (or avoiding) the high precision time, not covered in the Webinar and includes some information based on questions arising after the event.
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.
With over 50 million instruments carried by our realtime Elektron feed - answering that question would be overwhelming. This article shows you how to make Criteria Based Requests (CBR) aka Broadcast Data Stream (BDS) - to the Elektron Edge Device - which return a list of RICS matching a set specified criteria.
This article discusses the OMM to FIX Gateway capability for existing TREP clients to transmit pre-trade FIX messages to registered Approved Publication Arrangements (APA) to satisfy MIFID II regulatory requirements.
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?
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.
MiFID II - Extending the precision of timestamps supported on Elektron Real Time.
MRN & N2_UBMS Comparison and Migration Guide
This article explains how to develop RFA Java application to monitor the health of services. The general techniques could be applied to TREP real-time streaming APIs e.g. RFA.NET/C+, ETA C+/Java.
This article explains how to request particular fields of an item via RFA. The general techniques could be applied to any of real-time streaming APIs i.e. ETA C+/Java, EMA C++/Java.
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?
Learn how to create auto-expiring records on TREP.
This article is intended for Java software users who are developing RFA Java Consumer applications. It is going to explain how to verify, if the application is out of memory, due to slow processing data events/messages and the ways to solve the problem.
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.
This article examines the Thomson Reuters Machine Readable News offering, discussing its features, the most common use cases and provides specific details of implementation from the standpoint of an application developer.