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.
0
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
- 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
- 687 Datastream
- 1.4K DSS
- 622 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
- 254 ETA
- 557 WebSocket API
- 38 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
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 676 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
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛