I was working in Ubuntu platform and most of the time used the "tail -f xxx.log" command to tail the application logs. It also helps the administrator to keep an eye on the happenings at application side. I created a small application to tail the logs to the web UI. So the administrator can see the logs to web UI, even if he does not have the server login credentials.
Environment set up:
1. Install JDK 1.6 in your system or any platform you want.
2. Install Tomcat 6 followed by JDK installation.
3. Deploy the war file to " webapps" of Tomcat installation directory and start the server.(I configured the log path to "/usr/local/tomcat/logs/")
4. Now you can view the demonstration by entering "http://localhost:8080/DWR" to the browser location bar.
2. Install Tomcat 6 followed by JDK installation.
3. Deploy the war file to " webapps" of Tomcat installation directory and start the server.(I configured the log path to "/usr/local/tomcat/logs/")
4. Now you can view the demonstration by entering "http://localhost:8080/DWR" to the browser location bar.
Eclipse setup:
1. To work with the source code, please use eclipse 3.3 or higher version.
2. Download the source code.
3. Create a dynamic web project with name "DWR".
4. Copy the whole content of downloaded "DWR" folder to the workspace "DWR" folder and refresh the workspace.
5. Configure Tomcat to eclipse and add the project to that.
1. To work with the source code, please use eclipse 3.3 or higher version.
2. Download the source code.
3. Create a dynamic web project with name "DWR".
4. Copy the whole content of downloaded "DWR" folder to the workspace "DWR" folder and refresh the workspace.
5. Configure Tomcat to eclipse and add the project to that.
About the application:
The application will be keep listening to the log files and when ever a new line get added to that, the message will be get pushed to the client.
The whole process goes some thing like this.
1. When you start the server, the event engine will get started and will keep creating the event objects when ever there is any update to the log file.
2. Now you can view the demonstration by entering "http://localhost:8080/DWR/" to the browser location bar.
3. When ever there is any update to the log file, the message will be get to the UI.
Shared Items:
1. Source Codes or you can fork at GitHub.
2. War File
3. Java Doc
The application will be keep listening to the log files and when ever a new line get added to that, the message will be get pushed to the client.
The whole process goes some thing like this.
1. When you start the server, the event engine will get started and will keep creating the event objects when ever there is any update to the log file.
2. Now you can view the demonstration by entering "http://localhost:8080/DWR/" to the browser location bar.
3. When ever there is any update to the log file, the message will be get to the UI.
Shared Items:
1. Source Codes or you can fork at GitHub.
2. War File
3. Java Doc