first time connection to reuters
Hopefully this weekend we will have a working connection in our trading server,
our goal is to handle RIC ECI events
Currently our test app is based on consumer 291 (cpp,linux)
We were able to test\debug the code locally using sink_driven_src running on windows
My main questions:
- does this sample support RIC ECI events?
- does changing the name to USNFAR=ECI. is enough ? ( insted of JPY=)
- where should i enter the session information that ill recive (user\password )
- what else should i be aware of ?
Best Answer
-
It depends on the data feed that you are using.
If it is TREP, Elektron Edge Device, or Elektron as a Service, the example consumer100 or 120 is enough to subscribe to the data. To connect to that server, you need to know:
- Hostname or IP address of the server
- TCP port listening on the server. The default port is 14002
- Service name
- Username
For example:
AppClient client;
OmmConsumer consumer(OmmConsumerConfig().host("127.0.0.1:14002").username("user01"));
consumer.registerClient(ReqMsg().serviceName("API_ELEKTRON_EPD_RSSL").name("USNFAR=ECI"), client);
sleep( 60000 );The output is:
It is similar to connect to sink_driven_src.
However, if the data feed is Refinitiv Real-Time - Optimized (Cloud), you need to use the Con113 example.
OmmConsumer consumer( config.consumerName( "Consumer_3" ) );
consumer.registerClient( ReqMsg().serviceName( "ELEKTRON_DD" ).name( "USNFAR=ECI" ), client );
sleep( 900000 );To connect to Refinitiv Real-Time - Optimized, the following information is required.
- UserID/MachineID
- Password
- AppKey (Client ID)
Then, run the example with the following parameters:
./Cons113 -username <UserID or MachineID> -password <Password> -clientId <AppKey>
I have tested with the SDK version 1.5.0.L1.
Next, I will answer your questions.
1. does this sample support RIC ECI events?
The consumer 291 is for a custom domain. You should use consumer100 or 120 instead.
2. does changing the name to USNFAR=ECI. is enough ? ( insted of JPY=)
Yes, it is enough if the application subscribes to the MarketPrice domain.
3. Where should i enter the session information that ill receive (user\password )
4. what else should i be aware of ?You need to verify the types of data feed that you are using. If it is TREP, Elektron Edge Device, or Elektron as a Service, it requires the username. However, if it is a cloud, it requires a username, password, and appkey. You need to contact the account or Sales team for more information.
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
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 251 ETA
- 555 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 916 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛