DBE, un esempio diEcosystem Oriented Architecture,

la piattaforma tecnologica

Pierfranco FerronatoDBE Chief Architect

Soluta.net

Managing Technology Complexity

Ecosystem Architecture

E W

E1 W1 Wn

Enterprise Architecture

Application Architecture

Design

Adapted with permission from Mike Rosen

“Hic sunt leones” “Here there be tygers”

Across Enterprises = Ecosystem

A different set of problems

• Functional Reference Model• Single Point of failure• Technology - Registries• Technology – Repositories• UI non only RPC• Services...

Functional Reference Model

• The “single reference model” is not a feasible objective (even if was attempted in the past, aka “Big Picture”)

• Support different functional models• Interoperability?• There are standard reference models for each

business domain– Lack of universal vocabulary– Domain Ontology

• Who owns the models and registries?– Must be the community itself!!!!

A different set of problems - Services

• Across enterprises requires a new set of business services– Payment– Business Contract & Negotiations– Billing– Trust– Reputation– Legal compatibility

• Re-think:– Service Discovery– Reliability-guaranteed delivery– Security– Long running Transactions– XML Firewall

Single point of failure in SOA

Service Oriented Architecture is an architectural style that evolved from RPC

It does scale up, inside an enterprise

Where is semantics?

UDDI v3 is centralized

Designed for intranet!The owner of models and registries need to be the community itself

Would you give the keys of your house to an external entity for the benefit of the community?

The way to go: pills

Add semantics to service description

Model Repository (design time)Adopting a decentralized architecture

Service Registry (runtime)

logical name of service ->end-point of the servicesDynamic network architecture

Distributed data storage

P2P architecture can help (Don't have a prejudice)

Support IP service change

Implementing a evolutionary based schema for model repository

Dependency, versioning, inheritance, merge...

Digital Business Ecosystem

Topologia

H

H

H

H

H

H

H

H

H

H

C

PProvider

Consumer

Service invocation and

use

P

P

PP

P

P

P

P

CC

C

C

C

C

S

S

S

K

K

Evolutionary Environment

Service Execution Environment

Exploring/Search

Execution

Service Factory Environment

BusinessModelling

ComputingModelling

Development

DBE Development Process

● Publish Service Manifest● Register Proxy● Publish BPEL

DBE Community Instance

DBE Software Process

Service Factory

• Where services are described and developed

• Phases

1)Ontology Support

2)Business Modelling

3)Service Modelling

4)Service Development

• Support for code generation

• UML, MBA, MDA based,

• Eclipse framework 3.x based

– Automatic install and update

Execution Environment

• Where services are discovered, retrieved and executed

1)Publish

2)Search

3)Retrieve

4)Execute

• Contains a Servent (DBE Application Server, SERVer + cliENT)

• Java v1.4 based (migrating to v1.5)

• REST on HTTP protocol

• Contains a smart proxy deployment sub-system

• P2P based, origin from Sun's Jini(tm)

• Evolutionary Environment

– A parallel environment where service chains are created and optimized

Service FactoryBusiness Modelling

Business Modelling

• Ontology

• Business Modeling Languages (BML)– CIM description of the business side of firms– The BML contains information like: service offered and

requested, resources, processes, business model and motivation, policies and agreement, location and event related to business and so on.

• Ontology

• Business Modeling Languages (BML)– CIM description of the business side of firms– The BML contains information like: service offered and

requested, resources, processes, business model and motivation, policies and agreement, location and event related to business and so on

• SBVR

Business Model Package

Event*Associations

LocationTypePath*Associations

AssessmentInfluenceMeansEnds*Associations

CollaborationActivityBusinessActivityBusinessProcessTransactionCommitmentConstrainContractRole*Associations

BusinessEntityNetworkRoleNetworkProductServiceAsset*Associations

ServiceParameterServiceProfileContactInfo*Associations[1]

Event LocationMotivation ProcessOrganizationSSL

From original work of ITA, Spain

From the Zachman Framework

Ontology Editor

Ontology-type Attributes get “expanded” on the BML Data Editor

From original work of I\TA, Spain

From original work of ITA, Spain

BML Model: Hotel Example

BML Data Editor: Hotel Example

Entering Data for the Hotel model with the BML Data Editor

From original work of ITA, Spain

Service FactoryService Modelling

Service Modelling

• Service Description Language (SDL)– The SDL describes the technical specification of a DBE

service. – The SDL is able to describe the DBE service in a double-facet

fashion. One facet refers to the Semantic Description of DBE Services and the other refers to the description of the DBE Service Interaction Specification.

– SDL is a semantically rich abstraction of the WSDL

SDL MetaModel

– The SDL is defined using a UML MetaModel

Sdl MetamodelUml Editor(ArgoUmlPoseidon

MagicDraw)

Emf Plugin

Sdl Editor

SDL Editor:From Metamodel to Model

Dbe Developer

SME user

Service Model

(SDL model)

WSDL

KB

Java codeSdl

crosscompile

r

Generate/reverse

Execution

Environment

The Service Manifest

• It contains– Complete representation

of a Service– Business models +

computational model + Information• Price schema• Address

– Reference to 'foreign' ontology

• XML/XMI encoding of the models

XMI BML Model (M1)XML BML Data (M0)XMI SDL Model (M1)Fitness Data

Service Manifest

Distribute

dRegistry

P2P Net

work

Proxy

Ontology

DomainOntologie

s

Service FactoryService Development

Service development

• External Services are to be integrated in the DBE– Support for SMEs without any IT systems

• The DBE is a semantically rich middleware, not an IDE for service development– Not invasive

• The service proxy is a mediator to legacy services• It's auto generated

– Reflective capability

Modelling & Deploy

DBE StudioDBE Studio

Semantic

Distributed

Registry

P2P Network

(FADA)

ModelReposito

ry

IntegratedCIM

Editor

IntegratedCIM

Editor

IntegratedPIM

Editor

IntegratedPIM

Editor

IntegratedPSM

Editor

IntegratedPSM

Editor

XMI CIM Model (M1)XML CIM Data (M0)XMI PIM Model (M1)Fitness Data

Organizationserviceproductmotivationcontract...

input/outputsmessagestypeparameterserrors...

JavaexceptionsWSDLWS.Net...

Ontology

Register

Publish

➀➁

➂

➃

➄

BMLSDL

ServentServent Deploy

6

Execution Environment

Main Components

• Servent– P2P Application Server

• Service Registry– Service Manifest Registry– P2P based– Self healing

• Proxy Registry (aka FADA)– P2P based– Scale free network based (non random, non

hierarchical)• DBE Portal

– Entry point for SMEs,

The servent

DBE SERVENT(provider)DBE SERVENT

(consumer)

Adapter

SOAP layer

Exec

uto

r

ServiceProxy

LegacyConsumer application

LegacyProvider

application

UIMessag

es

• DBE “Operative System”– A decentralized P2P container

• Smart proxy– End-point mediator– Serializable Java imperative

code– Run-time generated– Run-time distributed– Concept borrowed from Jini

• Hides the underline complexity

• It keeps a reference to its Service Manifest

Search & Execute

XMI BML Model (M1)XML BML Data (M0)XMI SDL Model (M1)Fitness Data

Service Manifest

Semantic

DistributedRegis

try

Service

Registry

(FADA)

Proxy

Proxy

En

d p

oin

t

Download Proxy

Service Consumer

Service Provider

Execute Service

XMI BML Model (M1)XML BML Data (M0)XMI SDL Model (M1)Fitness Data

Servent Servent

Register ProxyDBE StudioDBE Studio

Publish SM

OntologyOntology

DomainOntologies

Download SM

1

2

Search SM

Application

Application

Fro

nt-

en

d

3

45

6

DBE Portal

From original work of Intel, Ireland

Multiple DBE Portals

From original work of Intel, Ireland

Structural Services

• Model Repository• Accounting• Billing• Security (Authentication)• Reputation• Decentralized Data Storage• Fitness data

DBE Architecture

From original work of LCE, UK

References

www.digital-ecosystem.orgwww.digital-ecosystems.org

a.nicolai@t-6.itpferronato@soluta.netmiguel.vidal@sun.itjohn.m.kennedy@intel.com