Simulating Transparent Migration in Java Java doesnt provide - - PowerPoint PPT Presentation

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 13

Simulating Transparent Migration in Java Java doesn’t provide transparent migration. programm “as if ” Use code instrumentation go() mymethod() { } mymethod(int x) { } if ( x==1) go() if ( x==2) save local variable values

• n demand only

for all methods currently on stack MigrateException non transparent

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 12

The Big Picture

SAE Agent Manager SAE Agent Scheduler SAE Realm Manager Resource Manager Comm Manager Agent Agent WWW Data Interface Security Manager SAE Agent GUI read write execute read write

HTTPD

Request Manager Content Manager CGI Manager Agent Manager Realm Manager Document Manager WWW Data Interface start restart Agent File System File Database Web-Server Request Response Security Manager read write execute Web Server Data

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 11

Contact

Stefan Fünfrocken fuenf@informatik.th-darmstadt.de http://www.informatik.th-darmstadt.de/~fuenf Alexanderstrasse 6 64283 Darmstadt Tel: (+49) 6151- 16 5411 Fax: (+49) 6151- 16 3052 Germany

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 10

For the Future

right now:

• basics are working
• security architecture
• SAE-Jigsaw resource
• Java transparent migration simulation

future steps:

• more sophisticated agents (simple services)
• service creator support
• graphical agent programming tool
• agent components
• service specification language
• real service scenarios and agents

Java Security API Java Crypto API Java E-Commerce API

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 9

Security

• encryption, authentication for network communication
• agent migration
• agent - agent GUI
• controlled access to local data
• no native Java IO methods (SecurityManager)
• special agent data interface (WWW DataInterface)
• file names confirm to local URLs
• fine grain realms
• user authorization for user data
• no native references between agents
• agent capabilities (general and local)
• Net of trusted SAEs (certified public keys)

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 8

Web Agent Communication

Agent - User:

• using Agent GUI (Applet)
• different views (User/Super user)
• extendable ‘on-the-fly’

Agent - Agent:

• using SAE Communication Manager
• Streams from/to other agent
• no references
• known agents only

Agent - Agent GUI:

• using SAE Communication Manger
• Streams from/to agent GUI

Web Browser Agent 1 GUI Agent 1 Agent 2 Comm. Manager SAE Request Connection Req. Conn. Stream Conn.

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 7

Agent

Web Agent Startup

• User sends start-request

http://<host>/<path>/agent.agt

• Server asks SAE to start agent
• SAE loads and starts agent
• agent may send its GUI:
• generated HTML page
• agent GUI applet
• user configures agent
• agent begins to work
• migrate to remote servers
• return and present results to user

Agent GUIs SAE Web Server Web Browser Req. redirect Resp. Agent Start GUI Agent load Agent Code HTML

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 6

WASP Infrastructure for Web Agents

• Java based system ( JDK 1.1.2 )
• HTTP server
• standard Web server functionality
• redirects agent related requests
• Server Agent Environment (SAE)
• load / start / migrate agents
• restrict access to local resources
• plug-in for Web servers
• Web agents
• multiple GUIs
• functional part

Web Browser Web Server SAE Agent Agent GUIs Agent Related Normal Request redirect

HTML CGI-BIN Server Data

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 5

The WASP Project

Web Agent based Service Providing:

• Overall goal: In search for well-suited mobile agent application areas
• Our scenario:
• (subscription) services on WWW-data
• service implementation by using mobile agents (Web Agents)
• the agent is the service
• Long-term:
• support for service creators
• agent creation (reusable agent components, graphical agent builder)
• service organization (advertising, installation, accounting, maintenance)
• Short-term:
• infrastructure for Web agents
• special mobile agent system

Web server Web server Web server Web server =Web server Server Agent Env.

Data Data Data Data Data

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 3

Agent Scenario

Network Agent place

Agent

Stefan Fünfrocken, Darmstadt University of Technology WETICE’97 Slide 2

Outline

— WASP Project — WASP Infrastructure for Mobile Agents — Web Agent

• Startup Scenario
• Communication

— Security — Outlook

Stefan Fünfrocken fuenf@informatik.th-darmstadt.de

Darmstadt University of Technology Germany

How to Integrate Mobile Agents into Web Servers