Your SlideShare is downloading. ×
0
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Web Services
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Web Services

294

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
294
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Web Services & SOA Get On The Right Course Steve Vinoski Chief Engineer, Product Innovation IONA Technologies, Waltham, MA USA
  • 2. Presented By Steve Vinoski Sean Flavin
  • 3. Real-world Enterprise Computing Source: Gartner
  • 4. Service-Oriented Architecture • SOA is a blueprint that governs creating, deploying, executing, and managing reusable business services – Services are the fundamental unit of the architecture – Services have well-defined interfaces, have encapsulated implementations, and can be accessed by users, applications, and services in a consistent manner no matter where they reside or how they were developed – A SOA defines guiding principles, artifacts, people/roles, processes, tools, etc. – A SOA enables the modeling of business problems in terms of services with reusable interfaces
  • 5. SOA Infrastructure • A SOA also defines the software infrastructure that allows different applications to interact – Allows IT systems to implement business processes, exchange data and execute transactions regardless of the technical platforms used by the underlying applications and IT systems • Good SOA infrastructure does not require replacement of existing technologies – Should be able to unite disparate systems and hide their differences
  • 6. The Goal: Business Services Service Consumer Service Provider Service Skeleton Service Proxy Service Contract Service Platform Service Service Service Contracts Registry/Lookup Proxies/Stubs Service-Level Service-Level Service-Level Data Model Security Management Service-Level Service-Level Multi-language QoS Comm Model bindings
  • 7. Realizing SOA with Web Services • Web Services are an economical way to build SOA – Cost-centric – largest IT cost is labor • Simple technology, short learning curve • Standards minimize the risk of vendor lock-in • Web services are inexpensive, no huge initial investment – Integration-centric • Instead of just doing yet another point-to-point integration between two applications, you can build a set of services that can be used by other applications in your enterprise – Business-driven • Web services can enable business-to-business (B2B) and business- to-consumer (B2C) trading and cooperation – Reuse-centric • Web services can easily wrap and thus enable reuse of existing computing services and applications
  • 8. Web Services compared to the Web • Web Services are not the same as Web pages or Web applications – No browsers, web servers, HTML, CGI, ASP pages, GUIs, etc. • Rather – exchange of XML documents between “co-operating” programs – Web Services technologies intended for program-to- program communications and interaction – Not human-to-web page communications
  • 9. Web Services Technologies Overview • XML Technologies – “Extensible Markup Language” – Base XML for documents – XML Schema for describing XML documents • SOAP – Formerly known as the “Simple Object Access Protocol” – How to format XML documents for transmission between applications • WSDL – “Web Services Description Language” – Defines all details about a service • UDDI – “Universal Definition, Discovery and Integration” – One way to advertise and discover services
  • 10. Participants in a Web Services Environment XML documents within SOAP messages defined by WSDL discovered via UDDI
  • 11. How will all of this work? A Web Services Infrastructure XML document Web Service WS Client XML document WS Server
  • 12. How will all of this work? A Web Services Infrastructure XML document Web Service WS Client XML document WS Server SOAP SOAP message SOAP Support SOAP message Support
  • 13. How will all of this work? A Web Services Infrastructure XML document Web Service WS Client XML document WS Server SOAP SOAP message SOAP Support SOAP message Support HTTP Support over network
  • 14. Web Service Technologies Relationships Deploy time Run time vs. Design Time Design and WSDL Specifies … Operations, Str Service ucture and Encoding Physical Communications Typing of And Transport of Endpoint Requirements: Messages Messages XML Schema SOAP execution Request Runtime Client E.g., Web XML Service HTTP SOAP Response
  • 15. What is the Web Service Server Doing? • The typical server pattern … – Wait on arriving XML documents contained within a SOAP envelope – Extract and analyze the document – Interact with other software components to complete the processing of the document – Optionally return another XML document in response SOAP server Database Request Web MQ SOAP Service Response CORBA
  • 16. From just using a Web Service to having a SOA Monolithic applications Application Application
  • 17. From just using a Web Service to having a SOA Monolithic Intermediate stage: applications Individual services broken out Application Application Application Application service service
  • 18. From just using a Web Service to having a SOA Monolithic Intermediate stage: Service-oriented applications Individual services broken out architecture Application Application Application Application Application Application service service service service service service service
  • 19. Benefits of service-oriented design (1) • More flexibility (“business agility”) – Assumption: business process logic and business rules are no longer buried inside applications – Result: • Since they are now explicit, processes can be changed easier • Existing services can be used in different contexts • Shorter time-to market for changed processes • Reduced cost of operation through consolidation – Assumption: Redundant functionality is eliminated – Result: • Fewer servers • Fewer licenses • Fewer assets to manage • Lower maintenance cost
  • 20. Benefits of service-oriented design (2) • Higher quality – Eliminating redundancy will reduce inconsistent data and inconsistent behavior – More transparency – Improved system architecture – easier to understand • Reduced risk, cost and complexity for development – Clean architecture reduced cost and risk – Increased developer productivity through reuse • Projects can leverage existing services – “Black box” reuse instead of copy&paste reuse • Lessen the dependencies on vendors – Service implementations can be replaced as long as interfaces stay the same – Services can be relocated from one platform to another – Services can even be outsourced to an external provider
  • 21. Benefits of service-oriented design (3) • Good service design (partitioning) will outlive your middleware or implementation technology – All you have to do is to put a wrapper around it, if required – Many mainframe systems today provide many useful services that should be made available to applications elsewhere in the enterprise • Commoditizing more and more parts of the IT infrastructure – Off-the-shelf infrastructure components are moving up the layers and coming closer to the application – Due to existing industry standards and available products, developers stop building this stuff themselves: • 1990: DBMS, TP Monitors • 1992: Networking stacks • 1995: CORBA, RPC Middleware, Reliable Messaging • 1998: Naming Service, Publish and Subscribe, Event Notification • 2000: Various J2EE Services
  • 22. Web Services and SOA Curriculum At A Glance Course Title Days Web Services and SOA Foundation Course for 1 IT Managers, Architects and Developers Web Services and SOA for IT Managers .5 Web Services and SOA for Architects 1 Web Services and SOA for Developers 2.5 Web Services and SOA Bootcamp 4
  • 23. Web Services and SOA Foundation Course Intro Standard Advanced Topic Area Why Web Services?  Web Services Technologies  Web Services Tools and Demos  SOA and Web Services  Web Services Design Aspects  Advanced WS Topics/Futures  Summary/References/Useful Links  Demos  Hands-On Exercise System
  • 24. Web Services and SOA for Managers Intro Standard Advanced Topic Area Why Web Services?  Web Services Technologies  Web Services Tools and Demos SOA and Web Services  Web Services Design Aspects Advanced WS Topics/Futures  Summary/References/Useful Links  Demos  Hands-On Exercise System
  • 25. Web Services and SOA For Architects Intro Standard Advanced Topic Area Why Web Services?  Web Services Technologies  Web Services Tools and Demos SOA and Web Services  Web Services Design Aspects  Advanced WS Topics/Futures  Summary/References/Useful Links  Demos  Hands-On Exercise System
  • 26. Web Services and SOA For Developers Intro Standard Advanced Topic Area Why Web Services?  Web Services Technologies  Web Services Tools and Demos  SOA and Web Services  Web Services Design Aspects  Advanced WS Topics/Futures  Summary/References/Useful Links  Demos  Hands-On Exercise System .NET or J2EE
  • 27. Web Services and SOA Bootcamp Intro Standard Advanced Topic Area Why Web Services?  Web Services Technologies  Web Services Tools and Demos  SOA and Web Services  Web Services Design Aspects  Advanced WS Topics/Futures  Summary/References/Useful Links  Demos  Hands-On Exercise System .NET & J2EE
  • 28. Common Training Scenarios Scenario Recommendation “I need to introduce an audience of •Web Services and SOA Foundation varying technical abilities to Web Course services.” •Or, run a series of audience specific classes “I need to train Managers in Web •Web Services and SOA for Managers services.” •Or, Foundation Course if time allows “I need to train Architects and/or •Web Services and SOA for Architects Business Analysts in Web services.” •If they want to work with the technology, could take one of the Developer courses “I need to train Developers in Web •Web Services and SOA for services.” Developers •Web Services and SOA Bootcamp
  • 29. Summary • The Web Services and SOA Bootcamp is being held from our Waltham, MA office from September 14-17, 2004. • Courses can also be delivered on-site at your location. • Complete course outlines are available at http://www.iona.com/training • If you need assistance, please call Amy Neveu at 781-902-8221 or send e-mail to training@iona.com. • Thanks for joining us today!
  • 30. Q&A

×