WicketLog4JView Files

7.10.2013: Added a sample log4j configuration (log4j.xml) and three sample log files for testing: an xml file, a tab separated file, a file which can be parsed with regular expressions. WicketLog4J1.4 uses wicket 1.4. WicketLog4JView uses wicket 6.

---------------

For support mail to:  develop(at)cschrall.de
Thank you for any feedback!

Log4J is enabled on allmost all application and web servers.
Nevertheless the application and web server do not provide a reasonable GUI for viewing and filtering Log4J traces.

WicketLog4J is a simple log viewer which displays log4j files (which are in xml format) in a structured way.
It also can be used for "live tracing". This means that traces, which are produced by the application server
can be displayed immedeatly (without saving to disk).
WicketLog4J offers filter mechanisms (log level, date, keyword)

WicketLog4J is a simple war file, which does not need any configuration and can be deployed to any java webserver. 
Hence you can access the application using a standard browser.
Settings can be preselected in the URL (hence they are bookmarkable)

====================================

Log4J is used by almost every developer in the JavaEE community, but in most cases unstructured log files are produced.
They are analysed with text editors, which is a painfull task.
This viewer is a simple .war file 
(tested on JBoss, Weblogic, Tomcat but should be suitable for all webservers/application servers), 
which displays the log input in a structured way on an HTML page and allows filtering.

Configuration page contains the form for entering the log path 
The logview page contains a table showing all entries, elements for filtering, buttons for 'refresh' and 'filter'.
A tree showing all available loggers can be opened from here.
For exceptions the exception stacktrace window can be opened.

Installation and configuration

The slf4j-api.jar must be available in the class path of the webserver.
Just deploy the .war file to JBoss ( e.g. copy it to /jboss/server/default/deploy).
jboss-log4j.xml (or jboss-logging-xml) must contain an appender with XMLLayout

Example:
   <appender name="XMLFILE" class="org.jboss.logging.appender.RollingFileAppender">
     <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
     <param name="File" value="${jboss.server.log.dir}/server.xml"/>
     <param name="Append" value="false"/>
     <param name="MaxFileSize" value="3000KB"/>
     <param name="MaxBackupIndex" value="10"/>
    <layout class="org.apache.log4j.xml.XMLLayout">
    </layout>
   </appender>


If you want to use live tracing you must have a free port and the log configuration must contain an appender like this

   <appender name="WEBVIEWERAPPENDER" class="org.apache.log4j.net.SocketAppender">
    <param name="remoteHost" value="localhost"/>
    <param name="port" value="8989"/>
    <param name="reconnectionDelay" value="10000"/>
    <param name="threshold" value="INFO"/>
   </appender>

   <root>
      <appender-ref ref="CONSOLE"/>
      <appender-ref ref="WEBVIEWERAPPENDER"/>
   </root>




Security and password:
User: test  Password: test.
(this can be changed by editing the web.xml!!!)