application integration, data access, and process change

Application Integration, Data Access, and Process Change

2

Thesis

• Service-Oriented Architecture will become an assumed infrastructure

• Web Services will be the near-term technology of choice for SOA deployment

• With planning, SOA can enable real-time processes, allow secure access to data elements, and support distributed development

• The University’s rate of deployment will depend upon central technologies and access policies

3

Agenda

• What is Service-Oriented Architecture?

• What are Web Services?

• How will these technologies mesh with NUIT’s architecture plans?

• What steps should application developers and planners be taking today?

4

Agenda





5

Service-Oriented Architecture

• Distributed functionality exposed as shared, reusable services

• Goal is to streamline deployment, reduce duplication of functions, and allow execution of business processes across diverse application platforms in a network

6

“SOA” circa 1970s

• Subroutine/function libraries (IMSL)

• OS services (I/O)

• Tightly-bound to object representation

• Embedded instances

7

Network SOA

Ap p lic a tio n A Ap p lic a tio n BS c h o o l

Ap p lic a tio n

Ap p lic a tio n C Ap p lic a tio n D D iv is io nAp p lic a tio n

E x ter n a l P ar tn erX

Un iv e rs ity Ne two rk

C o m m u n ic a tio n I n f r as tr u c tu r e

E x ter n a l P ar tn erY

C e n tra l B u s in e s s Fu n ct io n s

8

Agenda





9

Web Services for Implementing a Service-Oriented Architecture

• Document-oriented messaging scheme using http/https transport and security

• Documents are self-describing XML streams combining payload and control information

• Separates external interface (behaviors, logic) from internal objects, structures, and implementation (“Loose coupling”)

10

A Web Service …

• Has a URL

• Is described through a Web Service Definition Language (WDSL) “contract” for the benefit of potential consumers

• Uses SOAP messages over http/https

• Can be secured based upon polices in the WSDL description or external frameworks

11

SOAP Messages

WS-

Sec

urit

y h

eade

r

WS-

Rel

iabl

eMes

sagi

ng h

eade

r

SO AP H e ade rs SO AP B o dy

P aylo ad

SO AP E nve lo pe• XML document• Construction &

decoding within tools and run-time services

• Message may be encrypted via https and/or under WS-Security

12

SOAP Interceptors and Handlers

Trans po r t L aye r

M e s s age P ro c e s s ingSubs ys te m

Se r ial izat io n F ram e wo rk

Applic at io n D is patc he r W e b Se rvic e Age nt

T ra ns port In te rc e ptors(e nc ryption , c om pre s s ion , logging . . . )

M e s s a ge In te rc e ptors(va lida tion , tra ns form a tion . . . )

H e a de r P roc e s s or(s e c urity , s e s s ion m gm t, re lia b ility . . . )

X M L to language m apping

After Burton Group

13

Web Service Can …

• Be created through:– .NET (Visual Studio)– J2EE authoring environments (Eclipse)– C++ & Visual Basic 3rd party wrapers– PeopleSoft Component Interfaces– PeopleSoft Integration Points

• Be invoked through:– Dynamic discovery (UDDI)– Compiled WSDL definition

14

Web Services Require…

• New approaches to development– Services, not components– Flat documents, not structured data– Chunky, not chatty

• New infrastructure– WSDL– UDDI– Enterprise Service Bus / Integration Broker

15

Interface Granularity

Inte rac t ive c l ie nt Inte rac t ive s e rve r

Inte rac t ive s e rve rW e b s e rvic e s c l ie ntB us ine s sInte r fac e

Subm it O rde r

C re ate O rde r

Add Ite m

Add Ite m

Add Ite m

P ro c e s s o rde r

After Burton Group

16

Web Services for SOA

Ap p lic a t io n A Ap p lic a t io n BS c h o o l

Ap p lic a t io n

Ap p lic a t io n C Ap p lic a t io n D D iv is io nAp p lic a t io n

E x ter n a l P ar tn erX

Un iv e rs ity Ne two rk

Trans po r t o ve r ht tp/ht tps

E x ter n a l P ar tn erY

C e n tra l B u s in e s s Fu n ct io n s

U D D ISe rvic e

W SD LSe rvic e

Inte grat io nbro ke r

17

Agenda





18

Architectural Direction

• Business Drivers– Security– Mobility– Self-service– Real-time processes– Data availability– Rapid deployment

• Architecture– Central identity and

authentication– Portal navigation– Web-Service

integration– Standards-based

environment– Abstraction or

virtualization

19 System Architecture

SystemsManagement

Identity Security

Core Enterprise SystemsCore Enterprise Systems

Specialized Enterprise ApplicationsSpecialized Enterprise Applications

School/Department/Division ApplicationsSchool/Department/Division Applications

User Devices

Network

Processing Capacity

Data Management

Integration

Platforms

Business

Framew

ork

I P , Vo I P , h ttp ,w ir e les s , c e llu la r

Ap p lic a tio nS er v er s

Vir tu a l d a tas er v ic es

S er v ic e b u s ,f ed er a tio n

Bu s in es s lo g ic ,c o m p o s ite

ap p lic a tio n s ,s e r v ic e

p r o v id er s an dc o n s u m er s ,

r ep o r t in g

20

Abstraction or Virtualization

• Convert an application-specific service into a general infrastructure service

R o le- Bas ed Bu s in es s R u les

E n ter p r is e S er v ic e Bu s

Un if ied I d en tity M an ag em en tan d Au th en tic a tio n

Ap p lic a tio nBu s in es s R u les


D atab as es


Us er s

P r o c es s in g

F u n c tio n a lUn it

R es p o n s ib ilit ies

ITR

espo

nsib

ilit

ies

ITR

espo

nsib

ilit

ies

—Storage management—Authentication—Authorization—Computing platform—Database

21 Direct-to-Application Access

Us erp r o f iles

E x tr ac t

M an u al I n te r f ac e

C o d ein te r f ac e

( AP I )

tigh

t-co

upli

ng to

sch

ema

Us erp r o f iles

D atab as eq u er ies

R em o teP r o c ed u r e C all

I m p o r t

Batc h tr an s f er

tight-coupling to layout

C o n s u m in g Ap p lic a tio n ( L M I S , e tc . )

Res

pons

e

Req

ues t

Dow

nloadD a tab as e en g in e

Ap p lic a tio nBu s in es s r u les

Upload

tight-coupling to objects

22 Repository Virtualization

Us erp r o f iles

E x tr ac t

M an u al I n te r f ac e

Cod

e in

terf

ace

Us erp r o f iles

D atab as eq u er ies ( v iew s )

C o d ed q u er ieso r tr an s ac tio n s Batc h tr an s f er

Dow

nloadPu b

l ish

D a tab as e en g in e


R e po s i to ry E ngine

Us erp r o f iles

Updates

S e c u rity p e r im

e te r

R eq u es t &R es p o n s e

E R PAp p lic a tio n

C o ns um ing Applic at io n ( L M IS , e tc .)

23 Database Virtualization

Vir tual izat io n E ngine

Us erp ro f iles

Us erp ro f iles

Us erp ro f iles

Us erp ro f iles

C o ns um ing Applic at io n ( L M IS , e tc .)

Req

ues t

Response

Ap p A Ap p B Ap p C Ap p D

24 Web Services Access

Us erp r o f iles

C o d e in te r f ac eAP I

Us erp r o f iles

C o n s u m in g Ap p lic a tio n ( L M I S , e tc . )

D atab as e en g in e


E v en t/T r an s ac tio nD is tr ib u to r Us er

p r o f iles

E R PAp p lic a tio n

S er v ic eAb s tr ac tio n

S er v ic e Ab s tr ac tio n

C o d e in te r f ac e AP I

Request/R

e spo nse

Po s

t

P o s t

P u b lis hS u b s c r ib e

X M L

S er v ic ed ef in it io n s& p o lic ies

25 Web Services Infrastructure

So urc e s ys te m s

E nte rpr is e Se rvic eB us / Inte grat io n B ro ke r

D o wns tre amApplic at io n

E xtrac t /D o wnlo ad

U plo ad

M o nito r ing &po lic y e nfo rc e m e nt

Dat

a T

rans

form

atio

n

Sub scrib eP u

b lis

h

U D D I R e gis tryW SD L R e po s i to ryP o lic y R e po s i to ry

D o wns tre am Applic at io ns

Dir

ect i

n voc

a tio

n

M anage m e nt

R e al- t im em e s s age s

26

Abstraction of Business Processes

• The next step after SOA is composite applications and process orchestration– Once individual business functions are

exposed as Web Services, then new “meta-process” coding can be built “above” them

– Combined with workflows, this can substantially automate many functions

– This will be addressed by Business Process Execution Language (BPEL) tools

27 Meta-Processes

Ap p lic a tio n A Ap p lic a tio n BAp p lic a tio n C Ap p lic a tio n DE x ter n a l P ar tn er

XE x ter n a l P ar tn er

Y

P r o c e s s i ng

Sto r ag e

D atabas e s

Invoca tion

28

Distributed Development

p ers onal emp lo yee fac ulty fi nanc ialres earc h

Search 12:34O c to be r 12

c us tomize

(c ) No rthw este rn Univers ity 2003. Send c omments to w ebmaste r@ northw este rn.edu

Op e n e n ro llm e n t u n til 10 /3 1 - se e e m p lo ye e ro le

Dr P h ilip B e it.. Expe r ime nta ..J o hn Do e C ubs ga me t..F ra nc is Smith G ra nt a ppA nno unc e m... Ne w po r ta lB MB C B c ha ... F a c u lty me e ting

E -mail Inb ox15 ne w me ssa ge s

NSF A A -433 (due 10/03) S te m c e ll su r fac e s truc tureNIH A 9943 (due 11/03) P ro te in in te ra c tio ns o n s te mNIH B 8889 (due 1 /04)

mR NA c a ta lytic eff e c ts unde rNSF A B -448 (due 2 /04)

G rant O p p ortunitiesFro m N U Res earc h S erv ic es

NIH A 3773 (e xp ire s 8 /05) ba la nc e $34,567NIH Q 44T 5 (e xp ire s 11 /03) ba la nc e $11,333NSF 4 -44R (e xp ire s 8 /07) ba la nc e $134,987

G rant Informationa s o f 10 /12 09 :00

C yto lo gy ................ ................S te m C e ll ................

N IH N ew s feedth ro ugh 10/12 11:00ET

B MB C B ho meHuma n G e no me P ro je c tS te m C e ll A C T AC yto lo gy T o da yUC L A ga te w a y

B ookmarks

NU Ho meP la n it P urp leWe a the r.................................

N U B ookmarks

Add Or ganize

Portal

Web Service for

data access

Authored

JSR 168

Portlet

Web Services

Infrastructure

Authored

Application

Database

29

Agenda





30

What Steps Should Planners and Developers Take Today?

1. Stop buying or creating applications with “silo” approaches – use central services

2. Stop copying data around the network3. Start serious discussions with your users about what

data access services they need and can justify4. Determine your vendor’s plans for Web Service

integration – and influence those plans5. Train your staff on SOA and Web Services6. Talk with NUIT and your NU peers about authoring

tools, test environments, and other infrastructure – don’t “go it alone”

31

Stop Copying Data Around the Network

• Problem: send e-mail from within an application to a set of users– Bad: Get all NetIDs and e-mail addresses from SES,

HRIS, SNAP, etc. an include in local database– Poor: Get e-mail addresses for current users every

day and include in local database– Correct: Get user’s e-mail address from directory

service when needed, even in large numbers– Future? Invoke a Web Service to send e-mail

messages based upon standard identity (NetID)

32

Forecasts

• New financial system will rely first upon Web Services for integration, but many batch interfaces will take years to change as software is replaced

• Our community will push for real-time processes, and service units will need time to adjust

33

Questions?

QA&

34

Professional Development Topics

• SOA & Web Services• XML, SOAP & WSDL• OASIS and WS-*

standards• Enterprise Service

Bus (ESB)• Universal Description,

Discovery, and Integration (UDDI)

• Authoring tools for Web Services

• Microsoft .NET versus J2EE solutions

• Business Process Execution Language (BPEL)

• SOA governance

35

Suggested Reading

Haddad, Chris, “Web Services and Service Oriented Architecture: Collapsing Boundaries Between the J2EE and .NET Platforms”, Burton Group presentation, 18 Dec 2003.

Katz, Richard, “What Does System Integration Really Mean for Higher Education?”, Educause Review, Sep/Oct 2003.

Kobielus, James, “Orchestrating Web Services: Driving Distributed Process Execution Through Workflow Technology”, Burton Group, 18 Dec 2003.

Manes, Anne Thomas, et al, “VantagePoint 2005-2006 SOA Reality Check”, Burton Group, 29 Jun 2005.

Manes, Anne Thomas, Web Services – A Manager’s Guide, Addison-Wesley, 2003.

36

Local Documents

“University System Architecture for Integrated Enterprise Systems” http://www.it.northwestern.edu/bin/docs/UniversitySystemsArchitecture.pdf

“System Management for the e-University” http://www.it.northwestern.edu/bin/docs/systemmgmtforeuniversity.pdf

http://www.it.northwestern.edu/bin/docs/UniversitySystemsArchitecture.pdf

http://www.it.northwestern.edu/bin/docs/UniversitySystemsArchitecture.pdf

http://www.it.northwestern.edu/bin/docs/systemmgmtforeuniversity.pdf

http://www.it.northwestern.edu/bin/docs/systemmgmtforeuniversity.pdf

application integration, data access, and process change

Documents

network slide

network soa slide

wsdl definition slide

wssecurity slide

burton group slide

development services

process change slide

nuits architecture plans