+ All Categories
Home > Documents > Service-Oriented Architecture: UW's Migration Strategy

Service-Oriented Architecture: UW's Migration Strategy

Date post: 25-Jun-2015
Category:
Upload: zubin67
View: 197 times
Download: 0 times
Share this document with a friend
Popular Tags:
77
Service Oriented Architecture Jim Phelps, Senior I.T. Architect Division of Information Technology, UW-Madison EDUCAUSE SAC, August 2006
Transcript
Page 1: Service-Oriented Architecture: UW's Migration Strategy

Service Oriented Architecture

Jim Phelps, Senior I.T. ArchitectDivision of Information Technology, UW-Madison

EDUCAUSE SAC, August 2006

Page 2: Service-Oriented Architecture: UW's Migration Strategy

Agenda: 90 minutes

75%

8%

17%

Present Discuss

75%

8%

17%

75%

8%

17%

75%

8%

17%

75%

8%

17%

75%

8%

17%

Page 3: Service-Oriented Architecture: UW's Migration Strategy

Agenda:

•What is SOA and why should you care?

•Technology of SOA - Web Services and an Example App

•Migration Strategy - Organizational Change

•Technology in 1 year, Migration in 10

•What’s next for UW-Madison

•Open discussion

Page 4: Service-Oriented Architecture: UW's Migration Strategy

Part 1: What is SOA and why should you care

Page 5: Service-Oriented Architecture: UW's Migration Strategy

Define SOA• Gartner says, "a style of multi-tier computing that

helps organizations share logic and data among multiple applications and usage modes." [1]

• IBM says, “an application architecture within which all functions are defined as independent services with well-defined invokable interfaces which can be called in defined sequences to form business processes" [2]

5

Page 6: Service-Oriented Architecture: UW's Migration Strategy

In Pictures...

Application

Data

Business Logic Code

User Interface

API

Page 7: Service-Oriented Architecture: UW's Migration Strategy

7http://en.wikipedia.org/wiki/Image:SOA_Elements.png

SOA as a Picture

Page 8: Service-Oriented Architecture: UW's Migration Strategy

8http://en.wikipedia.org/wiki/Image:SOA_Elements.png

SOA: Where the Application lives on the bus

Application

Page 9: Service-Oriented Architecture: UW's Migration Strategy

SOA - My Definition

• SOA is the exposure of business functions as services for integration and orchestration into new and interesting applications.

• SOA is built on reusable, shared, networked services where each service is a well defined business function.

• SOA is NOT a technology though we implement it through technology.

• In this talk, that technology is Web Services

Page 10: Service-Oriented Architecture: UW's Migration Strategy

Why should you care?

Page 11: Service-Oriented Architecture: UW's Migration Strategy

11

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

rebuilt

•Brittle: When interfaces fail, people are unhappy (and often blame the wrong people). Monitoring via Help Desk.

• Expensive: Gartner - “up to 50% of large enterprise’s IT budget is spent on interfaces and integration”[3]

Page 12: Service-Oriented Architecture: UW's Migration Strategy

Integration Complexity n(n-1)

12

Page 13: Service-Oriented Architecture: UW's Migration Strategy

13

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 14: Service-Oriented Architecture: UW's Migration Strategy

14

Data vs. Service

SISCourse Roster

Library

Course Roster

Data

Page 15: Service-Oriented Architecture: UW's Migration Strategy

15

Data vs. Service

ServiceSIS

IsEnrolled Service

Library

Yes/No

StudentID, CourseID

SISCourse Roster

Library

Course Roster

Data

Page 16: Service-Oriented Architecture: UW's Migration Strategy

16

Reusability

ServiceSIS

IsEnrolled Service

LibraryYes/No

StudentID, CourseID

Page 17: Service-Oriented Architecture: UW's Migration Strategy

17

ServiceSIS

IsEnrolled Service

LibraryYes/No

StudentID, CourseID Point of Sales System

Reusability

Page 18: Service-Oriented Architecture: UW's Migration Strategy

18

ServiceSIS

IsEnrolled Service

LibraryYes/No

StudentID, CourseID Point of Sales System

PortalStudentID

CourseID

Reusability

Page 19: Service-Oriented Architecture: UW's Migration Strategy

19

ServiceReplication AnswersOpaque Process TransparentDisconnected ConnectedPoint-to-Point One-to-Many Reusable

Brittle RobustComposite Apps

Data

Page 20: Service-Oriented Architecture: UW's Migration Strategy

20

Data vs. Service

• Fundamental shift away from shipping data to providing services

Page 21: Service-Oriented Architecture: UW's Migration Strategy

21

Data vs. Service

• Move to SOA to:– Reduce cost and complexity– Increase security– Reduce data duplication– Gain transparency– Reusability– Enable cool new applications

Page 22: Service-Oriented Architecture: UW's Migration Strategy

SOA - My Definition

• SOA is the exposure of business functions as services for integration and orchestration into new and interesting applications.

• SOA is built on reusable, shared, networked services where each service is a well defined business function.

Page 23: Service-Oriented Architecture: UW's Migration Strategy

Part 1: What is SOA and why should you care

75%

8%

17%

Page 24: Service-Oriented Architecture: UW's Migration Strategy

Part 1: What is SOA and why should you carePart 2: Technology of SOA: Web Services

Page 25: Service-Oriented Architecture: UW's Migration Strategy

Admit New Student - an Example

• Imagine a future where a new student enrolls for the first time...

25

Page 26: Service-Oriented Architecture: UW's Migration Strategy

26

A New Student

EnrollmentApplication

Submit Application Create an SIS Identity

Will you need Financial Aid?Yes

Display Financial Aid OffersChoose One or more

Submit Application to F.A. Fill out Application

Want a Credit Union Account?Yes

Fill out Application Submit Application to CU

Need Housing? Yes

Choose One Display Housing Options

Get Deposit Requirements add to invoice

Get Account Info and add cost to invoice

Display BillSubmit Payment

Route Payment to partners

Page 27: Service-Oriented Architecture: UW's Migration Strategy

27

A New Student

EnrollmentApplication

Submit Application Create an SIS Identity

Will you need Financial Aid?Yes

Display Financial Aid OffersChoose One

Submit Application to F.A. Fill out Application

Want a Credit Union Account?Yes

Fill out Application Submit Application to CU

Need Housing? Display OptionsYes

Choose One Display Housing Options

Get Deposit Requirements add to invoice

Get Account initial cost and add to invoice

Display BillSubmit Payment

Route Payment to partners

This is an example of an orchestrated composite

application that SOA enables

Page 28: Service-Oriented Architecture: UW's Migration Strategy

28

EnrollmentApplication

Create an SIS Identity

Will you need Financial Aid?

Display Financial Aid Offers

Submit Application to F.A.

Want a Credit Union Account?

Submit Application to CU

Need Housing? Display Options

Display Housing Options

Get Deposit Requirements add to invoice

Get Account Info and add cost to invoice

Display Bill

Route Payment to partners

SIS - NewStudent

FA Institution - NewLoanFA Institution - NewLoanFA Institution - NewLoanFA Institution - NewLoanFA Institution - NewLoan

CreditUnion - NewAccount

DormSystem - NewRenter

HouseToShareBB - NewRenter

AppartmentAgency - NewRenterAppartmentAgency - NewRenterAppartmentAgency - NewRenter

PaymentProcessor - PaymentService

Back-end Services

Page 29: Service-Oriented Architecture: UW's Migration Strategy

29

EnrollmentApplication

Create an SIS Identity

Will you need Financial Aid?

Display Financial Aid Offers

Submit Application to F.A.

Want a Credit Union Account?

Submit Application to CU

Need Housing? Display Options

Display Housing Options

Get Deposit Requirements add to invoice

Get Account Info and add cost to invoice

Display Bill

Route Payment to partners

SIS - NewStudent

FA Institution - NewLoanFA Institution - NewLoanFA Institution - NewLoanFA Institution - NewLoanFA Institution - NewLoan

CreditUnion - NewAccount

DormSystem - NewRenter

HouseToShareBB - NewRenter

AppartmentAgency - NewRenterAppartmentAgency - NewRenterAppartmentAgency - NewRenter

PaymentProcessor - PaymentService

Back-end Services

The Application lives above these

services

on the “Service Bus”

as an orchestrated set

of events

and it is Business Process Driven

Page 30: Service-Oriented Architecture: UW's Migration Strategy

Technology Stack of Web Services

30

Service

Application

Security

Policy

Management

Service

Application

Security

Policy

Page 31: Service-Oriented Architecture: UW's Migration Strategy

Technology Stack of Web Services

31

Service

Application

Security

Policy

Management

Service

Application

Security

Policy

WS-SecurityWS-Policy

Page 32: Service-Oriented Architecture: UW's Migration Strategy

Technology Stack of Web Services

32

Service

Application

Service

Application

Registry

RepositoryWSDL

Schema

SLA

Page 33: Service-Oriented Architecture: UW's Migration Strategy

Technology Stack of Web Services

33

Service

Application

Service

Application

Registry

Repository

UDDI -

WSDL

Schema

SLA

Page 34: Service-Oriented Architecture: UW's Migration Strategy

Technology Stack of Web Services

34

Service

Application

Security

Policy

Management

Service

Application

Security

Policy

Registry

Repository

Orchestration

Business Activity Monitoring

Business Intelligence

Application Interface

Page 35: Service-Oriented Architecture: UW's Migration Strategy

Technology Stack of Web Services

35

Service

Application

Security

Policy

Management

Service

Application

Security

Policy

Registry

Repository

Orchestration

Business Activity Monitoring

Business Intelligence

B.P.E.L.

BAM

BI

Application Interface

Page 36: Service-Oriented Architecture: UW's Migration Strategy

Technology Stack of Web Services

36

Service

Application

Security

Policy

Management

Service

Application

Security

Policy

Registry

Repository

Orchestration

Business Activity Monitoring

Business Intelligence

SecurityApplication Interface

Page 37: Service-Oriented Architecture: UW's Migration Strategy

Technology Stack of Web Services

37

Service

Application

Security

Policy

Management

Service

Application

Security

Policy

Registry

Repository

Orchestration

Business Activity Monitoring

Business Intelligence

Enterprise Service Bus (ESB)

Page 38: Service-Oriented Architecture: UW's Migration Strategy

Part 1: What is SOA and why should you carePart 2: Technology of SOA: Web Services

75%

8%

17%

Page 39: Service-Oriented Architecture: UW's Migration Strategy

Part 1: What is SOA and why should you carePart 2: Technology of SOA: Web ServicesPart 3: Migration Strategy - Organization Change

Page 40: Service-Oriented Architecture: UW's Migration Strategy

40

Migration Strategy - SOAProcess - business process analysisInformation - data definitions and standard

schemasInfrastructure - architecture and technical gapsVendors - helping handsOrganization - Change Management

Page 41: Service-Oriented Architecture: UW's Migration Strategy

41

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 42: Service-Oriented Architecture: UW's Migration Strategy

42

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

•HR-XML.ORG• IMS• eduPerson, eduOrg

Page 43: Service-Oriented Architecture: UW's Migration Strategy

43

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 44: Service-Oriented Architecture: UW's Migration Strategy

44

Migration Strategy - SOA• Vendor - Evaluation to fill the gaps– Business Process Analysis– Enterprise Data Identification– Data Definitions / Standards Development– Service Design– Technology Gaps

Page 45: Service-Oriented Architecture: UW's Migration Strategy

45

Migration Strategy - SOA• Organization - Change Management– Culture shift from data to services– Staff training and support– Integration Competency Centers(3)

– New Expertise•Service Interface Designer (2)

•Service Library Manager (2)

Page 46: Service-Oriented Architecture: UW's Migration Strategy

46

People of the ICC

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

Page 47: Service-Oriented Architecture: UW's Migration Strategy

47

Page 48: Service-Oriented Architecture: UW's Migration Strategy

48

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 49: Service-Oriented Architecture: UW's Migration Strategy

49

Organizational Change• New Skills and the ICC• Misalignments• Governance• Forces for Change

75%

8%

17%

Page 50: Service-Oriented Architecture: UW's Migration Strategy

50

Misalignment• How we fund projects

• How do we measure our employees

Page 51: Service-Oriented Architecture: UW's Migration Strategy

51

Misalignment• How we fund projects– DATA - “please build an app for me”– SERVICE - “we need these reusable services”– Who should pay for the infrastructure?– Who should pay to build the service?– Who should pay to support the service?– Looks a lot like “Overhead”

Page 52: Service-Oriented Architecture: UW's Migration Strategy

52

Misalignment

• 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 53: Service-Oriented Architecture: UW's Migration Strategy

53

Governance - Complex and Difficult Mix

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

Page 54: Service-Oriented Architecture: UW's Migration Strategy

54

Page 55: Service-Oriented Architecture: UW's Migration Strategy

55

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 56: Service-Oriented Architecture: UW's Migration Strategy

56

SOA Governance framework

SOALeadership Group

IntegrationCompetency

CenterDRAFT

Page 57: Service-Oriented Architecture: UW's Migration Strategy

57

Who is the force for change?

ServiceSIS

IsEnrolled Service

Library

Yes/No

StudentID,CourseID

Point of Sales System

Portal

StudentID

CourseID1…

??

?

?

Page 58: Service-Oriented Architecture: UW's Migration Strategy

58

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 59: Service-Oriented Architecture: UW's Migration Strategy

59

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 60: Service-Oriented Architecture: UW's Migration Strategy

60

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 61: Service-Oriented Architecture: UW's Migration Strategy

61

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

Page 62: Service-Oriented Architecture: UW's Migration Strategy

62

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 63: Service-Oriented Architecture: UW's Migration Strategy

63

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 64: Service-Oriented Architecture: UW's Migration Strategy

64

Force 3: Service Provider

ServiceSIS

IsEnrolled Service

Library

Yes/No

StudentID,CourseID

Point of Sales System

Portal

StudentID

CourseID1…

Agree Or Pay

$$$

Page 65: Service-Oriented Architecture: UW's Migration Strategy

65

Organizational Change

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

• Governance• Forces for Change

Page 66: Service-Oriented Architecture: UW's Migration Strategy

66

One other sticky bit...

Page 67: Service-Oriented Architecture: UW's Migration Strategy

67

Phylogeny and Standards

Page 68: Service-Oriented Architecture: UW's Migration Strategy

68

Phylogeny and Standards

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

WSDL SOAP XML

WS-Security

WS-Policy

Page 69: Service-Oriented Architecture: UW's Migration Strategy

Part 1: What is SOA and why should you carePart 2: Technology of SOA: Web ServicesPart 3: Migration Strategy - Organization Change

75%

8%

17%

Page 70: Service-Oriented Architecture: UW's Migration Strategy

70

Campus Highway

Roadmap to SOA - 1000’ view

• Building/Funding an ICC • Establishment of Governance• Analysis of Business Processes and BPI• Reduction of Interfaces• Migration to Services• Core WS Technology

Page 71: Service-Oriented Architecture: UW's Migration Strategy

71

Our Next Steps• Developing Roadmap for an ICC• Developing a Roadmap for Governance• Funding model • Hosting model• Proof Of Concepts with vendor solutions– Oracle’s Fusion MWare stack– Sun– OpenSource

Page 72: Service-Oriented Architecture: UW's Migration Strategy

72

• Model for campus involvement• Working with UW-System on their role and

plans• Working with DOA @ State level

• I.T. Portfolio Management project– dovetails with the SOA project and

with Business Process Improvement

Our Next Steps

Page 73: Service-Oriented Architecture: UW's Migration Strategy

SOA - My Definition

• SOA is the exposure of business functions as services for integration and orchestration into new and interesting applications.

• SOA is built on reusable, shared, networked services where each service is a well defined business function.

Page 74: Service-Oriented Architecture: UW's Migration Strategy

74

Conclusion• Move to SOA to:– Reduce cost and complexity– Increase security– Reduce data duplication– Gain transparency– Reusability– Enable cool new applications

Page 75: Service-Oriented Architecture: UW's Migration Strategy

75

Conclusion• ICC is critical. • Must be seen as helping hands not an extra cost

and burden to projects.• Service providers could be our force for change• Governance, Policy and Security are sticky issues• The door has opened for SOA.

Page 76: Service-Oriented Architecture: UW's Migration Strategy

76

Thank you.

Questions?Service Oriented Architecture Jim Phelps, Sr. I.T. Architect, DoIT, UW-MadisonEDUCAUSE SAC, Auguest [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.

Page 77: Service-Oriented Architecture: UW's Migration Strategy

77

References1. Service Oriented Architecture, Roy W. Schulte and Yefim V. Natis, Gartner, 12 April 1996

2. Migrating to a service-oriented architecture, Part 1, Channabasavaiah et al, IBM, 16 dec 2003

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

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

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

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

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


Recommended