ebxmlrr: An Open Source eb. XML Registry for e. Gov Steve Capell: Red Wahoo Farrukh Najmi: Sun Microsystems Joseph Potvin: Govt. of Canada steve. capell@redwahoo. co m farrukh. najmi@sun. com Joseph. Potvin@pwgsc. gc. ca
Agenda ● ● ● Introduction to eb. XML Standards Overview of ebxmlrr open source eb. XML Registry Case Study: Government of Australia Case Study: Government of Canada Conclusions OASIS eb. XML Registry V 3
eb. XML: The Standard for “Business” Web Services ● eb. XML Messaging (eb. MS) – ● eb. XML CPPA (eb. CPA) – ● Describes an organization, its services, business processes and technical abilities eb. XML Registry (eb. Reg) – ● Provides reliable, secure, SOAP-based communication Is to B 2 B apps what databases were to enterprise apps eb. XML Core Component (eb. CC) – Enables B 2 B interoperability by a common vocabulary OASIS eb. XML Registry V 3
eb. XML Architecture OASIS eb. XML Registry V 3
eb. XML Registry Federation SQL & XML Queries Federate Secur Standards Cataloging e Based d & Validation Web Database of any Accessible Content / Content Manageme Web Directory Server eb. XML nt System Extensibl Registry Knowledge e Event Manageme Bus nt System Taxonom Content based User defined y Server relationships publish/subscrib e Event between User defined Notification content taxonomies, Content OASIS eb. XML Registry V 3
e. Gov Vision G 2 B G 2 G Other Government Federal Government G 2 C G 2 G G 2 C Citizen State Government OASIS eb. XML Registry V 3 Business G 2 B
Enabling e. Gov Via eb. XML Document Workflow Messaging Service DOCUMENT DOD VA HHS IRS DOT HUD eb. XML Registry Unified Web Site / Knowledge base ACME Citizen Business OASIS eb. XML Registry V 3
What is ebxmlrr ● A feature complete implementation of OASIS eb. XML Registry V 2. 1 standard – ● A sub-project of freebxml. org – – ● Includes several V 3 features as well Original code donated by Sun Developed in open source at Source. Forge 10+ international team of dedicated developers 100+ and growing Developer community Deliverables include: – – – eb. XML registry server JAXR client provider for eb. XML Registry Browser GUI OASIS eb. XML Registry V 3
Registry Browser & JAXR clients SOAPSender & SOAP clients JAXR Provider Life. Cycle. Manager Query. Manager Filter. Query. Processor Authentication. Mgr SQLQuery. Processor Authoriztion. Mgr XMLCataloging. Service Persistence. Mgr Repository. Mgr SQLPersistence. Mgr RDBMS OASIS eb. XML Registry V 3 File System ebxmlrr Server SOAP and HTTP Interface Ebxmlrr client Ebxmlrr Architecture
ebxmlrr: Business Case for Sun ● B 2 B is a strategic opportunity for Sun – – ● ● ● B 2 B requires reliable hardware and software Sun ONETM is a platform designed for B 2 B proliferates with open B 2 B standards such as eb. XML Open source ebxmlrr ensures eb. XML adoption Sun ONE products leverage ebxmlrr OASIS eb. XML Registry V 3
Some Customers of ebxmlrr ● ● ● ● Apelon: Medical guidelines registry COSMOS: Statistical data registry GM: eb. CPA, eb. BP registry HL 7: Conformance Profile registry Republica: CC/BIE registry - e. Gov Rosetta. Net: Tech. Dictionary registry SDMX: Global debt statistics registry OASIS eb. XML Registry V 3
ebxmlrr Development Roadmap ● Complete remaining V 3 features – ● XACML, Distributed Registries, Event Notification Thin client registry browser OASIS eb. XML Registry V 3
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 eb. XML Registry V 3
Key eb. XML Projects ● Two key projects started: – – ● The eb. XML Registry as the standards repository and partner profile store. The eb. XML-based SME toolkit as the small business enabler The eb. XML 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 eb. XML registry to become a central component of national infrastructure, federated with private sector OASIS eb. XML Registry V 3
Use Case Example Registry Service 2 Publish trading partner profile (white & yellow pages) Publish invoice service (green pages) 3 1 4 Download Reference Schema 5 Download ACME profile and invoice service description Search Registry for ACME Corporation Agree process & configure systems ACME Corporation ERP / Middleware Systems 6 7 Invoice SME Toolkit SME Application Remittance Advice 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 B 2 B infrastructure. OASIS eb. XML Registry V 3
eb. XML 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 eb. XML Registry V 3
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 eb. XML Registry V 3
ebxmlrr: First Impressions ● The ebxmlrr server: – – ● The ebxmlrr client – ● Easy to install, reliable & a complete implementation of the specification. Performance issue loading UNSPSC classification sample data Registry. Browser 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). OASIS eb. XML Registry V 3
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 eb. XML Registry solutions Flexible, re-usable technology. V 3
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 eb. XML Registry V 3
GSRM Government Strategic Reference Model ● "Program": A mandate to achieve outcomes. – Needs ● – Target groups ● – – Scope and extent of the mandate Outcomes and Impacts ● – Parties receiving outputs and/or benefits of services administered by the program Jurisdictions ● – Recognized by the program Desired trends in the level of need, and consequences Performance measures Services OASIS eb. XML Registry V 3
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 eb. XML Registry V 3
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 eb. XML Registry V 3
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 eb. XML Registry V 3
e-Enablers ● 10 e-Enablers – Business Interoperability ● ● – Information Interoperability ● ● – 1. e. Democracy 2. e. Business 3. Enterprise resource management 4. Relationship and case management 5. Knowledge Management 6. Business intelligence 7. Information management 8. Trusted identity Techical interoperability ● ● 9. Information and infrastructure protection 10. IT infrastructure OASIS eb. XML Registry V 3
e-Enablers ● 10 e-Enablers – Business Interoperability ● ● – eb. XML supports an IM strategy for selfmanaging 'smart' data. 1. e. Democracy 2. e. Business 3. Enterprise resource management 4. Relationship and case management Information Interoperability ● The open source 5. Knowledge Management eb. XMLrr is a 6. Business intelligence highly flexible, re 7. Information management << eb. XML -usable cost 8. Trusted identity ● 10. IT infrastructure << eb. XMLrr ● ● ● effective – Techical interoperability infrastructure ● 9. Information and infrastructure protection solution. OASIS eb. XML Registry V 3
e-Enablers ● Information Management Strategy – – – Create self-managing (i. e. "smart") data Adopt XML for all government data and documentation Use eb. XML in the architectural framework for government business systems design Engage open vendor-neutral standards Implement a distributed eb. XML registry/repository network across departments & agencies OASIS eb. XML Registry V 3
Pilot Projects with eb. XML ● 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 eb. XML Registry V 3
Pilot Projects with eb. XML ● Work needed to specify GSRM for eb. XML ● ● ● 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 eb. XML Registry V 3
First Pilot Cluster Project: Phase 1 (Completed 2002) – The eb. XML 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 eb. XML Registry V 3
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 eb. XML Registry V 3
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 eb. XML registry/repository ● ● Host and maintain the open source eb. XMLrr system Develop in-house technical expertise Write user documentation Provide technical assistance V 3 OASIS eb. XML Registry
First Pilot Cluster Project: Phase 2 (Planned 2003) ● Current "little learning pilot" start-up with eb. XMLrr – eb. XMLrr Server: (can be considered “free hardware”) ● ● ● – CPU: Pentium II - 266 mhz OS: Red Hat 7. 3 Database: postgre. SQL Java Servlet Engine: Tomcat Data: Experimenting so far only with eb. XMLrr-supplied demo data that comes with the server package. eb. XMLrr Client: ● ● CPU: Pentium III - 700 mhz OS: Windows 2000 Professional OASIS eb. XML Registry V 3
Contribute to the eb. XMLrr Community ● OASIS eb. XML Registry V 3
Contribute to the eb. XMLrr Community ● OASIS eb. XML Registry V 3
Conclusions ● ● eb. XML Registry Standard is a key enabler for e. Government Leading edge e. Gov projects are already using ebxmlrr to address real needs – ● Feature complete, royalty-free implementation Open source and e. Gov are a natural fit – Participation ofeb. XML Registry V 3 governments in OS is OASIS
More Information ● ● ebxml. org: http: //www. ebxml. org OASIS eb. XML 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 eb. XML Registry V 3
Скачать презентацию ebxmlrr An Open Source eb XML Registry for
64d3dc8617adc3b043b83a4adf34626a.ppt