Getting Started

This page has the following sections:

• Requirements
• Installation
• Setting the CLASSPATH
• Running a demo

 Requirements

1. An operating system that supports the Java Development Kit (JDK) version JDK1.1.6. The JDK can be obtained from http://www.javasoft.com. Use of the JDK compiler is strongly recommended.
2. For development, VisualAge for Java V1.0 or greater is highly recommended.
3. The computer has a TCP/IP stack installed and is connected to a network.
4. A Pentium class machine (166Mhz or greater) with 64Meg of memory.
5. 5 Meg of disk space.

1. Download the package distribution available in zip format from the Experimental Perpetuum Web page and save it in a temporary directory; e.g. Downloads.
2. Create a new subdirectory (e.g. c:\mct) into which the toolkit files will be extracted.
3. Use WinZip to extract the package into the subdirectory that you just created on step 2. The package will be exploded and yield the following tree setup which reflects the package breakdown of the toolkit. Source (.java) and class  (.class) files are stored together in the same directory:


 
• The mct directory contains the source and classes for the RMINetletDaemon.
• The configuration directory contains example properties files for mobile code daemons, facilitators and mobile code directories.
• The admin directory contains source and classes that are required for correct functioning of the toolkit and should not interest the user unless he or she intends to modify the daemon or add new services to the toolkit.
• The blackboard directory contains the source and classes for a simple blackboard application;
• The clients directory contains the source and classes for WinMCTRMIClient. The client application is used to inject mobile code into a running mobile agent system.
• The management directory contains source and classes for the management interface that can be used to control the execution of mobile code running on a mobile code daemon.
• The mediator directory contains the source and classes that implement the location service for mobile agents.
• The net directory contains the source and classes that implement the (deprecated) code transfer protocol.
• The rmi directory contains the source and classes that implement some simple RMI-enabled mobile code. It is of interest to users that need to create RMI-enabled mobile agents.
• The security directory contains the source and classes for the two security managers written for the toolkit.
• The users directory contains the source and classes that enable development of end user mobile agent applications.

 

Examples

Hello	Prints text on the console window.
McTicTacToe	Demonstrates that a mobile agent can maintain state carried along during migration. This netlet plays tic-tac-toe, making a move and then migrates to a new location, maintaining board positions as it does so.
NetletTester	Demonstrates that mobile code can access the data implemented in a Virtual Managed Component (VMC) container and is also capable of migration.
TelnetDaemon	Demonstrates how to add a new service (extension) to the NetletDaemon. In this case, the TelnetDaemon (server) can accept a telnet client application and prompts for commands.
Installer	Demonstrates how a piece of mobile code can install another mobile code. For instance, an agent Netlet is used to install a VMC that does not yet exist. The netlet will pull a mobile code from a local repository and install it on the daemon.
NetComm	Demonstrates simple communication between three mobile codes.
messaging	Two applications are provided. First, a demonstration of interaction between a simple blackboard and four communicating mobile agents. Second, a simple send and receive application.

 
1. Set the CLASSPATH environment variable.

In order to use this package you should set your CLASSPATH environment variable to include the classes defined in the toolkit. The CLASSPATH environment variable should be extended with the directory chosen for installation; e.g. \mct. It is recommended that you chose the default directory for installation as the configuration files do not then need to be edited before the demonstration applications can be run.

For example, if you are using version 1.1.6 of the JDK, then your CLASSPATH should be set as:

• setenv CLASSPATH .:/usr/local/jdk1.1.6/lib/classes.zip:$mctoolkit/ (UNIX)
• set CLASSPATH= .;c:\jdk1.1.6\lib\classes.zip;%mctoolkit%\ (DOS, WIN 95/NT)

Run Demo

Several programs have been written to demonstrate what this toolkit can do. The demonstration assumes that a single machine is used and that two mobile code daemons are running on it. It should be noted that this version of the toolkit relies heavily on the use of RMI. In the instructions below, a PC is assumed. Text in italics should be typed as written. If you want to run the demonstration using the batch (.bat) files provided, then install the software in c:\mct and c:\test\mct. Remove the c:\test\mct\examples directory in order to ensure that you test the actual transfer of code from the WinMCTRMIClient to the running mobile code daemon.

In order to run the demonstration applications, you must:

1. Run the rmiregistry process.
• Open a DOS console.
• type: rmiregistry
2. Create a mobile code region (or running mobile agent system).
• Configuration files for a two daemon mobile agent system can be found in %mctoolkit%\configuration; e.g. \mct\configuration.
• Open a DOS console.
• type: cd %mctoolkit%\configuration
• type: start java mct.mediator.RemoteMediator
• type: start java mct.RMINetletDaemon nd01.properties
• type: start java mct.RMINetletDaemon nd02.properties
3. Run the WinMCTRMIClient
• Using the DOS console created in step 2.
• type: start java mct.clients.WinMCTRMIClient

1. reg.bat [runs the rmiregistry]
2. rm.bat [runs the remote mediator]
3. nd01+nd02.bat [runs the two mobile code daemons, nd01 and nd02]
4. client.bat [runs the WinMCTRMIClient]

Running the examples

The WinMCTRMIClient, shown above, is used to inject a mobile agent. In order to inject a mobile agent, four pieces of information must be provided:

1. the mobile code name; e.g. Barney
2. the fully qualified class name; e.g. mct.examples.MyNetlet
3. the authority of the mobile agent; e.g. PUBLIC
4. the URL of the migration facility that is to receive the injected mobile code.

After you finish running the entire demo, hopefully you will understand some of what the package does. Now the challenge is yours to implement mobile code applications that suit your needs. Constructing a mobile agent provides more information of how your own mobile agent might be constructed using the toolkit.