Installing OntoWiki on Windows With Virtuoso
Recently I’ve been experimenting with Semantic Web techonogies. Currently I’m trying to choose tools for editing the ontology and more importantly instances. There are a number of tools, both commercial and free including my favourites: Protégé, NeON toolkit or Top Braid Composer. Each of those have some problem. NeON is nice but desktop only, Top Braid is not free and Protégé is very complex. Not to mention it comes in versions 3.x and 4.x with different set of functions which only makes the confusion grow…
In my search I have found OntoWiki. It is web-based, seems user-friendly and it’s recommended backend is Virtuoso, which I chose for it is Open Source and presumably mature and feature-rich. There is a walkthrough on setting up OntoWiki with Virtuoso, which I followed. Unfortunately things don’t always go right. Below are the problems I encountered and solutions which helped.
Problem 1: Setting up ODBC
My server is running Windows 2008 64bit. for now I have installed Virtuoso trial using the msi package available for download from OpenLink’s website. During installation it automatically sets up a System DSN:
There is a problem however. When I ran the test php script instead of graphs listed I got an error saying:
To resolve this a DSN must be created using 32-bit version of obdcad32.exe, which sits in c:\windows\sysWOW64. There is a problem however: installing 64-bit Virtuoso package does not install 32-bti driver. To get those you must install the Connectivity Suite available as a free download from OpenLink’s website. Then run odbcad32.exe to create a System DSN choosing OpenLink virtuoso driver. Now the php test script should work. Or should it?
Problem 2: Unexpected T_PAAMAYIM_NEKUDOTAYIM
I’m not a PHP developer and so seeing the above for the first in my life was pretty confusing. All it means is “double colon”. The problem comes from a file virtuoso.php,where it says:
Numerous people on the web suggest that instead of the double colon the arrow (->) should be used to access a member on this variable. However this was not the case. ERFURT_CACHE_NO_HIT is a constant field and only changing the above to a static call on the class resolved this issue:
1 2 3
I have filed an issue in Erfurt framework git repository.
Problem 3: Zend_Config_Ini::urlBase
Ok so finally I managed to run OntoWiki and my eyes saw the news/logon page. My url for now is uninteresting http://localhost:9454. Manual says to login as Admin with no password. Doing it points my browser to http://localhost:9454index.php/application/login. Diagnosis: wrong action attribute on form.
I haven’t actually resolved this. A workaround is described here: http://code.google.com/p/ontowiki/issues/detail?id=1004
Problem 4: URL routing
Even though I corrected how OntoWiki constructs URLs, when I tried to log in IIS returns 404 response for URL http://localhost:9454/application/login (and probably would for any URL). The reason is that IIS does not understand .htaccess files (obviously!)
Google pointed me to this post: http://blog.wilgucki.pl/2010/12/zend-framework-na-iis.html.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Basically you need to add the above web.config file to OntoWiki’s root folder to add rules for ISS’ URL rewrite module. You can read more on OntoWiki’s GitHub wiki
Problem 5: Unknown user identifier (Admin)
OntoWki’s wiki says that a fresh install should have a predefined user Admin. For me logging in fails with an error. Presumably this is due to invalid or incomplete model created by OntoWiki when it first ran. This model contains user credentials and user permissions.
The above problem remains a mystery, although I did manage to resolve it with help of Sebastian Tramp from the University of Lepzig.
What I did was first log in to OntoWiki using Virtuoso’s admin credentials, which works as access for SuperAdmin. Then I deleted Configuration KB as shown below.
This caused Virtuoso to complain it could not get access to
due to configuration. However this was not the case.
What helped though was deleting those two files and then deleting Virtuoso Database to make sure I was starting from scratch.
As an effect, the next time I ran OntoWiki a proper model was created and I was then able to log in as Admin.