administrator, editor
3
edits
Changes
Jump to navigation
Jump to search
==Getting Started==
====Requirements====
====Concurrent Operations====
==Standalone==
==Graphical User Interface==
==Client/Server==
===Server===
===Client===
==HTTP Server==
To run the HTTP Server, you need to [http://basex.org/products/download/ download] one of the full distributions of BaseX (exe, zip, war), as the JAR version does not include any additionally required libraries. It can then be started as follows(get more information on all [[Command-Line Options#BaseX HTTP Server|Startup Options]]):
[[Category:Beginner]]
fixed broken anchor-link
This article is part of the [[Getting Started]] Guide. It tells you how to get BaseX running.
First of all, [http://basex.org/download download] BaseX from our homepage.
* as standalone application, using the [[#Standalone|Standalone]] mode or the [[#Graphical User Interface|Graphical User Interface]],
* as [[#Client/Server|Client/Server]] application, or
* as [[#Web ApplicationHTTP Server|Web Application]], called from a web server.
It can also be embedded as a library in your own application.
BaseX is platform-independent and runs on any system that provides an implementation of [http://www.java.com Java] (JRE).
Linux (SuSE xxx, Debian, Ubuntu) and OpenBSD (4.x).
If you plan to perform concurrent read and write operations on a single database, you
to be written to is currently opened by another virtual machine.
The [[Standalone Mode]] can be used to execute XQuery expressions or run database commands on command line. It can also be used both for scripting and batch processing your XML data. It can be started as follows (get more information on all [[Command-Line Options#BaseX Standalone|Startup Options]]):
* Run one of the {{Code|[[Start_Scripts#Linux.2FMac:_basex|basex]]}} or {{Code|[[Start Scripts#Windows: basex.bat|basex.bat]]}} scripts.
It is important to remember that the standalone mode does ''not'' interact with the [[#Client/Server|Client/Server]] architecture.
The [[GUI]] is the visual interface to the features of BaseX.
explore your XML data.
It can be started as follows (get more information on all [[Command-Line Options#BaseX GUI|Startup Options]]):
* Double click on the {{Code|BaseX.jar}} file.
Note that the GUI does ''not'' interact with the client/server architecture.
The [[Database Server]] comes into play if BaseX is to be used by
By default, the server listens to the port {{Code|1984}}.
There are several ways of starting and stopping the server
(get more information on all [[Command-Line Options#BaseX Server|Startup Options]]):
* Run one of the {{Code|[[Start_Scripts#Linux.2FMac:_basex|basexserver]]}} or {{Code|[[Start Scripts#Windows: basex.bat|basexserver.bat]]}} scripts. Add the {{Code|stop}} keyword to gracefully shut down the server.
* Execute the following command: {{Code|java -cp BaseX.jar org.basex.BaseXServer}}. Again, the {{Code|stop}} keyword will ensure a graceful shutdown.
* On ''Windows'': Double click on the '''BaseX Server''' icon, which will also start the [[#BaseX HTTP Server|HTTP Server]], or the '''BaseX Server (stop)''' icon.
Pressing {{Code|Ctrl+c}} will close all connections and databases and shut down the server process.
The [[Database Server|BaseX Client]] interface can be used to send
It can be started as follows
(get more information on all [[Command-Line Options#BaseX Client|Startup Options]]):
* Run one of the {{Code|[[Start_Scripts#Linux.2FMac:_basex|basexclient]]}} or {{Code|[[Start Scripts#Windows: basex.bat|basexclient.bat]]}} scripts.
We provide additional clients in various [[Clients|programming languages]].
With the HTTP Server, BaseX can be used as [[Web Application]].
be started, which is accessible on port {{Code|1984}}.
* Run one of the {{Code|[[Start_Scripts#Linux.2FMac:_basexhttp|basexhttp]]}} or {{Code|[[Start Scripts#Windows: basexhttp.bat|basexhttp.bat]]}} scripts. Call the script with the {{Code|stop}} keyword to gracefully shut down the server.
* BaseX can also be deployed as [[Web Application#Servlet Container|web servlet]].
In the first two cases, the command-line output will look similar to the following lines (the JSP warning message [http://stackoverflow.com/questions/3521654/missing-jsp-support-in-jetty-or-confusing-log-message can be ignored]): <pre class="brush:xml">[main] INFO org.eclipse.jetty.server.Server - jetty-8.1.18.v20150929[main] INFO org.eclipse.jetty.webapp.StandardDescriptorProcessor - NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet[main] INFO org.eclipse.jetty.server.AbstractConnector - Started SelectChannelConnector@0.0.0.0:8984HTTP Server was started (port: 8984).</pre> You can adjust the Jetty logging level by adding the following properties to the start script: <pre class="brush:xml">-Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog -D{classref}.LEVEL=DEBUG</pre> After that, you can e. g. open your browser and navigate to the RESTXQ start page http://localhost:8984.
=Changelog=
* Updated: BaseXJAXRX has been replaced with BaseXHTTP
