Copyright OASIS, 2005 / 2006 Presenter Chair OASIS CAM TC Presentation January 14 th 2006 Washington DC Introducing CAM V1.5 Technology Overview

Copyright OASIS, 2005 Context Driven Content Processing n Structure Validation n Dynamic Versioning n Content Semantics n Business Rules n Rule Agent Integration n SQL Database Persistence n Transformation using xslt post-processing n Uses simple XML, XPath mechanisms n Coming soon… XSD integration

Copyright OASIS, 2005 Agenda n Introduction to CAM l Solution Summary; CAM status today - goals for 2005 n Use case analysis - what a typical CAM deployment looks like: l Grants application example l Architecture Overview n Anatomy of CAM templates n What’s Next? l Context and context driven assembly / validation l BIE, ACC, CCs and CAM structure components l Referencing Registry dictionaries - business nouns n Summary

Copyright OASIS, 2005 / 2006 Introduction to CAM Solution Summary Status today Goals for 2006

Copyright OASIS, 2005 Component Architecture mavenmaven

Copyright OASIS, 2005 Technology Solution Summary n XML-aware services: l Structure validation l Context driven versioning and includes l XPath l DOM n Rule-based services: l 30+ built-in functions l Integration with DROOLS l Call-out to Java methods n Data persistence / transformation services: l SQL l xslt

Copyright OASIS, 2005 Business Functionality n Agile Interoperability that scales without incurring exponential complexity and on- boarding costs (the limiter of traditional EDI) n Creating reliable domain solution templates for Communities of Interest (CoI) n Linking business process, partner collaborations and transaction exchanges into legally verifiable and deterministic solutions n Opening up business integration rules so that partners can confirm their usage n Handling local context drivers and flexibility n Validating and processing content with open public specification and rules base

Copyright OASIS, 2005 Technology solution mix? n How does W3C XSD schema help? n What does OASIS CAM provide? n Do we need ebXML Registry? n How does this work for UBL? n What about semantic tools like OWL and DITA? n Business domain linkage – CPA, MoU and process definitions, context and BPSS?

Copyright OASIS, 2005 Do we have test case measures? n Context of “person” with respect to “address” and n Linkage between passport and visa business process areas, and n Concept of e-Folders and secure information servers for citizen facing e-government services and n OASIS CIQ work and UPU work on addresses and people metadata and semantics

Copyright OASIS, 2005 Conceptual Scenario and Interaction Roles Government Partners XML Structure Rules XML Structure Rules Transport ebMS server Transport ebMS server Oracle database Oracle database Central ebXML Registry Central ebXML Registry CPA check CPA check CAM data validator CAM data validator Partner Management Web forms Partner Management Web forms (Persistent Storage) CPA instances CPA instances CPA instances CPA instances System Administrators Manage Partner Interactions Local Applicant Company Applicant Authority Proxy Submission Service Provider Messages e-Service authority system (passport / visa) Messages

Copyright OASIS, 2005 Sample Target Communities n Typical applications include regulatory submissions to e-Government n Law enforcement and security agencies n e-Healthcare network providers (verify foreign nationals and eligibility) n Disaster management n Center for Disease Control (CDC)

Copyright OASIS, 2005 CCT S Registry Dictionary / XSD schema CAM templates + Business rules + Context + Roles XML instances XML XSD schema / CAM templates UML models + Business rules + Context + Roles CCTS components Conceptual Method Stacks n Top Down n Bottom Up

Copyright OASIS, 2005 CAM services n Transaction Assembly and Integration / Formats n Assembly of XSD fragments into whole schema n Provide payload structure and content definition n Production validation and error handling n Local pre-deployment transaction checking n Industry Conformance and Compliance testing n Business Context Rules implementation n Simple business analyst friendly syntax and predicates n Alignment of Vocabularies / Legacy Semantics

Copyright OASIS, 2005 How do you put this all together? ActionEvent Information Rule What Why HowWhen Where / Who ActionEvent Information Rule What Why HowWhen ActionEvent Information Rule What Why HowWhen

Copyright OASIS, 2005 OASIS standards to consider n ebXML Registry n ebMS n CPA n BPSS n CAM n CIQ n DITA n BCM l l version 2.5 l l version 2.0 l l version 1.0

Copyright OASIS, 2005 CAM Status and Goals for 2005 n History n Status n Goals

Copyright OASIS, 2005 / 2006 Use Case Analysis What a typical CAM deployment looks like

Copyright OASIS, 2005 Some typical use cases n Collaborative community for e- Government scenario n e-Service solutions scenario - e- Healthcare n Accounting system integration – UBL n ebXML BPSS, ebMS and CAM specification align

Copyright OASIS, 2005 / 2006 Anatomy of CAM templates A,B,Cs of the components that make up CAM

Copyright OASIS, 2005 CAM template components

Copyright OASIS, 2005 / 2006 CCTS mechanisms supported by CAM Context and context driven assembly / validation BIE, ACC, CCs and CAM structure components Referencing Registry dictionaries - business nouns

Copyright OASIS, 2005 CCTS

Copyright OASIS, 2005 / 2006 UML production rules and CAM templates Schema Assembly Object support Conditional rule support Schema modelling example

Copyright OASIS, 2005 Scenario Management n The service provider can post new releases of business processes to the registry and establish connections to the e-Service business applications using discreet CPA profiles that point to the appropriate production and test environments. n Partners then simply select the appropriate CPA ID to connect to. n Participant organization profiles, CPAs, schemas and business rule templates are all managed by the registry and are classified according to the domain structure in the e-Service community.

Copyright OASIS, 2005 Technology Constraints n Cross-platform support n Work with common SQL databases n Must be scalable and extensible n Easy integration to back-end systems n Should use open public and industry standards wherever possible n Security must be robust without being restrictive

Copyright OASIS, 2005 Processing Constraints n Use XML based messaging n Support exchange of PDF format document attachments; as large as 50Mb size and up n Handle peak daily volume of 1,000+ exchanges n Be easy to deploy for typical internet enabled partners server environment n Provide self-service facilities with versioning n Secure and legally sound approach that extends existing paper based process authentication and intent models

Copyright OASIS, 2005 Software Components n Open Source components l ‘Hermes’ freebXML ebXML messaging server l ‘OMAR’ freebXML Registry system l jCAM content assembly mechanism and validation component with versioning capability n Oracle database server n Tomcat Server n Cyclone messaging server n ebXMLSoft Registry server

Copyright OASIS, 2005 ebXML Solution Architecture Capture Process Details with Participant Roles / Context and Message Exchanging Definitions Reference – Domain Ontology and Semantic Information Reference - Domain Transactions + Business Process Models References Business Agreement Templates 11 Messaging System Drives Messaging System Partner A Partner B Exchanges 22 Enveloping + Routing Transactions + Validation Handles Queue Integration Agent Controlled by 33 Processes – state management, linking and switching Integration – application system interactions Manages44 BPSS + Workflow – Models of Interaction Service / Actions CAM XML templates – Business Exchange Formats and Rules CPA – Exchange Agreements Produces

Copyright OASIS, 2005 Example Hub Deployment Setup Application Integration handler Application Integration handler XML Structure Rules XML Structure Rules Hub ebMS server Hub ebMS server Oracle database Oracle database ebXML Registry ebXML Registry CPA check CPA check Messages Partner ebMS server Partner ebMS server Content validation Content validation CPA instances CPA instances Partner Management Web forms Partner Management Web forms Admin Services Admin Services Audit and Control Web forms Audit and Control Web forms Existing Web-based Registration Interface Existing Web-based Registration Interface Existing backend Application(s) Existing backend Application(s) Application handler (staged delivery) Application handler (staged delivery) Oracle App Server

Copyright OASIS, 2005 ebXML CPA visual editing Participant Information Messaging preferences Message exchange details (DUNS Party ID Company Contact Web site Process Role Status Description) Demo Process Linkage

Copyright OASIS, 2005 Interaction Model

Copyright OASIS, 2005 Functional Summary n Each hub consists of the following functional components: l ebXML messaging server for transaction exchange – configured by CPA definitions l ebXML registry server for management of CPA documents and transaction definitions l Verification component for exchange details – who and what is allowed – (controlled via CPA) l Validation component for exchange transactions – business content information and format received (handled via jCAM XML template scripts) l User interface components to manage exchanges and partners l Transaction handler and integration emulation

Copyright OASIS, 2005 Processing Configuration Details Functionality: n n CPA management n n CPA driven validation n n Registry interfacing n n Content validation n n Messaging handling

Copyright OASIS, 2005 / 2006 Demonstration Scenario walk-through Message exchanges Data handler (application integration emulation) CPA setup CPA validation Transaction validation Error handling

Copyright OASIS, 2005 Scenario Walkthrough n We have two servers setup, each with Hermes server, Cyclone server, and then one with the Registry servers as well. n The two servers exchange messages with one acting as the central server (hub) that references the Registry to validate the CPA details it receives. This also runs the jCAM service to check transactions. n The data integration servlets provide the backend integration and workflow control

Copyright OASIS, 2005 Message Exchanges n Basic interchange will be demonstrated where: 1. Successful message exchange round trip 2. CPA editing and management with registry 3. CPA validation error handling 4. jCAM validation error handling 5. Review of data handler and data integration handling functionality 6. Message management facilities and CPA

Copyright OASIS, 2005 CPA lookup Unpack SOAP message Unpack SOAP message Transaction Interaction Integration handler Integration handler XML Structure Rules XML Structure Rules Receive Queue Receive Queue ebXML Registry ebXML Registry Request Partner ebMS server Partner ebMS server CPA instances CPA instances Hub ebMS server Hub ebMS server Ack CPA check Error Message Data Handler Message Data Handler Error Response jCAM validator jCAM validator Staged Delivery handler Staged Delivery handler

Copyright OASIS, 2005 / 2006 Part 2 – Specific Components Drilldown into components

Copyright OASIS, 2005 CPA Editing and Management n We have created a screen storyboard for the following scenarios: l Existing partner wants to use electronic submissions l Proxy Service provider for participants l Transaction validation services l System Administration of CPA profiles View Forms View Forms

Copyright OASIS, 2005 Aspects of Registry used n Storage and retrieval in registry and repository using registry services n http-binding queries to retrieve CPA instances n Content Management Capabilities l Content classification l Organization and user management l Typing of content l Security profiles and access control l Associations (between CPA, Schema and jCAM)

Copyright OASIS, 2005 Demonstration of ebXMLsoft Registry n Functional components: l User and Organization management l Security model l Classification of content l Generic XML content upload l Content management: approval, status, commenting, history, and user activity log l Search features l Accessing content programmatically n http accessing n Servlet API l Ease of installation considerations l Content Archiving Demo of Registry Demo of Registry

Copyright OASIS, 2005 jCAM validation error handling n Overview of jCAM functionality n Example of jCAM rules for example transactions n jCAM in action l valid transaction processing l Invalid transaction processing n Integration with registry as validation service On-line Testing On-line Testing Message Reporting Message Reporting Simple Template Simple Template View Input XML Input XML View Input XML Input XML Extended Template Extended Template Output Formatting Output Formatting

Copyright OASIS, 2005 Preview - jCAM and Registry n Noun management is currently being developed l Noun format for storage in Registry l Retrieval of noun definition from registry using http-binding and LID() method on UID values from CAM template l Allows jCAM to automatically match rules from Registry noun definitions against XML content instances l For more details see OASIS CAM TC site

Copyright OASIS, 2005 / 2006 Summary Review of Presentation

Copyright OASIS, 2005 What You Just Saw n ebXML components and configuration n Installation details and operational details n CPA management and configuration n XML templates for validation via jCAM n Review of message traffic and queues n Management of automatic response messages n Storyboard of user screens for CPA management n Demonstration of on-line transaction testing service n Configuration of application integration handlers

Copyright OASIS, 2005 Lessons Learned n Infrastructure exists today off-the-shelf to create communities of partners n You can use ebXML to manage and run an e-Service environment n The Registry provides crucial management and facilitation services n Providing self-service facilities is key to rapid adoption

Copyright OASIS, 2005 Implementation Planning n Understand your business needs n Identify business process and transactions n Build community buy-in n Create prototype deployment n Verify with pathfinder partners n Refine, configure, deploy!

Copyright OASIS, 2005 / Resources: