GraphDB-Enterprise Installation

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

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

Changes (4)

View Page History
A suitable application server must be installed. The examples in this guide assume [Apache Tomcat|http://tomcat.apache.org/] 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|http://www.ontotext.com/products/ontotext-graphdb/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|http://www.openrdf.org/] or higher is required for the longer installation. The examples in this guide use version 2.7.8.
Furthermore, a [Java Development Kit (JDK)|http://www.oracle.com/technetwork/java/javase/downloads/index.html] 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.