Steve Capell: Red Wahoo Farrukh Najmi: Sun Microsystems Joseph Potvin: Govt. of Canada ebxmlrr: An Open Source ebXML Registry for eGov m ca

OASIS ebXML Registry V3 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 ● ebXML CPPA (ebCPA) – Describes an organization, its services, business processes and technical abilities ● ebXML Registry (ebReg) – Is to B2B apps what databases were to enterprise apps ● ebXML Core Component (ebCC) – Enables B2B interoperability by a common vocabulary ● ebXML Business Process (ebBP) – Enables collaborative “Business” web services

OASIS ebXML Registry V3 ebXML Architecture

OASIS ebXML Registry V3 ebXML Registry Web Server Content Manageme nt System Federate d Database / Directory Event Bus Knowledge Manageme nt System Taxonomy Server ebXML Registry Web Accessible Secur e Cataloging & Validation of any Content Federation SQL & XML Queries Content based publish/subscrib e Event Notification User defined taxonomies, Content classification User defined relationships between content Standards Based Extensibl e

OASIS ebXML Registry V3 eGov Vision Citizen State Government Other Government G2B G2G G2C G2G G2C G2B

OASIS ebXML Registry V3 Enabling eGov Via ebXML DOCUMENT DODVAHHSIRSDOTHUD ACME

OASIS ebXML Registry V3 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 – Original code donated by Sun – Developed in open source at SourceForge – 10+ international team of dedicated developers – 100+ and growing Developer community ● Deliverables include: – ebXML registry server – JAXR client provider for ebXML Registry – Registry Browser GUI

OASIS ebXML Registry V3 Ebxmlrr Architecture SOAP and HTTP Interface LifeCycleManager QueryManager FilterQueryProcessor SQLQueryProcessor XMLCatalogingService SQLPersistenceMgr PersistenceMgr RepositoryMgr AuthenticationMgr AuthoriztionMgr File System RDBMS JAXR Provider Registry Browser & JAXR clients SOAPSender & SOAP clients ebxmlrr Server Ebxmlrr client

OASIS ebXML Registry V3 ebxmlrr: Business Case for Sun ● B2B is a strategic opportunity for Sun – B2B requires reliable hardware and software – Sun ONE TM 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 ● ebxmlrr a magnet for Sun ONE/Solaris

OASIS ebXML Registry V3 Some Customers of ebxmlrr ● Apelon: Medical guidelines registry ● COSMOS: S tatistical data registry ● GM: ebCPA, ebBP registry ● HL7: Conformance Profile registry ● Republica: CC/BIE registry - eGov ● RosettaNet: Tech. Dictionary registry ● SDMX: Global debt statistics registry ● Sun: Web Services registry

OASIS ebXML Registry V3 ebxmlrr Development Roadmap ● Complete remaining V3 features – XACML, Distributed Registries, Event Notification ● Thin client registry browser

Steve Capell, Red Wahoo m Piloting the ebxmlrr in the Australian Government

OASIS ebXML Registry V3 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 commercial registries.

OASIS ebXML Registry V3 Key ebXML Projects ● Two key projects started: – The ebXML Registry as the standards repository and partner profile store. – The ebXML-based SME toolkit as the small business enabler ● 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 registries.

OASIS ebXML Registry V3 Registry Service SME Toolkit ACME Corporation ERP / Middleware Systems Publish trading partner profile (white & yellow pages) Publish invoice service (green pages) Search Registry for ACME Corporation Download ACME profile and invoice service description SME Application Agree process & configure systems Invoice Remittance Advice Download Reference Schema 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. Use Case Example

OASIS ebXML Registry V3 Infrastructure Governance Population Pilot Operations Define requirements, deploy HW, build registry, deploy clients Data model, taxonomy, quality control, customer support, reference standards, etc. Process & payload schema, local system implementations, populate, test Handover to ongoing operations – technical & functional Today July 2003 Jan 2004 ebXML Registry Project

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 infrastructure.

OASIS ebXML Registry V3 ebxmlrr: First Impressions ● The ebxmlrr server: – Easy to install, reliable & a complete implementation of the specification. – Performance issue loading UNSPSC classification sample data ● 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 – This 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).

Joseph Potvin Management Team Member, Enterprise Architecture Information Technology Standards, Architecture, and Security Sector Department of Public Works and Government Services Canada (PWGSC) Piloting the ebxmlrr in the Canadian Government

OASIS ebXML Registry V3 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 ● Flexible, re-usable technology solutions

OASIS ebXML Registry V3 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 measures – Services

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 – Information Interoperability ● 5. Knowledge Management ● 6. Business intelligence ● 7. Information management << ebXML ● 8. Trusted identity – Techical interoperability ● 9. Information and infrastructure protection ● 10. IT infrastructure << ebXMLrr ebXML supports an IM strategy for self- managing 'smart' data. The open source ebXMLrr is a highly flexible, re-usable cost- effective infrastructure solution.

OASIS ebXML Registry V3 e-Enablers ● Information Management Strategy – Create 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 Pilot Projects with ebXML ● Pilot "Cluster Projects" are multi- department/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 ● Provide technical assistance

OASIS ebXML Registry 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: ● CPU: Pentium III - 700mhz ● OS:Windows 2000 Professional

OASIS ebXML Registry V3 Contribute to the ebXMLrr Community ●

OASIS ebXML Registry V3 Contribute to the ebXMLrr Community ●

OASIS ebXML Registry V3 ● 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 of governments in OS is growing – Open Source: A much better ROI for eGov! Conclusions

OASIS ebXML Registry V3 More Information ● ebxml.org: ● OASIS ebXML Registry Registry – ● freebxml.org: ● ebxmlrr: ● JAXR API: – ht tp://