ebxmlrr: An Open Source ebXML Registry for eGov
Steve Capell: Red Wahoo
Farrukh Najmi: Sun Microsystems
steve.capell@redwahoo.co m farrukh.najmi@sun.com
Joseph.Potvin@pwgsc.gc. ca
Joseph Potvin: Govt. of Canada
Agenda
Introduction to ebXML Standards ● Overview of ebxmlrr open source ebXML Registry ● Case Study: Government of Australia ● Case Study: Government of Canada ● Conclusions
●
OASIS ebXML Registry V3
ebXML: The Standard for “Business” Web Services
●
ebXML Messaging (ebMS)
– Provides
reliable, secure, SOAP-based communication an organization, its services, business processes and technical abilities to B2B apps what databases were to enterprise apps
B2B interoperability by a common vocabulary OASIS ebXML Registry V3
●
ebXML CPPA (ebCPA)
– Describes
●
ebXML Registry (ebReg)
– Is
●
ebXML Core Component (ebCC)
– Enables
ebXML Architecture
Application Layer
PO1
Application
PO2
Application
Business Document (heterogeneous)
ebXML Registry
BPS CPA CC UBL Schema
Run time Design time Business Collaboration Layer Business Integration Layer
Business Service Interface
PO
Business Service Interface
Business Document (uniform)
Messaging Service
PO
Messaging Service
OASIS ebXML Registry V3
SOAP MESSAGE
ebXML Registry
Secur Standards Cataloging e Based d & Validation Web Database of any Accessible Content / Content Manageme Web Directory Server ebXML nt System Extensibl Registry Knowledge e Event Manageme Bus nt System Taxonomy Content based User defined Server relationships publish/subscrib e Event between User defined Notification content taxonomies, Content
OASIS ebXML Registry V3
Federation SQL & XML Queries Federate
eGov Vision
G2G G2B
Other Government
G2C
Federal Government
G2G
Business
G2B
G2C
Citizen
State Government
OASIS ebXML Registry V3
Enabling eGov Via ebXML
Document Workflow
DOCUMENT
Messaging Service ebXML Registry
DOD
VA
HHS
IRS
DOT
HUD
Unified Web Site / Knowledge base
ACME
Citizen
OASIS ebXML Registry V3
Business
What is ebxmlrr
●
A feature complete implementation of OASIS ebXML Registry V2.1 standard
– Includes
several V3 features as well
●
A sub-project of freebxml.org
code donated by Sun – Developed in open source at SourceForge – 10+ international team of dedicated developers – 100+ and growing Developer community
– Original
●
Deliverables include:
– ebXML registry server – JAXR client provider for – Registry Browser GUI
ebXML Registry
OASIS ebXML Registry V3
Ebxmlrr Architecture
SOAPSender & SOAP clients Registry Browser & JAXR clients
JAXR Provider SOAP and HTTP Interface
Ebxmlrr client ebxmlrr Server
QueryManager
FilterQueryProcessor AuthenticationMgr
SQLQueryProcessor
LifeCycleManager
XMLCatalogingService
AuthoriztionMgr
PersistenceMgr
RepositoryMgr
SQLPersistenceMgr
RDBMS
OASIS ebXML Registry V3
File System
ebxmlrr: Business Case for Sun
●
B2B is a strategic opportunity for Sun
– B2B
requires reliable hardware and software – Sun ONETM is a platform designed for B2B
B2B proliferates with open B2B standards such as ebXML ● Open source ebxmlrr ensures ebXML adoption ● Sun ONE products leverage ebxmlrr
●
OASIS ebXML Registry V3
Some Customers of ebxmlrr
Apelon: Medical guidelines registry ● COSMOS: Statistical data registry ● GM: ebCPA, ebBP registry ● HL7: Conformance Profile registry ● Republica: CC/BIE registry - eGov ● RosettaNet: Tech. Dictionary registry ● SDMX: Global debt statistics registry
●
OASIS ebXML Registry V3
ebxmlrr Development Roadmap
●
Complete remaining V3 features
– XACML,
Distributed Registries, Event Notification
●
Thin client registry browser
OASIS ebXML Registry V3
Piloting the ebxmlrr in the Australian Government
Steve Capell,
Red Wahoo
steve.capell@redwahoo.co m
Strategic Direction
●
●
●
The registry project is operated by Standards Australia and primary focus for the registry is to act as a repository of standard schema (e.g. core components, process schema, etc. by vertical industry segment). The registry will also hold CPP and CPA to support the interoperability proof of concept & the toolkit project. In future it is expected that partner profile data (e.g. CPP, WSDL, etc) will typically be held in a federated set of
OASIS ebXML Registry V3
Key ebXML Projects
●
Two key projects started:
ebXML Registry as the standards repository and partner profile store. – The ebXML-based SME toolkit as the small business enabler
– The
●
The ebXML Registry Project
– Pilot
phase is based on ebxmlrr because it is a complete implementation and because it defers the decision on a commercial provider until the pilot project is complete. – Long term vision is for the ebXML registry to become a central component of national infrastructure, federated with private sector OASIS ebXML Registry V3
Use Case Example
2 Publish trading partner profile (white & yellow pages) Publish invoice service (green pages) 3
1 Download Reference Schema 4 Download ACME profile and invoice service description Search Registry for ACME Corporation
Registry Service
5
Agree process & configure systems
ACME Corporation ERP / Middleware Systems
6 7
Invoice
Remittance Advice
SME Toolkit
SME Application
SME Application user just searches the registry (through his application interface), finds a trading partner profile, and binds to selected services with no requirement to understand or configure the B2B infrastructure.
OASIS ebXML Registry V3
ebXML Registry Project
Today July 2003 Jan 2004
Infrastructure Governance Population Pilot Operations
Handover to ongoing operations – technical & functional Process & payload schema, local system implementations, populate, test
Data model, taxonomy, quality control, customer support, reference standards, etc.
Define requirements, deploy HW, build registry, deploy clients OASIS ebXML Registry V3
Why use ebxmlrr?
Difficult to do a vendor selection without experience. Use of ebxmlrr for the pilot phase provides the experience necessary to properly qualify vendor products for the production phase. ● Low cost permits us to spend limited funds on registry governance & operations rather than
●
OASIS ebXML Registry V3
ebxmlrr: First Impressions
●
The ebxmlrr server:
to install, reliable & a complete implementation of the specification. – Performance issue loading UNSPSC classification sample data
– Easy
●
The ebxmlrr client
– RegistryBrowser
too heavy for casual users who just want to query contents. A web client will be essential post-pilot.
●
Documents & sample data
is new technology and one of the biggest barriers to adoption is awareness & understanding. Need “best practice” configuration guide. – Need more realistic sample data – including sample BPSS, CPP, CPA schema and a more complete security model (roles, permissions etc).
OASIS ebXML Registry V3
– This
Piloting the ebxmlrr in the Canadian Government
Joseph Potvin
Management Team Member, Enterprise Architecture
Information Technology Standards, Architecture, and Security Sector Department of Public Works and Government Services Canada (PWGSC)
joseph.potvin
@pwgsc.gc.ca
Context:
"Federated Architecture Program" (FAP)
●
Adoption of three constructs
–A
framework for communication, planning & design – A business model: “Government Strategic Reference Model (GSRM)” – "e-Enablers"
● ● ●
Common strategies, designs and open vendor-neutral standards Flexible, re-usable business architectural components OASIS ebXML Registry solutions Flexible, re-usable technologyV3
GSRM
Government Strategic Reference Model
Architectural specifications for public service business design ● Key analytical tool for designing the business architecture (Zachman Rows 1 & 2) ● Libraries of services and process Patterns tailored to public sector setting and vocabulary
●
OASIS ebXML Registry V3
GSRM
Government Strategic Reference Model
●
"Program": A mandate to achieve outcomes.
– Needs
●
Recognized by the program
– Target
●
groups
Parties receiving outputs and/or benefits of services administered by the program
– Jurisdictions
●
Scope and extent of the mandate
– Outcomes
●
and Impacts
Desired trends in the level of need, and consequences
– Performance – Services
measures
OASIS ebXML Registry V3
GSRM
Government Strategic Reference Model
●
"Public Program": Services with public policy goals, with outputs that meet public needs
Example 1: Legal, Collective, Democratic & Human Rights Protection ● Services for the recognition and protection of legal, collective, human, and democratic rights and freedoms – Example 2: Natural Resources ● Services for using/consuming natural resources ● Services for sustaining/renewing natural resources
–
OASIS ebXML Registry V3
GSRM
Government Strategic Reference Model
●
"Provider Program": Services with corporate (enterprise) policy goals, and outputs that meet provider needs
Example 1: Corporate Policy, Planning and Management ● Services to shape the enterprise to address public goals – Example 2: Administrative Services ● Services to support deployment and use of the enterprise's resources, facilities and assets
–
OASIS ebXML Registry V3
GSRM
Government Strategic Reference Model
●
"Service Output Type": Services with public administration goals, with outputs that meet public needs
–
Example 1: Permissions: ● Services for regulating, licensing, permitting, certifying, identifying, authorizing Example 2: Agreements: ● Services for creating collaborations, negotiating agreements, settling disputes
OASIS ebXML Registry V3
–
e-Enablers
●
10 e-Enablers
– Business
● ● ●
Interoperability
●
1. eDemocracy 2. eBusiness 3. Enterprise resource management 4. Relationship and case management
– Information
● ● ● ●
Interoperability
5. Knowledge Management 6. Business intelligence 7. Information management 8. Trusted identity
– Techical
●
●
interoperability
9. Information and infrastructure protection 10. IT infrastructure
OASIS ebXML Registry V3
e-Enablers
●
10 e-Enablers
– Business
● ● ●
Interoperability
●
1. eDemocracy 2. eBusiness 3. Enterprise resource management 4. Relationship and case management
ebXML supports an IM strategy for selfmanaging 'smart' data.
– Information
●
The open source ebXMLrr is a ● highly flexible, ● re-usable cost● effective – Techical interoperability infrastructure ● 9. Information and infrastructure protection solution.
5. Knowledge Management 6. Business intelligence 7. Information management << ebXML 8. Trusted identity
●
Interoperability
10. IT infrastructure << ebXMLrr
OASIS ebXML Registry V3
e-Enablers
●
Information Management Strategy
self-managing (i.e. "smart") data – Adopt XML for all government data and documentation – Use ebXML in the architectural framework for government business systems design – Engage open vendor-neutral standards – Implement a distributed ebXML registry/repository network across departments & agencies
OASIS ebXML Registry V3
– Create
Pilot Projects with ebXML
●
Pilot "Cluster Projects" are multidepartment/agency collaborations.
– Generic
Project Goal: “To explore and validate a set of standards-based, reusable business transformation processes and methodologies, in order to implement a trusted digital relationship that supports electronic service delivery of a horizontal, cross-departmental, multi-jurisdictional activity.”
OASIS ebXML Registry V3
Pilot Projects with ebXML
●
Work needed to specify GSRM for ebXML
●
●
● ●
●
Develop GSRM data elements to be used in inter-system exchange information for individuals or organizations. Partition "common service" elements from "business process specific" elements Provide the base specification (data dictionary) Identify data elements used in existing departmental systems that need to inter-operate, and map these to the base data specification (where semantic equivalents exist). Enter and map stakeholder data to the common data dictionary
OASIS ebXML Registry V3
First Pilot Cluster Project: Phase 1
(Completed 2002)
– The
●
ebXML framework...
Offered a strategic means of achieving business and information inter-operability Enabled interoperability between the system's E-form and Business Process integration (BPi) components Reduced the complexity of data transformations
Supported downstream dissemination of information to authorized partners
●
●
●
●
Supported re-use of the data in other processes
OASIS ebXML Registry V3
First Pilot Cluster Project: Phase 2
(Planned 2003)
●
As a common service provider in the Government of Canada, PWGSC is assisting Cluster Projects in three ways:
– 1.
●
Methods and processes advice and assistance
Architecture and open standards identification and conformance management System lifecycle management Quality management strategy and plan Business models management
● ●
●
OASIS ebXML Registry V3
First Pilot Cluster Project: Phase 2
(Planned 2003)
– 2.
Provision of an architecture and development management extranet suitable to a Cluster Project
● ●
●
●
Revision management Issue management Document management Collaborative authoring security & access management
– 3.
Provision of a hosted ebXML registry/repository
●
● ● ●
Host and maintain the open source ebXMLrr system Develop in-house technical expertise Write user documentation OASIS ebXML Registry Provide technical assistance V3
First Pilot Cluster Project: Phase 2
(Planned 2003)
●
Current "little learning pilot" start-up with ebXMLrr
– ebXMLrr
● ●
● ● ●
Server: (can be considered “free hardware”)
CPU: Pentium II - 266mhz OS: Red Hat 7.3 Database: postgreSQL Java Servlet Engine: Tomcat Data: Experimenting so far only with ebXMLrr-supplied demo data that comes with the server package.
– ebXMLrr
● ●
Client:
OASIS ebXML Registry V3
CPU: Pentium III - 700mhz OS: Windows 2000 Professional
Contribute to the ebXMLrr Community
●
OASIS ebXML Registry V3
Contribute to the ebXMLrr Community
●
OASIS ebXML Registry V3
Conclusions
ebXML Registry Standard is a key enabler for eGovernment ● Leading edge eGov projects are already using ebxmlrr to address real needs
●
– Feature
complete, royalty-free implementation
●
Open source and eGov are a natural fit
– Participation
OASIS ebXML Registry V3
of governments in OS is
More Information
ebxml.org: http://www.ebxml.org ● OASIS ebXML Registry Registry
●
–
●
http://www.oasis-open.org/committees/regrep/
freebxml.org: http://freebxml.org ● ebxmlrr: http://ebxmlrr.sourceforge.net ● JAXR API:
– http://www.jcp.org/jsr/detail/93.jsp
OASIS ebXML Registry V3