Download - © 2005-2006 The ATHENA Consortium. 6-5. From PIM4SOA to Peer-2-Peer (P2P),

© 2005-2006 The ATHENA Consortium.

6-5. From PIM4SOA to Peer-2-Peer (P2P)

<Presenter>

<Company>, <Country>

<E-mail>

2© 2005-2006 The ATHENA Consortium.

Outline

• Distributed Resource Management and Coordination

• References


Distributed Resource Management and Coordination


Org. Z

Org. B Org. Y

Adaptive architectures (P2P)

• Peer-to-Peer business resource management for virtualization and decentral management of business objects, services, and processes

• Self-healing, -configuring, -optimizing, -protecting properties for distributed enterprise networks• Intelligent agents: pro-active event-driven communication & situated semantic reasoning nodes support

interoperability in decentrally managed, distributed enterprise networks

Support enterprise and business process evolution

Org. A

Resource

P Peer/Agent

P P P

P P

register, retrieve, search,,subscribe

Public Registry/Repository

Infrastructure


P2P Business Resource Management Framework

• Handling of Structured Business Documents

• Security and Access Control

• Integration with Business and Backend Storage Systems

• Integration with WSDL / SOAP based Web Services

• Support for robust execution of BPEL base business processes

BusinessApplication

WebService

ProcessExecution Engine

Resource Management Framework (RMF)

BR

MF Business Object Management Layer

Business Actor Management Layer

WS Discovery(P2P Registrar)

SOAP/HTTP Tunneling

Robust Process

Execution


Business Actor Management Layer

End User / Developer

Web ServiceRegistrar

(core)

API

End UserApplication

API

End UserApplication

API

End UserApplication

Robust ProcessExecution Support

(core)HTTP & SOAP

Tunnel

(core)


P2P system model (RMF)

Peer

PeerGroup

Application -represented by

1

1

*

-contains1

ResourceMetadata

-register, deregister

*

*

* *

-query : Query-credentials : RoleSet

RequestContext*-search, lookup, subscribe, retrieve

*-result, notify

-search, lookup, subscribe

*

-return, notify

*

P2P Resource

11

Business Resource

*

-contains 1Reference

*

-contains

1

1 -references

1

DHT PeerNo-Index Peer


P2P domain model (BRMF)

OrganisationUnit

Application

User

BusinessResource

ResourceMetadata

Role

-consists of1 *

1

*

-use*

*

-owns

1

*

-has-a

11

DomainAccessPolicy

1-access, consume, create, modify

*

-is assigned 1..*

*

*

-refers-to

1

RoleSet

-contains 1

*

BusinessObjectBusinessService BusinessProcess

BusinessDocument


Business Resource ManagementFramework (BRMF)


Object Binding Components (BOML)

BusinessObject

SchemaProfileEditor

Business Object Binding Compiler

Object SpecificQuery&Access API

Generic ResourceAccess APIA

pp

lic

ati

on

D

ev

elo

pe

r A

PI

RMF ResourceObject

Object BackendBinding

BusinessObject

RMFResource

ObjectManagement

System

RMF

ResourceBindingProfile

Representation in the P2P-infrastructure

e.g. documentIn a

documentmanagement

system

XML schemaXML binding description

Set of basic functionality (publish, search via generic properties)

Derived from concrete binding specification, may use predefined

profiles for specialized queries(e.g. for WSDL, ebXML)

dynamically plugged backendaccessor component


Schema + Binding description

<xs:schema …><xs:element name="RFQ" type="RFQ_Type"> …</xs:element><xs:complexType name="RFQ_Type"> <xs:sequence> <xs:element name="PartID" type="xs:int"/> <xs:element name="PartName" type="xs:string"/> <xs:element name="Quantity" type="xs:string"/> <xs:element name="TechnicalSpec" minOccurs="0"> <xs:complexType …>

… </xs:element> <xs:element name="Originator" type="Contact_Type" minOccurs="0"/> </xs:sequence></xs:complexType><xs:complexType name="Contact_Type"> <xs:sequence> <xs:element name="ContactName" type="xs:string" minOccurs="0"/> <xs:element name="ContactAddress" …/> </xs:sequence></xs:complexType></xs:schema>

<?xml version="1.0" encoding="UTF-8"?><cbf:binding xmlns:cbf="http://www.castor.org/SourceGenerator/Binding" defaultBindingType='element'>

<cbf:elementBinding name="RFQ"> <cbf:rmfBinding inlineWrapper="false" copyRootAccessors="true"> <cbf:keyWords> <locationPath>/RFQ/PartName</locationPath> </cbf:keyWords> </cbf:rmfBinding></cbf:elementBinding> </cbf:binding>

Java-Binding-Package

RFQ_RMFResource


Handling business documents from a programmer’s point of view

RFQ_RMFResource rfq =new RFQ_RMFResource();

rfq.setPartName(„Airbag");rfq.setPartID(1003452);rfq.setQuantity("100000");

rfq.requireCredentials(…);

rfq.publish();

// join P2P, set credentials

Enumeration<RFQ_RMFResource>rfqs = RFQ_RMFResource

.search_PartName(„Airbag“);

// select one rfq …rfq.trackRemoteUpdates(this);

rfq.setMaxCost(450);rfq.commitChanges();

natural access to the document content

restrict accessibility

publish the resource

Peer A Peer B

stay informed about the remote state

identify and retrieve objects based on special properties

propagate own changes


Realization of the CPD application

OEM

PU

T1-Supplier

T2-Suppliers

RfQ

references

Document Management

System

provideaccess

Mapping of EPC seems naturalTo a P2P system supportingPropagation of content based event

change of RfQ statecauses event at T1-Supplier

Then what is our relationship to theDifferent modelling layers/levels?


Components for backend access

RMF

ComponentManager

ObjectBinding

A

ObjectBinding

B

BackendBinding

X

Application

access part X

get binding X

return content of X

BackendBinding

Y

BackendBinding

XObject

ManagementSystem X

instantiateaccess

backendlocatable & loadable

on demand

components managedwithin the system itself


Layers, models & relationships (1/2)

WS

SOA

EM

CBP

Pla

tfor

mP

SM

PIM

CIM

WS

SOA

EM

CBP

RMF

P2P

„cross“-mappings exist

WS

SOA

EM

CBP

RMF

P2P

adaptive technologies may be used for WS


Layers, models & relationships (2/2)

WS

SOA

EM

CBP

Pla

tfor

mP

SM

PIM

CIM

WS

SOA

EM

CBP

RMF

P2P

WS

SOA

EM

CBP

RMF

P2P

in order to use them, theyshould be reflected in themodeling layer(s) above


References


References

• ATHENA A6, "D.A6.3: Model-driven and Adaptable Interoperability Framework", ATHENA IP, Deliverable D.A6.3, 2006.

• ATHENA A6, "D.A6.4: Model-driven and Adaptable Interoperability Infrastructure", ATHENA IP, Deliverable D.A6.4, 2006.


This course has been developed under the funding of the EC with the support of the EC ATHENA-IP Project.

Disclaimer and Copyright Notice: Permission is granted without fee for personal or educational (non-profit) use, previous notification is needed. For notification purposes, please, address to the ATHENA Training Programme Chair at [email protected]. In other cases please, contact at the same e-mail address for use conditions. Some of the figures presented in this course are freely inspired by others reported in referenced works/sources. For such figures copyright and all rights therein are maintained by the original authors or by other copyright holders. It is understood that all persons copying these figures will adhere to the terms and constraints invoked by each copyright holder.