Posting using OMM consumer
Posting using OMM consumer
Hi developer community
I'm using right now the RFA 7.6 java API. I'm trying to create an OMM consumer which will contribute prices to an ADH.
I'm using an off stream contribution (using login session), and then I'm trying to post messages.
Assuming that I'm contributing to a service X with a RIC Y, in each contribution (initial one or the updates), I’m using those parameters:
payloadOMMMsg.setMsgType(OMMMsg.MsgType.POST);
payloadOMMMsg.setIndicationFlags(OMMMsg.Indication.POST_INIT | OMMMsg.Indication.POST_COMPLETE);
The problem is that in the ADH, I'm seeing the number of active contributor incrementing on each updates, and in the logs, it seems that my RIC is created each time, meaning that the updates are not handled by the first RIC created. Could you explain me what I missed?
My goals is to contribute on a specific RIC Y, if it exists that’s cool, if not, the ADH should create it, after that, I should send price update to this specific RIC using OMM posting. How can I do that if my last approach is wrong?
Regards,
Best Answer
-
What are you seeing in the log to indicate the record is being created each time?
Have you confirmed this by consuming the Post record?
e.g. Post to Record Y initially with several Fields and then post again with only a subset of those Fields.
Consume the record after the 1st post and confirm all the fields are present. After the 2nd post confirm that it did not remove (or blank) the Fields that were only present in the first Post.
1
Answers
-
Thanks for the quick response,
I did not jave access to logs right now, our architecture team has left. I will post tomorrow the logs, and will try your approch.
Give you the feedback tomorrow.
Thanks a lot
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 中文论坛