To install WADI:
WADI nodes use a machine generated unique id to distinguish each other. For the purposes of logging and monitoring, WADI expects each node to also be given a more user-friendly id (ideally unique). This second id - the node's name - is used to label its configuration. The WADI demonstration uses colours (red, green, blue, ...) as node names. Configurations corresponding to these names may be found in $WADI_HOME/conf.
WADI integrates with a number of different web containers. To walk through the 'Getting Started' documentation, you will need at least one of the following installed and available to WADI. Choosing more than one container will allow you to test WADI's ability to cluster a mixed set of containers.
WADI nodes speak to each other via asynchronous messages over ActiveMQ. ActiveMQ may be configured with a variety of protocol stacks. Ultimately, WADI will use ActiveMQ's peer:// protocol. This allows peers in a cluster to message each other directly. Currently, due to a couple of issues in the peer:// stack, the demonstration needs to be run on the tcp:// stack. This necessitates the running of a standalone message broker to which all nodes connect and via which all messages are exchanged. This is an obvious single point of failure and will be removed as soon as the issues with peer:// have been resolved. We are working on this as a priority.