Running Pseudo Remote Threads

Starting the Host Selector

Open the the <PRT-HOME>\setEnv script and set the environment variables there.
Include any additional jars/classes to the classpath variable in the above file.
Save the setEnv script
Run the setEnv script
Run the startRmiRegistry script
Run the startHostSelector script

Starting the JobRunner

Open the the <PRT-HOME>\setEnv script and set the environment variables there.
Include any additional jars/classes to the classpath variable in the above file.
Save the setEnv script
Run the setEnv script
Run the startRmiRegistry script
Run the startJobRunner with an argument specifying the logical name of the job runner. Its possible to
have multiple job runners on the same physical host. However, the name must be unique amongst all runners cluster wide.
Example: startJobRunner runner1
In the above example, the job runner object is bound with name 'runner1' and also registered with host selector with the same name

Starting the client (JobDispatcher)

There is nothing needed to start the job dispatcher(client). It is a library. Whichever application uses the library should have the prt.jar and
the config directory in its classpath. Refer to the example aashish.prt.client.TestJob and aashish.prt.client.TestPrt for examples on defining a job
and calling it. Another example of defining a job is there in aashish.prt.xsl package. It defines a job to perform XSL transformation.