Types of Web Services and Their Components

(1)

Lehrstuhl Informatik V (Informationssysteme) Prof. Dr. M. Jarke Satish Srirama Matthias Jarke Wolfgang Prinz Mobile Web Services Mediation Framework Mobile Web Services Mediation Framework Satish Srirama Matthias Jarke Wolfgang Prinz

Mobile Web Services Mediation

Framework

(2)

Lehrstuhl Informatik V (Informationssysteme) Prof. Dr. M. Jarke Satish Srirama Matthias Jarke Wolfgang Prinz Mobile Web Services Mediation Framework Mobile Web Services Mediation Framework

Outline

z

Mobile Host

z

Mobile Host: QoS extensions

z

Mobile Host in P2P networks

z

Mobile Web Services Mediation Framework

z

Realization of MWSMF

(3)

Mobile Host

z Wireless developments

z Mobile web services [LA, OMA]

z Mobile web service provisioning z Implementation details – Implemented in PersonalJava – Uses kSOAP2 – SOAP over HTTP – Upgraded to J2ME z Performance analysis

– Acceptable performance levels for service delivery – The WS processing time at the Mobile Host (< 10%) – Directly proportional to achievable transmission rates – High data transmission rates with 3G & 4G

WS WS Service Requester WSDL SOAP UDDI Registry Mobile Host Find Refers Describe Publish WS WS Service Requester WSDL SOAP UDDI Registry Mobile Host Find Refers Describe Publish

(4)

Mobile Host QoS extensions –

Security issues

z

Security breaches

z

End-to-end security

z

Security Standards for web services

– XML Encryption [W3C]

– XML Signature [W3C]

– WSSE (WS-Security Standard) [OASIS]

– SAML (Security Assertion Markup Language) [OASIS]

z

Adaptability of WSSE for mobile web services

(5)

Security results

z Confidentiality & Integrity can be provided for reasonable

message sizes of 2kb

z Extra time to the WS invocation cycle is ~ 2 sec with

Confidentiality

z Integrity latency is 2 sec

z Signing on top of encryption ~3.5 sec

z Best scenario (Highly secured and better performance)

– AES-256 Symmetric key encryption

– RSA 1024 bit key exchange

– RSAwithSHA1 signature

(6)

Mobile Host QoS extensions –

Scalability issues

z Scalability aspects

– To achieve less data to transmit

y Significant for Mobile Host

y Transmission time constitutes 90% of invocation cycle latency

– Improves battery life

z Size of MWS message

B_msg = B_tp + B_mtp + B_soap + B_app

z Minimal encoding is not always the best option

z XML Compression

– XMill [Liefke and Suciu, 1999]

– Fast Infoset [Sandoz et al., 2004]

(7)

Scalability analysis

z

BinXML

[Ericsson and Levenshteyn, 2003]

– XML tags replaced by Unique byte value

– 6 reserved bytes (0x00-0x03, 0xFE, 0xFF)

– Effective for SOAP messages

z

Analysis

– BinXML enabled MH

– Message size 5 kb

– ~ 15% gain (1.3 sec)

z

MWS compression gain:

T_mwscg = δT_reqt + δT_rest − T_reqenc − T_reqdec − T_resenc − T_resdec

Comparision of mobile web service invocation times with and without BinXML compression

9297 691 0 8606 7964 1205 240 6519 0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000 Total time at client Server processing time Client processing time Transmission time Ti m e i n M il li s e c onds WithoutBinxml WithBinxml

(8)

Mobile Host in JXTA network

z Technical advantages to Mobile Host

– Eliminating the need for Public IP

– Better identification/access mechanisms (Peer ID) – Better service discovery

BTS1

BTS2 BTS3

JXTA Super peer (Relay & Rendezvous) JXTA Relay peer JXTA Rendezvous peer JXME edge peer JXME edge peer JXME edge peer JXTA Rendezvous peer JXTA Network WS WS WS WS WS WS WS WS JXME edge peer WS WS WS WS

Mobile Operator Network

Virtual P2P Network

BTS1

BTS2 BTS3

JXTA Super peer (Relay & Rendezvous) JXTA Relay peer JXTA Relay peer JXTA Rendezvous peer JXTA Rendezvous peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXTA Rendezvous peer JXTA Network JXTA Rendezvous peer JXTA Rendezvous peer JXTA Network WS WS WS WS WS WS WS WS JXME edge peer WS WS WS WS

Mobile Operator Network

(9)

Mobile web service discovery issues

z Web service discovery

z Huge number of services are possible with Mobile Hosts z Centralized UDDI not the best solution

– Problems with bottlenecks

z Mobile nodes are dynamic

– Binding information changes regularly

– Services are to be published again and again

z Dynamic service discovery mechanisms

– Announce listen model (e.g. Jini)

– Distributed P2P WS registry (VISR) [Dustdar and Treiber, 2006]

– Konark [Lee et al., 2003]

(10)

Mobile web services discovery

z Publishing mobile web services in JXTA / JXME

– JXTA Modules

– Life time of advertisements

z MSAs advertise mobile web services

z Discovery of MSAs with name & description

– Works, but not very precise

Module

Implementation

Advertise a platform specific implementation

Module Specification

Advertise how to access a Service

(API, messages)

Module class

Advertise the existence of a service Module Implementation Advertise a platform specific implementation Module Specification

(API, messages)

Module class

Advertise the existence of a service UDDI Registry Service Interface Service Implementation WSDL Module Implementation Advertise a platform specific implementation Module Specification

(API, messages)

Module class

Advertise the existence of a service Module Implementation Advertise a platform specific implementation Module Specification

(API, messages)

Module class

Advertise the existence of a service UDDI Registry Service Interface Service Implementation Service Interface Service Implementation Service Implementation WSDL <jxta:MSA> <MSID> . . . </MSID> . . . <Parm> <WSDL> . . . <WSDL> </Parm> . . . </jxta:MSA>

(11)

Advanced mobile web service

discovery

z Categorization using MCA

z MCAs simulate Category bags & tModels in UDDI z Peer Groups simulate business groups

z Post-filtering of mobile web services

– Search can also extend to WSDL information

– Search should be based on weight of keywords

– Apache Lucene tool

y Based on indexing

– Advanced Matching of Services (AMS)

z Context-aware service discovery [WSTalk]

– To achieve very precise results

(12)

Mobile Web Services Mediation

Framework

z

How to integrate mobile web services and P2P

domains taking care of QoS?

BTS JXTA Super peer JXTA Relay peer JXTA Rende-zvous peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer Virtual P2P Network BTS JXTA Super peer JXTA Relay peer JXTA Rende-zvous peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer Virtual P2P Network MWSMF _UDDI WS Accessible to IP network QoS Provisioning BTS JXTA Super peer JXTA Relay peer JXTA Rende-zvous peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer Virtual P2P Network BTS JXTA Super peer JXTA Relay peer JXTA Rende-zvous peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer Virtual P2P Network MWSMF _UDDI_UDDI WS Accessible to IP network QoS Provisioning BTS2 BTS3 BTS2 BTS3 Internet Internet WS Client JXTA Network JXTA Rende-zvous peer JXTA Rende-zvous peer BTS JXTA Super peer JXTA Relay peer JXTA Rende-zvous peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer Virtual P2P Network BTS JXTA Super peer JXTA Relay peer JXTA Rende-zvous peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer Virtual P2P Network MWSMF _UDDI WS Accessible to IP network QoS Provisioning BTS JXTA Super peer JXTA Relay peer JXTA Rende-zvous peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer Virtual P2P Network BTS JXTA Super peer JXTA Relay peer JXTA Rende-zvous peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer JXME edge peer Virtual P2P Network MWSMF _UDDI_UDDI WS Accessible to IP network QoS Provisioning BTS2 BTS3 BTS2 BTS3 Internet Internet Internet Internet WS Client JXTA Network JXTA Rende-zvous peer JXTA Rende-zvous peer JXTA Network JXTA Rende-zvous peer JXTA Rende-zvous peer

(13)

MWSMF realization

z

Why Enterprise service Bus (ESB)?

– Any SOA should be sufficient for the purpose

– Web services are best means of realizing SOA

– Latest developments in web services domain

z

Enterprise service Bus (ESB)

– “Enterprise Service Bus provides a set of infrastructure capabilities, implemented by middleware technology, that enable the integration of services in an SOA” [Gartner, Inc.]

z

Java Business Integration (JBI)

(14)

MWSMF - Components

Internet Internet

WS Client _Internet_Internet_Internet_Internet WS Client MWSMF HttpReceiver Broker XSLT Transformer ContentBased Router HttpInvoker N o r m a li z e d M e s s a g e R o u t e r QoS Verifier SAAJBinding P2PMapper Context Engine Binary Transformer Mobile Host WS WS Mobile Host WS WS Internet Internet

WS Client _Internet_Internet_Internet_Internet WS Client MWSMF HttpReceiver Broker XSLT Transformer ContentBased Router HttpInvoker N o r m a li z e d M e s s a g e R o u t e r QoS Verifier SAAJBinding P2PMapper Context Engine Binary Transformer Mobile Host WS WS Mobile Host WS WS

(15)

Message flows in MWSMF

z Supplementary features of MWSMF

– Hosts a UDDI registry

– Supports automatic startup of Mobile Hosts

y PushRegistry feature of WMA

HttpReceiver Broker HttpInvoker N M R Binary Transformer Mobile Host WS WS Mobile Host WS WS Internet MWSMF 1 2 3 4 5 6 7 8 9 10 11 12 JBI Container HttpReceiver Broker HttpInvoker N M R Binary Transformer Mobile Host WS WS Mobile Host WS WS Internet Internet MWSMF 1 2 3 4 5 6 7 8 9 10 11 12 JBI Container

(16)

Performance evaluation of MWSMF

z ApacheBench load generator

z Established on a laptop

z Successful in handling 110 concurrent requests z Mean value of handling a client ~ 130 ms

z Evaluation proved that MWSMF can handle large number of

concurrent clients Time-Diagram 0.00 5,000.00 10,000.00 15,000.00 20,000.00 25,000.00 30,000.00 35,000.00 10 30 50 70 90 ₁₁0 ₁₃0 ₁₆₀ ₂₀0 ₂₄0 ₂₈0 No of concurrent requests Ti m e t o ha n dl e s ingl e c li e nt ( m s ) Time TPS-Diagram 0 2 4 6 8 10 12 14 16 10 30 50 70 90 ₁₁0 ₁₃₀ ₁₆0 ₂₀₀ ₂₄0 ₂₈0 No of concurrent requests T ra n sact io n s p er sec o n d ( T P S ) TPS

(17)

Conclusions

z QoS aspects for MWS are discussed

z Alternatives for mobile web services discovery are identified z Architecture, features and realization details of MWSMF are

identified

z Discussed mobile web service message optimization

scenario

z Evaluation proved MWSMF deployment scenario is feasible

z Remaining components of the MWSMF are to be realized

– P2P Mapper

– ContextEngine

(18)

Lehrstuhl Informatik V (Informationssysteme) Prof. Dr. M. Jarke Satish Srirama Matthias Jarke Wolfgang Prinz Mobile Web Services Mediation Framework Mobile Web Services Mediation Framework Thank you