agentTool Installation

Installation version 1.8

The latest version of agentTool is now located on this disk in the "agentTool(1.8).zip" file. The zip file contains the "full" agentTool suite with the exception of the "SPIN" software used for automatic conversation verification.

If you unzip the file in the C:\ directory, it will create a C:\AgentTool_1.8 directory which will contain all the source code, executable code, and various MAML example files. If you have JDK 1.3 loaded (in the default C:\jdk1.3 directory), running the C:\AgentTool_1.8\agentTool.bat file will run agentTool directly without modification.

If you do not have JDK 1.3, do not have it loaded in the default directory, or don't load agentTool into the C:\AgentTool_1.8 directory, you will have to modify the agentTool.bat file. You will have to make the appropriate changes to point to the correct agentTool directory or the correct JDK directory.

set AT=c:\AgentTool_1.8
set path=c:\jdk1.3\bin;%AT%\spin\bin
set djgpp=%AT%\spin\djgpp.env
cd %AT%
java Editor.ATeditor 
rem java -Xmx200000000 Editor.ATeditor 

The command "set AT=c:\AgentTool_1.8" will create a new environment variable "AT" set to the path of the Agent Tool environment. You will need to set this to whatever your installation directory is. If you installed straight to c: then you won't need to change this. 

If you have the JDK installed in a different directory, you will need to make the appropriate changes to the path variable.

The line "set path= ... %AT%\spin\bin" and "set djgpp=%AT%\spin\djgpp.env" are used with SPIN verification tool. Because we did not develop SPIN, we do not distribute it directly. You need to download SPIN, compile it, and install it in the c:\agTool\spin directory.

The last three lines of this batch file are used to load AgentTool and should not need to be changed. The memory consumption issue for prior versions has been eliminated in version 1.8. There should be no need to extend the memory, but if this does become an issue this can be fixed by using the "-Xmx200000000" initialization. To do this simply switch which command is ignored by "rem". If this is insufficient, you can increase the amount of memory requested. If agentTool is acting "flakey", check the agentTool DOS window (which is minimized when agentTool runs) to see if you are getting "out of memory errors". If this happens, increase the memory allocated to agentTool via the -Xmx flag.

Send questions/report problems about agentTool