analyzeStorage

 Result: "Storage analyzed in 42 ms.W

busy

clear

commands

delete

The command del has been removed since Ontobroker 6.0. Instead, please use the delete command which has a richer syntax.

Here is an example of how to use delete instead of del.

Old syntax in OntoBroker 5.3

del otto[age->18].  // syntax from OB 5.3, invalid in OntoBroker 6.1

In OntoBroker 6.1 the corresponding command is

delete otto[name->"Otto"].

The delete command is used to remove facts and rules from an ontology. Its syntax is very similar to the insert syntax.

Example with single fact:

:- module <http://yourcompany.com/ontology1>.

delete Person[name *=> _string].

Example with multiple facts and rules:

:- module <http://yourcompany.com/ontology1>.

delete {

 Person[name *=> _string, age {0:1} *=> _integer].

 otto:Person[name -> "Otto Waalkers"].

 fritz[name -> "Fritz", age->9].

 @{rule1} ?X:Child :- ?X:Person, ?X.age < 18 .

}

Example with where clause:

delete {p(?X,?Y),q(?X),q(?Y).} where {@{options[inferOff]} ?- p(?Y,?X).}

Also note that it is allowed to specify query options (since OB 6.0 Build 382)

delete clauses

This command can be used to delete clauses (rules, queries, constraints) by their label.

For example to delete the rule with the id r1 and the query with the id q1:

delete clauses r1,q1

dump

Writes a full dump of the extensional and the intensional database (internal representation). The target folder is the so called dump folder where OntoBroker is installed.

exportAllModules

Writes a dump of all modules to the files system. The target folder is the folder where OntoBroker is installed.

The command "exportAllModules" supports additional options:

NOTE: If, in the command line, you specify a directory to load the ontologies from like "ontobroker -obl decrypt:v1:dir", the decrypt handler first of all checks if the file is encrypted. Example: ontobroker -obl decrypt:v1:C:\ontologies

Example

Save modules <http://yourcompany.com#ontology1> to file c:\data\onto1.obl with sorted option

save <http://yourcompany.com#ontology1> to "c:\\data\\onto1.obl",sort.

Save modules <http://yourcompany.com#ontology1> to file c:\data\onto1.obl with sort and encrypt option

save <http://yourcompany.com#ontology1> to "c:\\data\\onto1.obl",sort,encrypt.

Export all modules sorted

exportAllModules sort.

Export all modules sorted and encrypted

exportAllModules sort,encrypt.

NOTE: If "SerializerEscapeNewLines = on" is set in the OntoConfig.prp, new line characters in string constants are escaped on serialization (i.e. on commands like "exportAllModules" and "save")

This switch can be set in OntoConfig.prp via:

<SerializerEscapeNewLines> = <on|off>

generateDynamicSvc

There are now two commands for dynamic web services:

generateDynamicSvc "path-to-specification-module.obl".

The string argument must be a valid URL or path to the specification module file.

and

deleteDynamicSvc <module>

Here <module> is the module term of the specification module.

NOTE: OntoBroker must have been started with the "-webservice" option. The command is only available for Objectlogic

Example

:- module echo.

 

:- prefix in = "http://schema.ontoprise.com/dynamic-svc/in#".

:- prefix out = "http://schema.ontoprise.com/dynamic-svc/out#".

:- prefix meta = "http://schema.ontoprise.com/dynamic-svc/meta#".

 

// Spec for Input

in#Parameters[in#message {1:1} *=> _string].

 

// Spec for Output

out#Results[out#echo {0:1} *=> _string].

 

// Generation of Output

theResults:out#Results.

theResults[out#echo -> ?X] :- ?P:in#Parameters[in#message->?X].

h2 backup <output-name>

Caution – All files like "d:\\backup\\mybackup.*" are deleted during the copy action to prevent the possible mixing of old and new temporary database files.

NOTE: The command "h2backup" is only available if OntoBroker is running with H2 as storage.

info

Example output

------------------------------------------------------

IDB

------------------------------------------------------

[ ] program contains aggregation cycles (not allowed)

[ ] program is not bottomup evaluable (could be bad for performance)

[ ] program is not stratified and must be evaluated in wellfounded mode (bad for performance)

[ ] program contains rules with cross products (bad for performance)

[ ] program contains rules which apply aggregations incorrectly (not allowed)

# user rules: 0

# internal rules (including standard axioms): 48

# rules with negations: 3

# rules with aggregations: 0

# rules with connectors: 0

# rules with other builtins: 4

------------------------------------------------------

EDB: RAM.Packed (RAM.Packed)

# of tables: 1

------------------------------------------------------

1 tuples in obl:intern:module/1

...

insert

The command <add> has been removed since Ontobroker 6.0. Please use the insert command which has a richer syntax instead. Here are some examples of how to use insert instead of add.

Old syntax in OntoBroker 5.3:

add otto[name->"Otto"].  // syntax from OB 5.3, invalid in OntoBroker 6.1

add RULE r1: FORALL X p(X) <- q(X).  // syntax from OB 5.3, invalid in OntoBroker 6.1

In OntoBroker 6.1 the corresponding commands are:

insert otto[name->"Otto"].

insert {@{r1} p(?X) :- q(?X).}

The insert command is used to add facts and rules to an ontology. You can add multiple facts or rules with a single command if you use braces {...} around them.

Example with single fact:

:- module <http://yourcompany.com/ontology1>.

insert Person[name *=> _string].

Example with multiple facts and rules:

:- module <http://yourcompany.com/ontology1>.

insert {

 Person[name *=> _string, age {0:1} *=> _integer].

 otto:Person[name -> "Otto Waalkers"].

 fritz[name -> "Fritz", age->9].

 @{rule1} ?X:Child :- ?X:Person, ?X.age < 18 .

}

Note that you can add directives for the module and namespace alias as an header to the command.

You can also generate additional facts by inferencing if you add a where part to the insert statement. In this case, all variable bindings resulting from the query of the where part are replaced in the insert part.

Simple example:

:- module <http://yourcompany.com/ontology1>.

insert { ?X[lovesToys->true]. } where { ?- ?X:Child. }

Assuming that the results of the query ?- ?X:Child are fritz and susan, this example would insert the facts fritz[lovesToys->true] and susan[lovesToys->true].

isalive

kill

modify
With the modify command you can add and remove facts in a single step. As the variable bindings of the where part are used for both insert and delete, this can be quite useful and is easily covered by separate delete and insert commands.
Example:

// increment the age of all age attributes for persons

modify delete { ?P[age->?AGE]. } insert { ?P[age->?NEWAGE]. } where { ?- ?P:Person[age->?AGE], ?NEWAGE=?AGE + 1 .}

query

reload

removeExplanation

shutdown

stopQuery

Check for OWL 2 RL profile

Connector cache clear command

saveSessionSnapshot

loadSessionSnapshot