How to implement RFA provider with hotstandby enabled ?
Hello,
We're implementing a RFA provider in OMM and the feature "hot standby" is enabled on our TREP infrastructure but we don't have any documentation about this feature.
Is it related to "warm standby" or is it totally different ?
In the RFA documentation, we can read about "warm standby":
"a provider can be told to run as an Active or a Standby server, where the Active will behave as usual. The Standby will respond to item requests only with the message header and will forward any state changing information."
Do we have to implement the same behavior for "hotstandby" ?
When starting our provider, we have a message like this telling that "hot standby" is enabled:
<!-- Incoming Message from 'mkddev306' on 'localhost' interface -->
<!-- Time: 18:23:39:356 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<genericMsg domainType="RSSL_DMT_SOURCE" streamId="2" containerType="RSSL_DT_MAP" flags="0x14 (RSSL_GNMF_HAS_MSG_KEY|RSSL_GNMF_MESSAGE_COMPLETE)" dataSize="37">
<key flags="0x2 (RSSL_MKF_HAS_NAME)" name="ConsumerStatus"/>
<dataBody>
<map flags="0x0" countHint="0" keyPrimitiveType="RSSL_DT_UINT" containerType="RSSL_DT_ELEMENT_LIST" >
<mapEntry flags="0x0" action="RSSL_MPEA_ADD_ENTRY" key="1" >
<elementList flags="0x8 (RSSL_ELF_HAS_STANDARD_DATA)">
<elementEntry name="SourceMirroringMode" dataType="RSSL_DT_UINT" data="2"/>
</elementList>
</mapEntry>
</map>
</dataBody>
</genericMsg>
This message tells that our provider is on standby (cf. SourceMirroringMode = 2), so do we have to send only message with headers and no payload (like the "warm standby") ?
Thanks your answers.
Regards.
Best Answer
-
Refer to section 12.2 Hot Standby Requirements for Source Application in the ADH installation guide, each datafeed/source application must deliver the same update stream for each item open on the datafeed; i.e., the order of update delivery and the update’s data content must be the same for a given item.
Therefore, in Hot Standby mode, the source application of the standby server must send the same update messages as the source application of the active server.
0
Answers
-
Thanks for your reply.
0
Categories
- All Categories
- 6 AHS
- 37 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 中文论坛