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 /
  • EMA /
avatar image
Question by varma · Aug 21, 2017 at 10:03 PM · elektronrefinitiv-realtimeelektron-sdkrrtema-apielektron-message-apijava

Can we use EMA Consumer example to read Ticket Output Feed?

What are the parameters we need to pass in the following code snippet?

What we are trying to read is complete deal info to java code,

<FS>332<US>tag<GS>TCID # INFO<FS>

consumer.registerClient( EmaFactory.createReqMsg() .serviceName("ELEKTRON_AD") .name("BB.TO"), eventHandler );

Can someone please help on this? Am looking for an example for Reading Ticket Output Feed. Please help

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 Jirapongse · Aug 21, 2017 at 11:22 PM

EMA Java can be used to retrieve real-time data from ELEKTRON service (ELEKTRON_AD). Please see the sample market price data for BB.TO in the attached file (data.txt). The data is in field list. I couldn't find Ticket Output Feed in the returned field list.

For Ticket Output Feed, it could be from Transaction Product, such as Dealing. <FS>332 is not used by real-time data.

You should contact your Thomson Reuters account team for further assistance regarding TOF or contact the Dealing support team via http://my.thomsonreuters.com/ContactUsNew


data.txt (5.1 KiB)
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 · Aug 22, 2017 at 06:18 AM

Hi @varma

Reading between the lines, I am guessing that you want code to subscribe to the DealTicket TCID#INFO record and then consume each new ticket that is issued on the Dealticket #INFO record.

Firstly, I recommend you work through the first few steps of our EMA Java tutorials - up to the step 'EMA Consumer - Parsing and Decoding MarketPrice data' - to get a basic understanding of how EMA Consumer works.

You will note in the tutorial that you call registerClient with the RIC that you wish to subsrcibe to.

OmmConsumerClient infoEventHandler = this;
consumer.registerClient(
                  EmaFactory.createReqMsg()
                                .serviceName("ELEKTRON_AD")
                                .name("TCID#INFO"), 
				 infoEventHandler );		

This will result in the OnRefreshMsg invoked initially and then OnUpdateMsg invoked as and when new DealTicket records are generated on TOF.

From the OnRefreshMsg and OnUpdateMsg you would then call the decode method which iterates through the FieldList and extracts the LATESTID field (as well as others you require). Each time you get a new LATESTID field you would then call registerClient again - using the LATESTID as the RIC code - but this time you would only want a snapshot - not a streaming request so you would set the interestAfterRefreshFlag to false

consumer.registerClient(
                  EmaFactory.createReqMsg()
                                .serviceName("ELEKTRON_AD")
                                .name(latestTicketID)
				.interestAfterRefresh(false), //snapshot
				 _ticketEventHandler );	

NOTE the following:

  • I am guessing the field that contains the new TICKET number is LATESTID - it could be a different Field
  • I have used ELEKTRON_AD as the servicename - yours may well be different e.g. DEALING_DATA?
  • Note that I am using two different OmmConsumerClient instances - each with its own implementation (not shown) - infoEventHandler and _ticketEventHandler
  • You could use the same OmmConsumerClient instance (and implementation) - but using one to implement the code for handling #INFO records and one to implement the code for handling your Ticket records will make the code cleaner.
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 >
11 People are following this question.

Related Questions

(JAVA) Does using interestAfterRefresh(false) remove the need for deregistering items with Elektron?

Auto listener occupies 70-100% of CPU as we are waiting for the update(Consumer.dispatch)

EMA - How do I reset view to get all fields?

Where can I find details on the EMA instrument update message types?

Timestamp delay between EMA Java based App and rmdstestclient when subscribing the same universe.

  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Electronic Trading
    • Generic FIX
    • Local Bank Node API
    • Trading API
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Intelligent Tagging
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open Calais
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • RDMS
  • 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
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • Workspace SDK
    • Element Framework
    • Grid
  • World-Check Data File
  • 中文论坛
  • Explore
  • Tags
  • Questions
  • Badges