Changes

Each BaseX can be [[Startup]] mode can be launched with its own Start Script which can |started in turn be used with its own range of [[Command-Line Optionsdifferent ways]]. The BaseX [https://basex.org/download/ Windows and ZIP distributions] readily include all Start Scriptsvarious start scripts, which are presented in the following, and which can also be maintained separately.

* We recommend you to manually add the {{Code|bin}} directory of your BaseX directory instance to the [https://en.wikipedia.org/wiki/PATH_(variable) PATH variable] of your environment.* If you use the Windows installer, that’s done automatically.

* The Windows installer automatically adds the project’s {{Code|bin}} directory to your path environment.* If you work are compiling the source code with [[Maven]], you can directly run launch BaseX via the scripts in the [https://github.com/BaseXdb/basex/tree/master/basex-core/etc basex-core/etc] and [https://github.com/BaseXdb/basex/tree/master/basex-api/etc basex-api/etc] sub-directories subdirectories of the project.

If BaseX terminates with an {{Code|Out of Memory}} or {{Code|Java heap space}} error, you can assign more RAM via the {{Code|-Xmx}} flag (see below). The A conservative value that was chosen in our distributions ensures to ensure that BaseX will also run on 32 bit older JVMs.

The Use the following scripts to launch the standalone version of BaseX:

The scripts for starting the HTTP server, which gives access to the running [[RESTWeb Application|Web Applications]], [[RESTXQ]] and [[WebDAV]] services, can be found below:

The BaseX [https://basex.org/download/ Windows and ZIP distributions] readily include the following Start Scriptsstart scripts:

For the BaseX HTTP and database server, there are also additional stop scripts are available: