Download logFaces User Manual

Copyright ©2009-2015 Moonlit Software Ltd, All rights reserved
2.5 Server directory tree
Once installed and ran for the first time, the server will explode its default configuration and you will
find several new folders under installation directory. The table below is a brief summary of folders
and their purpose. Normally you won't need all the technical details, but it's a good idea to familiarize
yourself with some internals, some of the files and directories are referred to throughout this manual.
Path
Updated with version increments
/.install4j
yes
/bin
Description
Visible only on Windows, created by installers.
binaries only
Binaries for bootstrapping the server, content is OS
dependent
/admin
yes
Admin web application and resources
/conf
no
Server configuration files
/db
no
Relevant only for embedded database, contains actual
embedded database storage files
/doc
yes
Holds release notes and other documents
/legal
no
Holds end user license agreements
/lib
yes
Binary distribution libraries and dependencies
/log
no
Holds server internal logs
/overflow
no
Contains overflow files when server overloads
/dropzone
no
Location for manual log data imports
/temp
no
Temporally files, cleared on each server restart
Note that folders which are created and updated by the server (those which are not part of version
updates), can be located elsewhere and not necessarily under installation directory. We call these
folders artifacts and sometimes it's a good idea to keep them separately, for example for the backup
purposes or switching from one setup to another. By default all artifacts reside under installation
directory, this is the argument for running the server, and you can change it in /bin/lfs.conf like this:
wrapper.app.parameter.1=HOME
HOME can be an empty folder; when you run the server for the first time, it will create all default
artifacts automatically. Alternatively, you can move other artifacts into HOME or point the above
parameter to another location with different artifacts in there - this is what we often do during tests.
Once again, all this is not required, in most cases the default directory structure is good for nearly all
circumstances.
4