Grid Mobile-Agent System (GMAS) Mobility TIE Mobility TIE Mobility TIE Mobility TIE Mobility TIE Dartmouth University of West Florida Grid Mobile-Agent System (GMAS) (Contact: Arne Grimstrup, arne@cs.dartmouth.edu) Arne Grimstrup, Robert Gray, David Kotz Dartmouth College Daria Chacón, Martin Hofmann Lockheed Martin Niranjan Suri, Greg Hill, Tom Cowin University of West Florida e Goal: Dynamic Integration of Heterogeneous Mobile Agent Platforms through Communication and Migration Interoperability Phase 1: Communication Interoperability Native Message bearing a Grid Mobile-Agent Markup Language (GMAML) description of the agent Grid Message bearing GMAML description of the agent Native Agent Communications Bridge GMAS Server Server Agent Phase 2: Migration Interoperability Native Message Native Agent Communications Bridge Grid Service Grid Agent Native Message Grid Message Phase 3: Common API for Mobility Service GMAS Agents Java 2 programs implement the GridMobileAgentInterface and SelfSerializable (Type 1 Mobility) or Serializable (Type 2 Mobility) have an agent description attribute self-manage variable state (Type 1 only) GMAS Agent GMAS Agent GMAS Agent GMAS Server Mobility Service GMAS Server Mobility Service GMAS Server Mobility Service MobilityService provides two operations launchAgent cloneAgent manages all Grid communication for the operations converts agent to GMAML form D'Agents System EMAA System NOMADS System Demonstration Scenario BGW Database (EMAA & GMAS) Telephone Intercept Database (NOMADS & GMAS) Task Force HQ (D'Agents & Grid) US Platoon (D'Agents) UK Platoon (NOMADS) Position Updates DB Queries: Suspects in the AO Phone Intercept Info DB Query: Phone Intercepts for listed Suspects Relevant Phone Intercepts D'Agent GMAS Agent Grid Message GMAS Server Grid-enabled Java 2 program reconstructs agent from the GMAML form executes the agent using supplied launcher can be run standalone or as part of an agent system able to serve a single host or an entire network Development Road Map communication protocol interoperability migration interoperability common API and respective implementations translation of native methods to common API calls IDL to generate native method adapters Lessons Learned: Bean-like agent self-description through GMAML metadata is a powerful means of supporting interoperability. Two approaches are required to integrate a richly diverse set of mobile-agent systems: definition of APIs where possible, and clear specification of the necessary interactions between the systems. Also, a reference implementation was very helpful. Interaction between developers of disparate agent systems led to increased flexibility of the mobility API specification. Mobility TIE Mobility TIE Mobility TIE Mobility TIE Mobility TIE