Dependencies

The following software components are required for using the OLOS Middleware:

• Java 2 SDK. We were usings Sun's Java 2 SDK 1.4.x. This is actually required by the interface compiler but there should be no Java implementation dependencies in other components.
• hsqldb. This proof-of-concept implementation relies on hsqldb. Switching to other object-relational database is possible but not trivial. hsqldb is available here. We used version 1.7.1.
• An XML parser. We used Apache Xerces Java XML Parser, available here.

Also, Apache Ant is useful for building and running the components.

Parts using the Ekahau Positioning Engine are not present in the Open Source release (although they are mentioned in the original documentation).

How to Get Started?

The following steps loosely explain how to compile OLOS and run the Virtual Graffiti example application. (It is probably a better idea to start by reading about OLOS from the M.Sc. Thesis available at the documentation section.)

1. Get the OLOS source code from the download section.
2. Put hsqldb.jar, xercesImpl.jar, and xmlParserAPIs.jar into OLOS-x.x/lib/ directory or modify build.xml to refer to these jars.
3. Run ant jar.
4. Setup and run hsqldb, and create the OLOS Registry database. Creation commands can be found from registry_db.sql. Note that you must include olos.jar in the runtime classpath of hsqldb.
5. Run OLOS Registry with ant run_registry. Note that running the registry and other components require modifications to the deployment descriptors (.properties files) when they are run in different nodes. As a default, everything is configured to be run in localhost.
6. Start application server components for the example application: VirtualGraffitiFactory and VGUserFactory. These can be started with ant run_virtualgraffitifactory and ant run_vguserfactory.
7. Run the Virtual Graffiti user application: ant run_vgclient. Reading the documentation included helps a lot to understand the application... (Note that random circular track location data in IP-based when running multiple clients.)

The components should be shut down in reverse order, i.e. the client should be able to destroy the PhysicalOLOSObject (see documentation) it uses and the factories should be able to unregister their product classes from the OLOS Registry etc.

Note: If the factory and registry components seem to crash during shutdown, running them without ant typically solves the problem.

CVS Access

Currently no CVS, as nothing has been done since 0.1 version. A new repository can be initiated at sourceforge. Any interested developers?