Slide 1 Written by Dr Caspar Ryan, Project Leader ATcrc project 1.2 What is MobJeX? Next Generation Java Application Framework providing transparent component distribution via object mobility automatic replication/redundancy smart internet applications dynamic metrics based adaptation reduced development costs

Slide 2 Written by Dr Caspar Ryan, Project Leader ATcrc project 1.2 Automatic Distribution Automatically distribute application objects/components to MobJeX capable clients remove central point of failure operate when disconnected reduce server load improve application responsiveness/user experience move or use different objects in response to changing environment or changed requirements different users can use same data in different ways

Slide 3 Written by Dr Caspar Ryan, Project Leader ATcrc project 1.2 Automated Failover Support Seamlessly: replicate applications and components across multiple computers save applications or components to provide restore checkpoints move applications off a machine for maintenance then back when finished

Slide 4 Written by Dr Caspar Ryan, Project Leader ATcrc project 1.2 Applications Follow You Share applications with friends/colleagues let your friend/associate take over a game/work session on his/her own computer Take your applications on the move without closing files, synchronising or losing session state seamlessly switch from desktop to PDA when leaving the office Follow the Sun applications move around the world to follow workflows across time zones

Slide 5 Written by Dr Caspar Ryan, Project Leader ATcrc project 1.2 Adaptation Manual adaptation move software components from one device to another human controlled based on established procedures Automatic Adaptation System collects metrics from environment e.g. battery life memory usage network usage System collects metrics from software components frequency of use performance data (e.g. invocation time versus execution time)

Slide 6 Written by Dr Caspar Ryan, Project Leader ATcrc project 1.2 Reduce Development Costs MobJeX Framework provides: transparent object mobility and replication (no coding required) session state handling and data synchronisation configurable adaptation behaviour Reduce: lines of code and software complexity development, testing and maintenance effort project $$

Slide 7 Written by Dr Caspar Ryan, Project Leader ATcrc project 1.2 Fire Fighting Scenario KH Central Office Computer OC Truck Laptop 3G GSM/GPRS* EE a Fighter PDA 1 EE b WLAN* Bluetooth/ Infrared* Fighter Smartphone

Slide 8 Written by Dr Caspar Ryan, Project Leader ATcrc project 1.2 Fire Fighting Scenario The ‘Operation Coordination’ subsystem (OC) used by the commander in the truck contacts the ‘Knowledge Hub’ subsystem (KH) hosted in central office requests information such as building floor planes and navigation tools e.g. Edifice Explorer ‘Edifice Explorer’ (EE) subsystem is distributed to the devices of individual fire-fighters different data but same system component to manipulate it operate effectively and safely in different parts of the accident or fire scene Not only data exchange but dynamic deployment of a mobile application component to manipulate the information * 3G, GSM/GPRS, WLAN, Infrared and Bluetooth are merely representative of different wireless communications

Slide 9 Written by Dr Caspar Ryan, Project Leader ATcrc project 1.2 Dangerous Substance Scenario OC Truck Laptop DS PDA 1 DS PDA 2 P

Slide 10 Written by Dr Caspar Ryan, Project Leader ATcrc project 1.2 Dangerous Substance Scenario The ‘Dangerous Substance’ sub-system (DS) interacts with the ‘Operation Coordination’ subsystem (OC) help identify hazardous materials once identified, the corresponding handling procedure subsystem (P) is sent from the truck laptop to PDA2 If the battery of PDA1 is running out of power the ‘Dangerous Substance’ sub-system (DS) can be migrated to and operated from another PDA If the fire-fighters are operating in a hostile environment system components could be replicated to achieve redundancy tolerate possible hardware failures due to excessive heat or unexpected system crashes