TransSECS can be set to log at different levels for the SECS/GEM messages. By default the logger is a file called “SECSMessages.log” which rolls over after a size limit is exceeded.

There are three levels of SECS/GEM message logging: INFO, WARN, and DEBUG. In the log4j.xml file for TransSECS you will see a logger called “com.ergotech.transsecs.secs.Log4JLogger”. This is the logger which logs the SECS/GEM messages. If you set the logger level from the default “WARN” to “INFO” you will get more information in the log. The “DEBUG” level logging is set when you want to see the SECS/GEM messages as well as SECS events, including connection events, in the log.

Here is a summary of these logging levels:

WARN (or warn): This logs just the incoming and outgoing SECS/GEM messages and is the default logging level

INFO (or info): This logs the messages as well as the bytes in the messages

DEBUG (or debug): This logs the messages, bytes, and events. This is the highest level of logging and is usually needed to understand why the tool and host are having connection issues.

To change from the default WARN level to DEBUG, change the line in the log4j.xml file which looks like

    <logger name="com.ergotech.transsecs.secs.Log4JLogger" additivity="false">
      <level value="WARN"/> 
	  <appender-ref ref="SECSLogFile" />
     </logger>

to

    <logger name="com.ergotech.transsecs.secs.Log4JLogger" additivity="false">
      <level value="DEBUG"/> 
	  <appender-ref ref="SECSLogFile" />
     </logger>

Below is a typical log4j.xml file with defaults. The “appenders” are what the logger (java classes) logs to (could be files, console, etc.).

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration debug="false"
 
  xmlns:log4j='http://jakarta.apache.org/log4j/'>
 
 	<appender name="rootlog" class="org.apache.log4j.ConsoleAppender">
	 <param name="Target" value="System.err"/>
	   <layout class="org.apache.log4j.PatternLayout">
		  <param name="ConversionPattern"  value="[root]%-5p: %d{ISO8601} %m %l%n" />
	    </layout>
	</appender>
 
   <appender name="SECSLogFile" class="org.apache.log4j.RollingFileAppender">
	    <param name="append" value="true" />
	    <param name="maxFileSize" value="10MB" />
	    <param name="maxBackupIndex" value="5" />
	    <param name="file" value="SECSMessages.log" />
	    <layout class="org.apache.log4j.PatternLayout">
		  <param name="ConversionPattern"  value="%d{ISO8601} %m %n" />
	    </layout>
	</appender>
 
 
	 <appender name="SECSMatchingLogFile" class="org.apache.log4j.RollingFileAppender">
	    <param name="append" value="false" />
	    <param name="maxFileSize" value="10MB" />
	    <param name="maxBackupIndex" value="5" />
	    <param name="file" value="MessageMatching.log" />
	    <layout class="org.apache.log4j.PatternLayout">
		  <param name="ConversionPattern"  value="%d{ISO8601} %m %n" />
	    </layout>
	</appender>
 
	<appender name="rootlog" class="org.apache.log4j.ConsoleAppender">
	  <param name="Target" value="System.err"/>
	    <layout class="org.apache.log4j.PatternLayout">
		  <param name="ConversionPattern"  value="[root]%-5p: %d{ISO8601} %m %l%n" />
	    </layout>
	</appender>
 
 
<!--
WARN provides messages
INFO provides bytes and messages
DEBUG provides events, bytes and messages
-->
    <logger name="com.ergotech.transsecs.secs.Log4JLogger" additivity="false">
      <level value="WARN"/> 
	  <appender-ref ref="SECSLogFile" />
     </logger>
 
<!--
Change the level to "INFO" to see the logic of matching messages, "OFF" turns off this feature
-->	
     <logger name="info.com.ergotech.transsecs.secs.VIBMessageBean" additivity="false">
      <level value="off"/> 
	  <appender-ref ref="SECSMatchingLogFile" />
     </logger>
 
 
	<root>
	    <level value="INFO" />
		<appender-ref ref="SECSLogFile" />
	</root>
 
</log4j:configuration>