service oriented architecture:

55
1 Service Oriented Architecture: UW’s Migration Strategy a.k.a. What is it and how do we get one? Jim Phelps Sr. I.T. Architect, DoIT, UW-Madison [email protected] http://arch.doit.wisc.edu/jim

Upload: timothy212

Post on 20-May-2015

274 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Service Oriented Architecture:

1

Service Oriented Architecture:UW’s Migration

Strategy a.k.a.

What is it and how do we get one?

Jim Phelps

Sr. I.T. Architect, DoIT, [email protected] http://arch.doit.wisc.edu/jim

Page 2: Service Oriented Architecture:

2

What I’ll Cover

• Data vs. Service• Three Tiers (slides included FREE!)

• Migration Strategy• Sticky Bits• Roadmap• Next Steps (2 years)• Summary

Page 3: Service Oriented Architecture:

3

Integration is..•Complex: When systems change, interfaces need

to be rebuilt

•Brittle: When interfaces fail, people are unhappy (and often blame the wrong people)

•Expensive: Garther - “up to 50% of large enterprise’s IT budget is spent on interfaces and integration”(1)

Page 4: Service Oriented Architecture:

4

A Simple Use CaseeReserves:

• Library has books on reserve for a course.

• The Library checks those books out only to students in the course.

Page 5: Service Oriented Architecture:

5

Data vs. Service

SISCourse

Roster

Library

Course

Roster

Data

Page 6: Service Oriented Architecture:

6

Data vs. Service

Service

SISIsEnrolled Servic

e

Library

Yes/No

StudentID, CourseID

SISCourse

Roster

Library

Course

Roster

Data

Page 7: Service Oriented Architecture:

7

Reusability

Service

SISIsEnrolled Servic

e

LibraryYes/

No

StudentID, CourseID

Page 8: Service Oriented Architecture:

8

Service

SISIsEnrolled Servic

e

LibraryYes/

No

StudentID, CourseID

Point of

Sales System

Reusability

Page 9: Service Oriented Architecture:

9

Service

SISIsEnrolled Servic

e

LibraryYes/

No

StudentID, CourseID

Point of

Sales System

Portal

StudentID

CourseID

Reusability

Page 10: Service Oriented Architecture:

10

Service

Replication of all data

Pull as needed

Opaque TransparentDisconnected ConnectedPoint-to-Point One-to-Many

ReusableBrittle Robust

Composite Apps

Data

Page 11: Service Oriented Architecture:

11

Data vs. Service

• Fundamental shift away from shipping data to providing services

Page 12: Service Oriented Architecture:

12

Data vs. Service

• Move to SOA to:– Reduce cost– Increase security– Reduce data duplication– Gain transparency– Reusability

Page 13: Service Oriented Architecture:

21

Migration Strategy - SOA

Process - business process analysis

Information - data definitions and standard schemas

Infrastructure - architecture and technical gaps

Vendors - helping handsOrganization - Change Management

Page 14: Service Oriented Architecture:

22

Migration Strategy - SOA

• Process - Business Process Analysis– Prioritization - Most Pain, Most Gain

– Define/Document Business Process– Look for optimization opportunities

– Use disruption to your advantage– Data needs (timeliness, availability, etc)

Page 15: Service Oriented Architecture:

23

Migration Strategy - SOA

• Information - Enterprise Data Definitions– Let the Business Process Analysis drive the data definition process

– Don’t build a complete dictionary– Start with the most needed definitions

– Build on existing standards

Page 16: Service Oriented Architecture:

24

Migration Strategy - SOA

• Infrastructure - Architecture and Technology– Gap analysis - what pieces are missing

– Do we have the right architecture in place?

– Business Process Analysis and Data needs drive the effort.

Page 17: Service Oriented Architecture:

25

Migration Strategy - SOA

• Vendor - Evaluation to fill the gaps– Business Process Analysis– Enterprise Data Identification– Data Definitions / Standards Development

– Service Design– Technology Gaps

Page 18: Service Oriented Architecture:

26

Migration Strategy - SOA

• Organization - Change Management– Culture shift from data to services

– Staff training and support– New Expertise

•Service Interface Designer (2)

•Service Library Manager (2)

– Integration Competency Centers(3)

Page 19: Service Oriented Architecture:

27

People of the ICC

•Project Manager•Services Architect•Interface Designers•Registry / Library manager

•Schema experts

Page 20: Service Oriented Architecture:

28

Migration Strategy - SOA

Page 21: Service Oriented Architecture:

29

Building the ICC• Critical Success Factor

• Centrally funded not a charge-back center

• Unifying practices

• Easier to enact and deploy standards

• Manage the interface library (WS Registry a.k.a. UDDI Registry)

Page 22: Service Oriented Architecture:

30

Organizational Change• New Skills and the ICC• Forces for Change• Misalignments– Funding models– Employee Evaluation

Page 23: Service Oriented Architecture:

31

Who is the force for change?

ServiceSIS

IsEnrolled Service

Library

Yes/No

StudentID,CourseID

Point of

Sales System

Portal

StudentID

CourseID1…

?

??

?

Page 24: Service Oriented Architecture:

32

Force 1: Architectural Purity

ServiceSIS

IsEnrolled Service

Library

Yes/No

StudentID,CourseID

Point of

Sales System

Portal

StudentID

CourseID1…

Statement: It is good for the Enterprise. Model: We will all cooperate for the good of the whole.Never works. People don’t act for the good of all when their project / budget / timeline / comfort is at risk.

Page 25: Service Oriented Architecture:

33

Force 2: Consumer

ServiceSIS

IsEnrolled Service

Library

Yes/No

StudentID,CourseID

Point of

Sales System

Portal

StudentID

CourseID1…

Statement: We want a Web service for …..Model: The first Consumer will drive the change.Rarely works. Need an alignment of good will between the Consumer(s) and Service Provider.

Page 26: Service Oriented Architecture:

34

Force 3: Service Provider

ServiceSIS

IsEnrolled Service

Library

Yes/No

StudentID,CourseID

Point of

Sales System

Portal

StudentID

CourseID1…

Statement: It is the new “supported” wayModel: The Service Provider will set the standardShould work. Especially if the Service Provider can eliminate other feeds and if they impose costs on new feeds.

Page 27: Service Oriented Architecture:

35

How would this workService Provider eliminates multiple flat-file feeds - replaces with single Web Service.

Page 28: Service Oriented Architecture:

36

How would this work

• Use Web Service–Agree to SLA–ICC establish Security and Policy

–Register use in the WS Registry

Service Provider eliminates multiple flat-file feeds - replaces with single Web Service.Consumer can:

Page 29: Service Oriented Architecture:

37

How would this work

• Use Web Service–Agree to SLA–ICC would establish Security and Policy

–Register use in the WS Registry

• Request a Flat File– Go through review

– Pay to build & maintain feed forever

– Pay for whole cost of feed

– Agree to policy re:use, security, privacy etc.

Service Provider eliminates multiple flat-file feeds - replaces with single Web Service.Consumer can:

Page 30: Service Oriented Architecture:

38

Force 3: Service Provider

ServiceSIS

IsEnrolled Service

Library

Yes/No

StudentID,CourseID

Point of

Sales System

Portal

StudentID

CourseID1…

Agree Or Pay

$$$

Page 31: Service Oriented Architecture:

39

Organizational Change

• New Skills and the ICC• Forces for Change• Misalignments– Funding models– Employee Evaluation

Page 32: Service Oriented Architecture:

40

Misalignment• How we fund projects

• How do we measure our employees

Page 33: Service Oriented Architecture:

41

Misalignment• How we fund projects– DATA - “please build an app for me”

– SERVICE - “we need these reusable services”

– Looks a lot like “Overhead”

Page 34: Service Oriented Architecture:

42

Misalignment• How we fund projects– DATA - “please build an app for me”– SERVICE - “we need these reusable services”

– Looks a lot like “Overhead”

• How do we measure our employees– DATA - “I built these apps for these customers”

– SERVICE - “I made these reusable services”

– Hard to measure “value”

Page 35: Service Oriented Architecture:

43

Organizational Change

• New Skills and the ICC• Forces for Change• Misalignments– Funding models– Employee Evaluation

Page 36: Service Oriented Architecture:

44

Other Sticky Bits

•Standards

•Policy & Security

•Governance

Page 37: Service Oriented Architecture:

45

Security/Policy Enforcement

Service

SIS

IsEnrolled Service

Library

Yes/No

StudentID, CourseID

• Two models– Embedded (written into the interfaces)– In-line (proxy)

InLine

Embedded

Page 38: Service Oriented Architecture:

46

Phylogeny and Standards

Page 39: Service Oriented Architecture:

47

Phylogeny and Standards

http://genetics.nbii.gov/systematics.html

WSDL SOAP XML

WS-Security

WS-Policy

Page 40: Service Oriented Architecture:

48

Security/Policy Enforcement

Service

SIS

IsEnrolled Service

Library

Yes/No

StudentID, CourseID

• Two models– Embedded (written into the interfaces)– In-line (proxy)

InLine

Embedded

Page 41: Service Oriented Architecture:

49

Governance - Complex and Difficult Mix

When you hear the words: Funding, Policy, Security and Architecture in the same talk, you know that Governance can’t be far behind.

Page 42: Service Oriented Architecture:

50

Governance - Complex and Difficult Mix

Page 43: Service Oriented Architecture:

51

Identity Management framework

Identity ManagementLeadership Group

Registrar & H.R. co-chairMembers include:Business LeadersTechnical Leaders

AuthenticationAuthorizationCoordinating

Team

AccessTo

Data

ID CardEvaluation

Technical Assessment and

Policy Recommendations

Page 44: Service Oriented Architecture:

52

SOA Management framework

SOALeadership Group

IntegrationCompetency

Center DRAFT

Page 45: Service Oriented Architecture:

53

Roadmap to SOA

UW System Highway

Business Application Highway

Campus Highway

Page 46: Service Oriented Architecture:

54

Roadmap to SOA - 1000’ view

UW System Highway

• Integration Competency Center (ICC)

• Registry

• Establish Governance

• Development Standards

• Common Tools

Page 47: Service Oriented Architecture:

55

Roadmap to SOA - 1000’ view

• Analysis of Interfaces

• Analysis of the Business Processes

• Reduce the number of Interfaces

• Apply standard data definitions (schemas)

• Migration to Services

Business Application Highway

Page 48: Service Oriented Architecture:

56

Campus Highway

Roadmap to SOA - 1000’ view

• ICC or ICC Partners

• Establishment of Governance

• Analysis of Business Processes

• Reduction of Interfaces

• Migration to Services

Page 49: Service Oriented Architecture:

57

Next 2 Years• Analysis of Interfaces

– Document the interface and business process

– Starting with “Course Roster”• Look to refactor interfaces• Reduce the number of interfaces• Use standards for data representation (IMS)

• Request Official University Transcripts Electronically (ROUTE)– Expose two interfaces as Web Services (Student Bio-Demo and Holds/Fines)

Page 50: Service Oriented Architecture:

58

Next 2 Years - D2L Interfaces

• Refactoring the Grading Interfaces– Opportunity to make changes– Use disruption - Look for opportunities

• Refactor the Course Roster interface– Already using standards for data representation (IMS)

Page 51: Service Oriented Architecture:

59

Building the ICC• Critical Success Factor

• Looking at building an ICC

• Report to a Deputy CIO

• Service Team model (includes members from groups working on Web Services)

– Middleware

– Applications Development

– Others

Page 52: Service Oriented Architecture:

60

Conclusion

• Why SOA/Web Services? –Reduce the cost of maintaining interfaces.

–Buffer systems from changes. –Protect data. Provide Security. –Transparency. –Enforcement of business rules (FERPA).•This means Security, Governance and Policy

Page 53: Service Oriented Architecture:

61

Conclusion• ICC is critical.

–Must be seen and helpful not an extra cost and burden to projects.

• Governance, Policy and Security are sticky issues

• We have opportunities in front of us right now (D2L, PS8.9, etc)

• The door has opened for SOA.

Page 54: Service Oriented Architecture:

62

References

1.Enterprise Application Integration, Revere Group Presentation - June 26, 2003

2.Service-Oriented Architecture, A Field Guide to Integrating XML and Web Services, Thomas Erl - Prentice Hall

3.Introduction to Integration Compentency Centers, Darwinmag.com - http://www.darwinmag.com/read/070104/integration.html

4.Enterprise Service Bus, David A. Chappell - O’Reilly

5.VantagePoint 2005-2006 SOA Reality Check, Anne Thomas Manes, Burton Group

Page 55: Service Oriented Architecture:

63

Thank you.

Questions?

SOA - UW’s Migration Strategy a.k.a. What is it and how do we get one?

Jim Phelps, Sr. I.T. Architect, DoIT, UW-Madison

EDUCAUSE MWRC06, March 2006

[email protected] http://arch.doit.wisc.edu/jim

Copyright Jim Phelps, 2006. This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author.