Database Reference
In-Depth Information
$EXIST_HOME/webapp/WEB-INF/controller-config.xml
This tells eXist what to do when a request with a certain URL is entered. There's
more information in
“The controller-config.xml Configuration File” on page 206
.
$EXIST_HOME/webapp/WEB-INF/data/
This is the default location for eXist's database (unless you specified somewhere
else during the installation process).
If you peek inside this directory, you'll find underneath the
fs
subdirectory all the
non-XML files stored in the database. However, your XML files are not there;
they have seemingly disappeared. Don't despair: they're absorbed into the
*.dbx
files you see in the root of the database directory. You'll find more information
about this in
“Help: Where Is My XML?” on page 87
.
You might be tempted to change the non-XML content
underneath the
fs
subdirectory directly.
Don't do this
. It will
ruin the database's internal administration. Use only the nor‐
mal mechanisms for this, like WebDAV, the dashboard, or the
Java Admin Client tool.
$EXIST_HOME/webapp/WEB-INF/logs/
Here you'll find several logfiles that can help you find out what's going on under‐
neath eXist's hood.
The Java Admin Client
Through the eXist controller application (visible in the system tray), you can start the
Java Admin Client
. This pops up a small and, admittedly, rather old-fashioned-
looking program. It allows you to do maintenance work on the database like backups
and restores, imports and exports, checking and setting properties, and creating col‐
lections.
Figure 2-4
shows how it looks on a freshly installed database.
The eXist Client tool is a standard GUI application, and its functionality speaks for
itself.
Most of this tool's functionality is also present in the new dashboard application, so
there's a good chance you'll never need it. However, there are circumstances in which
it can be useful, such as when you're working on a production server where you don't
want the dashboard to be present.
Search WWH ::
Custom Search