How to get the SeriveName in Provider from consumer, during application shutdown at consumer
we are having a provider(RFA), and a Consumer(Ema).
When subscribing to the MarketDataService from the Consumer, the ServiceName appears on the Provider side through Trep.
However, during application shutdown on the Consumer side, automatic unsubscription calls are made, which we observe at the Provider end. Unfortunately, we can't see the ServiceName on the Provider side during this process. We are not explicitly unsubscribing during the shutdown.
1. During shutdown, is the EMA/Trep responsible for the automatic unsubscription?
2. Do you have any suggestions for retrieving the ServiceName on the Provider side during application shutdown?
NOTE: we are usnig Ema:3.5.0.1, language: Java
Answers
-
Hello @tuhin4uu,
The interactive provider application is responsible for handling all the subscription and unsubscription requests.
>> During shutdown, is the EMA/Trep responsible for the automatic unsubscription?
When the EMA application is terminated, it might not have the time to send an unsubscribe request. If RTMDS is used in the middle, the infrastructure will detect a channel down event, and might send unsubscribe on the consumer's behalf (need to verify this)
>> Do you have any suggestions for retrieving the ServiceName on the Provider side during application shutdown?
The provider application should maintain a map of all the item handles and subscription details like item name, service name etc. When an unsubscribe request is received for a handle, the app should be able to retrieve this information from the internal map and remove the handle.
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 中文论坛