Can I rely on ACK ID from onAckMsg to confirm the processing status of the price publication request
I got a question on Refinitiv EMA API call with EMA jar version 3.6.2.2.
I would like to confirm if it is safe to assume a price publication request sent to EMA API is accepted and successfully processed when we receive the ACK ID from onAckMsg api? Or that simply means the request has been received by the API handler only and no guarantee if the request is processed successfully?
If that's the later case can you advise is there any recommendation on how we can perform a completeness check to confirm all requests have been processed successfully?
Many Thanks
Best Answer
-
Thanks for reaching out to us.
The acknowledgment message carries success or failure (i.e., a negative acknowledgment or ‘NAK’) information to the consumer. When acknowledging a Post message, ACK ID typically matches the post message’s PostID so the ACK ID is used to match the post message.
To verify if the post message is processed successfully, you need to check the presence of NakCode. If present, this message indicates a NAK (a negative acknowledgment). The NakCode is an enumerated code value (ranging in value from 1 to 255) that provides additional information about the reason for the NAK.
You can also check the text in the message which provides additional information about the acceptance or rejection of the message being acknowledged. For more information, please refer to the EMA Reference Guide regarding the AckMsg.
I hope that this information is of help.
0
Answers
-
Hello @denny.c.h.ma
Additionally from my colleague @Jirapongse answer, the example messages are as follows:
Post success (acceptance case with EMA Java posts to RCC):
----- Ack message ----
AckMsg
streamId="6"
domain="MarketPrice Domain"
ackId="10"
AckMsgEndPost failure (reject case with EMA Java posts "invalid RIC" to RCC)
----- Ack message ----
AckMsg
streamId="6"
domain="MarketPrice Domain"
ackId="5"
nackCode="DeniedBySource"
text="RIC has been disabled"
AckMsgEndThe message pattern should be mostly identical to either RCC, ATS, or local RTDS contribution scenarios.
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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛