Date: 2011-04-18 12:36:32
From: Fabian.Cretton@hevs.ch
Hello,
I am currently trying to install the basic sesam/BigOWLIM/Tomcat and test a repository on Windows XP, but can't make it work.
Basically, I can follow the steps described in the BigOWLIM User Guide: I do create the repository with the sesame console, with no error. Then, from the workbench, I can see the bigOWLIM repository, but can't use it. For instance, when selecting "Namespaces" from the "Explore" menu, I do get:
javax.servlet.ServletException: org.openrdf.repository.RepositoryException: org.openrdf.repository.config.RepositoryConfigException: Unsupported Sail type: owlim:Sail
What I can see so far, is that there seems to be a big mess with the 'Application Data' directory.
That's why I guess it is not a version problem (bigowlim, sesame or tomcat)...but I could be wrong.
Without specifying anything, so using the defaults, the sesame console would create:
C:\Application Data\Aduna\OpenRDF Sesame console
and that's where I put the 'templates' files
Then, starting the workbench, it creates:
C:\Documents and Settings\NetworkService\Aduna\OpenRDF Sesame
So, i did follow the instructions I found online to configure tomcat and adding:
-Dinfo.aduna.platform.appdata.basedir=C:\Application Data\Aduna
But now, what happens is that the console still creates:
"C:\Application Data\Aduna\OpenRDF Sesame console"
and the workbench does create:
"C:\Application Data\Aduna\OpenRDF Sesame"
Is this the cause of my problem ? or does the problem come from elsewhere and this 'Application Data' behaviour is totally correct ?
Another question: is the bigOWLIM repository created as a folder or files ? I can't find anything happening in those folders (at least not just looking at the 'repositories' folders that only have a 'SYSTEM' sub-folder.
Thank you very much for any help
Fabian

asked 03 Apr '13, 06:13

Discussion-Board-Archive's gravatar image

Discussion-B...
6.1k133156205
accept rate: 30%

edited 03 Apr '13, 06:13


Date: 2011-04-19 11:26:09
From: Fabian.Cretton@hevs.ch
I got it working with sesame 2.3.3
I guess my mistake was to copy .jar files that were not only 'not needed', but making the server crash
For instance, I was copying all the OWLIM .jar files from bigowlim-3.5.3402\lib
and all the extension .jar files from bigowlim-3.5.3402\ext
(I saw somewhere a recommendation online saying to better copy all of them, but I think that is a mistake and thats where the errors came from)
Thanks again
Fabian
link

answered 03 Apr '13, 06:14

Discussion-Board-Archive's gravatar image

Discussion-B...
6.1k133156205
accept rate: 30%

Date: 2011-04-18 14:34:23
From: barry.bishop@ontotext.com
Hi Fabian,
Sorry to hear that you are having trouble.
It sounds to me like everything has gone correctly, except that the 
owlim jar (and possibly the other 3rd party ones) is missing from the 
openrdf-sesame/WEB-INF/lib directory.
Can you check again that it/they are there? (The workbench does not need 
them, but the sesame server does).
Good luck,
barry
link

answered 03 Apr '13, 06:13

Discussion-Board-Archive's gravatar image

Discussion-B...
6.1k133156205
accept rate: 30%

Date: 2011-04-19 08:10:19
From: Fabian.Cretton@hevs.ch
I have now moved to sesame 2.3.2 (instead of 2.3.3), and this problem is no more showing up (but others are):
- With exactly the same configuration, I can now open the bigOWLLim repository without getting "Unsupported Sail type: owlim:Sail"
- The two different Application Data folders still exist
- A directory is now created for the repository
So once the "Unsupported Sail type: owlim:Sail" was solved in the workbench, I first got: "The currently available JVM memory is 63.6M which is not enough to satisfy the configured memory requirements of 80.0M", which seems to be fixed now.
But now, when using a workbench menu as 'Explore'-'Query' on that repository that has just been created with the sesame console, I get the error HTTP 500: "javax.servlet.ServletException: org.openrdf.repository.RepositoryException: FATAL ERROR: File 'entities-doc' is truncated"
Googling for that I can't find any answer.Thanks for any help, meanwhile I will try to setup bigOWLIM using Joseki
Fabian
link

answered 03 Apr '13, 06:14

Discussion-Board-Archive's gravatar image

Discussion-B...
6.1k133156205
accept rate: 30%

Date: 2011-04-19 08:26:06
From: barry.bishop@ontotext.com
Hi Fabian,
BigOWLIM has been tested against Sesame 2.3.2, but not the latest 2.3.3. 
replacement.
The message you are getting is because the binary storage files are 
corrupt, most likely due to the above issue or because during your 
activities the tomcat server was stopped prematurely.
It might be possible to simply delete the files from the 
open-sesame/tomcat OWLIM storage folder and restart tomcat. This should 
just cause the storage files to be re-initialised. Otherwise, please use 
the sesame console (v2.3.2) to create a BigOWLIM repository with a 
different name.
I hope this helps,
barry
link

answered 03 Apr '13, 06:14

Discussion-Board-Archive's gravatar image

Discussion-B...
6.1k133156205
accept rate: 30%

Date: 2011-04-19 09:04:52
From: Fabian.Cretton@hevs.ch
Hi Barry,
Great, thank you, it does work now and I can start to play ;-)
May I ask you the following questions for which I can't easily find an answer:
- as you said, the repository files where corrupted and I did delete the folder to solve the problem. But then,  what should be taken care of when handling a real repository ? Could it happen that the files are corrupted ? Do we simply make a copy of the folder "in case of" ?
- it seems that the sesame console and the sesame workbench work on two different 'Application Data' folders, is that right ?
If it is correct, is the repository created from the console and accessed by the workbench the same one ?
- in the name OWLIM, what does IM stand for ?
But finally my most important question:
To build a solution based on BigOWLIM, where we want to programmatically update the content of the repository and query it, is it true to say that using the existing interfaces as Sesame-WorkBench or Joseki is not enough ? I mean that those are user interfaces, but they don't expose web services we could call to update a namedgraph or execute a query, is that correct ?
If so, the solution in a project is anyway to developp something using the API (sesame or jena) ?
Thanks a lot
Fabian
Hi Fabian,
BigOWLIM has been tested against Sesame 2.3.2, but not the latest 2.3.3. >From your experience, it seems it is not possible to do a drop in replacement.
The message you are getting is because the binary storage files are corrupt, most likely due to the above issue or because during your activities the tomcat server was stopped prematurely.
It might be possible to simply delete the files from the open-sesame/tomcat OWLIM storage folder and restart tomcat. This should just cause the storage files to be re-initialised. Otherwise, please use the sesame console (v2.3.2) to create a BigOWLIM repository with a different name.
I hope this helps,
barry
link

answered 03 Apr '13, 06:14

Discussion-Board-Archive's gravatar image

Discussion-B...
6.1k133156205
accept rate: 30%

Date: 2011-04-19 10:01:19
From: barry.bishop@ontotext.com
Hi Fabian,
Good to hear that things are working. Comments inline below:
I think the main problem was that the wrong version of the sesame 
library was used. Once a repository has been properly created, it should 
be able to recover itself even in the event of an abnormal termination 
(by replaying transaction logs and so on).
You are correct, the simplest back-up method is to shut down the 
repository (gracefully) and make a binary copy of the storage folder 
(and any sub-folders).
By default, yes, but if you followed the installation instructions 
correctly, the first thing you should have done is: 'connect 
http://localhost:8080/openrdf-sesame .' in the console.
From this point on, everything you do (i.e. create a repository) will 
be in the context of the tomcat hosted sesame server.
Yes, if you started by connecting to the server on the first step. Both 
the console and the workbench connect to a server (and then a repository 
under that server as necessary).
Not many people ask this! It comes from 'In Memory' and was the name for 
what is now called SwiftOWLIM - which keeps everything entirely 
in-memory. BigOWLIM uses a file-based storage system, but somehow the 
name has stuck.
Kind of. Without SPARQL 1.1, there is no way to update a repository 
except by using the Sesame API. Joseki understand SPARQL 1.1 so updates 
can be performed this way.
However, have a look at the getting started application. This 
demonstrates how to instantiate and use a local repository, but also 
using a remote repository - simply by using a RemoteRepositoryManager 
object instead of a LocalRepositoryManager object. The APIs remain 
exactly the same, only the implementation is swapped underneath.
Also, the open-sesame server exposes a SPARQL endpoint, as does Joseki.
If you want to do updates using SPARQL then you will need to use 
BigOWLIM with Joseki.
Otherwise, use the Sesame APIs.
No problem. Good luck!
barry
link

answered 03 Apr '13, 06:14

Discussion-Board-Archive's gravatar image

Discussion-B...
6.1k133156205
accept rate: 30%

Date: 2011-04-19 11:42:17
From: barry.bishop@ontotext.com
Ah ha, good to know. Thanks for the information.
I hope you enjoy BigOWLIM from now on.
barry
link

answered 03 Apr '13, 06:14

Discussion-Board-Archive's gravatar image

Discussion-B...
6.1k133156205
accept rate: 30%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×261
×242

Asked: 03 Apr '13, 06:13

Seen: 13,001 times

Last updated: 02 Jun, 05:45

powered by BitNami OSQA