investigating service oriented architecture (soa)
DESCRIPTION
Investigating Service Oriented Architecture (SOA). University of Washington October 25, 2007. Who are we?. Tony Chang, Computing and Communications Erik Lundberg, Computer Science and Engineering Todd Mildon, Office of the Registrar Scott Stephenson, Office of Information Management. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/1.jpg)
Investigating Service Oriented Architecture
(SOA)University of Washington
October 25, 2007
![Page 2: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/2.jpg)
Who are we?• Tony Chang, Computing and Communications• Erik Lundberg, Computer Science and
Engineering• Todd Mildon, Office of the Registrar• Scott Stephenson, Office of Information
Management
![Page 3: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/3.jpg)
Who do we represent?
![Page 4: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/4.jpg)
University of Washington• Public research university• Three campuses: Seattle, Tacoma, Bothell• 17 schools and colleges, quarter system• 41,000 students• 23,500 faculty & staff• #1 public institutional recipient of Federal R&D $
$• Two medical centers and a medical school• Biennial operating budget: $2B (11% state)
![Page 5: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/5.jpg)
UW Vision & Values• www.washington.edu/discovery/ • Uniquely Washington• Discovery is at the heart of our university• We discover timely solutions to the world’s most
complex problems and enrich the lives of people throughout our community, the state of Washington, the nation, and the world
• integrity ~ diversity ~ excellence ~ collaboration ~ innovation ~ respect
![Page 6: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/6.jpg)
UW Vision & Values• Standards of Excellence
– best, most diverse, and innovative faculty and staff• World Leaders In Research
– culture of innovation and collaboration• Spirit of Innovation
– determined persistence that engenders innovation– belief that our goals can be realized
• World Citizens– active pursuit of global engagement and connectedness
• Being Public– serving all our citizens– collaborate with partners from around the world
![Page 7: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/7.jpg)
Computing Environment• Central administrative applications (finance,
payroll, HR, etc.) on Unisys mainframe; no ERP
• Many admin. Web applications front-end the mainframe apps
• Heterogeneous technologies– Environments/Languages: .NET, J2EE, Perl, PHP,
Ruby, Python, …– OSs: Windows, Unix (various flavors)– DBs: SQL Server, Informix, Oracle, MySQL,
PostgreSQL
![Page 8: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/8.jpg)
Computing Environment• Infrastructure services: WebLogin, Shibboleth
(authn); ASTRA (authz); Person Directory
• Lots of development happening in academic units
• Local shadow systems: lots and lots of data duplication
• Mainframe is only real-time central data store; ODS for analytics; growing EDW
![Page 9: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/9.jpg)
The Evolving Environment
![Page 10: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/10.jpg)
Broad Conceptual Shifts• Past: everyone else was “them”; lots of
complaining; applications delivered by central IT often didn’t meet local needs
• Present: trying to understand local wants/needs to deliver the right application
• Future: partnership and collaboration; local groups take part in building things
![Page 11: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/11.jpg)
Broad Cultural Shifts• New perspectives on technology &
information• Central IT’s glasnost: customer focus• From consumers to technologists: can
see how things might be different (Web 2.0, open-source, crowd-ware, etc.)
• Start feeling like partners instead of clients
![Page 12: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/12.jpg)
Information is an Asset• Squander it or steward it• The Great Starvation: central IT can’t possibly keep up
with demand• Uniquely, the more it’s available, the more valuable it
is• Availability enables innovation• “Free the data”: move from “who you know” data
surface to a role-based, flexibly presented one• Common data definitions are key!
![Page 13: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/13.jpg)
Codified Business Process is an Asset
• Squander it or steward it• Tied up in tightly-coupled, opaque legacy systems
with proprietary, closed interfaces: poor business agility
• “Free the processes”• Move to loosely-coupled, transparent systems• Requires common data definitions
![Page 14: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/14.jpg)
The Time is Ripe for SOA
![Page 15: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/15.jpg)
Reached a Crossroads• Release of the “Future of Information
Systems Task Force” final report• Computing and Communications (IT)
strategic planning and restructuring efforts
• Creation of the new Office of Information Management
• Commitment from high-up for change
![Page 16: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/16.jpg)
IS Futures Report Recommendations
• Create a well-defined organizational structure• Develop a clearly defined, coordinated IT strategy• Create a culture of awareness across the University
community• Create a system of regularly updating and improving IT• Move ahead aggressively with the Data Warehouse to
support administrative goals• Make use of innovation and integration to develop new
solutions• Evaluate lifespan of the legacy systems and plan accordingly• “It’s not about technology, it’s about business practices”
![Page 17: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/17.jpg)
Office of Information Management
• Created in late 2006• Vice Provost-IM/CIO Sara Gomez• Mission is to “direct information management and
information systems throughout the University of Washington”
• Four Divisions– Business Applications– Community and Partnership Development– Enterprise Information Services– Strategic Projects and Portfolio Management
![Page 18: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/18.jpg)
Enabling the UW Mission• Excellence• Innovation• Discovery• Partnership• Collaboration• Global connectedness• Serve citizens
![Page 19: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/19.jpg)
The Vision• Free the data; free the processes; free the
academic units• Put business (academic units) in the
driver’s seat• Business agility is key• Be an information provider to the world
(and internally)
![Page 20: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/20.jpg)
Why SOA?• Looks like the Web
– Network addressable– Pervasive and ubiquitous– Open and interoperable– Adaptable/evolvable– Enables loosely-coupled systems
• Pushes app. dev. to the “edge” (composite apps/mashups): those who know best
![Page 21: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/21.jpg)
Why SOA?• Stop redundancy (data, systems & services)• Replacing the legacy administrative systems
– Demand for loose coupling / abstraction– Evolution not revolution
• Agent for cultural change– Requires partnership and collaboration– All about culture (not technology)
• Another assault on mythical reuse
![Page 22: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/22.jpg)
Exploring SOA
![Page 23: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/23.jpg)
The Journey
![Page 24: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/24.jpg)
SOA Pilot Project Goals• Demonstrate unassailable business value• Solve some existing problem• Simple, but useful• Non-sensitive data (defer auth to keep it simple)
• Provide a good discovery vehicle (WS, SOA …)
• High chance of success
![Page 25: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/25.jpg)
Why the Time Schedule?• Centrally-held data that many units need• Relatively "simple" data (in size and
structure)• Fairly easy for central data providers to
dip their toes into the SOA waters• Fairly easy for campus data consumers to
dip their toes into the SOA waters
![Page 26: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/26.jpg)
Why the Time Schedule?(cont.)
• Non-sensitive (public) data, so avoids the complexity of authentication and authorization
• Easy to steer clear of mission-critical usage, so changes would not present major difficulties for participants
• Easy to expand participation in a controlled way
![Page 27: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/27.jpg)
Courses• Single place for everything:
webservices.washington.edu• The Service: ……………………………./courses• The API: ………………………………./docs/courses• Code Library:
…………………….….…./docs/courses/code• Together: a Registry• REST v. SOAP• This is not SOA, but a vehicle for exploring it
![Page 28: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/28.jpg)
One Place for All Services webservices.washington.edu
![Page 29: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/29.jpg)
The APIwebservices.washington.edu/docs
![Page 30: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/30.jpg)
The Service
webservices.washington.edu/courses
![Page 31: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/31.jpg)
The Payloadwebservices.washington.edu/courses/
0.2/Seattle/CSE/341/2007/Winter|Spring
![Page 32: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/32.jpg)
A Business Use
![Page 33: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/33.jpg)
Collaboration Story• Partnership involving all four areas…
– OIM– C&C - Emerging Tech & Catalyst– Business Process Owner - Registrar’s Office– Depts & Colleges - CSE & College of Education
![Page 34: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/34.jpg)
The Emerging UW SOA Landscape
Registrar’sOffice
OIM
Course data flow
C&C
CSE
Col. ofEduc
/courses/
![Page 35: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/35.jpg)
The Emerging UW SOA Landscape
Registrar’sOffice
OIM
Col. ofEduc
Course data flow
Applicant data flow
/courses/
Col. OfEng
GradSchool
C&C
CSE
![Page 36: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/36.jpg)
Registrar’sOffice
OIM
Col. ofEduc
Course data flow
Applicant data flow
/courses/
Col. OfEng
Grades data flow
Campus MapClassroom Routes(w/accessible layer)
C&C Portal(MyUW)
GradSchool
C&C
CSE
The Emerging UW SOA Landscape
![Page 37: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/37.jpg)
Registrar’sOffice
OIM
Col. ofEduc
Course data flow
Applicant data flow
/courses/
Col. OfEng
Grades data flow
Campus MapClassroom Routes(w/accessible layer)
C&C Portal(MyUW)
Gradebook
GradSchool
C&C
CSE
Catalyst
The Emerging UW SOA Landscape
![Page 38: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/38.jpg)
Course data flow
Applicant data flow
/courses/
Grades data flow
Campus MapClassroom Routes(w/accessible layer)
C&C Portal(MyUW)
Gradebook
GradSchool
CSE
Catalyst
Col. OfEng
OIM
Registrar’sOffice
Col. ofEduc
C&C
The Emerging UW Collaboration Landscape
![Page 39: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/39.jpg)
Course data flow
Applicant data flow
/courses/
Grades data flow
Campus MapClassroom Routes(w/accessible layer)
C&C Portal(MyUW)
Gradebook
GradSchool
CSE
Catalyst
Col. OfEng
OIM
Registrar’sOffice
Col. ofEduc
C&C
The Emerging UW Collaboration Landscape
![Page 40: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/40.jpg)
Course data flow
/courses/Campus Map
Classroom Routes(w/accessible layer)
C&C Portal(MyUW)
Gradebook
GradSchool
CSE
Catalyst
Col. OfEng
OIM
Registrar’sOffice
Col. ofEduc
C&C
Applicant data flow
Grades data flow
The Emerging UW Collaboration Landscape
![Page 41: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/41.jpg)
Discoveries
a reflection on our journey
![Page 42: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/42.jpg)
Challenges• New design methods – REST & ATOM• Transforming known structured data
to XML & JSON• Building the right security model• What does SOA mean to us?• Moving from Micro to Macro
![Page 43: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/43.jpg)
More Challenges• Independence; uncoordinated
diverse development• Staff and systems are siloed
– Redundant systems– Resist change– Limited “big picture” visibility– How to embrace change?
• Systems are tightly coupled
![Page 44: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/44.jpg)
More Challenges• Some business process owners don’t want to
take part• Be agile while still respecting schedules and
priorities• Become less risk averse while still being
secure• Few incentives for developing shared services
– Cost, support burden, etc.• What does SOA Governance mean to us? How
do we agree on it?
![Page 45: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/45.jpg)
Key Learning• Being a good service-oriented citizen• Build new collaborative relationships • Leverage skills outside of your immediate group• Develop in manageable chunks• We chose REST• Utilize what’s already out there
![Page 46: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/46.jpg)
More Key Learning• A central registry for services and
documentation• Encourage and reward innovative thinking
and action• Identify agents for change in the organization• Identify stakeholders early• Build a strong relationship with the business
owner
![Page 47: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/47.jpg)
Collaboration Success• A model for effective working
relationships
• Agile Development
• Opening new communication channels
•It’s Fun!
![Page 48: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/48.jpg)
Moving Beyond the Pilot
![Page 49: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/49.jpg)
What Now?
![Page 50: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/50.jpg)
Creating a Culture of Collaboration
A Partnership…Responsibility and
LeadershipOn an Equal Footing
![Page 51: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/51.jpg)
Recommendations• Lead by example – create working, valuable
services• Foster a collaborative culture• Start with micro-SOA, IT-driven• Move gradually to macro–SOA, business driven
MicroMacro
Time
![Page 52: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/52.jpg)
More Recommendations• Governance is key!• Create an SOA competency center• Develop SOA policies, guidelines and best practices• Enforce policies by process and community oversight• Mandate SOA principles • Affect cultural change• Establish a Central Registry of services• Common data definitions• Resource model for exposing data and processes
![Page 53: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/53.jpg)
Federated Governance Model
![Page 54: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/54.jpg)
An Evolving Governance Model• Trust• A Leaderfull community• Collaboration• Flattening
![Page 55: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/55.jpg)
Next Steps• Tackle governance• Inform the OIM Roadmap
– Governance, architecture, technology, etc.
• Develop business success metrics
• Develop guiding principles and best practices
• Identify areas needing cultural change & nurture the change
• Training & evangelism
![Page 56: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/56.jpg)
Actualize The Vision• Free the data ; free the processes ; free
the business & academic units• Put business/academic units in the
driver’s seat• Create business agility• Enable the institution to become an
information provider to the world – by becoming so internally
![Page 57: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/57.jpg)
Questions and Discussion
![Page 58: Investigating Service Oriented Architecture (SOA)](https://reader036.vdocuments.net/reader036/viewer/2022062501/56815b68550346895dc95c6e/html5/thumbnails/58.jpg)
Discussion Points• Yet More Challenges
– Metrics for success?– Disruptive– Coping with change
• What’s going on in your institution?