NI Provider Example No Getting Login Response

Using RFAJ 7.4 example/..StarterProvider_NonInteractive - I do not get a Login Response.If, for the provider I provide the wrong DACS account, server or port, I receive an error. However, if all details are correct, I get the message stating that the service is up, but I never get a Connection event (via dispatch). A Consumer, using the same credentials generates/catches a Login event. The consumer works on both SSL and RSSL.
We have an RFAJ v5 Provider using SSL with a now deprecated API on the above credentials. This works too. Is their a bug in the example, or is these some special permissioning required for OMM Contributions?
Best Answer
-
Hello @anthony.leon
The possible reasons that causes StarterProvider_NonInteractive does not receive login response are listed below:
1. Improper RFA configuration. The RFA configuration should be:
- the connectionType is RSSL_NIPROV
- servereList and portNumber is ADH host and port.
StarterProvider_NonInteractive connects to ADH not ADS that the Consumer
application connects to as
shown in the diagram below:QuickStart NI-Provider is another example of NI
provider. Hence, StarterProvider_NonInteractive has the same connection as QuickStart
NI-Provider.To get the correct ADH server/port/a valid user
info, you should contact your ADH admin if you use company’s ADH. Otherwise,
please contact Thomson Reuters Account team.2. Firewall problem which does not allow send/receive message between StarterProvider_NonInteractive
machine and ADH. Please contact your network admin to verify this.0
Answers
-
Hello @anthony.leon
OMM Connection event is provided since RFA 7.5. Hence,
you do not receive these events via RFA 7.4 even the application connects to ADH
successfully. Anyway, After StarterProvider_NonInteractive RFA 7.4 gets
successful login response, it can start publishes its service info(directory
message) and data.Moreover,
RFA7.4 has been end of life. Please refer to API Compatibility Matrix that shows products compatibilities and
the supported products. If you use MarketData interfaces(SSL) as well, you
should upgrade to RFA7.6.1. If not, you should upgrade to RFA 8.0.1(only OMM
interfaces are provided). Both versions can be downloaded at https://developers.thomsonreuters.com/thomson-reuters-enterprise-platform/robust-foundation-api-rfa-0/downloads0 -
I was using RSSL, not RSSL_NIPROV. I now get a log-in response. This fixed it. Thanks for responding.
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
- 687 Datastream
- 1.4K DSS
- 621 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 ETA
- 557 WebSocket API
- 38 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
- 276 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
- 669 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
- 229 TRKD
- 917 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
- 48 中文论坛