/*
 *   '$Author: berkley $'
 *   '$Date: 2007-07-13 09:22:43 -0700 (Fri, 13 Jul 2007) $'
 *   '$Revision: 6322 $'
 */

6/20/07
berkley, gilbert

Note: this is preliminary work.  This sequence is known to work but you may
have to tinker with it on your specific system.  It has been tested with 
java 1.5.x.  Also note that this uses a wideopen security policy.  This will 
allow any host to connect to the RMI port.  If you don't know what you're
doing with security/firewalls/etc, you probably don't want to do that :)

Distributed Kepler HOWTO

1) compile the distributed code.  this can be done with 'ant compile'
2) creat the rmi stub.  From $KEPLER:
cd build/classes
rmic -classpath $KEPLER/build/classes:$PTII/build/classes org.kepler.distributed.SlaveController
3) start the rmiregistry with the kepler classes in the classpath 
(on both the slave and master):
rmiregistry -J-classpath -J$KEPLER/build/classes:$PTII/build/classes
4) start the SlaveController on the remote.  Make sure you have a policy file:
java -Djava.security.policy=$KEPLER/configs/ptolemy/configs/wideopen.policy -cp $KEPLER/build/classes:$PTII/build/classes org.kepler.distributed.SlaveController
5) start kepler and create your workflow using the DistributedCompositeActor
6) run the workflow.  You should see any part of the workflow that is 
inside the DistributedCompositeActor executed on the slave
7) if you want to run this on other than localhost, change the config file 
located in kepler/configs/ptolemy/configs/DistributedKepler.config to point 
to the host(s) that you want to run remotely on.  Note that the 
SlaveController and the rmiregistry must be installed and running on each host.

