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

2. 2 © 2005-2006 The ATHENA Consortium. Outline Distributed Resource Management and Coordination References

3. 3 © 2005-2006 The ATHENA Consortium. Distributed Resource Management and Coordination

4. 4 © 2005-2006 The ATHENA Consortium. Org. ZOrg. BOrg. 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

5. 5 © 2005-2006 The ATHENA Consortium. 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 Business Application Web Service Process Execution Engine Resource Management Framework (RMF) BRMF Business Object Management Layer Business Actor Management Layer WS Discovery (P2P Registrar) SOAP/HTTP Tunneling Robust Process Execution

6. 6 © 2005-2006 The ATHENA Consortium. Business Actor Management Layer End User / Developer Web Service Registrar (core) API End User Application API End User Application API End User Application Robust Process Execution Support (core) HTTP & SOAP Tunnel (core)

7. 7 © 2005-2006 The ATHENA Consortium. P2P system model (RMF)

8. 8 © 2005-2006 The ATHENA Consortium. P2P domain model (BRMF)

9. 9 © 2005-2006 The ATHENA Consortium. Business Resource Management Framework (BRMF)

10. 10 © 2005-2006 The ATHENA Consortium. Object Binding Components (BOML) Representation in the P2P-infrastructure e.g. document In a document management system XML schema XML 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 backend accessor component

11. 11 © 2005-2006 The ATHENA Consortium. Schema + Binding description … … <cbf:binding xmlns:cbf="http://www.castor.org/SourceGenerator/Binding" defaultBindingType='element'> /RFQ/PartName Java-Binding-Package RFQ_RMFResource

12. 12 © 2005-2006 The ATHENA Consortium. 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 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

13. 13 © 2005-2006 The ATHENA Consortium. Realization of the CPD application OEM PU T1-Supplier T2-Suppliers RfQ references Document Management System provide access Mapping of EPC seems natural To a P2P system supporting Propagation of content based event change of RfQ state causes event at T1-Supplier Then what is our relationship to the Different modelling layers/levels?

14. 14 © 2005-2006 The ATHENA Consortium. Components for backend access locatable & loadable on demand components managed within the system itself

15. 15 © 2005-2006 The ATHENA Consortium. Layers, models & relationships (1/2) WS SOA EM CBP Platform PSM PIM CIM WS SOA EM CBP RMF P2P „cross“-mappings exist WS SOA EM CBP RMF P2P adaptive technologies may be used for WS

16. 16 © 2005-2006 The ATHENA Consortium. Layers, models & relationships (2/2) WS SOA EM CBP Platform PSM PIM CIM WS SOA EM CBP RMF P2P WS SOA EM CBP RMF P2P in order to use them, they should be reflected in the modeling layer(s) above

17. 17 © 2005-2006 The ATHENA Consortium. References

18. 18 © 2005-2006 The ATHENA Consortium. 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.

19. 19 © 2005-2006 The ATHENA Consortium. 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 rg@uninova.pt. 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.rg@uninova.pt