Transcript MobileMAN Project Web Service Location in Ad Hoc Network

MobileMAN Project
Web Service in Ad Hoc Network
Veronica Vanni
NETikos S.p.A.
Helsinki, June 7th 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 7th 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 7th 2004
IAB Meeting
Web Service Scenario
Interactions: SOAP
•
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
Provider
Data: XML
Communication: HTTP
Service
Broker
Helsinki, June 7th 2004
UDDI/WSDL Service
Find
User
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 7th 2004
IAB Meeting
Web Service in Ad Hoc network [cont]
UDDI-m
UDDI-m
UDDI
Client
UDDI
Client
UDDI
Server
UDDI
Server
API publishing
API inquiry
UDDI-m
UDDI-m
UDDI
Client
Helsinki, June 7th 2004
UDDI
Server
UDDI
Client
UDDI
Server
IAB Meeting
Interaction between middleware and application
Possible Architectures
MobileMAN Architecture
Legacy Architecture
Applications WSL
Middleware-CROSS-ROAD
Middleware-Pastry
Transport
Transport
Network
Network
MAC + Physical
MAC + Physical
Network
Status
Applications WSL
• WS application can exchange information
with other protocol through NeSt.
• It can exploit CROSS-ROAD advantages
simply implementing the P2P common API
Helsinki, June 7th 2004
• With this same interface (P2P
common API) WS can interactive with
Pastry on a classical legacy architecture
IAB Meeting
Software Architecture
user/provider Interface
(jsp, html, cgi…)
Application level
Publishing/inquiry
API
UDDI4m
db
Middleware level
P2P common
API
Helsinki, June 7th 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)
Modify the UDDI
registries
inquiry API
void FindBusiness (key KE, method_search ms)
void FindService (key KS, method_search ms)
void FindBinding (key KB)
void FindtModel (key KtM)
Inquiry the
UDDI registries
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
Helsinki, June 7th 2004
IAB Meeting
Relational database model
tModel
Business_Entity
businessKey
Name
Description
Contact
0..n
1..1
Business_Service
serviceKey
businessKey
Name
Description
1..n
tModel_Instance_Info
Binding_Key
TModel_key
Overview_url
Instance_parms
Description
Tmodel_key
Name
Description
1..1
1..1
tModel_Descr
Tmodel_Key
Class_id
Category_id
Kind_id
1..n
Class
Tmodel_Key
class_id
Name
1..1
1..1
Binding_Template
binding_Key
service_Key
Description
Access_Point_Url
Access_Point_Type
Helsinki, June 7th 2004
Category
Tmodel_Key
category_id
Name
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
Kind
Tmodel_Key
kind_id
Name
IAB Meeting
Database model
Business_Entity
BusinessKey
BE200403161132
Name
Description
NETikos
……
Business_Service
ServiceKey (PK)
Businesskey
Name
Description
BS200403161140
BE200403161132
Content Sharing
……
BS200403161137
BE200403161132
Video/Conferencing
……
BS200403161212
BE200403161132
Chat
……
BindingTemplate
BindingKey
BT200403161140
Helsinki, June 7th 2004
ServiceKey
BS200403161140
Description
…..
Type_AP
AccessPoint
HTTP
http://
mobileman.netikos.com/cgibin/SoapServer/content.cgi
IAB Meeting
Database model [cont.]
tModel
Class
IdentifierBag
TM200403161140
Name
Description
OverviewDoc
Content Sharing
…..
……
Class_id
2
Name
ENTERTAINMENT
TModel_Descr
IdentifierBag
Class_id
Category_id
Kind_id
TM200403161140
2
4
1
TM200403161140
2
4
2
TM200403161140
2
4
3
Category
Category_id
4
Name
Music
Kind
Kind_id
Helsinki, June 7th 2004
Name
1
POP
2
ROCK
3
CLASSIC
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
Helsinki, June 7th 2004
IAB Meeting