SWP Setup: Mac OS X

The following notes cover installation of the packages described in SWP Setup on an (Intel-based) Mac Pro, running Mac OS X 10.5.8 and 10.6.1.


Snow Leopard (Mac OS X 10.6.*)

Snow Leopard, as of 10.6.1, has 1.6.0_15-b03-219 installed. Nothing to see here, folks; move along...

Leopard (Mac OS X 10.5.*)

By default, Leopard 10.5.8 has Java 1.5 installed. However, Apple has an update which supplies Java SE 6 version 1.6 (while leaving the original version alone). Note that this requires a 64-bit, Intel-based Macintosh.

  • Go to the download page.
  • Click the "Download" button.
  • Double-click (if need be) on the downloaded DMG archive.
  • Double-click on the installer package (*.pkg) in the DMG.

To try out the updated version, you'll need to specify its location:

$ /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Commands/java -version
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-9M3125)
Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode)


Note: Although the Pellet web site describes 2.0.0-rc7 as "the latest stable version", I couldn't get it to work. In any case, this section describes Pellet 1.5.2, which is what the book suggests.

It appears that there are two ways to use Pellet (as an independent command and as a Protégé plugin), so it has to be installed twice. The following instructions should install Pellet and set it up for use as a command:

  • Go to the download page.
  • Download Pellet 1.5.2.
  • If desired, move the Zip archive to a more appropriate location.
  • Double-click on the Zip archive (pellet-1.5.2.zip).
  • Bring up a Terminal window.
  • Go to the Pellet directory (pellet-1.5.2).
    Hint: Type "cd " in the Terminal, then drag over the folder from the Finder.
  • Run the help command, as a sanity check: "sh pellet.sh -help".
  • Start the server: "sh pellet-dig.sh".

If you are unable to download the archive using a web browser, you can use curl on the command line:

$ curl http://pellet.owldl.com/downloads/pellet-1.5.2.zip > pellet-1.5.2.zip


Although Protégé is Open Source (MPL), they really want folks to register so they can track usage, etc.

  • Go to the gateway page.
  • If need be, visit the registration page.
  • Go to the download page.
  • Under "Protégé 4.0 Release", click on "Protégé" in "Download Protégé - platform independent installer program".
  • Click on "Download (xx.xM)" on the "MacOSX" line.
  • If desired, move the Zip archive to a more appropriate location.
  • Double-click on the Zip archive (eg, install_protege_4.zip).
  • Double-click on the installer app (eg, install_protege_4.app).

Now we have to tell Protégé to use the Pellet Plugin. There are some fancy instructions here, but this list should serve:

  • Double-click on the Protege app to start it.
  • Click on the "Create new OWL ontology" link.
  • Click on the "Continue" button, accepting the default Ontology URI.
  • Click on the "Continue" button, accepting the default Physical Location.
  • Click on the "Finish" button, accepting the default Ontology Format.
  • In the File menu, select "Check for plugins...".
  • In the Downloads tab, scroll down to "Pellet Reasoner Plug-in".
  • Check the "Install" box next to the Name.
  • Click the "Install" button.
  • Click the "OK" button on the informational dialog.
  • In the Protege menu, click "Quit Protege".
  • Click the "No" button under "Save modified ontologies?".

To check this out, restart Protégé:

  • Double-click on the Protege app.
  • Click on the "Create new OWL ontology", "Continue", "Continue", and "Finish" buttons.
  • In the Reasoner menu, select "Pellet".

For some reason, this causes all but the Apple and Protege menus to disappear. I was able to get them back by clicking the "Quit Protege" item in the "Protege" menu, then clicking the "Cancel" button. Then, when I inspected the Reasoner menu, Pellet was checked. However, something is clearly amiss...


In order for OWLViz to run, you will need to install Graphviz. The Leopard version of Graphviz works OK; just install it. The Snow Leopard version seems to install and work OK, as of 2009.1017, but it is still listed as suspect. So, install it, but stay tuned...


The Eclipse Downloads page lists a number of similar-looking ways to download the package, so be careful!

  • Click the "Mac Cocoa 32bit" link in the "Eclipse IDE for Java Developers" section.
  • Pick a mirror site.
  • If desired, move the Zip archive to a more appropriate location.
  • Double-click on the GNU-zipped tar archive (eg, eclipse-java-galileo-macosx-cocoa.tar.gz).
  • Navigate to the Eclipse directory (eg, eclipse).
  • Double-click on the Eclipse app (eg, Eclipse.app).
  • Select a directory for Eclipse to use as its default workspace.
  • Quit Eclipse.


  • Go to the main Jena page.
  • Click on the "downloads" link in the left sidebar.
  • Click on the "Download Jena X.Y.Z" link in the Jena section.
  • If desired, move the Zip archive to a more appropriate location.
  • Double-click on the Zip archive (eg, jena-2.6.0.zip).
  • Navigate to the Jena directory (eg, Jena-2.6.0).
  • Try out, as in SWP_Chap_05.


It's possible to set up a SPARQL endpoint, using a combination of Java, Jena, Jetty, and Joseki. Although we already have Java and Jena installed, the following procedure doesn't use those copies. Nor does it follow the procedure outlined in the book (which I was unable to get to work).

  • Go to the main Joseki page.
  • Click on the "Download" link at the top of the page.
  • Click on "The Joseki-SPARQL release area" link in the Downloads section.
  • Click on joseki-3.4.0.zip, under the Joseki-3.4 disclosure triangle.
  • If desired, move the Zip archive to a more appropriate location.
  • Double-click on the Zip archive (joseki-3.4.0.zip).

The rdfserver script (Joseki-3.4.0/bin/rdfserver) expects to find Java 1.6 in a "bin" directory, but Mac OS X's Java update for Leopard (10.5.*) installs Java in a "Commands" directory. If you have performed this update, modify the script as follows:


Now, run some Mac OS X shell commands in a Terminal window. The uname nastygrams are caused by an error in Joseki's bin/make_classpath script ("uname -o" is not supported by Mac OS X). However, this does no real harm...

$ cd Joseki-3.4.0
$ export JOSEKIROOT=`pwd`
$ chmod +x bin/*
$ bin/rdfserver joseki-config.ttl
uname: illegal option -- o
usage: uname [-amnprsv]
02:25:36 INFO  Configuration        :: ==== Configuration ====
02:25:36 INFO  Configuration        :: Loading : <joseki-config.ttl>
02:25:37 INFO  log                  :: Started SelectChannelConnector@

Finally, using a web browser, navigate to http://localhost:2020 and try out the endpoint.

This wiki page is maintained by Rich Morin, an independent consultant specializing in software design, development, and documentation. Please feel free to email comments, inquiries, suggestions, etc!

Topic revision: r16 - 31 Jan 2010, RichMorin
This site is powered by Foswiki Copyright © by the contributing authors. All material on this wiki is the property of the contributing authors.
Foswiki version v2.1.6, Release Foswiki-2.1.6, Plugin API version 2.4
Ideas, requests, problems regarding CFCL Wiki? Send us email