Quick Start

Execution Instructions:

1. First, if you don't already have it, download the JDK 1.0.2. You can get it at JavaSoft's website.
2. Next, download the Java(tm) Agent Template Version 0.3 distribution. Click here to download.
3. Unpack the compressed tar file: "zcat JAT_0.3.tar.Z | tar xf -". This will create a directory titled JAT_0.3.
4. Set the execution parameters:

   JAT agents require a set of execution parameters which can be provided via either applet parameters or commandline arguments. I have created a set of both C shell scripts and html pages for simplifying the excution process. (If you want to execute the agents from the commandline and are running this on either a 95, NT or MacOS machine you will have to either manually specify the args or create appropriate scripts.) You will need to modify both the html (contained in JAT_0.3/applet/) and script (contained in JAT_0.3/scripts/) files to provide the correct values for these parameters. (For Example 1, you will need to modify either the scripts or html pages for the "Agent" and "ANS" agents. For Example 2, modifications must be made to the files for the ServiceBroker, ServiceAgent, FDATAgent and ClientAgent agents). The following parameters must be set:

   • init_file: URL location of the initialization file. This file contains a set of KQML messages which are "sent" to the agent at startup, one of these messages must contain the location of the Agent Name Server (ANS).
   • shared_classes: URL providing the remotely accessible location of the directory which contains Java classes and general files which the agent will share with other agents. This URL will be given to other agents so that they can retrieve selected files. For agents executing on remote machines this URL must have the http protocol; for agents all on the same host, the file protocol can be used.
   • shared_dir: Local path to the shared classes directory. This is used by the agent to modify the contents of shared files. User must have write permission.
   • working_dir: Local path to a directory in which the agent can cache acquired/generated files. User must have write permission.
   • gui: Determines if the agent will be executed with a graphical user interface. These parameter can be set to false for agents which will be run as "daemon" processes. (e.g. you want to run the ANS like a http server)
   • name: String name for the agent.
   • port: Local port for the SocketInterface's ServerSocket. If set to 0, an open port will be automatically selected.
5. Change to the JAT_0.3/scripts/ directory. Modify the env file to correctly set the CLASSPATH environment variable to include the JAT_0.3/classes directory.
6. Modify the init_file to correctly specify the current host and port you want the ANS to communicate through. (For example 2, the FDAT agent needs a special init_file: FDAT_init_file).
7. Execute an ANS and one or more Agents:

   To execute using the appletviewer:

   • If you want the agents to be able to perform local file IO, then you will have to edit the ~/.hotjava/properties file ( or its equivalent on non-Unix platforms) to include the lines: "acl.write={some_dir}/JAT_0.3/working/:{some_dir}/JAT_0.3/files" and "acl.read={some_dir}/JAT_0.3/working/:{some_dir}/JAT_0.3/files", where some_dir provides the absolute path to the JAT_0.3 directory. If this is not done you must remove both the shared_dir and working_dir parameters from the appropriate html file.
   • Source the env file: "source env".
   • Start the appropriate applet using the appletviewer: "appletviewer <agent name>.html &"
   • Press the "Create <agent name>" button to start the Agent.

   To execute as a stand alone application:

   • Execute the Agent by executing the appropriate script: "<agent name>"
   See the Examples for more information.

   ---

   frost@cdr.stanford.edu