Applies to: All versions of Ephesoft Transact.

Issue

You may be asked to set your Ephesoft Transact installation to INFO level logging if you have encountered an error that Ephesoft 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 that you collect INFO level logs before escalating an issue to support.

Affected Log Files

The table below shows the log files that will need to be configured for INFO level logging.

Operating System	Log File
Windows	[Ephesoft_Directory]\Application\logs\dcma-all.log [Ephesoft_Directory]\Application\logs\dcma-report-all.log [Ephesoft_Directory]\JavaAppServer\logs\stdout.log [Ephesoft_Directory]\JavaAppServer\logs\catalina.log
Linux	[Ephesoft_Directory]/Application/logs/dcma-all.log [Ephesoft_Directory]/Application/logs/dcma-report-all.log [Ephesoft_Directory]/JavaAppServer/logs/catalina.out [Ephesoft_Directory]/JavaAppServer/logs/catalina.<date>.log

Enabling INFO Level Logging

Follow the steps below to enable INFO level logging for Ephesoft Transact 2020.1.03 and newer.

1. Stop the Ephesoft Transact service.
2. In the log4j.xml file, located in [Ephesoft_Directory]\Application\log4j.xml, locate the <Logger name="com.ephesoft" additivity="false" level="ERROR" and <AppenderRef ref="CORE" level="ERROR"/> parameters.
3. Change the level="ERROR" parameters to level=”INFO”
4. The com.ephesoft logger should now read as follows:

<Logger>
<Logger name="com.ephesoft" additivity="false" level="INFO">
<AppenderRef ref="CORE" level="INFO"/>
<AppenderRef ref="MONITOR" level="INFO"/>
<!--<AppenderRef ref="LOG_MONITOR"/> -->
</Logger>

5. Save and close the log4j.xml file.
6. Start the Ephesoft Transact service.

Follow the steps below to enable INFO level logging for Ephesoft Transact 2020.1.02 and older.

1. Stop the Ephesoft Transact service.
2. In the log4j.xml file, located in [Ephesoft_Directory]\Application\log4j.xml, locate the <level value=”ERROR” /> parameter.
3. Change the value=”ERROR” to value=”INFO”
4. The com.ephesoft logger should now read as follows:

<logger>
<logger name="com.ephesoft">
<level value="INFO" />
</logger>

5. Save and close the log4j.xml file.
6. Start the Ephesoft Transact service.

Note: 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 steps as above, but change the level from INFO to ERROR.

Enabling INFO Level Logging for Reporting

Follow the steps below to enable INFO level logging for reporting.

1. Stop the Ephesoft Transact service.
2. In the log4j.xml file, located in [Ephesoft_Directory]\Application\log4j.xml, locate the <Logger name="com.ephesoft.dcma.report" level="ERROR" additivity="false"> parameter.
3. Change the level="ERROR" parameter to level=”INFO”

4. The com.ephesoft.dcma.report logger should now read as follows:

<Logger>
<Logger name="com.ephesoft.dcma.report" level="INFO" additivity="false">
<AppenderRef ref="REPORT_APPENDER"/>
</Logger>

5. Save and close the log4j.xml file.
6. Start the Ephesoft Transact service.

Note: 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 steps as above, but change the level from INFO to ERROR.