What is the best practice for establishing an OmmConsumer connection?
Opening/closing for each request or keeping a single client connection open for the life of the application to be used for all requests?
If only a single connection is required, is there anything that needs to be closed?
We use the batch process and the uninitialize() does not work. Does the batch process close the session on its own?
Best Answer
-
Hello @joe.hong
Normally, a single connection is used to get data from a server. The simple workflow to use batch request is
- EMA Java application connects to the server and login.
- it sends a batch request to ADS.
- ADS responds by sending the items as if they were opened individually as shown in the figure below:
4. the application processes data messages sent from ADS.
Before the application exits, it should logout and closes all items. These can be done by calling OmmConsumer.uninitialize() as mentioned in the EMAJ_DevGuide.pdf shown below:
When OmmConsumer.uninitialize() is called, EMA sends a request to close the login stream(logout) for the session/connection to the server. Then, all item opened under the session/connection are closed. Hence, the application does not need to send close request for each item stream.
Please see the example370__MarketPrice__Batch which demonstrates how to use of batch request and close session.
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
- 684 Datastream
- 1.4K DSS
- 615 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
- 251 ETA
- 555 WebSocket API
- 37 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
- 275 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
- 643 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
- 228 TRKD
- 916 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
- 46 中文论坛