dailab/owls-fileserver repository overview

⁠OWL-S File Server

This is an extension of the generic JIAC File Server found in the webserver repository. This extension provides a few more actions used by the Semantic Service Manager (SSM) in Eclipse. Particularly, whenever a OWL-S file is deployed to the server, all the internal URLs are adapted to point to the file's own final URL on the server.

Note, however, that OWL-S files that are already present in the file server's repository when it starts are not rewritten to match it's final URL and IP.

Besides that, the OWL-S File Server can still be used like the generic file server, in combination with the File Server View in Eclipse or with SSM.

⁠Running the Docker Image

The minimal command for running the image is

docker run -e fileserver=null -e gateway=172.17.0.1 dailab/owls-fileserver

Here, the fileserver parameter is required, but can be null. It specifies the preferred host address to be used by the file server (for URI rewriting etc.). If it is not specified, the file server will guess its own host address, but might come up with a wrong IP if there are multiple available. The gateway parameter is optional. It specifies the IP of the gateway node to connect to, if any. If not specified, the node will just use multicast.

For the gateway itself, you can use the dailab/jiac-gateway image.

Note, however, that this way the files hosted on the fileserver will not be accessible from outside of the fileserver (except through the file server's own API, of course), and will not be persisted when the image is restarted. For this, the directory has to be linked with a directory on the hosting computer:

mkdir ~/REPO
docker run -e fileserver=null -v ~/REPO:/root/.owlsfileserver/ dailab/owls-fileserver