Applies to: All versions of Ephesoft Transact
You may be asked to set your Ephesoft installation to info level logging if you have encountered an error that support needs more information to resolve. By default, only error messages are logged in the Ephesoft logs. Info level logs help us to better diagnose your issue, as it allows us to see exactly where the error is happening in the application process.
Note: It is recommended (but not required) that you collect info level logs before escalating an issue to support.
Changing Log Level
Perform the follow steps:
- Stop the Ephesoft Transact service.
- In the log4j.xml file, located at [Ephesoft_Directory]\Application\log4j.xml, locate the following parameter:
<level value=”ERROR” />
- Change the value from ERROR to INFO.
Example of original entry:
<logger name="com.ephesoft">
<level value="ERROR" />
</logger>
Example of edited entry:
<logger name="com.ephesoft">
<level value="INFO" />
</logger>
- Save and close the log4j.xml file.
- Start the Ephesoft Transact service.
Files Affected
Windows
- [Ephesoft_Directory]\Application\logs\dcma-all.log
- [Ephesoft_Directory]\JavaAppServer\logs\stdout.log
- [Ephesoft_Directory]\JavaAppServer\logs\catalina.log
Linux
- [Ephesoft_Directory]/Application/logs/dcma-all.log
- [Ephesoft_Directory]/JavaAppServer/logs/catalina.out
- [Ephesoft_Directory]/JavaAppServer/logs/catalina.<date>.log
Notes
INFO level log files can grow very quickly. It is recommended that you change back to ERROR level after you have supplied the info level logs to the Support team. Follow the same directions above, but change the value from INFO to ERROR.