1 / 15

Jim Farmer As presented at the Common Solutions Group Meeting May 9, 2002 Chicago, Illinois

Web Services: A Perspective. Jim Farmer As presented at the Common Solutions Group Meeting May 9, 2002 Chicago, Illinois. Web Services defined. An information technology architecture for the exchange of business messages using open-standards. The business case.

louise
Download Presentation

Jim Farmer As presented at the Common Solutions Group Meeting May 9, 2002 Chicago, Illinois

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. Web Services: A Perspective Jim Farmer As presented at theCommon Solutions Group Meeting May 9, 2002 Chicago, Illinois

  2. Web Services defined An information technology architecture for the exchange of business messages using open-standards.

  3. The business case • Originally, the exchange of data with others. • Now, integration between disparate application, disparate computer systems, disparate operating systems, disparate programming languages—the Enterprise Application Integration EAI bus. ___________________________________________ ”Getting access to stove-piped data is the primary reason for implementing Web services.” Uttam Nasrsu GIGA Information Group At the FSA CIO Update Conference Arlington, Virginia, May 8, 2002

  4. EDI and Web Services compared

  5. The standards • Data XML • Validation Schema • Transport SOAP (real-time) SMTP (batch) • Security SAML • Description WSDL • Directory UDDI • Transformation XSLT Note: Message content is not defined by any of these standards.

  6. Industry content standards

  7. In higher education • Digital library search and retrieval (Columbia, Cornell) • Transcripts (California Community Colleges, Florida, Arizona, Ohio) • Student Aid (NCHELP, U.S. Department of Education) • Security (Internet 2 Shibboleth) • Portals (JA-SIG)

  8. Process content standards

  9. Why XML and SOAP? “[XML and SOAP] will become a widely implemented ‘standard’ because they are simple.” Barry Walsh University of Indiana at the FSA CIO Update Conference Arlington, Virginia May 8, 2002

  10. Typical SOAP implementation HTML over HTTP SOAP over HTTPS College Target Data Provider Access Provider

  11. Meteor prototype model Web Services HTML Meteor XML Student Access Provider Data Provider

  12. Meteor Channel in the uPortal

  13. Authentication and authorization TLS Authentication Login & Password SAML Assertion College Target Data Provider Access Provider ebXML Security Profile 3 Non-persistent confidentiality and non-persistent authentication

  14. Building web services • Web services architecture overview 2 find UDDI Service Web service requestor look up web service 3 bind 4 call Call Web Service 1 publish Retrieve WSDLDefinition Register Web Service(at development time) Web service provider WSDL Document

  15. The End Jim Farmer instructional media + magic, inc. jxf@immagic.com

More Related