Specifying EmaConfig.xml when running EMA Consumer application using start-stop-deamon
There are two issues that I am facing :
1 . Though the EmaConfig.xml in the directory specifies log type as stdout , the application prompts that file could not be opened .
Exception Type='OmmInaccessibleLogFileException', Text='Failed to open emaLog_13892.log file for writing log messages.'
2 . In case the log type is file , what is the location in which the file will be created , or can we specify the file log path
Best Answer
-
#1 what you mean is your application print the Logger message to console and it also try to open a new file to write a logger messages at the same time?
If there are some typo in LoggerType such as using LoggerType::Stout instead of LoggerType::Stdout, it looks like EMA will write logger messages to the file by default.
And if the application does not have permission to write file in running directory it will throw the exception. Not sure if this is the case or not.#2 if your application installed as daemon for example, using windows services. It will run from a different context than normal user-mode applications, it's best if you don't make any assumptions about working directories or relative paths and the permission. As far as I understand default running directory for the service should be system folder such as c:\windows\system32. Using an absolute path to the file that your service needs should avoid this problem entirely.
For EMA, I can't find configuration to specify log location/folder but you can set absolute path to Log file name as below
<LoggerType value="LoggerType::File"/>
<FileName value="c:\myapp\Logs\emaLog"/>Don't forget to create folder "c:\myapp\Logs" before start the service or daemon.
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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛