Use API directly connect to EED but got 121 event error
User is using trep api now but wants to directly connect the api to eed
can't work
For a deeper look into our Elektron API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
1
●0 ●0 ●0
Use API directly connect to EED but got 121 event error
Hello @1457482470
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If so please can you click the 'Accept' text next to the appropriate reply. This will guide all community members who have a similar question.
Thanks,
AHS
Hi,
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
25.3k
●87 ●12 ●25
Hi @1457482470
Is the user permissioned to connect directly to the EED?
A DACS id with permission to connect to an ADS on TREP may not be permissioned to connect directly to an Edge device.
It is very difficult to make full sense of the small screen capture you have provided. It would be better if the full text of the message was captured and included as a text attachment to your reply.
Also, if the developer can enable the RFA Java low-level trace, this may provide a more detailed understanding of the problem.
To enable RSSL tracing in RFA API, please add ipcTraceFlags and logFileName to the RFA connection config. The value of ipcTraceFlags is 31.
The trace file will show the messages sent and received by the RFA API to and from the server.
UPDATE:
I have just confirmed that connecting directly to EED is non-compliant since the consumer is bypassing DACS and would then have direct access to all the data available on Elektron.
7.6k
●15 ●6 ●9
For diagnostic purposes, I would suggest you print the details from the Login response status to console output or log in to your application log, so next time if your client found any error they can report the error with additional information such as status text.
