0

Disclaimer : At the moment, due to lack of a Linux dev/test server, I am currently unable to test this myself. Hence me asking the question here. I will have a Linux box eventually but am currently confined to using Windows.

I am designing a webapp that will run in Tomcat 7 on Windows & Linux.

Supposing on both systems the WAR is deployed in the following locations (respectively)

/opt/Tomcat/webapps/MyApp

C:/opt/Tomcat/webapps/MyApp

The Webapp has a Servlet which needs to process files from the OS file system in the following locations

/work/logs/<logfiles>

C:/work/logs/<logfiles>

On Windows I can specify C:/work/logs and the Servlet knows to pick up this absolute path and it works fine. I suspect because the C: at the start. I know this because I have tested this.

My real question is...

On Linux, in the absence of a drive letter, if I ask it to look in /work/logs will it try to look at a relative path :

/opt/Tomcat/webapps/MyApp/work/logs

or will it look in the file system (/work/logs) as I'd like it to?

I'm asking this now because it will ultimately affect the overall design.

thonnor
  • 1,206
  • 2
  • 14
  • 28

2 Answers2

2

Leading slash in Linux means "absolute path", so you can be sure that if you use path like /work/logs/<something> it will understand it as an absolute path.

BTW if you use the same path in Windows it will work and use current disk, i.e. if tomcat's working directory is on C: it will use C: drive, however if tomcat is running on D: this drive will be used.

AlexR
  • 114,158
  • 16
  • 130
  • 208
  • Thanks Alex, this actually is a better answer than I'd hoped for. I am going to try out the /work/log path on Windows now, which will ultimately mean even more portability and less config :) – thonnor Dec 11 '14 at 13:15
  • Just tested this out on a Windows Server and would you believe that /work/logs/20141211.log found this C:/work/logs/20141211.log - Thanks Alex – thonnor Dec 11 '14 at 14:40
1

I can recommend using CATALINA_HOME environment variable to find a folder in which you place your config. For my projects I have the following structure:

$CATALINA_HOME/appconfig/   <-- config
$CATALINA_HOME/webapps/somewar.war     <-- your webapps

Inside appconfig I will place a somewar.properties which functions as the configuration for that server. (I also place log4j.properties, and any special certificates / other things that are specific to the server instance you run on, but I try to keep it to a minimum) As there will always be a CATALINA_HOME set for your project it is reusable.

inside the somewar.properties I would then list

work.path=/work/logs

Using /work/logs will work on both linux and windows as @AlexR mentions (in his much more to the point answer) but you can get into trouble as on linux you would need root access to be allowed to create the /work folder. It depends on who is managing the server and how strict they are. I prefer the configuration solution so if you end up working on a machine that won't let you use a certain location, you can switch. Ofcourse you do need to be allowed to write inside CATALINA_HOME ;)

Joeblade
  • 1,735
  • 14
  • 22
  • Thanks Joe, I've got a config file in place similar to how you suggest. The paths I mention are under the control of "us" but will definitely be referred to via a properties file in case they should change. Nothing is hard-coded (where possible anyway) – thonnor Dec 11 '14 at 13:23