NIP publishing on 2 ADH without multicast
I'm working on a NIP which needs to publishes on my TREP infrastructure. Here's my need:
- One NIP
- Two ADH
- I can't use multicast on the server which hosts the NIP
- I need a fault tolerant solution on the TREP side
Here's what I'm doing currently:
And here’s my test scenario:
- I start the ADH pair:
hot standby : ADH1 active / ADH2 standby
cache resiliency : True
cache percistency : True - I start the NIP
- When the NIP starts, it connects to the first server of its list: ADH1
- My NIP publishes a couple of updates on InstrumentA
- I shutdown the NIP
- I kill ADH1
- If I dump the cache of ADH2, there’s no trace of InstrumentA <= this is a problem
Another scenario:
- I start the ADH pair (same configuration)
- I start the NIP
- When the NIP starts, it connects to ADH1
- My NIP publishes a couple of updates on InstrumentA
- I kill the ADH1. (ADH2 is now active)
- The NIP connects to ADH2
- I restart the ADH1. (ADH2 is still active, so ADH1 is standby)
- I kill the NIP
- I start the NIP
The NIP connects to the first server of its list: ADH1 (which is standby) <= this is another problem…
Am I doing something wrong?
Is there something I should do on my NIP in order to post simultaneously (via RSSL, because I can't use multicat) on both ADH?
Best Answer
-
I am not sure which TREP API you are using but I assume it is RFA.
If you want RFA to connect to both ADH, you have to use connectionList.
\Sessions\SessionOMMNIProv\connectionList = "Connection_RSSL_NIPROV,Connection_RSSL_NIPROV2"
\Connections\Connection_RSSL_NIPROV\connectionType = "RSSL_NIPROV"
\Connections\Connection_RSSL_NIPROV\rsslPort = "14003"
\Connections\Connection_RSSL_NIPROV\hostName = "192.168.27.30"
\Connections\Connection_RSSL_NIPROV2\connectionType = "RSSL_NIPROV"
\Connections\Connection_RSSL_NIPROV2\rsslPort = "14003"
\Connections\Connection_RSSL_NIPROV2\hostName = "192.168.27.60"With this configuration, RFA should connect and publish to both ADHs.
0
Answers
-
I'm working on a NIP which needs to publishes on my TREP infrastructure. Here's my need:
- One NIP
- Two ADH
- I can't use multicast on the server which hosts the NIP
- I need a fault tolerant solution on the TREP side
Here's what I'm doing currently:
And here’s my test scenario:
- I start the ADH pair:
hot standby : ADH1 active / ADH2 standby
cache resiliency : True
cache percistency : True - I start the NIP
- When the NIP starts, it connects to the first server of its list: ADH1
- My NIP publishes a couple of updates on InstrumentA
- I shutdown the NIP
- I kill ADH1
- If I dump the cache of ADH2, there’s no trace of InstrumentA <= this is a problem
Another scenario:
- I start the ADH pair (same configuration)
- I start the NIP
- When the NIP starts, it connects to ADH1
- My NIP publishes a couple of updates on InstrumentA
- I kill the ADH1. (ADH2 is now active)
- The NIP connects to ADH2
- I restart the ADH1. (ADH2 is still active, so ADH1 is standby)
- I kill the NIP
- I start the NIP
The NIP connects to the first server of its list: ADH1 (which is standby) <= this is another problem…
Am I doing something wrong?
Is there something I should do on my NIP in order to post simultaneously (via RSSL, because I can't use multicat) on both ADH?0 -
(sorry, I posted my question in the "answer"... I'm still new with the forum and I don't see how to edit my question)
0 -
Thanks a lot Warat, it's working perfectly fine!
I just had to modify the Reuters example (ommprovnimdi /
LoginClient.java) in order to always call processLogin(true) as it's explained in the code comments:
// If there is more than one Connection, then this could would
// need to be changed to always call processLogin(true) when the
// re is a refresh. In general, if applications wish to use two
// Connections, it is recommended that they use two Sessions.
// (...)
// if (!_loggedIn)
//{
_loggedIn = true;
_mainApp.processLogin(true);
//}
}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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛