Starting a TaskServer

java -cp $JICOS/lib/jicos-system.jar                   \
     -Djava.security.policy=$JICOS/policy/policy   \
      edu.ucsb.cs.jicos.services.TaskServer <hsp-machine> [numHosts]

• Since the policy file policy within $JICOS/policy grants all permissions, it is used only in testing situations.
•  The TaskServer registers with the Hsp on the machine whose domain name is <hsp-machine>.
• For easily constructing a non-trivial JICOS system (for testing purposes), there is an optional command-line parameter (following <hsp-machine>: the number of Host objects to be started in the same JVM (default = 0). For example,
  

java -cp $JICOS/lib/jicos-system.jar                   \
     -Djava.security.policy=$JICOS/policy/policy   \
      edu.ucsb.cs.jicos.services.TaskServer <hsp-machine> 10

starts 10 hosts within the same JVM as the task server.


• In a production deployment, you want 0 Host objects running on the same machine as a TaskServer; each Host & TaskServer is intended to maximally utilize its machine's resources.
  
• The TaskServer binds its service name into an RMI registry running on its machine: Only 1 TaskServer can be executing on any given machine.