from message passing to service orientation. - aalto message passing to service orientation. ......

SoberITSoftware Business and Engineering Institute

HELSINKI UNIVERSITY OF TECHNOLOGY

From message passing to service orientation.

EAI, SOA, BPMTimo Itälä

SoberIT T-86.51414.10.2006

@ Paavo Kotinurmi & Timo Itälä 2006 2



Contents

Business and technology viewsProcess maps, need for integration (EAI)Integration topology optionsEnterprise Application Integration stackBusiness integrationEvolution of transactional systems architectureService oriented architecture SOABusiness Process Management (BPM)After this: Case METSO 15:00




EAI, SOA, BPM: Business and technologyviews

e.g. DATA

ENTERPRISE ARCHITECTURE - A FRAMEWORK

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEMMODEL(LOGICAL)

TECHNOLOGYMODEL(PHYSICAL)

DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)

Sub-Contractor

FUNCTIONINGENTERPRISE

DATA FUNCTION NETWORK

e.g. Data Definition

Ent = FieldReln = Address

e.g. Physical Data Model

Ent = Segment/Table/etc.Reln = Pointer/Key/etc.

e.g. Logical Data Model

Ent = Data EntityReln = Data Relationship

e.g. Semantic Model

Ent = Business EntityReln = Business Relationship

List of Things Importantto the Business

ENTITY = Class ofBusiness Thing

List of Processes theBusiness Performs

Function = Class ofBusiness Process

e.g. Application Architecture

I/O = User ViewsProc .= Application Function

e.g. System Design

I/O = Data Elements/SetsProc.= Computer Function

e.g. Program

I/O = Control BlockProc.= Language Stmt

e.g. FUNCTION

e.g. Business Process Model

Proc. = Business ProcessI/O = Business Resources

List of Locations in which the Business Operates

Node = Major BusinessLocation

e.g. Business Logistics System

Node = Business LocationLink = Business Linkage

e.g. Distributed System

Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics

e.g. Technology Architecture

Node = Hardware/SystemSoftware

Link = Line Specifications

e.g. Network Architecture

Node = AddressesLink = Protocols

e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING

MOTIVATIONTIMEPEOPLE

e.g. Rule Specification

End = Sub-condition

Means = Step

e.g. Rule Design

End = ConditionMeans = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business ObjectiveMeans = Business Strategy

List of Business Goals/Strat

Ends/Means=Major Bus. Goal/Critical Success Factor

List of Events Significant

Time = Major Business Event

e.g. Processing Structure

Cycle = Processing CycleTime = System Event

e.g. Control Structure

Cycle = Component CycleTime = Execute

e.g. Timing Definition

Cycle = Machine CycleTime = Interrupt

e.g. SCHEDULE

e.g. Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations

People = Major Organizations

e.g. Work Flow Model

People = Organization UnitWork = Work Product

e.g. Human Interface

People = RoleWork = Deliverable

e.g. Presentation Architecture

People = UserWork = Screen Format

e.g. Security Architecture

People = IdentityWork = Job

e.g. ORGANIZATION

Planner

Owner

to the BusinessImportant to the Business

What How Where Who When Why

John A. Zachman, Zachman International (810) 231-0531

SCOPE(CONTEXTUAL)

Architecture

e.g. STRATEGYENTERPRISE

e.g. Business Plan

TM

Business Side

Technology Side




Contents

Business and technology viewsProcess maps, need for integration (EAI)Integration topology optionsEnterprise Application Integration stackBusiness integrationEvolution of transactional systems architectureService oriented architecture SOABusiness Process Management (BPM)After this: Case METSO 15:00




Process map

Supplier CustomerFunctions

Core processes




Example: Paper sales and distributionCore business processes

Sales forecasting and budgetingOrder entry and delivery

FunctionsAdministrationProductionShipmentsmanagementSales/shipmentsCustomer

Information flows withina business processbetween functions

Source: Jouko Hannus: Prosessijohtaminen, 1993




Example: Integration of information flow

Applicationsare functionallydevelopedhave interfacesexchange messagesuse common data codes and formats

Business processescover severalapplicationsneed seamlessinformation flowEnterprise ApplicationIntegration?

Source: Jouko Hannus: Prosessijohtaminen, 1993




Integration of functional applications

ChoicesERP: Enterprise wide application in onepackageEnterprise Applicaton Integration (EAI): Integration of multiple applications usingstandard interfaces and messages

Enterprises use several applicationsERP, PDM, SCM, CRM, HR and othersBusiness partners need also integrationWe need EAI anyway, both within and between enterprises




Contents

Business and technology viewsProcess maps, need for integration (EAI)Integration topology and stackBusiness integrationEvolution of transactional systems architectureService oriented architecture SOABusiness Process Management (BPM)After this: Case METSO 15:00




Integration topology options

Point-to-point Hub and spoke Common definitions




EAI Stack: Integration needs

Integration is needed:Communications protocol, network, routing, addressing, messagewrappersAuthentication, authorization, securityApplications protocol, messages, syntaxSemantic interoperability, codes, vocabulariesBusiness process protocolGoals, objectives, metricsProcurement, share of costsImplemantation, training, support




Integration options

Point-to-point

n(n-2)/2 connections

Hub and spoke

n communicationsconnections

n(n-2)/2 semanticconnections

Common definitions

n communicationsconnections

n semanticconnections

n(n-2)/2 business connections

Adapter




EAI Stack

EAI Stack integratesCommunications protocol, network, routing, addressing, message wrappersAuthentication, authorization, securityApplications protocol, messages, syntaxSemantic interoperability, codes, vocabulariesBusiness process protocolGoals, objectives, metricsProcurement, share of costsImplemantation, training, support

Key decisionsThe roles and responsibilities of the Hub and the Spokes




EAI services include

Platform, protocol management..

Asynchronous,Synchronous messaging support..

Security services, encryption,non-repudiation..etc

Routing services, publish/subscribe..

Directory services..

Metadata management & repository services..

Event management, topology & synchronization..

Data mapping & transformation services.. (not always unified data model behind)




Business to business integration (B2Bi)

EAI

EAI

EAI

EAI

Different requirementswithin enterprises and between enterprises

Different approacheswithin enterprises and between enterprises

EAI

Company A

Company B

B2Bi services

Company D




Technology framework for EAI/B2Bi

Business process Integration

Private Public

EAI Data Integration B2B Trade

Application integration Services

Native data

Multiple Platforms

Diverse Protocols

Partner management Services

Standard data (XML)

Platform independence

Primarily HTTPS, SOAP




Contents





EDI background

The creators of Electronic Data Interchange (EDI) were

mainly concerned about the size of their messages.

EDI messages are very compressed and use codes to

represent complex values.

The metadata is stripped from an EDI message

makes the message difficult to read and debug (but

they are meant for computers not human)

EDI programmers are hard to train and expensive to

keep. This complexity drives cost.

No one global EDI standard (UN/CEFACT, X.12)




EDI (EDIFACT order)UNH+0002771776+ORDERS:D:99A:UN:FI0084’BGM+105+40063000277177602748497+9’DTM+4:20000705:102’DTM+2:20000706:102’DTM+9:20000705:102’NAD+BY+003709895955:100++TRADEKA OY’NAD+SE+003702134547:100++OY HARTWALL AB’NAD+CN+40063000::92++VALINTATALOHERVANTA+LINDFORSINKATU 2+TAMPERE++33720’LIN+1++6413600001584:EN’IMD+F+8+:::HTW NOVELLE ORANGE LIME 1,5 L’QTY+21:144’LIN+2++6413600000280:EN’IMD+F+8+-:::VICHY 0,33L/HARTWALL’QTY+21:430’UNS+S’CNT+2:2’UNT+17+0002771776'

Source: TIEKE (EDI standards implementation guidelines document)




Motivation for integration & e-business standards

Data transfer needs high, volume high, probability of human errors high,

frequency of data transfer Integration is needed between systemsXML has been central element in recent B2B standardization but XML alone is not enoughAlthough following are all human readable/interpretable, computers have problems in these things

<e-business/> <date>4.10.2006</date><eBusiness/> <date>10/4/2006</date><E-business/> <xs:date>2006-10-04</xs:date>

XML provides a syntax way to represent information

Need standard to define commonly understood business documents

B2B standards often don’t just standardize the business documents, but define also the inter-company business processes and how the business documents can be securely transported over the Internet




Automatic process

Business Document is standardized message encoded using XML or EDI

Reliable messaging =“postal service”




RosettaNet messaging principle

Internet & XML

RosettaNet defines processes and a framework for how data gets passed over the Web and certain handshake criteria.

Company A

SAPERP

Company Specific processing

I2APS

Company BCompany Specific

processing

Translate from RosettaNet standards to Company A system data set.

Translate from RosettaNet standards to Company Bsystem data set.

source: RosettaNet




Problem that RosettaNet tries to solve

Standards needed to enable system-to-system

B2B collaboration.

Helps solving some semantic problems in

specific industry by providing message

guidelines, dictionaries and unique identifiers

Defines standard business processes

Reliable messaging over Internet




B2B Process Integration

Process PO

Send POCustomer

Send POSupplier

ProcessSales Order

Customer Supplier

Receive POAcknowledge

Send POAcknowledge

Send POResponse

Close

Send PO

Receive POResponse

Send POResponse

Acknowledge

Receive PO

Send POResponse

Receive POResponse

Acknowledge

Receive PO

CheckCustomer

CheckCredit

CheckAvailability

Create SalesOrder

Receive POAcknowledge

Send POAcknowledge

Send POResponse

Close

Receive PORequest

SelectSupplier

GenerateRFQ

SendRFQ

Select RFQResponse

SendPO

Close

Send PO

Receive POResponse

Send POResponse

Acknowledge

Receive PO

Send POResponse

Receive POResponse

Acknowledge

Receive PO

CheckCustomer

CheckCredit

CheckAvailability

Create SalesOrder

Private process(Company -specific)

Public process(Standard)

Public process(Standard)

Private process(Company -specific)

PO

CRM

SCM

ERP

Fig

ure

prov

ided

by

Vitr

iaS

yste

ms




ebXML Provides a Standard Way to:

Exchange business messages

Conduct trading relationships

Communicate data in common terms

Define and register business processes

source: www.ebxml.org




What does ebXML do?

Lowers the cost/complexity of electronic business

Facilitates global trade and puts SMEs and developing nations in the picture

Expands electronic business to new and existing trading partners

Converges current and emerging XML efforts

Eliminates dependence by supporting any language, any payload, any transport




ebXML Specs--Modular Suite

Technical Architecture

Business Process

Registry and Repository

Collaboration Protocol Profile and Agreement

Message Services

Core Components




ebXML ExampleUsage Example

33 Build System

Specifications

Profiles

Scenarios

Request ebXML specification

11

44 Register company profile

Query about Company X

55

Request Company X’s S

cenario

99

DOBUSINESS!

11

DOBUSINESS!

11

Send Company X’s Scenario

1010

ebXML BP Model

ebXML BO Library

Send Company X’s Profile

66Submit TPA77

TPA Accepted88

Send ebXML specification 22




ebXML Registry & Repository

Repository

Registry

SECURITY LAYER

POINTS AT

API

BusinessApplication Interface

HumanInterface

PUBLISH TO

ebXML specificationSchemas TPP

Objects w. MetaDataReference Content




ebXML Registry & Repository

Content

XML Content ReferencingAccess Index

Registry

Interface Information Model

Associated References

Registration of Domain

Classification & Ownership

ebXML conformant XML object

Collections & Versioning

TransportLayer

Request Response

Detail Constraints

Industry DomainBusiness Process

Details Content

Action Status

Remote ebXMLRegistry

Registry Service InterfaceOther Registry

Service Interface(s): UDDI, CORBA

Compatibility Wrappers

Registry Services

Repository

Access Syntax in XML




Contents





Paradigm shift

Service orientationService oriented architecture (SOA)Service oriented computation (SOC)Enterprise service bus (ESB)




Tiers 1,…,n; where are we coming from

UI User Interface

Application

DB Database

Terminal

MainframeMini

File server

DB server

PC Client

UI

App

DB server

PC Client

UI

Client App

1-Tier 2-Tier 3-Tier

Server App

DB servers

PC Client

Browser

n-Tier

Server Apps

Client Apps

Server Servers

Components




Middleware

Application logicTransactionProcessing Monitor

Middleware

User Interface




Read or update the database?

To ReadTo Update

Are very differenttypes of applications




TransactionsTransaction

is an action that changes the state of an enterpriseis a collection of actions that are governedby "ACID" properties

ACIDAtomicity

All or nothingConsistency

Achieve a stable end state or abortIsolation

The changes that the transactionmakes to shared resources becomevisible only after the transactioncommits

DurabilityTransaction´s effects are permanentafter it commits.

Transaction Processing Monitor helpsthe applications to achieve ACID properties




Distributed transactions

Distributed transactionsCan span multiple nodesCan update different types of databases from different vendorsCan span different tp-monitorsConfirm to ACID properties

CoordinationCommit coordinator (root node)Subordinate NodesTwo-phase commit protocol1. Prepare-to-commit2. Commit

Root node

Subordinatenode

Subordinatenode




Distributed transactions in practiceComponent based programming

Everything is made of componentsReusable components

Application server platformsmanage componentstransactions and ACID properties"component containers"Hide complexities of transactionmanagement

Distributed transactionsDifficult to implementDifficult to manageDifficult to use for B2Bi




Client - Server applicationsExample: Material system for health careGUI: SQL WindowsApplication and database platform: Tandem Nonstop (today HP NonStop)Client components support business functions

Customer and organization managementProduct and inventory managementInventory managementOrder management

Server components offer servicesInsert, update, delete, query

CustomersProductsOrdersDeliveries

ServicesExpose interfacesHide internal data structuresInvoked by nameLocation independenceCheck for authorization to useVersion control from very start




Contents

Business and technology viewsProcess maps, need for integration (EAI)Integration topology and stackBusiness integrationEvolution of transactional systems architectureService oriented architecture (SOA)Business Process Management (BPM)After this: Case METSO 15:00




Web services

XML – Standard Language for denoting information content and process control SOAP - (Simple Object Access Protocol) XML based Messaging ProtocolUDDI - (Universal Description, Discovery and Integration) Yellow Pages for Web ServicesWSDL - (Web Services Description Language)

Middleware

Data Tier

Web server

Java components

html pages

Servlets

html over http

xml over http

soap over http

Web services acronyms




Service oriented architecture (SOA)

New buzzword in Enterprise systems architecture

SOA expresses a software architectural concept that defines the

use of services to support the requirements of software users

Most definitions of SOA identify the use of Web service

technologies (SOAP and WSDL) in implementation. However,

SOA can use any service-based technology

SOAs comprise loosely joined, highly interoperable application

services (platform independency)

E.g. Wikipedia (www.wikipedia.org) good for current information




Enterprise service bus (ESB)

“ESB refers to a category of Web services standards based middleware infrastructure products or technologies that enable aservice-oriented architecture via an event-driven and XML-based messaging engine”Key benefits

faster and cheaper accommodation of existing systems increased flexibility: easier to change as requirements change standards-based




SOA and ESB

Source:www.ibm.com/developerworks/ web/library/wa-soaesb/.




Contents





Process map

Supplier CustomerFunctions

Core processes




Modeling the business process

Actors, participants in the process: SwimlanesTask: Input, process, outputFlow: Sequence of tasksControl: Decisions that affect the sequenceEvents: Start, End, ExceptionsMessages: Message exchange between actorsCompositets: Groups of tasks







From process model to process exection

BPMN (Business Process Modeling Notation)Human understandable version of the process

BPEL (Business Process Execution Language)Machine understandable version of the process




Orchestration of a process

Execution of the business process (BPEL code)

BPEL engine

Web Services - interfaces

Business services

Core data




BPMS addresses the business process life-cycle

Design•Graphical modeling

•Business & process rules•Simulation and testing

Execute Process•Workflow

•Automation•Integration

•Business rules•Portal/forms

Monitor/Manage•Real time dashboards

•Reporting

Analyze/Optimize•Dashboards

•Historical analytics•Performance mgmt

•Simulation

BPMS

Business ProcessManagement Suite

Source: Forrester




The confusing BPMS vendor landscape

BPMFunctionality

EnterpriseApplication

SAP, Oracle

Pure-Play BPM

Lombardi, MetastormPegasystems, Savvion

Integration

TIBCO, Vitria, webMethods

EnterpriseContent Mgmt

EMC/documentum,Open Text, FileNet

ApplicationPlatform

IBM, BEA, Microsoft,Sybase, SUN

Traditional B2B

Sterling Commerce,Inovis, GXS

Source: Forrester




Two different kinds of BPMS

Separate market

Mid-late1980s

Mid-late 1990s

Workflow

Document imaging

Business Process

Management

Expanded into BPM

2002-05 2006+

Enterprise ApplicationIntegration

BusinessProcess

IntegrationPROCESS

FOCUS

Business Process

Management

Human-centric

Integration-centric

Source: Forrester




Match BPMS to process characteristics

•Document management integration

•Contract management

•Accounts payable

•Claims dispute resolution

Document intensive

•Business rules engine

•Business intelligence

•Underwriting

•Loan origination

Decision intensive

•Task list/workflow portal

•UI development

•Organization management

•Forms management

•Claims processing

•Employee on-boarding

People intensive

•Integration tools

•Transaction management

•Partner profile mgmt

•Order fulfillment

•HIPA transactions

•Straight thru processing

System intensive

Required featuresExample processesProcess Characteristics

•Document management integration

•Contract management

•Accounts payable

•Claims dispute resolution

Document intensive

•Business rules engine

•Business intelligence

•Underwriting

•Loan origination

Decision intensive

•Task list/workflow portal

•UI development

•Organization management

•Forms management

•Claims processing

•Employee on-boarding

People intensive

•Integration tools

•Transaction management

•Partner profile mgmt

•Order fulfillment

•HIPA transactions

•Straight thru processing

System intensive

Required featuresExample processesProcess Characteristics

Source: Forrester




Business Process Management (BPM)




Processes and services

Referral

Acute care

Need for care?

Plan care Make orders Assess results

Care needed?

Assesment DischargeExecute care

Book service Execute service Record results




BPM & SOA, business meets technology

Business processesBusiness servicesCompositeservicesAtomicservicesApplications




Questions?

from message passing to service orientation. - aalto message passing to service orientation. ......

Documents