OwlStartRepositoryServer

To start a server that will act as a repository of versioned ontologies, use the org.hypergraphdb.app.owl.versioning.distributed.VDHGDBOntologyServer class. If you have a clone of the git repo of the project, you can do this with:

mvn exec:java -Dexec.mainClass="org.hypergraphdb.app.owl.versioning.distributed.VDHGDBOntologyServer" config.json /var/db/owlrepo

The first command like is a JSON configuration file that tells how to connect to the P2P network. The second is the directory where the HyperGraphDB instance storing the ontologies is. It looks like this:

{
    "interfaceType"	: "org.hypergraphdb.peer.xmpp.XMPPPeerInterface",
    "peerName"	: "OntologyServer",
    "bootstrap" : [ {"class" : "org.hypergraphdb.peer.bootstrap.AffirmIdentityBootstrap", "config" : {}},
                    {"class" : "org.hypergraphdb.peer.bootstrap.CACTBootstrap", "config" : {}}
                    ],
    "interfaceConfig" :
    {
        "user" : <the XMPP P2P username>,
        "password" : <the password to the XMPP server> ,
        "serverUrl"	: <the hostname of the XMPP server, e.g. evalhalla.com>,
        "room" : the URL of the XMPP chat room where peers reside
        "autoRegister" : false,
        "ignoreRoster" : false
    }
}

For more information on how to setup your own P2P server and configure HyperGraphDB peers, please see https://github.com/hypergraphdb/hypergraphdb/wiki/ConfigurationXMPP.

The database directory does not have to be created in advance. If it is not present, it will be automatically created and initialized to store OWL ontologies. Once the server was started, other peers, including the ProtegeOWL plugin can connect to it to perform versioning operations such as clone, push etc.