EMA Java - having different emaconfig.xml for different environment
In EMA Java, it will always look up "emaconfig.xml" when creating the OMM Consumer.
Can I have a different emaconfig.xml for different environment ?
How can I override the config file name?
e.g.
emaconfig_dev.xml
emaconfig_prd.xml
Best Answer
-
Hello @OX,
If the primary purpose is to switch between production and development environments then you could incorporate these into the same EmaConfig.xml by adding a Consumer entry for production and another for development, giving them a consumer name of "Prod" and "Dev" respectively. You can then select the required environment using the OmmConsumerConfig.consumerName() method. e.g.
config.consumerName("Dev");
0
Answers
-
Hello @OX
The EmaConfig.xml configuration file name is hard coded in the EMA Java API . You can change it to read another file in the EMA Java source code level in ConfigReader.loadFile() function.
The EMA ConfigReader.java source code is available at <Elektron SDK package>\Ema\Src\main\java\impl\com\thomsonreuters\ema\access folder.
//ConfigReader.java
protected void loadFile() {
_configFileName = "EmaConfig.xml";
_configFileLocation = System.getProperty("user.dir");0 -
Please note that advise given here is for advanced users. EMA is an open source API and Thomson Reuters provides ready to use API libraries. Any modification to API will have to be maintained by user themselves and may open up to additional bugs. A strong understanding of ETA API is required to modify EMA source code.
0 -
The file "EmaConfig.xml" will be read from the current directory.
You can have the two EmaConfig.xml files in different directories, say "/dev" and "/prod", and then just make sure you launch your application with the relevant directory as the current directory. Done!
Alternatively create a Pull Request on Github if you think this should be easier than what I propose. For example you can imagine that the file name can optionally be controlled via a OS Environment Variable and if that doesn't exist it would default to "EmaConfig.xml".
0 -
Hello @OX
The next ESDK release - ESDK
release 1.1.1 - will include a feature that allows application developers to
supply an optional path to a configuration file. The path may be a directory, in which
case the library will load a file named EmaConfig.xml from that directory, or a
filename.In Java, one will supply this path
as an argument to createOmmConsumerConfig; see the
example111__MarketPrice__UserSpecifiedFileConfig example for more
details. This example is new for this release.In C++, one will supply this path
as an argument to the OmmConsumerConfig constructor; see the 111__MarketPrice__UserSpecifiedFileConfig example for more details. This
example is new for this release.1
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 中文论坛