AgentBean Development Kit (ADK)


General
Introduction
Application Areas
Documentation

Recent Work
Component Model
Visual Construction
Abstraction Layer

Current Work
Event Model
Service Adaptation
Time Planner
 
 
 

For Students
Praktika!
Diplomarbeiten!

Download
Status
Download
 

Component Model

We have identified 3 categories of tasks that will be implemented by most mobile agents (in the following, we mean mobile agents whenever we use the term agent): 
  • Each agent includes some kind of navigation logic and can be implemented in its own component.
  • Each agent has to perform some set of tasks (i.e. collecting some information, updating software, ...).
  • Most agents need to somehow report back its results. Either by collecting and combining them and reporting it after termination or by directly reporting back each collected data item.
Typically, an agent consists of one navigator, one or several performers and zero or more reporters. The components interact with each other using an event/action-based communication. 

We decided to use JavaBeans to model our components. Since most software components for Java come as Java Beans we are able to reuse those components for mobile agents. 

Visual Construction

To support the visual construction of mobile agents we have extended Sun's BeanBox implementation to allow for the construction of mobile agents. The BeanBox we have used is shipped with the Bean Development Kit (BDK) and is available in source code form. 

For a detailed list of modifications, please have a look at the ADK distribution. 

Abstraction Layer

We have implemented an abstraction which isolates the diversity of the underlying agent system and provides a stable interface to our agents. Using the abstraction layer, mobile agents created with the ADK can move between different agent systems. 

Last update: Tue May 11 14:24:19 CEST 1999