Cambridge, March 23 rd 2004 MobileMAN Project MobileMAN Project Web Service in Ad Hoc Network...

Cambridge, March 23rd 2004 MobileMAN Project

MobileMAN ProjectWeb Service in Ad Hoc Network

Veronica Vanni

NETikos S.p.A.


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


Web ServicesWS 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..


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


Web Service Scenario [cont.]

ServiceBroker

ServiceUser

ServiceProvider

UDDI/WSDLFind

Pub

lish

UD

DI

Bind

SO

AP

Communication: HTTP

Data: XML

Interactions: SOAP


Web Service in Ad Hoc networkIn 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


Web Service in Ad Hoc network [cont]

UDDI-m

UDDIClient

UDDIServer

UDDI-m

UDDIClient

UDDIServer

UDDI-m

UDDIClient

UDDIServer

UDDI-m

UDDIClient

UDDIServer

API publishing

API inquiry


Interaction between middleware and applicationPossible 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

Net

wor

k St

atu

sLegacy ArchitectureMobileMAN Architecture

• With this same interface (P2P common API) WS can interactive with Pastry on a classical legacy architecture


Interaction between middleware and application

New node

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


Interfaces user and publishers

UDDI API publishing

Interface publisher

UDDI API inquiry

Interface user

UDDI database

P2P commonAPI

Application level

P2P commonAPI

Middleware level


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 knownKeyword, if you want search for keywordAll, if you know all publisher or services contained in the network


Relational database modelBusiness_Entity

businessKeyNameDescription

tModel

IdentifierBagNameDescriptionOverviewDoc

Class

class_idName

Business_Service

serviceKeybusinessKeyIdentifierBagNameDescription

Binding_Template

bindingKeyserviceKeyDescriptionType_APAccessPoint

tModel_Descr

IdentifierBagClass_idCategory_idKind_id

0..n

1..1

1..1

1..1

Category

category_idName

Kind

kind_idName

1..n

1..n

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


Database modelBusiness_Entity

BusinessKey Name Description

BE200403161132 NETikos ……

Business_Service

ServiceKey (PK) Businesskey Name Description

BS200403161140 BE200403161132 Content Sharing ……

BS200403161137 BE200403161132 Video/Conferencing ……

BS200403161212 BE200403161132 Chat ……

BindingTemplate

BindingKey ServiceKey Description Type_AP AccessPoint

BT200403161140 BS200403161140 ….. HTTPhttp://

mobileman.netikos.com/cgi- bin/SoapServer/content.cgi


Database model [cont.]

tModel

IdentifierBag Name Description OverviewDoc

TM200403161140 Content Sharing ….. ……

TModel_Descr

IdentifierBag Class_id Category_id Kind_id

TM200403161140 2 4 1

TM200403161140 2 4 2

TM200403161140 2 4 3

Class

Class_id Name

2 ENTERTAINMENT

Category

Category_id Name

4 Music

Kind

Kind_id Name

1 POP

2 ROCK

3 CLASSIC


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


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

Cambridge, March 23 rd 2004 MobileMAN Project MobileMAN Project Web Service in Ad Hoc Network...

Documents

Transcript of Cambridge, March 23 rd 2004 MobileMAN Project MobileMAN Project Web Service in Ad Hoc Network...