1. Fionn Murtagh Dimitri Zervas Pedro Contreras Royal Holloway, University of London Munich, 24 of June 2005 JXTA P2P, Web Services and WS-Talk

2. Why P2P? Scalable Decentralise Self-organised Performance Interoperable

3. Why JXTA? P2P organisation Set of language independent protocols Open source Active developers community Implementations in Java and C –Free, platform independent XML base Support for security protocols like SSL

4. How JXTA works? Protocols –P. Discovery P., P. Resolver P. (generic query), P. Information P. (net monitoring), Pipe Binding P. (addressable messaging), Rendezvous P. (propagation service), Endpoint routing P. Communication channel is called pipe Communication based in XML advertisement –Module class adv., Module specification adv., Module implementation adv., Pipe adv., Peer group adv., Peer adv.

5. JXTA / SOAP / WSDL Integration

6. JXTA and SOAP SOAP usually are put in HTML request/response and handle by a web server We want send SOAP messages using JXTA pipes –Some work had been done in “JXTA-SOAP” project using Apache Axís

7. JXTA and WSDL Advertise WSDL service in JXTA through a Module Specification Advertisement Module Specification Adv. (XML File) WSDL Service Description (XML File) …….. ……..

8. Current and Future Work Integration and Deployment JXTA/SOAP Integration and Deployment JXTA/SOAP/WSDL

9. Problems to tackle Determine search method in P2P context Libraries (we’d like to use standard libraries for web service) Ontology integration (We have to decide which standard RDF?, DAML-OIL?, OWL?, OWL-S? etc..)

10. Conclusion We have a pure JXTA P2P service registry working, then JXTA  JXTA/SOAP should work  (Based in kevin Burton, Daniel Elenius work) JXTA/WSDL should work  (Based in Daniel Elenius works) Where we are?