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.
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.'