from real time API to DSS API

This client is currently using LSEG real time service and considering switching to DSS REST API to snap financial data.

They would like to migrate from the current API "RFA Java 7.6 + Marketfeed format" to the DSS REST API as easily as possible.

With RFA Java 7.6 + Marketfeed format, RIC and fields were set in Java XML format, so They wanted to understand how it would work in Java.

Please find the following 3 questions:

1. If they are going to use Java, they would need to use separate programming because they wouldn't be using the SDK, so is it correct to assume that this would make the migration more time-consuming?

2. They understand that using the SDK makes the migration easier. Please advise if this understanding is correct.

3. They understand that the SDK will be written in C#, and would like to know how will the RIC and fields be configured? Currently, the data is acquired in the attached XML file format (converted to text file to attach) , so I would appreciate it if you could check this.

Configuration_for_FSCM01 xml to text.txt

Javaを利用しようとする場合、SDKを使用しないため別途プログラミングが必要となり、より移行に手間がかかる認識でよいでしょうか。
SDKを使用したほうが簡単に移行できるものと理解しておりますが齟齬あればご指摘いただきたいと思います。
SDKの場合、C#の言語となると理解しておりますが、RICや取得項目の設定はどのようになるでしょうか。現在は添付のxmlファイルのような形式で取得しておりますので、ご確認いただけますと幸いです。

Find more posts tagged with

java

dss-rest-api

#technology

Accepted answers

All comments

wasin.w V3

Hello @HirokoGoto_1

I am not the DSS expert. However, the https://developers.lseg.com/en/api-catalog/datascope-select/datascope-select-rest-api is the HTTP-REST API, so the coding will be different from the Real-Time APIs (including RFA).

I am strongly suggesting the client checks the DSS REST API official page to learn about the API.

If the client is using Java, the client can use any Java HTTP Client libraries such as the Java 11 built-in java.net.http.HttpClient, Apache HttpComponents, Kong Unirest for Java, etc. to connect and consume data from the DSS REST API HTTP endpoint. There is the DSS REST Java HTTP Example available on the https://developers.lseg.com/en/api-catalog/datascope-select/datascope-select-rest-api/download page.

If the client is using C#, the client can use the DSS REST API SDK for .NET (see the Quick Start page), or pure HTTP code using the .NET HttpClient class, or 3rd Party like RestCharp.

The client can see more details on the DSS REST API Tutorials pages:

I hope this helps.

wasin.w V3

Hello @HirokoGoto_1

I am wondering why the client choose to migrate to the https://developers.lseg.com/en/api-catalog/datascope-select/datascope-select-rest-api ? The API does not provide the real-time snapshot data for consumer.

If the client needs only real-time snapshot data, there are a lot of choices in the https://developers.lseg.com/en/use-cases-catalog/real-time and Delivery Platform (aka Data Platform, RDP)

The ADS server can be configured to be HTTP REST server for consuming real-time snapshot data (see https://developers.lseg.com/en/article-catalog/article/get-stock-prices-using-rest-with-ads article).
The strategic Real-Time API like the EMA (Enterprice Message API) supports snapshot data request (Image/Refresh message only).
Even the RFA Java 8.x with the OMM Interface supports snapshot data request (Image/Refresh message only).
There is the service on the RDP that provides real-time snapshot data over HTTP REST endpoint.

There is the https://developers.refinitiv.com/en/article-catalog/article/choosing-your-refinitiv-realtime-streaming-api article that might help the client.

HirokoGoto_1

Hi Wasin, Sorry for the delayed response. Thank you for your insight. I ve shared your resolution to the client. The reason why they are currently looking at DSS isntead of real time is that their way of data usage is simply snap data even though this is streaming service. Thats why they are looking at changing from real time to DSS.

umer.nalla02

Hi @HirokoGoto_1
What is the frequency of the snaps and is it only end of day pricing or intraday and what fields are they snapping?
If they have not yet fully evaluated and confirmed that DSS is suitable for their requirement then, the RDP Historical Pricing API could also be an option too - depending on answers to the above.
The data on HPA is can be available earlier than on DSS - if timing is of concern.

EXPLORE OUR SITES