EMA API

Dennis-Refinitiv

Hi, Client's vendor is using RTO for their development for client software. Once tested, they will pass the coding for client to deploy on the EED with RTDS environment. Understand RTO will need to have authentication and token where RTDS just required DACS ID. Is there a big change for the coding to deploy on EED with RTDS.

Also, client wants to use the same session/connection to do streaming on equity rics and snapshot at 5PM on some composite rate. Is that possible with the EMA API or they need to have 2 sessions where 1 for streaming and another for snapshot. What is the suggestion?

wasin.w V3

Hello @Dennis-Refinitiv

Question 1: Is there a big change for the coding to deploy on EED with RTDS.

Answer: Do you mean is there a big application code change from RTDS connection to RTO connection?

If so, yes there is some change needs to be done, but not that big change.

• The client needs RTO account. I hope we will grant the Version 2 Authentication (Service Account) for the client, not the Machine-ID/Password (Version 1 Authentication). See https://developers.lseg.com/en/article-catalog/article/account-authorization-v1-to-v2-migration-cheat-sheet article for more detail.
• The RTO connection is mixed of Delivery Platform Authentication and Service Discovery HTTP REST calls and the RSSL connection to the RTO Real-Time endpoint. The API manages all those tasks for the client. However, the client network/firewall need to whitelist a connection to api.refinitiv.com and RTO endpoints.
• The api.refinitiv.com static IP Address information is on this document page.
• The RTO real-time endpoints whitelist information is on this RTO Config and Install Guide page.

Regarding the code. I strongly suggest example 113 of the EMA Java, C++, and C#. The client can find how to run the example 113 on each edition quickstart guide as follows:

• EMA Java: Quick Start - Connecting to the Real-Time -- Optimized with Authetication Version 2 (Note the Java Quickstart uses example450, which do some tasks in example113 manually.
• RTSDK (EMA/ETA) C/C++ Quick Start
• Real-Time SDK - C# - (ETA/EMA) Quick Start

Authentication Method

The code is change from just input DACS User to input RTO credential.

Example from EMA Java:

OmmConsumerConfig config = EmaFactory.createOmmConsumerConfig();
config.clientId("client-id").clientSecret("client-secret");
OmmConsumer consumer  = EmaFactory.createOmmConsumer(config.consumerName("Consumer_4")
.clientId(clientId).clientSecret(clientSecret));

Then set required RTO endpoint regions in the “Location” property with the "EnableSessionManagement" = "1" of EmaConfig.xml file. See the RTO Config in Install Guide document for getting the list of supported regions

<Channel>

        <Name value="Channel_4"/>

        <ChannelType value="ChannelType::RSSL_ENCRYPTED"/>

        <CompressionType value="CompressionType::None"/>

        <GuaranteedOutputBuffers value="5000"/>

        <!-- EMA discovers a host and a port from LDP service discovery for the specified location

             when both of them are not set and the session management is enable. -->
<Location value="us-east-1"/>

        <EnableSessionManagement value="1"/>

        <ObjectName value=""/>

</Channel>

Question 2: Is that possible with the EMA API or they need to have 2 sessions where 1 for streaming and another for snapshot."

Answer:

With the Authentication Version 2 (client-id and client-secret), it supports up to 5 concurrent RTO sessions used by a single account.

However, if the client gets the Machine-ID (GE-A-XXXXXXXX-X-XXXX) account type. It is recommended to use multiple Machine-IDs with multiple sessions.