1 / 22

Web Services at the University of Wisconsin-Madison

Web Services at the University of Wisconsin-Madison. JA-SIG – December 8, 2003 – Miami, FL Jim Helwig Project Manager University of Wisconsin-Madison Division of Information Technology. Overview. Super Short Web Services (WS) Primer WS at UW-Madison Origins WS at UW-Madison Inventory

qabil
Download Presentation

Web Services at the University of Wisconsin-Madison

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 at the University of Wisconsin-Madison JA-SIG – December 8, 2003 – Miami, FL Jim HelwigProject Manager University of Wisconsin-Madison Division of Information Technology

  2. Overview • Super Short Web Services (WS) Primer • WS at UW-Madison Origins • WS at UW-Madison Inventory • Where do we go from here? • Other examples? *Disclaimer JA-SIG 12/2003 Miami, FL

  3. Super Short Web Services Primer • WS is a collection of standards for Web-based communication facilitating enterprise application interoperability • WS developed from the bottom up, building on existing technology • A collection of players play a role in developing WS standards, including W3C, OASIS, IBM, Microsoft and Sun JA-SIG 12/2003 Miami, FL

  4. The Web Services Stack • XML – eXtensible Markup LanguageImplementation independent, object oriented data representation • XML-RPC – XML Remote Procedure CallSimple data types over TCP/IP • SOAP – Simple Object Access ProtocolXML over HTTP, data and meta-data, header and body • WSDL – Web Services Description LanguageWS metadata, describes service, facilitates consumption JA-SIG 12/2003 Miami, FL

  5. The Web Services Stack (cont.) • UDDI – Universal Description, Discovery and IntegrationDirectories of WS, white/yellow pages • Security – authentication, authorization, digital signature, encryption, trust • Business Process – transactions, quality of service, workflow, coordination JA-SIG 12/2003 Miami, FL

  6. WS at UW-Madison Origins • Increasing demand for integration of disparate applications • Increased awareness of WS • Increased support of WS in tools • Bottom up, grassroots • Many different projects, approaches, no coordination or communication JA-SIG 12/2003 Miami, FL

  7. WS at UW-Madison Inventory JA-SIG 12/2003 Miami, FL

  8. ATS ↔ ATS • ATS – Academic Technology Solutions • Prod – Activity Creator, client-side Flash and Java application authoring standards-compliant activities + Using XML-RPC to allow improvedaccess to local disk JA-SIG 12/2003 Miami, FL

  9. UDS (LDAP) ↔ ADI • UDS – University Directory Service • ADI – Application Development and Integration • Dev – General authentication service + Abstracts implementation + Generic, easily extended - Working on security issues JA-SIG 12/2003 Miami, FL

  10. UDS (Oracle) ↔ UDS (LDAP) • Prod – Registry Synchronization • Prod – Listener looks for events registered in Oracle table, notifies other clients, clients retrieve and translate data as necessary (for LDAP, Novell eDirectory, text files) JA-SIG 12/2003 Miami, FL

  11. UDS (LDAP) ↔ WiscMail • WiscMail – Campus-wide email service • Prod – Admin tool for provisioning mail domains and accounts • Security – Custom Perl mod for authN/authZ using app name, IP, certs + Abstraction of a very messy combo ofLDAP schema and flat files JA-SIG 12/2003 Miami, FL

  12. UDS (LDAP) ↔ WiscCal • WiscCal – Campus-wide calendaring service • Dev – Admin tool for provisioning accounts + WSDL may help w/ tool integration, explicit enumeration of data types JA-SIG 12/2003 Miami, FL

  13. ISIS ↔ Learn@UW • ISIS – Student information system using PeopleSoft 8 Student Administration • Learn@UW – Course management system using Desire2Learn • Prod – Exchange of course registrationinfo using batch generated XML files • Future – PS8 XML w/ HTTP post toD2L listener • Future – Documentation service unitinginfo from D2L Web site, D2L app, UWauthored materials presented via WS JA-SIG 12/2003 Miami, FL

  14. APBS ↔ ISIS • APBS – Appointment, payroll and benefit system implement with Lawson • Dev – A manual process creates a data extract that is converted to XML used to load a database table that is in turn uploaded into PeopleSoft • Future – Replace with a more standards-based approach - Lack of vendor support JA-SIG 12/2003 Miami, FL

  15. ? ↔ My UW-Madison • My UW-Madison – Campus-wide portal • Prod – Various semi-static XML/XSLT feeds are retrieved via HTTP and incorporated into the portal • Future – SOAP, WS, WSRP • WSRP – Web Services for RemotePortals + Planned support by portal vendors JA-SIG 12/2003 Miami, FL

  16. Shibboleth ↔ ? • Pilot - Pilot making library electronic journal reports available to multi-institutional audience • Dev – Stable development environment • Future – Internet2 blog JA-SIG 12/2003 Miami, FL

  17. PASE ↔ ? • Populations, Affiliations, Services and Entitlements • Proposed campus-wide, standard authorization service • Future – WS interface JA-SIG 12/2003 Miami, FL

  18. PHIN ↔ PHIN • PHIN – Public Health Information Network • Prod – Data exchange, ex. Clinics → Researchers, State Lab of Hygiene → Hospitals • Prod – Lightweight Java/Tomcat process accessing proprietary DB, “flawless” for 1 ½ years • Security – 2-way certificate exchange • Future – Directory of shared data pools serving diverse groups and applications + SOAP provides detailed error messages JA-SIG 12/2003 Miami, FL

  19. FP&M ↔ FP&M • FP&M – Facilities Planning and Management • Prod – Fleet Reservations • Prod – Abstraction of data access and biz logic • Security – IP restriction • ex. makeRez(info) → rez# or failure info • Future – Easier integration w/ portal + Flexibility of consumers + Centralized DB access (drivers issues) + Organized, “Data with meaning” + Allows transparent relocation JA-SIG 12/2003 Miami, FL

  20. Where do we go from here? • WS Special Interest GroupLoose group of developers, currently DoIT but planning on opening up to all of campus • Access to Data ProjectCross-campus group trying to facilitate data exchange between enterprise applications, considering WS • UW-System Common Systems Interoperability Architecture Working GroupRecommend and support best practices, architectures and tools that support interoperability between information systems across the UW system, considering recommending service oriented architecture, considering WS JA-SIG 12/2003 Miami, FL

  21. Summary • WS started bottom up • WS use at UW-Madison started bottom up • Numerous projects by multiple groups using various pieces of WS stack in various states of planning/development/deployment • Communication and coordination is increasing • WS use is gaining momentum JA-SIG 12/2003 Miami, FL

  22. Questions?Other examples of WS use? Jim Helwig: jim.helwig@doit.wisc.edu DoIT Web site: http://www.doit.wisc.edu My UW-Madison: http://my.wisc.edu JA-SIG 12/2003 Miami, FL

More Related