What is MobJeX?

1. 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

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

3. 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

4. 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

5. 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)

6. 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 $$

7. Fire Fighting Scenario Central Office Computer Fighter PDA1 WLAN* KH EEa Fighter Smartphone Truck Laptop Bluetooth/ Infrared* OC EEb 3G GSM/GPRS*

8. 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

9. PDA1 DS Truck Laptop PDA2 OC DS P Dangerous Substance Scenario

10. 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