An Adaptation Methodology for the Deployment of Mobile Component-based Applications

1. An Adaptation Methodology for the Deployment of MobileComponent-based Applications • Dhouha Ayed, Chantal Taconet, Guy Bernard and Yolande Berbers

2. Overview • Introduction • Deployment of component-based applications • Deployment adaptation rules • Deployment adaptation process • Conclusion and perspectives

3. Introduction (1) • Mobile hand-held devices are becoming a powerful platform. • Scarce resources • Constant context change: location, network connection, physical environment, etc.

4. Introduction (2) • Repetitive deployment tasks: • installation, • configuration, • uninstallation, • reinstallation, • reconfiguration, • etc.

5. Requirements of mobile users • Deployment automation • Adaptive deployment • Just-in-time deployment

6. Overview • Introduction • Deployment of component-based applications • Deployment adaptation rules • Deployment adaptation process • Conclusion and perspectives

7. Existent Component-based Deployment Solutions • Package and Deployment of CCM (Corba Component Model) • J2EE, Sun • D&C (Deployment and Configuration) of OMG • .NET, Microsoft

8. Deployment Parameters • Application architecture • Placement of each component • Component implementation • Property values

9. Solution • Definition of a set of rules which specify the variability of the deployment parameters • identify the context information which impacts the deployment parameters • define how the deployment parameter can vary according to the context • Adaptation algorithms • Dynamic determination values of the deployment parameters

10. Online Shopping Application GUI AccessControl DB LocalSelection ViewSelection LV CartMgmt Cart PurchaseMgmt Selection

11. Node I Node B Node A Zone I Laptop Zone B GUI screen>14’’ version DB Zone A LV Cart Node J Node B Node A Zone J Node I PDA Zone B GUI PDA version DB Zone A LV Cart

12. Overview • Introduction • Deployment of component-based applications • Deployment adaptation rules • Deployment adaptation process • Conclusion and perspectives

13. Adaptation Rules • Adaptation rules • constraintiparameter = valuei, or • constraintiparameter = ContextMapping(cxti) • Two levels • Component level rules • Application level rules

14. Component Level Rules • Properties ’ adaptation rules : default values and the values that can be taken according to the context • Functional properties • Non functional properties Maximum LV size property: AvailableMemorysize < 30MB => size=100kB AvailableMemorysize > 30MB => size=200kB DefaultSize=10KB Languages property: Language=action:contextMapping(UserLanguage) DefaultLanguage="English"

15. Component Level Rules (2) • Choice of implementation versions rules • Several implementation versions • Context constraints required by each version: strong or weak implementation 1: constraint 1: os name="WinNT" \/ os name="Win2000 type=strong constraint 2: disk size> 30MB type=strong . implementation n: constraint_j: os name="WinCE" type=strong . constraint_z: ..

16. Application Level Rules • Variability of the application architecture according to the context • Complete component level rules that depend on the application semantics

17. Architecture Variability • Obligatory components/connections : deployed whatever the context state • Optional components/connections : require specification of context constraints OPT (userzone = ”nearnoncoveredzone”) \/ (LVpreferable = ”true”) => Existence(LV) = true OBL OBL OBL OPT OPT OBL OPT OPT OPT

18. Adaptation Rules : Consistency Check • Two types • Inconsistency in the description of the application architecture • At the application level • Deployment of detached components • Inconsistency in the description of the rule constraints • At the component and application levels • Contradiction between the rules associated with the same deployment parameter

19. Overview • Introduction • Deployment of component-based applications • Deployment adaptation rules • Deployment adaptation process • Conclusion and perspectives

20. Deployment Adaptation Process (1) • Collection of the context information and filtering of the relevant ones. • Extraction of the deployment adaptation rules at the application level. • For each component instance: • Check its existence, if exist do: • If placement rules specified at the application level are specified, assign its placement • assign its properties values : if no rule can be applied , apply rules at the component level

21. Deployment Adaptation Process (2) • Determine the connections between the components. • use a generic algorithm to determin the placement and the implementation of the component instances

22. placement and implementations process • Find the valid implementations/nodes assignments: • For each component, find a placement node for each of his implementations • Select the best assignment • maximizing the number of satisfied weak constraints • optimizing the resources consumption

23. Implementation Context-aware Application Component Middleware Context-aware deployment service DeploymentAdapter CCM deployment tool Deployer Context-aware Infrastructure

24. Evaluation

25. Conclusion • Methodology to adapt the deployment of component-based applications to the context • Adaptation rules • Generic adaptation algorithms • Adaptation of the deployment parameters • Adaptation rules are divided into two levels: The rules which

26. Perspectives • Dynamic reconfiguration of the application assembly. • Map our model on .NET, J2EE. • Study different policies to uninstall applications