MobileMAN Project Web Service in Ad Hoc Network

1. MobileMAN ProjectWeb Service in Ad Hoc Network Veronica Vanni NETikos S.p.A. MobileMAN Project

2. Summary • Web Service definition • Web Service in Ad Hoc Network • Interaction between middleware and our application • Interfaces users and providers • Database’s description used in the application MobileMAN Project

3. Web Services WS are services to build distributed applications, to use methods and properties of objects installed on other server: • Each information system can publish contents through WS • Each information system can use contents published from other publisher • Use of UDDI (Universal Description Discovery and Integration) to define a way to publish and discover information about Web Services • Use of SOAP (Simple Object Access Protocol) to access to remote services, defines a simple way to package information to exchange across systems. SOAP bindings to HTTP defines a way to make remote procedure calls between systems. based on XML, a neutral language to several devices • WSDL (Web Service Description Language), in XML format, that describes the content in terms of methods, parameters, types and etc.. MobileMAN Project

4. Web Service Scenario • The provider of services creates the service and its WSDL description • The provider publishes its service in UDDI • The user finds the services trying UDDI register • The application connects to Web Services and calls its operation via SOAP MobileMAN Project

5. Web Service Scenario [cont.] Service Provider Interactions: SOAP Data: XML Communication: HTTP Bind SOAP Publish UDDI Service Broker Service User UDDI/WSDL Find MobileMAN Project

6. Web Service in Ad Hoc network In Ad Hoc Network, we take care of the features of this type of network: • No client-server application, but peer-to-peer communications • Each node has an client side and server side • Distributed database that stores information relative on available services presented on the network • Database is distributed on the nodes using Pastry or Cross-ROAD protocol MobileMAN Project

7. UDDI-m UDDI-m UDDI-m UDDI-m UDDI Client UDDI Client UDDI Client UDDI Client UDDI Server UDDI Server UDDI Server UDDI Server Web Service in Ad Hoc network [cont] API publishing API inquiry MobileMAN Project

8. Applications WSL Applications WSL Middleware-Pastry Middleware-CROSS-ROAD Network Status Transport Transport Network Network MAC + Physical MAC + Physical Interaction between middleware and applicationPossible Architectures Legacy Architecture MobileMAN Architecture • WS application can exchange information with other protocol through NeSt. • It can exploit CROSS-ROAD advantages simply implementing the P2P common API • With this same interface (P2P common API) WS can interactive with Pastry on a classical legacy architecture MobileMAN Project

9. New node Interaction between middleware and application • New node entries in the network: • activates the pastry or CROSS-ROAD service • obtains the nodeId and the node set that participate to UDDI service • if the new node should publish some contents then publishes its contents on this node set (use UDDI API publishing) • there’s a redundancy of contents, but it’s necessary considering the mobility and dynamic of the Ad Hoc Network • updates network imply calls to P2P common API to update the information relative to Ad hoc network topology (i.e. new node entries in the network, node leaves the network) node set MobileMAN Project

10. UDDI API publishing UDDI API inquiry P2P commonAPI P2P commonAPI Interfaces user and publishers Application level Interface publisher Interface user UDDI database Middleware level MobileMAN Project

11. API publishing/inquiry API publishing void SaveBusiness (key KE) void SaveService (key KS) void SaveBinding (key KB) void SavetModel (key KtM) void DeleteBusiness (key KE) void DeleteService (key KS) void DeleteBinding (key KB) void DeletetModel (key KtM) API inquiry void FindBusiness (key KE, method_search ms) void FindService (key KS, method_search ms) void FindBinding (key KB) void FindtModel (key KtM) You can find business entity or service for: Key, if the key is known Keyword, if you want search for keyword All, if you know all publisher or services contained in the network MobileMAN Project

12. Relational database model tModelIdentifierBagNameDescriptionOverviewDoc Business_Entity businessKeyNameDescription 1..n • Database is in keeping with UDDI standard: • Business_Entity describes the publishers; • Business_Services describes the services published from publishers in the network • Binding_Template describes the services in technical features • tModel and tModel_Descr are template service 1..1 1..1 0..n tModel_DescrIdentifierBagClass_idCategory_id Kind_id 1..1 Business_ServiceserviceKeybusinessKey IdentifierBagNameDescription 1..n Classclass_idName 1..1 1..1 Binding_TemplatebindingKeyserviceKeyDescriptionType_AP AccessPoint Categorycategory_idName Kindkind_idName MobileMAN Project

13. Database model MobileMAN Project

14. Database model [cont.] MobileMAN Project

15. Development’s state The state of application’s development is: • The API publishing/inquiry are developed in perl language • MySQL database is used to realize the UDDI database • The API publishing/inquiry will be ported in java language in order to optimize middleware’s interface (P2P commonAPI) • The choice of perl language is been made because it’s faster than use of java so it’s more useful on small platforms MobileMAN Project

16. Planning steps • The next steps : • porting of the API publishing/inquiry in java language (July 2004) • integration between WS application and middleware in java (July 2004) • application demo on local computer (maybe July 2004) • application demo on Ad Hoc Network using laptop (end of September 2004) • application demo on Ad Hoc Network using PDA MobileMAN Project