Elektron-SDK-1.4.0.L1.java.rrg - Override NI_PUB default serviceName
Hi, in the Examples for this SDK, Non Interactive Provider, is there a way to override the default publisher serviceName of NI_PUB? This is hard coded several places in the SDK. Thanks, Bill C.
Best Answer
-
Hello @billy.w.cunningham
By default, the API always sends a Source Directory Service refresh message to ADH with a service name “NI_PUB”. There are three choices to configure the Source Directory refresh message based on your application requirement and implementation logic.
- Choice 1: Copy the API’s EmaConfig.xml file to the application working directory, then you can change the service values of "Directory_1" node to match your service name
- Choice 2: Manual sends a Source Directory refresh message to ADH server, so you can change a service name in the application source code to match your TREP/Elektron environment. Please see more detail in NIProvider example 300__MarketPrice__Streaming
- Choice 3: Use API Programmatic configuration. The EMA Java also provides a programmatic configuration feature for developers. It lets you configure the EMA Java configurations including a default Source Directory in your source code to match your service name and service id. The example for NIProvider is example421__MarketPrice__ProgrammaticConfig application.
For your reference, please see more detail in the following resources:
- EMA Java Configuration Guide: section 3.6 Directory Group.
- Developer Article: EMA Configuration Overview.
- EMA Java Configuration Guide: section 4.5 Programmatic Configuration.
0
Answers
-
Hello @billy.w.cunningham,
Yes, one can replace the hard-coded serviceName NI_PUB, with the service name that is required, in code.
However, the provider example connects to ADH infrastructure component. ADH is usually not on the localhost, ADH should have the service configured, and user should be permissioned to run it. Running this example requires coordinating with one's market data group or infrastructure team, to be able to connect according to one's infrastructure setup.
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
- 368 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 中文论坛