Getting started

• Download a WSMX binary distribution from sourceforge or get the latest nightly build from [[1]]

• Optional step: Start up a JavaSpaces compliant space implementation such as Outrigger or Blitz. If WSMX does not find a space during boot time it will substitute a virutal space that works as long as components only have local communication requirements

• The microkernel within the executable wsmx.core can be run from the command line given that sufficient privileges are granted: java -Djava.security.policy=/path/to/policy -jar wsmx.core (A sample policy file (policy.all) which grants unrestricted access is supplied with the release.)

• To deploy a developed component, copy the packaged component archive to the systemcodebase. WSMX will discover it automatically and inject it into the running instance.

• You may monitor and administer WSMX through either the GUI-based web console, the TUI-based SSH console, or the eclipse-base WSMT. Point your browser to http://localhost:port, where port is the port number which has been defined in the kernel configuration and is 8080 by default, if undefined and fallback for invalid ports. Point your SSH client to localhost and login with user root at the port defined in the configuration.

• You may shutdown WSMX through any of it's management consoles or by pressing Crtl-C on the OS console (Ctrl-C does not work from within the eclipse console as it is not bound to an OS process kill signal in this environment)