CODEWITHSUNDEEP
javatomcat
nos
nos

Reputation: 229344

Where/how to store persistent data with tomcat?

Where should I store persistent files in a Tomcat web app ?

Upvotes: 12

Views: 12282

Answers (5)

yossis
yossis

Reputation: 1273

Storing the files in a webapp directory under the home directory of the user running Tomcat is a good and convenient option. It is outside of Tomcat, which means it will survive redeployment, and it is usually a writable directory (because it is created under the users' home dir). But it is always a good idea to allow overriding the location of such directory via system property.

Upvotes: 4

mhaller
mhaller

Reputation: 14222

Generally, this would go to the database. But since the OP insists on not using a database, I'd try a different approach:

  • Filesystem path which is known: ${user.home}/.myapp. Applications sometimes use this for e.g. search indices which can be recalculated based on data in the database. Might be okay for your use case to use the user's home.
  • Store the configurable filesystem path in a configuration repository such as the database or perhaps Java Preferences (if you don't like to use servlet init params). Commercial applications such as Atlassian JIRA use a configurable (but absolute) filesystem path where they store issue attachments. If they don't know a better way, i don't know who does :)

Upvotes: 1

Pascal Thivent
Pascal Thivent

Reputation: 570595

Answering the title of the question, what about using a database, a DataSource and JDNI? Even in a web only context, writing to files using java.io is not really recommended because of concurrency, threading, security, clustering, portability issues. Some of these problems can be "workarounded" but still, this is not really a best practice. The standard approach is to use a database and I'd suggest to reconsider this option, throwing "file-based" lightweight database like HSQLBD or JavaDB into the mix.

(EDIT: For an unknown reason, database is not an option. Using JNDI or context parameters or init parameters to pass an absolute path - which are the less worse options IMHO - is excluded too. For a relative path, maybe look at user.home or user.dir then - or any other system property that you could pass on the command line. I don't like it, I wouldn't do it, and this doesn't solve the issues previously mentioned, but it's your choice after all.)

Upvotes: 5

Andy Gherna
Andy Gherna

Reputation: 2165

Our team does this a lot. A general rule we follow is outside the web app and outside Tomcat.

Our sysadmin set up a directory on our server that the tomcat user has rw permissions to (e.g. /var/tomcat/persist). We have a built a directory structure under this that tomcat uses to store files, read app-specific init files, etc.

If you don't want to use an absolute path in your init-params for your servlet, consider setting a system property when tomcat is started up. The good thing about that is every application running under tomcat will have access to it. The bad thing about that is every application running under tomcat will have access to it. You could set a property named base.persist.dir and build subdirectories for each application underneath it. We set system properties in the setenv.sh script in the bin/ directory under the CATALINA_OPTS environment variable.

Upvotes: 10

Suppressingfire
Suppressingfire

Reputation: 3286

I generally would suggest to use a database to store persistent data and expose it via a DataSource.

If you don't want to do that, I guess you could consider using the "user.home" system property (I have seen this used in a few circumstances). But... there are no guarantees that your servlet will be run with permission to write access unless you configure that yourself.

Upvotes: 0

Related Questions