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
Best Answer
-
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
0
Answers
-
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.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛