Running Elektron-SDK's C++ Example Step2: what do we need to customize?
Hello,
we've downloaded
- Elektron SDK - C/C++ - 1.1.0 - Windows
- and the examples from https://developers.thomsonreuters.com/system/files/EMA%20Tutorials.zip
Then we set the environment variable EMAInstall to
C:\Projects\API\EMA\Elektron-SDK\ema where we've unzipped Elektron SDK and we can compile the project ...step2\Consumer_VS120.vcxproj without errors. That works.
Now we'd like to run Step2 and obtain some response data.
The source code is:
.....................
cout << "Connecting to market data server" << endl;
// create OMM consumer
OmmConsumer consumer(
OmmConsumerConfig()
.host( "TOR_ADS:14002" )
.username( "user" )
);
.....................
we're waiting from Reuters person with whom we signed the contract the data like
hostname, portnumber, service name, DACS user name
The questions:
1) In the above example is it enough to change only "TOR_ADS:14002" and "user" with our account's data we will get from Reuters person?
2) Should'n we insert a password somewhere? How to you authenticate users?
3) Is it possible to know all port numbers we need to open in our firewall? Only TCP port 14002? That's all?
Thanks in advance
Best Answer
-
Hello,
This is a very good question, how to get started using Elektron via API and are
EMA Tutorials a good starting point.
Yes:
1) A developer will need to point their Consumer application at their assigned infrastructure, usually ADS, the statement you are looking at is designed to point, and TOR_ADS is just a placeholder for the assigned ADS, that will need to be replaced with it, once available.
In addition, a developer will need to replace a placeholder service, such as ELEKTRON_AD with the assigned service, and the placeholder RIC (Reuters Identifier Code for an instrument) "IBM.N" in the example, with a permissioned RIC that they are looking to subscribe.
2) The user is authenticated by the infrastructure they are connecting to, by means of DACS (Data Access Control System) and, therefore, only permissioned users will be able to login, and they only be able to subscribe to RICs they are permissioned for. Depending, if the connection is over a private line or over a dedicated secure channel, the assigned "user" credentials will be necessary and sufficient to connect and authenticate.
3) As you are planning to utilize EMA for subscription, you will be using OMM, and it's facilitated over RSSL protocol. RSSL is provided by default on port 14002. Unless you are planning to use a deployed infrastructure where you are planning to implement custom changes, the port will be 14002.
Hope this explanation helps
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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛