WP8: PEPPOL infrastructure WP8 - Solution architecture, design and validation

WP - Participants Denmark – NITA – (WPC & Technical Director) ‏ Norway – DIFI Austria – PEPPOL.AT Finland – VM All other beneficiaries

WP8 goals Solutions architecture – design and validation – will focus on design and validation of the common specifications and building blocks which together will define the technical interoperability layer required to provide an operational e-business infrastructure.

WP8 vision Pan European exchange of business documents between any private company and any EU governmental institution should be as easy as sending s.

Architectural goals Secure and reliable Realizable with internet technologies Leverage investments in existing infrastructures Federated and scalable Lowering barriers

WP - Outcomes An architecture – A federated, secure and reliable infrastructure for electronic document transport. Specifications – Based on internationally recognized open standards – For secure and reliable transport of electronic documents. Software – Dual license (EUPL and MPL 1.1 where applicable) ‏ – Lowering barriers for implementers – Provides reference implementations – Demonstrates “that it is easy”

Candidates ebXML RASP (DK)‏ OSCI (DE)‏ PRESTO (FR)‏ AMQP Etc. Requirements Inclusive Secure Reliable Scalable X509 Open standards Etc. ? WP8 process and deliverables

Status - Workplan and progress Requirements gathered and consolidated High level architecture defined POC Demonstrator Client – December 21 th – available for download Architecture conference – January 29th-30 th 2009

PEPPOL infrastructure overview

V V V V V V V V Country A Country B Country C Network G G G G G G Gateway Transport layer G G C C C C Client C C G G C C C C R R Registries C C C C C C R R R R G G G G R R G G R R G G R R G G C C C C V V Certificate validation V V R R Big picture

Example use of PEPPOL infrastructure SAP-ERPXI National eProcurment platform (AT)‏ A Web Adaptors AMQP? WS* Registry of registries Value Added Services ? Value Added Network / Service Privider (NO)‏ B Customers Company A Which registry? Company A What, Where, How? Middleware product Business software

Expected benefits Easy to connect to the PEPPOL infrastructure for – Service providers (e.g. banks) ‏ – Value Added Networks – Public sector institutions – Large companies – SME's

POC Demonstrator client Purpose – To demonstrate the concepts of the PEPPOL transport infrastructure Focus: – Testing registry infrastructure – Providing an application framework Expected to be ready for download Monday December 21 th

Requirements and position paper

Architecture conference January 29 th and 30 th 2009 Target group Software vendors ERP-companies The big 5 (MS, IBM, SAP, Oracle, SUN)‏ Contractors to the PEPPOL consortium Service providers Architects from other WP's STORK, Expert Group on E-invoicing etc.

Thursday January 29th 2009 Welcome and program Key note PEPPOL introduction – CIP, Goals, vision, CEN BII Architecture overview – High level Business opportunities – ERP, Middleware, Service providers Governance set up Connecting to PEPPOL

Friday January 30th 2009 Welcome Architecture overview – Recap for techies Registry Architecture Certificate validation Standards profiles – Transport standards Open Source software libraries – Interoperability testing