1 / 9

Navigating SOA and Web Services at UChicago: Strategies and Experiences

This piece explores the implementation of Service-Oriented Architecture (SOA) at the University of Chicago, emphasizing the importance of Web Services (WS) in addressing integration challenges. It discusses the benefits of loose coupling, identifier translation, and account management, as well as early experiences with WS and Identity Management. The text outlines strategic considerations for designing WS interfaces, securing implementations, and optimizing data services. Additionally, it highlights the role of collaboration in fostering effective data stewardship and the technology infrastructure necessary for successful SOA deployment.

avi
Download Presentation

Navigating SOA and Web Services at UChicago: Strategies and Experiences

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. SOA Baby Steps Tom Barton University of Chicago

  2. U Chicago & SOA • No Big App dropping it on us, yet • Wanna be prepared though • Web Services seems like a good approach to solving some problems • Loose coupling: interfaces are at high enough level to enable client & server technologies to evolve independently • Language neutral • Range of integration: batch to latest application designs • Early experiences with WS & Identity Management • Even a trivial SOA, with just 1 S, can be powerful

  3. WS & Identity Management • Identifier translation • Translate among ChicagoID, SSN, NetID, hospital employeeID, alumID, studentID, ISO, (RFID) • Facilitate conversion from SSN to ChicagoID in Systems of Record and downstream systems • Client: CLI to add/translate identifiers in batch flows in transit • Account management • Register usernames in multiple namespaces • Avoid assigning conflicting usernames • Client: VBscript to coordinate UC Hospital’s account management with rest of UC’s

  4. Net of early experience • Service contract: WS interfaces package high level functions and objects • Independent from underlying relational structure and implementing code • Loose coupling • Good division of labor • In-memory RDBMS to optimize batch performance

  5. Data Services • Data flow problems • Long history of point-point custom batch interfaces • Hard to steward • Hard to upgrade SoRs • Hard to get new flows • Narrow data query service led to even more data copying • Strategy: data delivery as a service • Combination of reporting & WS capabilities • Business Intelligence Services is front office • Data Stewardship program for policy and implementation support

  6. Services of Record (Allstate)

  7. Steps Towards Our First SOA • Look for cowpaths in institutional data • Choose WS’s to reinforce a common data model across systems • Technology choices • Infrastructure: servlet platform, ESB • Development framework • Organizational choices • Providers, Consumers, Implementers, Policy-setters

  8. Designing Grouper’s WS Interfaces • It takes 4 WS interface styles to please enough Grouper adopters • How many styles will you need for your Web Services?

  9. Securing Grouper WS • WS adds a tier to your environment • What needs will you have, and what options available, for securing your WS implementations? • How distributed will your WS clients be? • What principals should act in the back-end? • Are some WS’s more like a web application, others more like a traditional interface?

More Related