Changes

Various [[Command-Line_Options#HTTP Server|command-line options]] are available to simplify batch processing. The [[Start_Scripts|start script]] can be adjusted for individual purposed purposes (e.g. if the default memory limit is too restrictive).

An instance of the [https://www.eclipse.org/jetty/ Jetty Web Server] will be started, which by default listens to the port {{Code|8984}}. Additionally, the BaseX [[Database Server]] will be started, accessible on port {{Code|1984}}. The command-line output will look something like that (the JSP warning message [http://stackoverflow.com/questions/3521654/missing-jsp-support-in-jetty-or-confusing-log-message can be ignored]):

An instance of the [httpsAfter startup, you can access an HTML welcome page via http://www.eclipse.org/jetty/ Jetty Web Server] will be started, which by default listens to the port {{Code|localhost:8984}}. Additionally, the BaseX database server will be started, accessible on port {{Code|1984}}.

After startup, the HTML welcome page can be accessed via http://localhost:8984. You can adjust the The Jetty logging level can be adjusted by adding the following properties to the start script:

Initial database options Unless BaseX is deployed as servlet, the location of the web application directory can be adjusted via the {{Option|WEBPATH}} option, and compression of HTTP responses can be specified in enabled via the {{CodeOption|web.xmlGZIP}} fileoption. They need to  Further database options can be defined as context parameters and prefixed with in the {{Code|org.basexweb.xml}}file. The most important options for the web application context are as follows:

All options are prefixed with {{Code|org.basex.}}. Local file paths in options may be absolute or relative. If a relative path is specified, its root will be the servlet servlet’s ({{Code|webapp}}) path: