Web Services Phraping Implementation

thingyvirginiaInternet και Εφαρμογές Web

30 Ιουλ 2012 (πριν από 4 χρόνια και 10 μήνες)

373 εμφανίσεις

Web Service
Implementation

Maitreya, Kishore, Jeff

Objective


Creating a web
-
service to exploit and get a
better understanding of the Web Service
Architecture


Learn the usage of SOAP, WSDL and UDDI


Perform coordination among parallel services


Exploit the feature of parallel processing to
simplify an otherwise very time
-
taking task of
running “phrap” on a chicken EST file

Why Web
-
Services?


Interoperability


Reuse


Ubiquitous


Flexibility of wrapping the service to
customize as per needs


Easy application integration

Tools in WebSphere for Web
Services development


Discover
. Browse the UDDI Business Registries to locate existing
Web services for integration.


Create or Transform
. Create Web services from existing artifacts,
such as Java beans, enterprise beans.


Build
. Wrap existing artifacts as SOAP and HTTP GET/POST
accessible services and describe them in WSDL. Assists in
generating a Java client proxy to Web services described in WSDL


Deploy
. Deploy Web services into the WebSphere Application
Server.


Test
. Test Web services running locally or remotely in order to get
instant feedback.


Publish
. Publish Web services to a UDDI v2 Business Registry.

Supported Specifications


Web Services Definition Language
(WSDL) Version 1.1


Apache SOAP Version 2.3


Universal Description, Discovery, and
Integration Version 2.0

Web services on WebSphere
(WoW)

Service Provider

Service Broker

Service Requestor

publish

bind

find

Web services on WebSphere
(WoW)

Service Provider

Service Broker

Service Requestor

publish

bind

find

Publish

Uses IBM’s UDDI 4J

Enquiry

Uses IBM’s UDDI 4J

Discovery

Web services on WebSphere
(WoW)

Service Provider

Service Broker

Service Requestor

bind

find

Description


WSTK’s java2wsdl

Generate Stub


WSTK’s wsdl2java

Description

publish

Web services on WebSphere
(WoW)

Service Provider

Service Broker

Service Requestor

bind

find

Request
-
Response

publish

Apache Proxy

Generated from WSDL

Apache SOAP

rpc router

Message router

Apache SOAP 4J

Java based SOAP API

Purposed Architecture

Web Service

Provider

(WebSphere

Appication server)

UDDI Registry

Containing service

Description of Phrap

Web service

Web Browser

Containing Client Stub

Of the Web service

Phrap WebService

Phrap WebService

Phrap WebService

*

*

*

Service Registration

Service

Discovery

Service Request

Response

Parallel

Instances

Implemented Architecture

Web Service

Provider

(WebSphere

Appication server)

UDDI Registry

Containing service

Description of Phrap

Web service

Web Browser

Containing Client Stub

Of the Web service

Phrap Service

Phrap Service

WSDL Document

Soap Request

Response

Socket

Communication

Strauss server

UDDI

Request

WSDL

Document

Problem Encountered


Software Unavailability


Websphere Server


Unix version


Phrap


Windows Version


Implementation problems


Communication between Windows and Unix
using Sockets


Resource constraints on strauss


Inability to do socket communication between
ece/eecis machines and localhost

Phrap Execution Time

No. of input
ESTs

No. of output ESTs

(contigs + singlets)

Execution
time (min)

2,000

1,441

1.5

5,000

3,277

3.25

10,000

5,076

15

20,000

9,405

~50

50,000



150

Service

Provider

Phrap

Service

Phrap

Service

Phrap

Service

Phrap

Service

*

*

*

Service

Provider

23 instances
Phraping

20,000 ESTs
each

Service

Provider

Service

Provider

23 chunks of

20,000 ESTs

23 chunks of

~12,000 ESTs

23 instances
Phraping

~12,000 ESTs
each

Phrap

Service

Phrap

Service

Phrap

Service

Phrap

Service

*

*

*

23 chunks of

~5,000 ESTs

Phrap

Service

Phrap

Service

Phrap

Service

Phrap

Service

*

*

13 instances
Phraping

10,000 ESTs
each



~50 mins

~25 mins

~15 mins



∑ = ~200mins

Conclusions


We could substantially reduce the time
required to phrap a chicken EST file, by
parallel execution of multiple instances of
phrap Web Service.


Web Service interface provides an easy,
interoperable and reusable application


User is unaware of the underlying
complexity of the architecture involved