Register multiple batch request

Hi Team,
There is a 65535 byte limit on the size of the ElementList entry that is used when making the Batch request for EMA API. Could you pls give us a demo how to send another Batch request if the RIC list exceed 65535 byte ?
BTW, what is the meaning of consumer.unregister(arg0);
thanks
Gang
Best Answer
-
Hello @gang.chen1
According to the EMA Java API Reference document, the OmmConsumer's unregister function accepts the handle value as an input parameter to specify which stream the application wants to close.
The EMA API assigns all opened items or instruments a unique numeric identifier (e.g. long), called a handle, which is returned by the OmmConsumer.registerClient() call. A handle is valid as long as its associated item stays open.
Note: The EMA Java API Reference document at the <RTSDK package>\Java\Ema\Docs\refman\emajava folder.
However, for the batch subscription, the API automatics unsubscribe the batch stream for the application (this is why the application receives the "Stream closed for batch" message), so the application does not need to call OmmConsumer.unregister(batch_handle) manually.
0
Answers
-
hi @gang.chen1 ,
For sending multiple batch requests, could you please check the answer provided in this thread
0 -
Hi samasiri,
Thanks and I saw that before. Double confirm we can just send consumer.registerClient again and again ? and no need to call consumer.unregister(arg0) in the middle ?
finally, what is the usage of consumer.unregister(arg0);
thx
0 -
hi @gang.chen1 ,
regarding the meaning of consumer.unregister(arg0);
you may check the documentation provided in Message API - Java: Development and Configuration Guides with Examples > EMA J RDM Usage Guide
page 7. mentioned that OmmConsumer.unregister() is the Close Message (Request)
Page 9. for the general domain use,
When the consumer is no longer interested, it sends an CloseMsg to close the stream
0 -
Hi Samasiri,
Thanks and what is the arg0 parameter should be? seems no explanation for it , or just call consumer.unregister();
thx
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.8K Refinitiv Data Platform
- 622 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛