Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
avatar image
Question by daniel.roig · Feb 05, 2019 at 10:04 AM · elektron sdk - javasfc

SFC API vs Elektron SDK

Sorry if this post seems a bit confusing, but I inherited some legacy code that uses SFC to send and receive data. If I were to switch to Elektron SDK, is there a 1-to-1 mapping of the fields used in SFC to Elektron or are some fields no longer supported im Elektron?

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

2 Replies

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by David Thomas · Feb 05, 2019 at 10:42 AM

@daniel.roig

The underlying data being represented by SFC is also represented by the Elektron SDK, they both source data from our IDN/Elektron real-time networks and the data dictionaries used have to be very similar in order to do this;

i.e. Subscribing to any RIC from the Elektron real-time feed using SFC, all the same fields will also be available through the Elektron API.

But there are some additional fields contained in the Elektron data dictionary that cannot be handled by SFC: This simply reflects the fact that the Elektron API's are capable of providing additional data models such as Market-by-price which are now available on our Elektron real-time feed.

Perhaps a more significant change for you will be the fact that SFC has Object representations for the data (Records,Services etc) the Elektron SDK consists of a Message API (EMA) and a low level Transport API.

Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
REFINITIV
Answer by umer.nalla · Feb 05, 2019 at 10:58 AM

Hi @daniel.roig

The list of fields you receive from the server is not dictated by the API - it is determined by the data source / server you connect to.

Assuming that you are consuming MarketFeed format data using SFC, the TREP infrastructure can convert a MarketFeed payload to an OMM FieldList - which you would consume using the Elektron SDK.

There maybe some subtle differences in the content of individual fields e.g. OMM data can represent blank fields - whereas MarketFeed can use "+0" to represent a blank price field for example.

Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
8 People are following this question.

Related Questions

Elektron SDK and maven repository EMA is out of sync

Ema 3.2.1.0 has few classes removed compared to 3.2.0.2

Recreating Rhistory query using Elektron in the Cloud

Validate RIC prior to registerClient with Elektron API

NIP and DACS issue after distribution (Elektron Java SDK)

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges