What is the name of the ETA log file and where is it
An application team has a Vendor product which uses ETA Java. We need them to be able to log errors such as connect/disconnect, entitlement error, bad ric. They don't know where the API log file is. Where would the default place be for the log file and its name and would it log these errors. If not, what configuration do they need to enable the log file.
Find more posts tagged with
Sorry - I should have been clearer - although the marked answer in the above link does refer to ETA C, the other answers on the page had references to ETA Java e.g.
It appears that the ETA for Java does its XML tracing through the Msg interface. The Msg interface is a subclass of XMLDecoder which can be used to log your messages to stdout, file, etc.
You see how it is utilized within the Eta\Applications\Examples\src\main\java\com\thomsonreuters\upa\examples\consumer folder. That example has a -x switch which dumps trace message to XML....
In terms of things like Login issues, entitlement issues, invalid RIC etc - you would receive these as Status message responses for Login or individual item requests and are not considered API errors. They would be included in any XML trace - along with all the other valid data responses etc. Therefore if you wanted to just log specific messages/events etc it would be an application-level implementation to log them as required to an appropriate log file.
ETA is a low-level API designed primarily for low-latency and highest performance. In the ETA DevGuide it states that ETA 'Does not have external configuration, log file, or message file dependencies: everything is programmatically supplied, where the user can define any external configuration or logging according to their needs.'
Sorry - I should have been clearer - although the marked answer in the above link does refer to ETA C, the other answers on the page had references to ETA Java e.g.
It appears that the ETA for Java does its XML tracing through the Msg interface. The Msg interface is a subclass of XMLDecoder which can be used to log your messages to stdout, file, etc.
You see how it is utilized within the Eta\Applications\Examples\src\main\java\com\thomsonreuters\upa\examples\consumer folder. That example has a -x switch which dumps trace message to XML....
In terms of things like Login issues, entitlement issues, invalid RIC etc - you would receive these as Status message responses for Login or individual item requests and are not considered API errors. They would be included in any XML trace - along with all the other valid data responses etc. Therefore if you wanted to just log specific messages/events etc it would be an application-level implementation to log them as required to an appropriate log file.
ETA is a low-level API designed primarily for low-latency and highest performance. In the ETA DevGuide it states that ETA 'Does not have external configuration, log file, or message file dependencies: everything is programmatically supplied, where the user can define any external configuration or logging according to their needs.'
Hi @Michael Moore
Please refer to this existing post for ETA - Enable logging in Consumer application
Hi. I saw that question/answer before. It is not really what I am looking for. We don't need the application team to turn on 'tracing' - i.e. logging all fields in a subscription update. We just need them to log higher level events such as connect/disconnect to TREP, entitlement denied, bad ric, etc. These are fundamental for support of the application. So then the question would be is are these logged by default, or do they need to turn them on in code? The documentation reference you gave is for ETA C and it looks like they are using ETA Java (if such a thing exists). Also, clicking on the links gives no information saying developers.refinitiv.com refused to connect.