Copyright OASIS, 2004 Team Leader Chair OASIS CAM TC Presentation November 16 th XML 2004 Washington DC ebXML Registry Interoperability Demonstration

Copyright OASIS, 2004 Scenario n Showcase use of ebXML Registry to manage a large community of participants in an e-Service and e-Business system n The service provider deploys the Registry as a central resource to allow partners to quickly join the community and integrate their own applications into the e-Service network n Partners can select the business process they want to use, pick the version(s) of transactions they can support, create their CPA configuration(s), test compliance, certify their ebMS systems and begin interacting

Copyright OASIS, 2004 Scenario Interaction Roles Industry 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 Applicant Company Applicant Institution Proxy Submission Service Provider Messages e-Service authority system Messages

Copyright OASIS, 2004 Sample Target Communities n Typical applications include regulatory submissions to e-Government n e-Healthcare network providers n Marketplace service providers such as DOD EMall n For this demonstration - focus is on showing an e-Service based application

Copyright OASIS, 2004 ebXML in a nutshell n Globally developed standard (ISO15000) for: l Exchanging business messages l Conducting trading relationships l Defining and registering business processes l Communicating data in common terms l Assembling business transactions n Using Internet as delivery vehicle

Copyright OASIS, 2004 ebXML in the News "As ebXML becomes standardized, it will become the de facto way everyone does business." --Tony Scott, CTO, General Motors Interview in Information Week – March,

Copyright OASIS, 2004 Industry Groups Backing The Open Healthcare Group

Copyright OASIS, 2004 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, 2004 OASIS standards utilized n ebXML Registry n ebMS n CPA n BPSS n CAM l l version 2.5 l l version 2.0 l l version 1.0

Copyright OASIS, 2004 Team Member Contributors :- n Cyclone Commerce n Adobe n ebXMLsoft Registry n NIST n OASIS Registry, BPSS, CPA, ebMS and CAM TC members

Copyright OASIS, 2004 Agenda n Who, What, Why and How? l Functional overview + Summary of components n Demonstration – Part1 l Scenario walk-through l Message exchanges + Data Handler (application integration) n Component Drill-down – Part2 l CPA setup + CPA validation l Transaction validation + Error handling n Summary

Copyright OASIS, 2004 Functional Overview Scenario and Deployment Constraints

Copyright OASIS, 2004 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, 2004 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, 2004 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, 2004 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, 2004 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, 2004 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, 2004 Building the BPSS model Demo

Copyright OASIS, 2004 ebXML CPA / BPSS functions ebXML BP identifies Business processes including multi-party, multi- step exchanges Roles an organization must play Business transactions Messages being exchanged Context variables Business rules of edge conditions Transaction handling services Error handling ebXML CPA provides: Service name and parameters Endpoint for invocation Role of an organization in the context of a service Organization demographic information Failure scenarios Business process scenario and business transaction activity step Link to partner responsibilities Transaction Messages being exchanged Transport level QOS parameters Certificate and Encryption configuration Business status of agreement

Copyright OASIS, 2004 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, 2004 Interaction Model

Copyright OASIS, 2004 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, 2004 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, 2004 Demonstration Scenario walk-through Message exchanges Data handler (application integration emulation) CPA setup CPA validation Transaction validation Error handling

Copyright OASIS, 2004 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, 2004 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, 2004 Demonstration 1. Action – partner sends a message l Response – error – incorrect CPA details 2. Partner uses Registry to setup CPA and re- sends l Re-sends message with attachment l Round-trip works and sends back response 3. Partner makes new message test l Sends new message l Validation checks if it is OK l Sends back results 4. CPA action validation l CPA is on-file – but that type of action not valid Demo

Copyright OASIS, 2004 Part 2 – Specific Components Drilldown into components

Copyright OASIS, 2004 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, 2004 Summary - CPA handling and use n From messaging server – check that l CPA information does not match registry entry l CPA entry missing from registry l New CPA entry in registry n n CPA management considerations l l Issuing secure CPA id values + hash to grantee details l l Sequencing CPA id based on service l l Secure unique lookup of CPA via registry API l l Managing incoming message versions l l Transitioning partners from test to production l l Remote management of partner systems Review CPA Review CPA

Copyright OASIS, 2004 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, 2004 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, 2004 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, 2004 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, 2004 Linkage - Cyclone API Interchange SDK n Document submission: l Enables a backend system to programmatically invoke the messaging capabilities of Interchange. (Usage of this API in 5.2 requires assistance of Cyclone Professional Services). l Eventing is already supported in CI 5 as a feature. It’s no longer an API. n Extensibility APIs: l In-line processing. Allows user-defined Java classes to be executed as the message is processed, produced or consumed. l Pluggable transports. Allows user-defined Java classes to implement transport protocols not supported out of the box, e.g. database-based transport. l Startup Services. User-defined Java classes can be run in the same JVM with the rest of the Cyclone application. As an example, this API may be used to set up services that need to be co-located for efficiency or consistency.

Copyright OASIS, 2004 Summary Review of Demonstration

Copyright OASIS, 2004 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, 2004 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, 2004 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, Resources: