GraphDB-Enterprise Installation

compared with
Current by Dimitar Manov
on Nov 05, 2014 18:25.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (9)

View Page History
h1. Easy install

GraphDB is normally built against the latest version of the [Aduna OpenRDF Sesame framework|]. If using GraphDB with this version then the easiest way to deploy an a GraphDB server instance is to copy the re-packaged Sesame Web applications (.war files) in to the Tomcat {{webapps}} directory. They can be found in the {{sesame_owlim}} directory in the GraphDB distribution ZIP file. These Web applications have been modified as follows:

* *openrdf-sesame.war:* The Sesame server application. All GraphDB-Enterprise and 3{^}rd^ party jar files have been added to this package, so that it can be used immediately after deployment.
After deployment, GraphDB-Enterprise master and worker nodes can be created using the workbench application as follows:
* Start a browser and go to the Workbench Web application using a URL of this form: [http://localhost:8080/openrdf-workbench/] \- substituting {{localhost}} and the {{8080}} port number as appropriate.
* Click 'change server', if necessary, to select a Sesame server instance, if it is running on a different machine. The server URL will be of this form: [http://localhost:8080/openrdf-sesame].
* After selecting a server, click 'New repository'.
* Select 'GraphDB-Enterprise worker node' or 'GraphDB-Enterprise master node' from the drop-down list and enter the repository ID and description. Then click 'next'.
* For master nodes, there is nothing more to be specified, so just click 'create'. For worker nodes, fill in the fields as required (referring to the owlim-configurator spreadsheet as necessary) and click 'create'. You can specify a worker node license file at this step, if you have one, but note that you must use forward slashes ('/') as file separators (even on Windows).
* A message is displayed, which gives details on the new repository and this should also appear in the repository list (click 'repositories' to see this).

All worker nodes that take part in the same cluster (connect to the same master), must be configured identically (apart from the repository name and label).

A suitable application server must be installed. The examples in this guide assume [Apache Tomcat|] version 6.x is used. Importantly, the user must have sufficient privileges to write to the Tomcat {{webapps}} directory and to stop and start the Tomcat daemon.

A [GraphDB-Enterprise|] distribution is required. This is published as a zip file. The examples in this guide use version 5.6.
The [Aduna OpenRDF Sesame framework version 2.7|] or higher is required for the longer installation. The examples in this guide use version 2.7.8.
Furthermore, a [Java Development Kit (JDK)|] version 1.6 or later is necessary since this contains the {{jconsole}} management application.

* Ensure that the replication cluster is loaded by the HTTP server by starting the openrdf workbench and selecting it. To do this open a browser and connect to the workbench using this url (or similar): {code}http://localhost:8080/openrdf-workbench/{code}
* Use the workbench to select the correct HTTP server where the replication cluster instance is running. Then choose the replication cluster repository instance. This will have show the repository ID as entered when the repository was created.
* It will likely be necessary to 'force' the repository to load and initialise by clicking on the *query* button. This will cause an exception to be displayed exception, containing the text 'No available worker nodes'.
* Start a JMX client, e.g. {{jconsole}} from the Java Software Development Kit.
* Connect to the Tomcat process using the port number selected above. When using a non-standard port number (as in this case), connect as a remote process using localhost:<port_number>. In this example enter the following: {code}localhost:8089{code}
h2. Put the cluster in to read-write mode

In 5.6 GraphDB 6 all masters are always read-write, there is no additional step to put the master in RW mode, as in previous versions.