Difference between revisions of "OntoBase"
Lenyabloko (talk | contribs) (→Installation) |
Lenyabloko (talk | contribs) m (→Installation) |
||
Line 44: | Line 44: | ||
</nowiki></pre> | </nowiki></pre> | ||
− | Note: JDBC driver corresponding to entered URL must be specified in following line of protege.lax file | + | Note: JDBC 4.0 driver corresponding to entered URL must be specified in following line of protege.lax file |
− | <pre><nowiki>lax.class.path=protege.jar;dbdrivers/ojdbc6.jar; | + | <pre><nowiki>lax.class.path=protege.jar; ... ;dbdrivers/ojdbc6.jar; ... </nowiki></pre> |
Revision as of 08:37, March 2, 2008
OntoBase
by Len Yabloko
OntoBase is a plug-in that connects Protege to relational databases. It allows ontologies to be used as views and forms for data entry.
Versions & Compatibility
This section lists available versions of OntoBase.
If you click on the button below to add a new version of OntoBase, you will be asked to define a page title for the new version. Please adhere to the naming convention of OntoBase X.X.X when you define the new page!
Changelog
Version | Changes in this version |
---|---|
OntoBase 3.4.2 | GUI improovements and bug fixes |
OntoBase 3.4.1 | Compatible with Protege 3.4 OWL and RDF backend |
OntoBase 3.4.0 | tested with Protege-Frames 3.4.4 (build 579) |
OntoBase 3.3.7 | Improved user dialog and performance |
OntoBase 3.3.6 | - automatically generate SQL joins |
OntoBase 3.3.5 | -Automatically switching between several connected databases;
-Improved data access performance using separate Java thread; -Automatic synchronization of ontology with source databases upon loading of the project; |
OntoBase 3.3.4 | Support for PostgreSQL added. |
OntoBase 3.3.3 | Support for database engines can now be added/extended |
OntoBase 3.3.2 | full read/write access to Oracle, Microsoft SQL and MySQL |
OntoBase 0.3.3 | see page for more details |
More Details
Description
OntoBase is a plug-in that turns any relational database into ontology, and Protégé - into application container that can be easily programmed and connected to different data sources. It allows Protégé to be used as "Model" and "View" for simple database applications. OntoBase can also be used as “back end” for Protégé in order to store parts of knowledge base which must be shared with other applications. In its current form OntoBase can be simply “snapped on” any relational database to provide access to data, virtually without any programming.
Installation
The ONTOBaseTab can work with "basic" or "full" installation of Protege 3.x, but it requires JDK 1.6. To make sure Protege loads with correct JVM change following line in protege.lax file
lax.nl.current.vm=C:\\Program Files\\Java\\jre1.6.0_04\\bin\\java.exe
1) Extract OntoBase_X.X.X.zip into Protege installation root directory.
2) Open New Project using Protege files(.pont and .pins) or XML file
3) Go to Project->Configure and check ONTOBaseTab box.
4) When OntoBase window appears enter JDBC address of database and click connect button.
Following are some examples of JDBC database URLs:
jdbc:oracle:thin:@machine_name:port_number:instance_name jdbc:mysql://host_name:port/dbname
Note: JDBC 4.0 driver corresponding to entered URL must be specified in following line of protege.lax file
lax.class.path=protege.jar; ... ;dbdrivers/ojdbc6.jar; ...
5) Wait until connection is established and then click on "run" icon.
Note: If import does not start in a few moments or stops before 100%, then you may need to adjust application memory allocation by editing following line in protege.lax file
lax.nl.java.option.java.heap.size.initial=100000000The protege.lax file is located in the root directory of your Protege installation