Installing OntoBroker under Microsoft Windows
The installation of OntoBroker is fast and easy. After starting the installation file, the installation process is initiated. In the following, you have to confirm the prompts in the windows that appear. Before installing OntoBroker, you have to check whether your computer meets the system requirements for the recommended configuration. Before installing OntoBroker, close all of the programs and applications on the computer. The installation wizard will guide you through the further installation process. During the installation, you will be asked for the KeyFile which should be stored in the OntoBroker installation folder.
NOTE: Keyfiles for different versions can be put into the same directory
Installing OntoBroker under Linux
Before installing OntoBroker make sure you have an appropriate Java runtime environment installed (OntoBroker requires Java 1.6). Then:
Unzip the OntoBroker distribution into a folder (e.g. /usr/shared/ontoprise/ontobroker),
Copy the license key file (ob_prof.key.xml) into the same folder.
The setup process is now finished. You should be able to start OntoBroker using the commandline utilities.
NOTE: The installer automatically installs the correct runtime dependending on the target machine's bit-version.
- Windows 7 or higher
- Windows Server 2016 or higher
- Linux (tested on SUSE, Debian and Ubuntu) Java platforms: Sun/OpenJDK Java 6 and later
- Minimum: 2 core, 2 GHz and better, 4 GB RAM, 500 MB free hard disk space
- Recommended: Quad core, 2.4 GHz and better, 8 GB RAM, 500 MB free hard disk space
Important Note About the Key File
When installing the keyfile, during the installation process you must make sure that the keyfile has the original name given by semafora and the original extension.
From the Windows Start menu select: Start -> All Programs -> OntoStudio Version -> Uninstall.
Remove legacy OntoStudio with the help of the uninstall wizard.
Click on Next.
The uninstall wizard guides you through the further uninstall process.
- Click on Uninstall.
All of the OntoStudio components are removed.
- Click on Accept.
- Click on OK.
The deinstallation starts.
- Click on Close.
The deinstallation is finished and the OntoStudio software is not on your computer anymore.The window closes.
Ontology / Logic Languages
OntoBroker supports multiple ontology languages:
OntoBroker provides native support for RDF/RDFS and OWL. This makes OntoBroker applicable for a wide range of semantic applications and scenarios. It is possible to use OntoBroker as a high-performance RDF triple store (or quad store), for typical OWL reasoning tasks (e.g. consistency checks) for conjunctive queries against an OWL ontology, for high performance ObjectLogic reasoning for evaluating and debugging rules. It is possible to use different storage systems with all ontology languages. This means that you can use the persistent storage H2 for storing OWL axioms, RDF triples and ObjectLogic facts and rules.
You can use SPARQL (W3C standard for RDF query languages) for executing queries in combination with all other ontology languages (see the "Query Languages" chapter for further details). OntoBroker also provides a powerful Java-based API which can be used to open, modify and store ontologies, convert ontology languages (e.g. from OWL to ObjectLogic) and to execute queries against an ontology. This API was designed to be independent from the ontology language. This makes it easy to access OntoBroker from your own applications and to write applications which can deal with all ontology languages.
The ontology language can be set in the OntoConfig.prp configuration file of the OntoBroker server:
OntologyLanguage = ObjectLogic
OntologyLanguage = RDF
OntologyLanguage = OWL
Using Ontobroker as RDF Triple Store
OntoBroker RDF is an RDF triple store, query and inferencing engine. It is well integrated into
the general OntoBroker suite, allowing close interaction between the other supported
knowledge representation formats OWL and ObjectLogic. Staying close to the official
Semantic Web standards like RDF, RDF Schema, and SPARQL is one of the primary design
goals. However, the implementation on a horn logic-based model imposes some restrictions
in standard compliance -- and some unique features too. This section will give a pragmatic
overview of OntoBroker RDF, focusing on RDF-related options and features. For more
general issues, see the provided locations in the main OntoBroker documentation.