overview: application integration, data access, and process change november 16, 2005 tom board, nuit

36
Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

Upload: arleen-atkinson

Post on 04-Jan-2016

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

Overview:Application Integration, Data

Access, and Process Change

November 16, 2005

Tom Board, NUIT

Page 2: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

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 will enable real-time processes, allow secure access to data elements, and support distributed development

• Success will depend upon skill with the technologies and central adoption of SOA

Page 3: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

3

Agenda

• What are the Problems?

• Industry Trends in Application Integration

• What is NUIT Planning?

• How Should Application Administrators and Planners Prepare?

• Wrap-up

Page 4: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

4

Agenda

• What are the Problems?

• Industry Trends in Application Integration

• What is NUIT Planning?

• How Should Application Administrators and Planners Prepare?

• Wrap-up

Page 5: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

5

Problems

• Sluggish inter-office business processes

• Current costs to integrate applications and maintain linkages over software changes

• Meeting community expectations for processes– Paper to electronic– Daily to real-time

Page 6: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

6

Today’s Point-to-Point Approach

S tude ntS ys te m s

H um a nR e s ourc e s

F ina nc ia lV oya ge r

H ous ing

C T E C

T e le c omS tude ntL oa ns

W ildc a rd

P a rking

R e s ourc e25 S N A P

A lum ni

B la c kboa rd

E ffortR e porting

T im eE ntry

R D IA

P re -a w a rd

e IR B

IS IS

G R A N IT E

D a taW a re hous e??

Page 7: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

7

Point-to-Point is Not Easy

• Definitions of data items must be reconciled between systems

• Methods of moving data must be agreed• Data interchange representations must be

agreed• Software to move internal representations

to/from interchange form must be written, tested and maintained

• Security/encryption must be agreed• Linkage is often unique and not reused

Page 8: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

8

Implications

• Scale Problem– Cost to establish linkages – custom coding– Cost to maintain custom linkages– Linkages are brittle due to object dependency– Testing all links when software is changed

• Data Definition Problem– ANY linkage requires common definitions– Push for real-time processes requires

definitions across multiple linkages

Page 9: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

9

Agenda

• What are the Problems?

• Industry Trends in Application Integration

• What is NUIT Planning?

• How Should Application Administrators and Planners Prepare?

• Wrap-up

Page 10: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

10

Industry Finally “Gets It”

Vendors are moving to:• Eliminate custom linkages through reusable

service interfaces• Eliminate object representation dependencies

through standard data types• Design for heterogeneous, network-based

application environment• Settle upon and deploy standards!

Are we approaching a “fax” breakthrough?

Page 11: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

11

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

Page 12: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

12

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

Page 13: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

13

Why is SOA a Solution?

Point-to-Point SOA• Definitions of data items must be

reconciled between systems• Problem remains: data item definitions

must be reconciled between systems

• Method of moving data must be agreed • Standard set – http/https

• Data interchange representation must be agreed

• Standard set – XML/SOAP

• Software to move internal representations to/from interchange form must be written, tested and maintained

• Tools within vendor products are transparent (e.g. .NET-to-SOAP, J2EE-to-SOAP, C++-to-SOAP, etc.)

• Security/encryption must be agreed • Standard set – WS-Security

• Linkage is often unique and not reused • Services are designed for reuse

Page 14: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

14 Service Example

H ir ing E ve nt

P ro vis io nN e tID

P ro vis io nW ildc ard

E n c u m b er s a la r yan d b en ef its

P ro vis io napplic at io n

Sc he duletraining

P ro vis io nE TE S

N o tifys upe rvis o r

Subs c r ibe toe m ail l is ts

Q ue ue toB us ine s s U nit

N o tifys upe rvis o r

P rovis ions c hool s e rv ic e s

P ro vis io nc ale ndar

N o tify unitfunds m gr

H um an R e s o urc e s Sys te m

E nableAc c e s s

E nte rpr is e Se rvic eB us

Page 15: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

15

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”)

Page 16: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

16

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

Page 17: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

17

Web Service Can …

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

Page 18: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

18

Web Services Require…

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

• New infrastructure– WSDL – service “contracts”– UDDI – service governance and polices– Enterprise Service Bus – legacy interfaces and

publish/subscribe platform

Page 19: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

19

Web Services for 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

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

E nte rpr is eSe rvic e B us

Page 20: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

20

Agenda

• What are the Problems?

• Industry Trends in Application Integration

• What is NUIT Planning?

• How Should Application Administrators and Planners Prepare?

• Wrap-up

Page 21: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

21

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– Distributed

development– Abstraction or

virtualization

Page 22: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

22 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

Page 23: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

23 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

Page 24: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

24 Timeline*

* This timeline is for illustrative purposes only and should not be used in planning – please consult with an experienced professional. The views expressed are those of the author and not those of NUIT. No warranty expressed or implied. YMMV. All bets are off.

2006 2007Task Jan-Mar Apr-Jun Jul-Sep Oct-Dec Jan-Mar Apr-Jun Jul-Sep

Ph ase 1

S ign contrac tsH R IS 8 .9 Im plem enta tion

Im plem ent W A MD eploy W A M

E xperim enta tion w ith p-to-pD eploy W S D L and U D D I

E xp lore S OA m gm t optionsD eploy S OA m gm t

C reate IdM W eb S ervicesC utover to IdM

S E S 8.9 Im plem enta tionFinancial S ystem Implemnta tion

Page 25: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

25

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

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

D atab as es

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

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

Page 26: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

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

Page 27: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

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

Page 28: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

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

Or WSRP

Portlet

Web Services

Infrastructure

Authored

Application

Database

Page 29: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

29

Agenda

• What are the Problems?

• Industry Trends in Application Integration

• What is NUIT Planning?

• How Should Application Administrators and Planners Prepare?

• Wrap-up

Page 30: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

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. Work to reach community consensus on data

definitions so that integration is possible4. Start serious discussions with your users about

what data access services they need and can justify

5. Determine your vendor’s plans for Web Service integration – and influence those plans

6. Train your staff on SOA and Web Services

Page 31: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

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)

Page 32: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

32

Agenda

• What are the Problems?

• Industry Trends in Application Integration

• What is NUIT Planning?

• How Should Application Administrators and Planners Prepare?

• Wrap-up

Page 33: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

33

Wrap Up

• SOA and Web Services are the accepted future (example: Oracle Fusion Middleware)

• Real-time processes will improve all systems – assume it in all new designs

• Data definitions are vital for future integration – we must solve this aspect before it prevents desirable improvements

• Users and stewards together should begin designing the future now

Page 34: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

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

Page 35: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

35

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

Page 36: Overview: Application Integration, Data Access, and Process Change November 16, 2005 Tom Board, NUIT

36

Questions?

QA&