Changes

Jump to navigation Jump to search
1 byte added ,  15:17, 19 March 2012
m
In order to deploy BaseX HTTP Services in a servlet container, one needs to download the WAR distribution of BaseX from the [http://basex.org/products/download/all-downloads download site]. The downloaded WAR file can be then deployed following the instructions of the corresponding servlet container ([http://docs.codehaus.org/display/JETTY/WebAppDeployer jetty], [http://tomcat.apache.org/tomcat-6.0-doc/deployer-howto.html tomcat]).
 
==Servlet Container Configuration==
 
Configuring port, context path, etc. can be done following the corresponding instructions of the used servlet container.
==Database Access==
<br/>
<b>Note:</b> when the web application stores data in the local file system of the servlet container, then by default it will use a separate directory as home directory. This is because, in many production environments, the servlet container runs as a dedicated user without a {{Mono|$HOME}} directory. However BaseX needs to store somewhere it's settings and data. This is why, even when running a servlet container with a normal user (i.e. one which has a {{Mono|$HOME}} directory), the web application will not use by the default the settings stored in {{Mono|$HOME/.basex}} and will have a different set (or empty set) of databases than the one in the case of the standalone HTTP server. However, this behavior can be changed by manually setting the BaseX home directory to {{Mono|$HOME}}, in which case the web application will use the same databases as in the case of the standalone server.
 
==Servlet Container Configuration==
Configuring port, context path, etc. can be done following the corresponding instructions of the used servlet container.
==Configuring Available Services==
administrator, Bureaucrats, editor, reviewer, Administrators
98

edits

Navigation menu