The five most asked questions about WSRR

1. The five most asked questions about WSRR Tim Griffith Performance Lead, WSRR tim.griffith@uk.ibm.com WSRR – Common Questions

2. Agenda • What is a Service Registry? • Why not just use UDDI? • Compliance and Interoperability – where does WSRR stand? • Developed as an ‘Agile’ approach – what does that mean for us? • How do I get involved? • Your questions WSRR – Common Questions

3. Calc + - * / What is a Service Registry? – Layman's terms SOA Traditional fixed infrastructure Scenario WSRR – Common Questions

4. Calc + - * / What is a Service Registry? – Layman's terms SOA(2) Traditional fixed infrastructure Scenario – service upgrade /v2 WSRR – Common Questions

5. Calc + - * / ( ) What is a Service Registry? – Layman's terms SOA(3) Traditional fixed infrastructure Scenario – service rollout WSRR – Common Questions

6. Calc / ( ) Service Registry What is a Service Registry? – Layman's terms SOA(4) SOA – runtime + - * /v2 Enterprise Service Bus WSRR – Common Questions

7. Service Registry What is a Service Registry? – Layman's terms SOA(5) SOA – Service Lifecycle Calc + - * / Enterprise Service Bus Design Calc v2 ( ) /v2 Development Production retired WSRR – Common Questions

8. Why not just use UDDI? • Currently the Only standard for a Service Registry • Designed by a very large group of companies • Used as the backing standard for the “Universal Business Repository (UBR)” • Discontinued in 2006 • Post mortem of the UBR • Three distinct areas of weakness • Model • Query support • Security • Despite claims to the contrary UDDI standard definitely tailored to the global concept (UBR) • Not so applicable for the single organisation service organisation and management • Various important parts of the standard, undefined or open to speculation • User defined taxonomies • Vendor specific implementation • The UDDI Standard becomes its own legacy • Must be backwards compatible with previous versions • Fundamental issues in the standard cannot be addressed • Model structure is deliberately inflexible WSRR – Common Questions

9. wsdl : portType wsdl : message wsdl : types Why not just use UDDI? – Content model • UDDI has four internal structures • Business • BusinessService • BindingTemplate • TModel • Maps to WSDL as follows • Primary focus is on the endpoint • What about WS-Policy? • SCA? • Restful service definitions? wsdl : service wsdl : port wsdl : binding WSRR – Common Questions

10. Why not just use UDDI? - Querying • Queries in UDDI can be over any of the four types • Since UDDI v3 the query language has been enhanced to support with inner queries • Inner queries can only be conducted on tModels • tModels cannot support inner queries • Inner queries are for dynamic provision of the tModelBag selector • Those with no results break the outer query – by specification • Operation of the UDDI query comes in two forms • Interactive “Browse” form; constantly refining down • “retrieve to evaluate” pattern • Neither pattern effective for runtime consumption • What information does a service invocation contain? • Message types (input and expected output) • Number of messages • Service name • Is service name enough? – unlikely • What WSRR does… • ‘XPath like’ open query format: • Can traverse as much or as little of the model as required • /WSRR/WSDLService[@name=“myService”]/ports[@binding(.)/classifiedByAllOf(‘a’)] • Supports querying over User Modelled definitions as well • Provides both property and graph queries • Fast queries across large datasets with property queries • Variable depth datagraph queries to depths 0, 1 and -1 WSRR – Common Questions

11. Why not just use UDDI? – Security / Access • UDDI access control designed primarily to: • Give very open access to “read” operations • Very restrictive access to publish / modification operations • This caused problems with the UBR • Difficult to maintain user published service definitions • Explicit published user required to modify their services • Extremely coarse (all or nothing) access control • What WSRR does… • Role based access control • Users can be associated with multiple roles • Permissions defined at the role level • Fine grained access control • Can restrict access to subparts within the object structure • Very flexible mechanism requiring fewer explicit rules WSRR – Common Questions

12. Compliance and Interoperability? • is Service Registry J2EE compliant? • Yes, but uses proprietary platform features of the WebSphere Application Server • Currently cannot be deployed on other application servers • Proprietary Interactions only? • When WSRR v6.0.0 released; yes • v6.0.2 introduced synchronization to UDDI • IBM UDDI v3 ships with WSRR • Can be used as an effective UDDI interface to WSRR data • Architects keen to work with the community to develop the next generation of service registry • High priority objective to comply with the new standards • John Colgrave, senior architect contributed to the UDDI standard and wrote the current Technical note as to representation of WSDL information. • What WSRR does offer • Consumable as a Web Service (SOAP) • RESTful interface for query / retrieve functionality • Proprietary simple Java API using SDO type objects • User model and taxonomy definitions in OWL DL (with a few restrictions) WSRR – Common Questions

13. Developed as an ‘Agile’ project • Does the ‘Agile’ development process effect us? • Yes! • Traditional software delivery pattern does not really apply • New function delivered frequently in major releases • Fix packs are purely for corrections • Can be a bit of a system shock for customers! • Allows highly responsive feature development • Keeps focus on what’s important: customer features • Developed in monthly iterations • Release consists of several monthly deliverables • Codebase is regularly solidified • Many of the monthly deliverables are exposed to the EAP • More of an explanation due later • Allows constant re-evaluation of priorities • Other products that integrate with WSRR can test integration with new releases throughout the development cycle WSRR – Common Questions

14. Project started 11/05 Shipped 09/06 Well received, but noted there was no HA, no standards compliance Shipped 05/07 Clients requests now focused on ease of use (consumability) Shipped 12/07 V6.1 Release started 06/07 Developed as an Agile Project (2) • A Brief history of the WSRR project: V6.0.0 V6.0.2 Release started 10/06 2007 2008 2006 WSRR – Common Questions

15. Where / how can I get started? • ‘Try before you buy’ • We have an ‘Early Access Program’ (EAP) • Allows access to monthly drops of the in development WSRR • Provides a forum for interaction with the Architects, Developers and project managers. • Gives us the opportunity to • The only condition is signing an NDA • Technical briefings • Mostly conducted at Hursley • Aim at giving not just executive level pitches but also exposure to the development team • PoC activity • Strong Technical Sales team drive to show WSRR in the SOA environment • Support WSRR – Common Questions

16. your questions… WSRR – Common Questions