the next generation messaging technology - makes web services effective maria e orlowska the...

The Next Generation Messaging The Next Generation Messaging Technology Technology

- - Makes Web Services EffectiveMakes Web Services Effective

Maria E OrlowskaMaria E OrlowskaThe University of QueenslandThe University of Queensland

School of ITEESchool of ITEE

AustraliaAustralia

APWeb’04 – April 04

2

OverviewOverview

• Process oriented computing,

• Issues with BPM (Business Process Management),

• WS (Web Services) – a new promise,

• Why it is hard to deploy WSs,

• Will HMT (Harmonising Message Technology) – a smart messaging help ?


3

Process meets TechnologyProcess meets Technology

• Could web services live up to their promise and spell the end of integration dramas forever?

– Several success stories already reported,

– Web services standards around collaborative capabilities of UDDI (Universal Description, Discovery and Integration)

WSDL ( Web Services Description Language) and SOAP (Simple Object Access Protocol) which respectively

catalogue, describe and publish the various Web services offered by a service provider,

– Web services should hide the complexity of business processes and focus on getting data flow as efficiently and simply as possible,


4

‘It is a massively complex undertaking and the devil is literally in the detail’

David Clarke, Managing Director, Webjet


5

Process-Oriented ComputingProcess-Oriented Computing

Business Process

Management

Application Services and Components

Database Management

User Interaction

Configure,Coordinate,Collaborate,Integrate

Execute

Persist

Present,Interact

PresentationLogic

ProcessLogic

BusinessLogic

DataLogic


6


Business Process

Management


Database Management

User Interaction


Execute

Persist

Present,Interact

PresentationLogic

ProcessLogic

BusinessLogic

DataLogic

Focus of Business Focus of Business Process Modeling and Process Modeling and

ManagementManagement


7


Business Process

Management


Database Management

User Interaction


Execute

Persist

Present,Interact

PresentationLogic

ProcessLogic

BusinessLogic

DataLogic

Focus of Application Focus of Application DevelopmentDevelopment


8


Business Process

Management


Database Management

User Interaction


Execute

Persist

Present,Interact

PresentationLogic

ProcessLogic

BusinessLogic

DataLogic

Focus of process-Focus of process-oriented application oriented application

development and development and deploymentdeployment


9

Key issue - Separation of Process LogicKey issue - Separation of Process Logic

Process Logic

Application Logic

Data

Process Logic

Application Logic

Data

DBMS

Process Logic

Application Logic

Data

DBMS

WFMS


10

Wfs - Current Computational ModelWfs - Current Computational Model

• Isolation of process logic triggers;– User initiated flow - reflecting activity/task progress

– Workflow engine initiated flow- reflecting process progress

Activity Activity

Activity

ActivityActivity Activity


11

Wfs - Current Computational Model (cont)Wfs - Current Computational Model (cont)

• Each task has predefined, generic FSM,– Creates difficulty to map activity logic to engine readable

states,

– Provides a strict meaning of the process flow,

• Simplicity for the price of restrictions,


12

Activity ExecutionActivity Execution

Scheduled Active CompletedAllocate Complete

Terminated

Abort

Recall

Process Model level

Workflow Engine level

User level

Activity


13

Process ExecutionProcess Execution


Terminated

Abort

Recall

Activity


Terminated

Abort

Recall

Activity


14

Instances ExecutionInstances Execution


15

Impossible Instances ExecutionImpossible Instances Execution - -


16

End to End Process Management (Example)End to End Process Management (Example)

Create Purchase Request

Create Purchase

Order

Send Purchase

Order

Receive Goods

Receive Invoice

Send Payment

Process

Purchase Request Service

Purchase Order

Service

Shipment Notice Service

Payment Service

Application Services

Database

Application Database


17

BPM, Application Services, and Data Model (N – M)BPM, Application Services, and Data Model (N – M)

PR PO SN INV

PR I PO I SN I INV I

N M N M N M

N M N M N M

1

N

1

N

1

N

1

N


Create Purchase

Order

Send Purchase

Order

Receive Goods

Receive Invoice

Send Payment

Purchase Request Service

Purchase Order

Service

Shipment Notice Service

Payment Service


18

Process ModelingProcess Modeling

PR 1A 20B 30C 20

PR 2A 30D 10E 15

PO 1A 50B 30

PO 2C 10D 10

PO 3C 10E 15

SN 1A 50B 30C 10

SN 2D 5

SN 3D 5

SN 4C 10E 15

INV 1A 50B 30C 10D 10

INV 2C 10E 15


Create Purchase

Order

Send Purchase

Order

Receive Goods

Receive Invoice

Send Payment


19

Process ModelingProcess Modeling

PR 1A 20B 30C 20

PR 2A 30D 10E 15

PO 1A 50B 30

PO 2C 10D 10

PO 3C 10E 15

SN 1A 50B 30C 10

SN 2D 5

SN 3D 5

SN 4C 10E 15

INV 1A 50B 30C 10D 10

INV 2C 10E 15


Create Purchase

Order

Send Purchase

Order

Receive Goods

Receive Invoice

Send Payment

Item C is no longer required and is cancelled on the purchase

request


20

The HMT ConceptThe HMT Concept

• A technology allowing messages coordination from multiple parties,

• Some characteristics:– It should be easy to use – minimal technical skills required to set

up a collaboration,

– It should be easy to join (leave) the collaboration arrangement,

– Rich and extensible language to specify relationships between messages,

– Provide a natural subsumption of workflows-like collaboration,


21

Functionality Functionality

• HMT supports:

– Checking the message template for completeness and authentication (check)

– Storing the message persistently (store),

– Evaluate specified collaboration rules (evaluate) with resulting one of the functions:

1. Create a new instance of a msg template (create),

2. Send a message (send),

3. Store for re-evaluation (delay),

4. Accept transaction (transac)


22

Collaboration SpaceCollaboration Space

• Massage harmonization is defined within a Collaboration Space,

• A Collaboration Space (CS) consists of:– Registered Partners (security issues, who is allowed to

participate)

– Set of message templates ,– Set of rules (temporal first order logic in terms of message

attributes)

• Only one create function is expected to be applied before send,

• CS deals with many “single steps” to form the overall collaboration,


23

Message TemplateMessage Template

• Each Message Template (MT) has it’s XML schema,

• Several functional parts can be distinguished;– Scheduling attributes such as CS_id, MT_type_id, instance _id

(optional)

– Content structural attributes (those which forms terms in rules specification),

• Attributes can be mandatory and optional,

• Other constraints


24

Rules SpecificationRules Specification

• Each rule LHS is an expression (temporal first order logic expression) with literals being attributes of MTs from that CS,

• Each rule RHS is a HMT function either create (MT) followed by send (MT) or send (MT)

• Rules may be in conflict and not leading to a unique action – need for methods for design and verification,


25

Further issues for MT and RulesFurther issues for MT and Rules

• Those two entities must be tightly “integrated”,

• One framework for design and specification – systems completeness:

– Each rule is supported (LHS and RHS),

• Impacts of modifications either rules or MTs


26

Collaboration Space in Messaging ServiceCollaboration Space in Messaging Service

Collaboration Space

Message Templates

MT01 MT02 MT03 MT04 MT05 MT06

Incoming MessageInstances

Outgoing MessageInstances

MT07 MT08

MessageTransformationRules

MT08.I001

MT01.I002

MT01.I003

MT02.I001

MT03.I001

MT03.I002

MT05.I001

MT08.O001

MT06.O001

MT09.O001

MT07.O001

MT06.O003

MT06.O002

MT04.I001

MT09

MT07.O002

MT08.O002

S01

S02

S03

S04

S05

R01

R02

R03

R04

R05

ReceiversSenders


28

Message-Oriented BPM using HarmonizationMessage-Oriented BPM using Harmonization

Messaging Service ensures that A, B, C, and D are performed in the right order as well as only messages are used to communicate with BPM Objects. This is the goal of the HMT invention. The HMT would provide a SINGLE platform to manage both coordinative and collaborative communication.

MessagingService

BPM Object X

MessageTemplates

Outgoing Messages

Incoming Messages

Public MethodsMessageHandler

BPM Object Y

MessageTemplates

Outgoing Messages

Incoming Messages

Public MethodsMessageHandler

A B C D


29

ChallengesChallenges

• Requirements for HMT:– Traditional Wf model must be a special case,

– Simple graphical language to specify the rules,

– Process modelling shouldn’t be harder,

– Validation and verification methods should assist with specification,

– Process monitoring and transactional behaviour should be guaranteed,

– The model should formally capture Wf integration,

– Scalability for process-intensive environments,


30

Concluding RemarksConcluding Remarks

Promise:

• HMT offers flexible service composition,

• HMT is applicable to communicating active RFID devices,

Status: first demo scheduled for Nov 2004 at SAP Future Scope event, Germany,

More Info: http://www.itee.uq.edu/~dke

the next generation messaging technology - makes web services effective maria e orlowska the...

Documents

activity logic

process flow

management slide

deployment slide

webjet slide

ws web services

web services standards

various web services