The information contained in this section should be sufficient to get started with GraphDB-Enterprise, i.e. to install and configure the software on both master and worker nodes.
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 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:
The repackaged openrdf-sesame.war Web application must be deployed to all cluster nodes. The openrdf-workbench.war Web application need only to be deployed on a single machine and this does not have to be a machine taking part in the cluster. However, for simplicity, it is more straightforward to deploy the workbench to all nodes simultaneously with the Sesame server.
After deployment, GraphDB-Enterprise master and worker nodes can be created using the workbench application as follows:
The last steps to get the cluster connected and running are as follows:
To set up additional master nodes, please refer to the "Longer install" section below.
This longer install process should be used when a different or modified version of Sesame is being used. In this case, all the GraphDB-Enterprise files need to be installed alongside Sesame in a step-by-step process as follows.
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 6.
No part of this guide is intended to supersede the documentation published with the 3rd party software components and the reader is strongly advised to familiarise himself/herself with them.
Assuming that an instance of Tomcat is available on all cluster nodes, the installation proceeds as follows:
One thing to remember is that although workers behave like a standard GraphDB-SE instance, worker nodes need to expose a cluster management end-point (when necessary) using a port number that is given by the Tomcat port number plus 10, i.e. usually 8080 + 10 = 8090. You must make sure that no other software is listening on this port number.
Install worker nodes
Installation of worker nodes proceeds exactly the same as when installing GraphDB-SE using the Sesame HTTP server, see the GraphDB-SE installation section. However, there are several important differences:
Install master node
Setting additional master nodes
If you want to setup several master nodes for the cluster, then before bringing each master online, configure its config file "cluster.properties" properly:
After that, continue with tomcat restart and Sesame console:
At this point the master node is running, but the cluster it manages has no attached worker nodes.
Connect the worker nodes
As soon as one or more workers have been attached, the cluster can now be used as a read-write repository, notifications and statistics can be monitored through the JMX client.
Put the cluster in to read-write mode
In GraphDB 6 all masters are always read-write, there is no additional step to put the master in RW mode, as in previous versions.
Skip to end of metadata Go to start of metadata