This document discusses using WSO2 products to enable interoperability between government organizations. It describes how paper-based exchange of documents between public agencies can be replaced by digital exchange. WSO2 Enterprise Service Bus and Governance Registry allow organizations to securely integrate and share data using standard integration patterns. This improves processes for citizens and businesses by automating document retrieval and validation between organizations digitally.

1. Seamless Integration
of Data in
eGovernment
Interoperability with WSO2

2. About WSO2
• Providing the only complete open source componentized cloud platform
– Dedicated to removing all the stumbling blocks to enterprise agility
– Enabling you to focus on business logic and business value
• Recognized by leading analyst firms as visionaries and leaders
– Gartner cites WSO2 as visionaries in all 3 categories of application infrastructure
– Forrester places WSO2 in top 2 for API Management
• Global corporation with offices in USA, UK & Sri Lanka
– 200+ employees and growing
• Business model of selling comprehensive support & maintenance for our products

3. Our Customers

4. Agenda
▪ About us
▪ Business problem statement
▪ Powered by WSO2 solution

5. About me
Oscar Azañón Esteire
▪ CEO at Vitruvio Systems, S.L.
▪ 15+ years of SW Architecture in different verticals: banking, Telco, eGovernment, etc.
▪ Coauthor of W3C’s TR Improving Access to Government through Better Use of the Web
http://www.w3.org/TR/egov-improving/
▪ Broad experience in SOA transformation programs.

6. About us
▪ Vitruvio Systems is a Software Architecture company,
based in Spain (EU).
▪ Helped several organizations to embrace Service Oriented Architectures for
eGovernment, implementing leading ESB stacks.
▪ Develop a SOA eGovernment platform.
▪ Independent SI, so we can asess the great value proposition in WS02 products.

7. Case Studies
From Distributed systems to SOA.
Help several public organizations to migrate from a Distributed
Systems to SOA landscape.
▪ Radically improved capabilities, time-to-market, etc.
▪ Huge business case / value in SOA.
▪ Leading core eGov indicators and rankings nationwide..

8. Case Studies
Interoperability.
Help several public organizations to perform electronic
exchange of documents, as opposed to paper-based
exchange.
▪ This talk’s scope.

9. Case Studies
Public Procurement – Auction!
Public organizations buying goods where sellers bid to offer
lowest price.
▪ All in digital format.
▪ Several MM€ bought through our platforms.

10. Business Problem
statement
Why did we do this?

11. Business Problem statement
Paper-Based Exchange of information
▪ Citizens and companies to gather all documents from the
different public organizations (or even the same).
▪ Public administrations to validate documentation and perform
administrative business processes.
▪ Hundreds of thousands of paper documents for small to
medium-size organizations.
▪ Public organizations are increasingly becoming digital.

12. Business Problem statement
Interoperability in digital format – Use Case
▪ A citizen needs to perform a process with a Public Sector
Organization (PS1).
▪ A document from a Third Party is required.
▪ Citizen agrees that interoperability can be used.
▪ PSO1 to request document to PSO2 on his/her behalf.
▪ Exchange happens in digital format.
▪ Data can now be used digitally – supports and fosters digital
governments.

13. Business Problem statement
Great (business?) benefits for all parties
▪ Citizens, private organizations, NGOs
▪ Public Organizations
Applies also for departamental interoperability.

14. Business Problem statement
Some elements in EU’s approach to interoperability
▪ The IDABC Programme (Interoperable Delivery of European
eGovernment Services to public Administrations, Business and
Citizens). 2005-2009.
▪ ISA (Interoperability Solutions for European Public
Administrations), 2010-2015.
▪ European Interoperability Framework (EIF). Three dimensions
▪ Semantic
▪ Organizational
▪ Technical

15. Business Problem statement
Some elements in EU’s approach to interoperability
EU countries creating national interoperability frameworks to
perform interoperability by digital means.
▪ Cross-country interoperability networks
▪ National-wide networks (Spain’s SARA)
▪ Public organizations plug-in into the networks and offer & use
services.

16. Business Problem statement
Semantic Dimension
Ability of two systems to understand each other when defined by
different organizations.
▪ Different sources, regulatory, mental models.
▪ Share data with unambiguous meaning. Avoid diverging
interpretations of data.
▪ Doesn’t handle representation, but makes sure meaning travels
with information.
▪ Usually involves handling metadata.
▪ Very (very) hard problem at an internet size – W3C semantic web.
▪ ISA joinup (osor.eu + semic.eu)

17. Business Problem statement
Organizational Dimension
Ability of Organizations and process to interoperate
within their actuation scope.
▪ Legal dimension. What are the legal consequences of
the data exchange?
▪ Entitlement.
▪ Agreements among PO.

18. Business Problem statement
Technical Dimension
▪ A set of agreed upon norms and standards.
▪ Shared Schemas
▪ Web service invocation.
▪ Security: A&A. Non repudiation, integrity, etc. Credentials
management.
▪ QoS
▪ Custody of records and audit
▪ Etc.

19. Powered by WSO2
A sample case – plugging one Public Organization into SARA

21. eGovernment solution

22. Powered by WSO2
WSO2 portfolio
WSO2 provides an excellent product portfolio to address
these situations.
The basic pieces here being:
▪ WSO2 ESB
▪ WSO2 Governance Registry

23. Powered by WSO2
ALL is SOA patterns
All integration scenarios handled by SOA patterns and
infrastructure.
▪ WSO2 ESB runs integration sequences.
▪ WSO2 Governance Registry to perform resource
management (i.e. WSDL).

24. Powered by WSO2
Basic integration sequence
▪ Authenticate client
▪ Sign request
▪ invoke
▪ Authenticate & validate response
▪ Log & Custody
▪ Generate reply
▪ Error handling

25. Integration Sequence
Exchange sequence is parameterized
in the ESB using Registry Elements

26. Integration Sequence
Store all exchanged data with 0 lines
of coding.

27. Greater Visibility
See what happens in your network

28. Powered by WSO2
Conclusions
▪ Pattern based integration.
▪ Toolset to facilitate integration using parameterization.
▪ Greater capabilities / lower development / faster time-to-
market as opposed to development.

29. Engage with WSO2
• Helping you get the most out of your deployments
• From project evaluation and inception to development and going into production,
WSO2 is your partner in ensuring 100% project success