EMA consumer Posting Data : state="Closed, Recoverable / Suspect / None / 'Capability not supported'
Hello,
We are tying to implement EMA Consumer Posting Data to contribution channel, and we connect TREP we get below message with state ="Closed, Recoverable / Suspect / None / 'Capability not supported'"
****************
TunnelStreamClient processSourceDirectoryRefresh
RSSL encrypted connection Login accepted and Directory is UP, starting Tunnel Stream...
TunnelStreamClient Start Tunnel Stream
----- TunnelStreamClient Status message ----
StatusMsg
streamId="6"
domain="System Domain"
privateStream
state="Closed, Recoverable / Suspect / None / 'Capability not supported'"
name="TUNNEL1"
serviceId="261"
serviceName="ATS"
StatusMsgEnd
****************
Any idea? Thanks
Best Answer
-
Hello @y.attar
Do you want to contribute data to your local ATS or to the Real-Time platform with RCC?
Based on the give log, you are using the tunnel stream feature (which is required when connecting to RCC directly) and try to post data to a service name "ATS".
Please be informed that the API can connect to the ATS server via local RTDS directly without using the tunnel stream. The tunnel stream is for connecting to RCC only.
If you want to post data to your local ATS, there are the following resources that might help you.
- Implementing Refinitiv Real-Time API applications to work with ATS - Part 1 article.
- Implementing Refinitiv Real-Time API applications to work with ATS - Part 2 article.
The suggest EMA example for the ATS posting are as follows:
- EMA Java: ex341_MP_OffStreamPost
- EMA C++: Cons341
- EMA C#: 341_MP_OffStreamPost
0
Answers
-
Hi @y.attar,
Are you sure you are using TREP for contributions to Contribution Channel? This step requires additional configuration within TREP as described within this article.
For Contribution Channel, the service name is DDS_TRCE typically. Service name ATS is typically used for contributing to local ATS and not contribution channel.
Also, for EMA, you can directly contribute the data to contribution channel without using RTMDS (TREP). See this tutorial for an example.
0 -
Hello @wasin.w
Thank you for your help and in fact after review EMA API documentation/example (Implementing Refinitiv Real-Time API applications to work with ATS - Part 1 & Implementing Refinitiv Real-Time API applications to work with ATS - Part 2 ), just yesterday I have tested with success to connected/Publish on ATS via API example 341_MP_OffStreamPost.
Thanks again,
Younes
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛