e Business Architectures Sept 05

8/10/2019 e Business Architectures Sept 05

1/52

Adomas Svirskas

Architectures and Techniques for modern E-business Systems

Architectures and Techniques for modern

E-business Systems


2/52

Adomas Svirskas


Agenda

E-Business, E-Commerce, C-Commerce

E-business Architecture

Integration issues and solutions E-business Integration Patterns

ebXMLthe Newest Global Standard

Positioning

Main concepts State of the Art

Quality of Business Service


3/52

Adomas Svirskas


E-Business and E-Commerce

The two concepts do not mean the same

They are often confused

E-commerce is a part of E-business along with: Infrastructure

Customer Relationship Management (CRM)

Business Intelligence

Supply Chain Management


4/52

Adomas Svirskas


E-Business and E-Commerce

E-commerce, or electronic commerce, is conducting business

communications and transactions via computers and over networks. It

is buying and sellingof goods and services through digital

communication. E-commerce also includes transactions on the WorldWide Web and Internet, and modes such as electronic funds transfer,

smart cards, and digital cash.Introduced around 1994 (Amazon.com).

E-business, or electronic business, derived (the term) from 'e-

commerce'. It is conducting business on the Internet, but not just

buying and selling but also servicing customers and collaboratingwith business partners. The term conveys that the business conducts its

business entirely online.Introduced around 1997 (IBM).


5/52

Adomas Svirskas


E-business Systems Evolution

Proprietary corporate solutions

EDIE-business for the big

Ad-hoc solutions using the Internet

The XML promise and reality

The need for E-business standards

ebXMLthe latest focal point of E-

business standardisation efforts


6/52

Adomas Svirskas


Collaborative Commerce

Opening-up ERP systems and business

application of SMEs

Integrating them into multi-enterprise

collaborative commerce framework

Interaction between businesses independent

on size and geographical location


7/52

Adomas Svirskas


It is All about Integration

The High-Level Goals:

Independence of business operations from

underlying technology

Flexibility

Ease of access for businesses of various size

Cost effectivenessInvestment protection


8/52

Adomas Svirskas


Types of Integration (scope)

With regard to integration scope there are

two major classes:

Enterprise Application IntegrationEAI

Typically occurs within an enterprise

Known as Application-to-ApplicationA2A

Business-to-Business Integration

B2Bi

Typically used for inter-enterprise integration

Known as Extended Enterprise


9/52

Adomas Svirskas


Types of Integration (technology)

Application Tiers

Business Process

Presentation Application

Database

Integration Middleware

Component frameworks

J2EE, .NET, CORBA

Message Queuing

JMS, MQSeries

Application Servers

Web Services EDI

XML Vocabularies


10/52

Adomas Svirskas


Business Process Integration

From http://eai.ebizq.net/bpm/aubin_1.html

Commercial Products:

TIBCOVitria

BEA

Sybase

Oracle

...


11/52

Adomas Svirskas


E-business Integration Patterns

Mentioned positioning of Integration types

theoretically yields 3D classification matrix

Not all combinations are equally viable

Most frequently used proven approaches are

referred to as patterns

IBM did a good job describing E-business patterns

http://www.ibm.com/developerworks/patterns


12/52

Adomas Svirskas


E-business Integration Patterns

The document exchange pattern

The exposed applications pattern

The exposed business services pattern

The managed public processes pattern

The managed public and private processespattern


13/52

Adomas Svirskas


Document Exchange Pattern


14/52

Adomas Svirskas


Document Exchange Pattern

Suited for partners replacing papers by

electronic data interchange

Data formats and communication channels

must be agreed by partners

Tight coupling between external and

internal processes

Typically batched processingclassic EDI


15/52

Adomas Svirskas


Exposed Application Pattern


16/52

Adomas Svirskas


Exposed Application Pattern

Application tier exposed directly to the

outside world

Message Queuing or ComponentFramework as middleware

Direct coupling among partner applications

leads to poor flexibility


17/52

Adomas Svirskas


Exposed Business Services Pattern


18/52

Adomas Svirskas


Exposed Business Services Pattern

A layer between the backend enterprise

system and partner tier

This layer exposes an e-business orientedinterface

Business service interface to be agreed by

partners

Web Services technology is an example


19/52

Adomas Svirskas


Managed Public Process Pattern


20/52

Adomas Svirskas


Managed Public Process Pattern

Private and Public processes are separated

more strictly

Public processes are identified, analysedand formally described

Integration occurs at Business Process level

RosettaNet is an example

Trading Partner Agreements TPA


21/52


22/52

Adomas Svirskas


Managed Private/Public Process

Unified management environment for

public and private processes

An ambitious effort, requires redesigning ofinternal applications to externalise the

business process state and the process flow

logic


23/52

Adomas Svirskas


Layered E-business Architecture

Business Modelling Layer

Integration Layer

Business Integration Layer

Services Integration Layer

Infrastructure Layer


24/52

Ad S i k


25/52

Adomas Svirskas


ebXML and Integration Patterns

ebXML is intended to support managed

public processes pattern:

Various middleware types are supported

Focus on E-business application rather

application integration

Declarative definition of public businessprocesses

Support of partner agreements

Ad S i k


26/52

Adomas Svirskas


ebXML Modelling Methodology


27/52

Ad S i k


28/52

Adomas Svirskas


ebXML Functional Services View

The FSV Addresses:

Functional capabilities

Business Service Interfaces

Protocols and Messaging Services


29/52

Adomas Svirskas


30/52

Adomas Svirskas


ebXML Framework contd

Core Components: Those provide the business

information that is encoded in business documents

that are exchanged between business partners. Registry/Repository: This is useful for more than

merely conducting business searches. Some

business scenarios depend heavily on registries to

support setting up business relationships.

Adomas Svirskas


31/52

Adomas Svirskas


ebXML Framework contd

Collaboration Protocol Profiles (CPP)andAgreements (CPA): These are XML documentsthat encode a party's e-business capabilities or two

parties' e-business agreements, respectively.

Transport, Routing and Packaging:TheebXML messaging services provide an elegantgeneral-purpose messaging mechanism. TheebXML messaging service is layered over SOAP(Simple Object Access Protocol) and can transportarbitrary types of business content.

Adomas Svirskas


32/52

Adomas Svirskas


ebXML Business Scenario

Adomas Svirskas


33/52

Adomas Svirskas


ebXML State of the Art

Started in November 1999 sponsored by

OASIS and UN/CEFACT

Framework specifications delivered in May2001

Steady adoption by commercial vendors,

government organisations and Open Sourcecommunity

Adomas Svirskas


34/52

Adomas Svirskas


ebXML State of the Art contd

ebXML in production

www.steel24-7.com

www.papinet.org

HL7

ebXML pilots

Sun Microsystems with Sabre

Sun Microsystems with GM

US CDCwww.cdc.org

British Telecom

Adomas Svirskas


35/52

Adomas Svirskas


ebXML State of the Art contd

Not all the parts of the framework areadopted equally

ebXML Messaging gets most of theattention

Core Components are of wide interest

Full-scale support of business processmodelling and run-time interpretation is stillto come

Adomas Svirskas


36/52

Adomas Svirskas


Towards Quality of Service

Integration-level QoS

Business-level QoS

Service Level Agreements

Research directions

Adomas Svirskas


37/52

Adomas Svirskas


Integration-level QoS

Collective measure of the level of service aprovider delivers to its customers or

subscribersAvailability (downtime)

Response time and throughput

Abandoned transactions

Speed of fault detection and correction

...

Adomas Svirskas


38/52

Adomas Svirskas


Business-level QoS

Based on business metrics and profit

models

A simple profit model:Time = W- the response time constraint

Revenue = r * (number of completed transactions)

Cost = c * (number of responses longer than W)

Profit = Revenue - cost

Closely related to the integration-level QoS

via profit-oriented feedback control

Adomas Svirskas


39/52

Adomas Svirskas


SLAMain Aspects

Legal: Provides for the negotiations

between customer and service provider

Operational: Provides for the execution ofthe services under the SLA

Financial: Provides an assessment of the

financial implications in the SLA

Adomas Svirskas


40/52


Research Directions

Modelling of inter-relation between the

integration-level and business-level QoS

Monitoring, measurement and managementof business processes based on QoS levels

Instrumenting of the above in ebXML or

similar environment

Implementing in practice

Adomas Svirskas


41/52


Related Work

Integration-level QoS and BP management

SLA specification language

Adomas Svirskas


42/52


Q2B (QoS to Biz) Framework

Developed by HP Labs, 2001

Intended to:

Monitor and correlate QoS with business

metrics

Visualise results

Issue alerts according to defined thresholdsAdapt and optimise business processes based

on the


43/52

Adomas Svirskas


44/52


Q2B - Monitoring of QoS

From HPL-2001-96, HP Laboratories

Adomas Svirskas


45/52


SLAngan SLA Language

Developed by Department of Computer

Science, University College London

Part of an EU IST project

http://www.cs.ucl.ac.uk/staff/d.lamanna/tapas.html

Adomas Svirskas


46/52


SLAng Goals

Producing a formal language, with a welldefined syntax and semantics for describingservice level specifications (SLSs)

Specification of non functional features (servicelevel) of contracts between independent partiesto allow the integration with the functionaldesign of a distributed component system

Parameterisation, compositionality, validation ofservice level agreements

Adomas Svirskas


47/52


SLAng Positioning


48/52

Adomas Svirskas


49/52


SLAng - SLA Classification

Adomas Svirskas


50/52


SLAng - SLA Classification

Adomas Svirskas


51/52


SLAng Importance

Modelling and reasoning about SLAs

Translating an SLA into another

format (XML-based) Monitoring compliance to SLA

Toolkit for service composition andanalysis (assist ASP in determiningwhat SLSs they can undertake to meet)

Adomas Svirskas


52/52

Conclusions

Significant standardisation effort is being carried

out in E-Business area

Collaborative commerce is supported bypromising architectural frameworks

Quality of Business Services becomes more and

more important

Questions, comments: Adomas Svirskas [email protected]

Bob Roberts [email protected]

Documents

e Business Architectures Sept 05