Helsinki, June 7 th 2004 IAB Meeting MobileMAN Project Web Service in Ad Hoc Network Veronica Vanni NETikos S.p.A.

Helsinki, June 7 th 2004 IAB Meeting Summary Web Service definition Web Service in Ad Hoc Network Interaction between middleware and our application software Architecture : -developed API -relational database model

Helsinki, June 7 th 2004 IAB Meeting 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..

Helsinki, June 7 th 2004 IAB Meeting 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 Service Broker Service User Service Provider UDDI/WSDL Find Publish UDDI Bind SOAP Communication: HTTP Data: XML Interactions: SOAP

Helsinki, June 7 th 2004 IAB Meeting Use of Web Service Remote server Local client Gateway SOAP Request Exports the methods of a object (i. e. Method_i) SOAP Response Calls the remote methods (i. e. Method_i) When a local client would invocate methods that a remote server exported them:

Helsinki, June 7 th 2004 IAB Meeting 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 to obtain overlay network of UDDI service we can use Pastry or Cross-ROAD protocol

Helsinki, June 7 th 2004 IAB Meeting Web Service in Ad Hoc network [cont] UDDI-m UDDI Client UDDI Server UDDI-m UDDI Client UDDI Server UDDI-m UDDI Client UDDI Server UDDI-m UDDI Client UDDI Server API publishing API inquiry

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

Helsinki, June 7 th 2004 IAB Meeting Software Architecture user/provider Interface (jsp, html, cgi…) Publishing/inquiry API UDDI4m db Application level P2P common API Middleware level

Helsinki, June 7 th 2004 IAB Meeting publishing/inquiry API publishing API 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) inquiry API 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 Modify the UDDI registries Inquiry the UDDI registries

Helsinki, June 7 th 2004 IAB Meeting Relational database model Business_Entity businessKey Name Description Contact tModel Tmodel_key Name Description Class Tmodel_Key class_id Name Business_Service serviceKey businessKey Name Description Binding_Template binding_Key service_Key Description Access_Point_Url Access_Point_Type tModel_Descr Tmodel_Key Class_id Category_id Kind_id 0..n 1..1 Category Tmodel_Key category_id Name Kind Tmodel_Key kind_id Name 1..n 1..1 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 tModel_Instance_Info Binding_Key TModel_key Overview_url Instance_parms Description

Helsinki, June 7 th 2004 IAB Meeting Database model Business_Entity BusinessKeyNameDescription BE NETikos…… Business_Service ServiceKey (PK)BusinesskeyNameDescription BS BE Content Sharing…… BS BE Video/Conferencing…… BS BE Chat…… BindingTemplate BindingKeyServiceKeyDescriptionType_APAccessPoint BT BS …..HTTP mobileman.netikos.com/cgi- bin/SoapServer/content.cgi

Helsinki, June 7 th 2004 IAB Meeting Database model [cont.] tModel IdentifierBagNameDescriptionOverviewDoc TM Content Sharing…..…… TModel_Descr IdentifierBagClass_idCategory_idKind_id TM Class Class_idName 2ENTERTAINMENT Category Category_idName 4Music Kind Kind_idName 1POP 2ROCK 3CLASSIC

Helsinki, June 7 th 2004 IAB Meeting Development’s state The state of application’s development is: In the first time the publishing/inquiry API are developed in perl language. The choose of perl language is been made because it’s more flat than use of java so it’s more useful on small platforms Then, the publishing/inquiry API are developing in java language in order to optimize middleware’s interface (P2P commonAPI) MySQL database is used to realize the UDDI database Configuration of laptop or desktop to run the application