There is no option to upgrade from prior version to version 4.
1.Install the war file
a. Deploy the LogViewer.war file in your application server.
b. Follow the normal deployment steps for your application server. If you are using WebSphere, then you much make sure that you change the Context Root to /LogViewer. Weblogic and Tomcat should default to that Context Root.
c. Start application
2.Set Security
a. Access url: \http://server[:port]/LogViewer/admin/security.jsp
b. Select desired security model and click Update
c. Stop and then restart the LogViewer application in your application server.
d. If you selected SOME security, go into your application server and create a role called "LogAdmin". Then add users to that role.
e. If you selected FULL secuirty, go into your application server and create two roles: "LogUser" and "LogAdmin". Then for every user that will be access the application, add them to the "LogUser" role. Plus for those users that will also be accessing the administration screens, add them also to the "LogAdmin" role.
3.Configure Application
a. Access url: \http://server[:port]/LogViewer
b. Log in if prompted
c. This will display a message that the system is not configured. Click on the Configuration button.
d. If you want you can change the title that will be display when the application is accessed. This is helpful if you have a Prod, Test, Dev, etc instances.
e. For each log file, enter a friendly name and the full UNC path and file name of the log file. If the file name has the current date in it, you can replace where the date goes in the file name with "[yyyy-MM-dd]". Between the brackets you use java's simple date format to define the date format.
f. When done, click save.
4.Testing Installation
a. If you are still on the configuration screen, click Exit. Otherwise access url: \http://server[:port]/LogViewer
b. Select a log file to view and click Load/Reload. Make sure each log file works. If not go back into the configuration screen and correct the UNC.