1 / 89

Escaping the Legacy Jungle

Escaping the Legacy Jungle. XML and Web Services in Digital Government. Today’s Speakers. Dave McComb, Semantic Arts Sanjeev Batta, Coraxis Corporation Todd Shelton, Netdesk Corporation Rick Cook and Paul Piper, TAAG, Web Services Subcommittee. Agenda.

tovi
Download Presentation

Escaping the Legacy Jungle

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Escaping the Legacy Jungle XML and Web Services in Digital Government

  2. Today’s Speakers • Dave McComb, Semantic Arts • Sanjeev Batta, Coraxis Corporation • Todd Shelton, Netdesk Corporation • Rick Cook and Paul Piper, TAAG, Web Services Subcommittee

  3. Agenda • Dave McComb: Web Services and Legacy Apps: A Marriage of Convenience? • Sanjeev Batta: Service Oriented Architecture • Todd Shelton: Getting to Web Services • Rick Cook and Paul Piper: Web Services TAAG

  4. Web Services and Legacy Apps:A Marriage of Convenience? Dave McComb Semantic Arts, Inc www.semanticarts.com (970) 490-2224

  5. Three responses • What’s one more string? • Cutting the Gordian Knot/ Starting over • Untangling the mess, a bit at a time

  6. Frustration • Being a systems person these days is frustrating • Everything takes many times longer than we know it could, because we have to deal with the spiderweb of existing interconnections

  7. Before we get to the answer • How did we get in this situation? • Mostly through a series of ad hoc decisions about what things mean, and how systems should communicate • How do we get out? • This will require some leadership above the project level to determine the language systems should use to talk to each other • It requires renegotiating new agreements between systems • This presentation is about…

  8. Hope • New technology • New approaches • New methods and with hope comes…

  9. Buzzwords • XML • Message Oriented Middleware • Web Services

  10. The Distinctionary • Is: a glossary • Is distinct from other glossaries: structurally each definition first specifies what the more general type of thing the word is, and then provides a way to distinguish this thing from others that are similar.

  11. XML • Is: a markup language <person> Dave McComb </person>

  12. XML • Is distinct from other markup languages: by allowing tags that at least have some hope of being Semantic html for instance <H1> Dave McComb </H1> <H1> Fido </H1>

  13. What makes XML interesting and potentially useful for us • Preserves context and structure • Document/ Message duality • Potential for application to application communication But for the most compelling factor in XML’s future success…

  14. The Final Jeopardy Answer 4’ 8 ½”

  15. What is how far I can throw someone I don’t trust?

  16. What was the adult height of Neanderthal man?

  17. What is the distance between North American standard gauge RR tracks, and a good analogy for the reason for XML’s coming ubiquity?

  18. MOM (Message Oriented Middleware) • Is: Infrastructure Software • Is distinct from other infrastructure software: in that it allows you to send messages between applications without necessarily knowing the identity or location of the other application, and without necessarily waiting for a response.

  19. Other Interesting Things About MOM • Promotes asynchronicity • Promotes loose coupling • Allows broadcast of messages & multiple use of messages • Opens up many avenues for redundancy and parallel conversions

  20. Web Service • Is: A way to invoke functionality remotely • Is distinct from other ways to invoke functionality remotely: in that it allows you to express the calling arguments in XML over the internet.

  21. Other Interesting Things About Web Services • Exposing your API as XML • Unaffected by many changes to invoking message • SOAP allows inter-machine calls, even through firewalls • Easy to set up and use

  22. Web Service“show me” • Normally, there is nothing to show • It’s systems integration, when it works you don’t see it • Mostly behind the firewall • But here is a pretty public example

  23. “If Amazon were as easy to use as Google” www.mockerybird.com

  24. I type my search into mockerybird’s site, they then call amazon through their web service

  25. Mockerybird then reformats the returned results. I then add one of these books to my “list”

  26. Zoom in on “Your List” my selected item immediately shows up… I click checkout

  27. I get a summary, and some options, including buying from Amazon

  28. I’m at amazon’s site now (new window) and the book I selected from Mockerybird is right in with my other amazon selections!

  29. Two ways to think about web services • From the consumers standpoint • And from the producers standpoint

  30. Web Services, from the providers standpoint • You have a value added service, you’d like to make it available to the widest possible audience • You might want to charge for this privilege • Maybe something as simple as reporting air quality at a certain location, or most recent outbreaks of west nile virus. • Maybe it’s supplying 9 digit zip codes for addresses.

  31. Web services from the consumers standpoint • What additional information would you like to make available at the point of consumption? • What additional services would you like to make available?

  32. EAI, Portals and Composite App • There are three main points of consumption for Web Services: • EAI • Portals • Composite Apps

  33. Finding and Negotiation with a Web Service UDDI WSDL SOAP

  34. Some Example Web Service(very fine grained) • Calculation • Currency Conversion • Email validation

  35. Some Example Web Service(medium grained) • Immigration status • Language Translation (gist) • Issue Line of Credit • Immunization Requirement for Travel to Foreign country

  36. Some Example Web Services (coarse grained) • Outbound Correspondence • Imaging • Accounts Receivable • Auditing • Abstracting

  37. Some Example Web Services (very coarse grained) • Contact management • Payroll

  38. Strategies for taking advantage of this trend • Message Enable your legacy systems • Publish Services that will add value and help you at the same time (ZIP +4) • Implement Portals and Composite Apps with • Internal Services, and • Optional external services

  39. Untangling Gulliver XML Message Bus Web Service or other Adapters

  40. Compelling reason to get on the Web Services Bandwagon • Freedom – from the legacy bonds of confinement • Economics – it’s far cheaper to build systems this way • Looking good – this will be the measure of eGov success in the future • Not looking bad – avoid having to explain why you can’t do this

  41. Thank you If you have questions, or would like additional copies of this material, feel free to contact me: Dave McComb Semantic Arts (970) 490-2224

  42. Service Oriented Architecture Sanjeev Batta Coraxis Corporation Sanjeev@coraxis.com

  43. Industry Projections • IBM • “Web Services will be bigger than Java or XML” – Rod Smith, VP of Emerging Technology, IBM • Forrester Research • By 2003, the market for software components used to build services will represent a $14.5 billion industry. • Gartner Group • Within the next 4 years, 60% of all new business applications will utilize a service-oriented architecture • By 2004, 40% of financial services transactions and 35% of online government services will be web service-based

More Related