1. Web Service Implementation Maitreya, Kishore, Jeff

2. 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

3. Why Web-Services? Interoperability Reuse Ubiquitous Flexibility of wrapping the service to customize as per needs Easy application integration

4. 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.

5. Supported Specifications Web Services Definition Language (WSDL) Version 1.1 Apache SOAP Version 2.3 Universal Description, Discovery, and Integration Version 2.0

6. Web services on WebSphere (WoW) Service Provider Service Broker Service Requestor publish bind find

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

8. Web services on WebSphere (WoW) Service Provider Service Broker Service Requestor bind find Description WSTK’s java2wsdl Generate Stub WSTK’s wsdl2java Description publish

9. 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

10. 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 ****** Service Registration Service Discovery Service Request Response Parallel Instances

11. 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 WSDL Document Soap Request Response Socket Communication Strauss server UDDI Request WSDL Document

12. 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

13. Phrap Execution Time No. of input ESTs No. of output ESTs (contigs + singlets) Execution time (min) 2,0001,4411.5 5,0003,2773.25 10,0005,07615 20,0009,405~50 50,000…150

14. Service Provider Phrap Service Phrap Service Phrap Service Phrap 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

15. 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