Elektron SDK C++ tutorial example - Unable to login

I am currently trying the tutorial example for contributing data "Elektron Message API - Consumer Tutorial - Posting data to TR Contribution Channel" on a Windows 10 machine.
The following line seems to timeout:
OmmConsumer consumer(OmmConsumerConfig().host("ecc01-emea1.fr.aws.thomsonreuters.com:443").username("GE-A-01281282-3-2411"));
And I get the following error:
Exception Type='OmmInvalidUsageException', Text='login failed (timed out after waiting 45000 milliseconds) for ecc01-emea1.fr.aws.thomsonreuters.com:443)', ErrorCode='-4052'
I believe the server and port are correct and the username is the one I received.
Any ideas?
Thanks
Best Answer
-
For Windows, EMA needs to have an encrypted protocol type set to SOCKET. Please see the Channel_3 configuration in EmaConfig.xml provided in Cpp-C/Ema/Examples.
The line is:
<EncryptedProtocolType value="EncryptedProtocolType::RSSL_SOCKET"/>
This encryption type requires OpenSSL libraries, which are not built by the Elektron SDK package. Please see chapter 4.3.3: Encrypted Connections in the EMA Developer's Guide for more information.
0
Answers
-
The above host value is a valid TRCC mount point and should be working fine.
Just want to check you are following all the steps in the tutorial - including changing the Channel Type to RSSL_ENCRYPTED from the default RSSL_SOCKET
Rather than hard coding the host:port into the source code, change the config file as described in the tutorial for now and confirm it all works.
0 -
Hi,
Below is a screenshot that illustrates the usage and the error I am getting. As you can see the xml is updated for Channel 1 and 2. It is in the same directory as the source. When run it is somehow still picking up localhost.
I guess that's the default when not specified:
OmmConsumerConfig& host( const EmaString& host = "localhost:14002" );
See error below.
Any ideas on whats wrong? Thanks
0 -
Hi,
Have you had a chance to review my last post please. This is quite an urgent issue for us.
Thanks
0 -
The EmaConfig.xml files needs to be in the Working Directory which defaults to the location where the Project files etc are located i.e. $(ProjectDir)
For example, on my PC I placed the EmaConfig.xml file in
C:\Code\ESDKC131VS2017\Cpp-C\Ema\Examples\Training\Consumer\300_Series\341__MarketPrice__OffStreamPost
where C:\Code\ESDKC131VS2017 is the location of my main esdk.sln file.
If you copy the file to that location, it should pick up the contents of the file.
0 -
Hi,
Thanks for looking into this. I have tried that but now get a different error.
0 -
Hi,
I provide my EmaConfig.xml and the latest log file. Please note I had to rename the files extension to txt in order to upload here.
Thanks
emaLog_16628.log.txtEmaConfig.xml.txt
0 -
Is this a new thing? The current tutorial does not reflect this setting:
0 -
This functionality was added in 3.3.0, which was released in March 2019.
0 -
Thank you for pointing this out. It is working now.
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
- 695 Datastream
- 1.5K DSS
- 631 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 562 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 736 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛