1 / 31

SOA Conference - May 23 rd 2006 Cory Casanave, Data Access Technologies

SOA Conference - May 23 rd 2006 Cory Casanave, Data Access Technologies. SOA CoP Demo. SOA Demo.

finn-ayala
Download Presentation

SOA Conference - May 23 rd 2006 Cory Casanave, Data Access Technologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SOA Conference - May 23rd 2006 Cory Casanave, Data Access Technologies SOA CoP Demo

  2. SOA Demo The SOA Community of Practice is sponsoring a demonstration of the business value and technical feasibility of SOA. This demonstration will encompass the full life-cycle of a multi-party SOA solution using multiple participants and multiple technologies collaborating via SOA standards in an architected community. Goals; To provide a concrete example of how the SOA approach provides business value to a community To provide confidence that the approach and technologies are real – secure, reliable, performing and practical. To validate that independently developed applications can interoperate using SOA standards

  3. Approach Defines communities that will interact over a set of services and enact common scenarios Define an architecture for these communities with a set of technical specifications to support their interaction Participants implement these services, in accordance with the community architecture, and then participate in the community – participants will get substantial visibility to government and commercial markets

  4. Status Emergency response is an existing demo, specification for other participants needs to be developed Broker demo has an initial specification, participants are refining it. It includes both a business architecture (MDA CIM) and generated WS-* & BPEL technology specifications After specs are nailed down, we will implement prototype service components It is expected that multiple participants will use their own products and approaches – use demo scenario as a common basis to show your stuff! This is an invitation to participate!

  5. Supply Chain Community Simple, classic supply chain – should be easy to understand and to implement Buyer/Broker/Manufacturer with a community registry

  6. Broker Community Scenarios Registration of a new actor in the community A simple registration service at a well known community portal Manufacturer listing products with broker Manufacturer discovers a broker and negotiates a listing deal and asserts a product list, cost and capacity. Buyer requesting quote from broker Buyer requests a quote from a broker based on product, cost, schedule and quantity. Purchase (Buyer to broker to chosen manufacturer) Buyer places an order with a broker that is then distributed to manufacturers based on quantity, price and delivery schedule. For simplicity, an order will be for one product. Registration and use of a taxonomy of products in the community registry So that all buyers, sellers and brokers can talk about the same merchandise, a standard taxonomy is used.

  7. Example Community MakeItFast:Manufacturer Jane:Buyer SuperBuy:Broker Joe:Buyer CheapStuff:Manufacturer Jim:Buyer GeneralStore:Broker Frank:Buyer Big:Manufacturer Sue:Buyer Virtual:Manufacturer OurClub:CommunityRegistry

  8. Example Scenario GeneralStore:Broker Register Customer Customer Agreement Quote Request Quote Sue:Buyer Register Actor Request Accepted Register Actor Request Accepted Request Brokers OurClub:CommunityRegistry Broker List

  9. Architecture of the Broker Community

  10. Services Produced and Consumed

  11. Example Service Interactions

  12. Example Web Service Spec BPEL WSDLSchema <?xml version="1.0" encoding="US-ASCII"?> <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:schema="http://osera.gov/xslt/functions/schema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:bpel="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http:/gov.osera.bpel" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:mof="http://osera.org/bpel/mof" xmlns:DataElements="http://osera.org/bpel/DataElements" xmlns:Messages="http://osera.org/bpel/Messages" xsi:schemaLocation="http://schemas.xmlsoap.org/wsdl/ http://schemas.xmlsoap.org/wsdl/ http://schemas.xmlsoap.org/ws/2003/05/partner-link/ http://schemas.xmlsoap.org/ws/2003/05/partner-link/" targetNamespace="http:/gov.osera.bpel"><wsdl:documentation> <uuid>platform:/resource/SoaModel/model/SoaEngine.edoc_1_0_b#280c42_10a7a3b420d_-5f66</uuid> </wsdl:documentation> <plt:partnerLinkType xmlns="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" name="MfgRelationship"> <plt:role name="Manufacturer"> <plt:portType name="tns:MfgRelationship.MfgRelationshipCallback"/> </plt:role> <plt:role name="Broker"> <plt:portType name="tns:MfgRelationship.MfgRelationship"/> </plt:role> </plt:partnerLinkType> <?xml version="1.0" encoding="US-ASCII"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs2001i="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:mof="http://osera.org/bpel/mof" xmlns:DataElements="http://osera.org/bpel/DataElements" xmlns:Messages="http://osera.org/bpel/Messages" targetNamespace="http://osera.org/bpel/DataElements" elementFormDefault="qualified"><xsd:annotation> <xsd:appinfo> <uuid>platform:/resource/SoaModel/model/SoaDemo.edoc_1_0_b#100c776_10a6acc3ea7_-7fad</uuid> </xsd:appinfo> </xsd:annotation> <xsd:element type="DataElements:ActorURIType" name="ActorURI"> <xsd:annotation> <xsd:appinfo> <uuid>platform:/resource/SoaModel/model/SoaDemo.edoc_1_0_b#100c776_10a6acc3ea7_-7e2f</uuid> </xsd:appinfo> </xsd:annotation> </xsd:element>

  13. Joseph Chiusano, Booz Allen Hamilton Utilizing theData Reference Model

  14. DRM 2.0: Data Sharing Customer, Product, Shipment, etc. Business transaction description Electronic definitions of documents Brokers, Manufacturers Brokers, Buyers Role Data Asset query interface

  15. DRM 2.0: Data Description Data Schema Role Data Asset data models Documents exchanged between roles

  16. DRM 2.0: Data Context Role Data Asset Product taxonomy, Community taxonomy, Interaction protocol taxonomy Taxonomy hierarchies Products, Communities, Interaction protocols

  17. Farrukh Najmi, Sun Microsystems SOA and Registries

  18. Role of the Registry in SOA • Enables secure, federated information management for all types of electronic content annotated with rich metadata • XML, Schema, WSDL, BPEL, Policy... • System of record for SOA deployments • Publish, management, governance, discovery and reuse of SOA Artifacts • Provides for a community “meeting place”, as in the demo scenario “Community Registry” • Allows buyers, brokers and manufactures to find and identify each other • Provides for a registry of commodity products in this community • Registry/repository being used for the demo is the "freebXML Registry" a royalty-free open source implementation of the ebXML Registry standard (ISO 15000, part 3-4) • More info: <http://ebxmlrr.sourceforge.net/wiki/Overview>

  19. Key Features of ebXML Registry Registration, Discovery, Queries ebXMLRegistry Taxonomies, Classifications, Associations Federated Queries, Inter-registry links SOA Registry Repository Federated Information Management Standard Metadata Cataloging, Validation, Version Control,Lifecycle Support,Extensible Info Model SOA Governance Secure Architecture Digital Signatures, Audit Trail, Access Control Events Content-Based Event Notification

  20. Uses of ebXML Registry • SOA Repository (Sun Microsystems) • Business Vocabulary Management (BVM) (United Nations / CEFACT) • Business process catalog (United Nations / CEFACT) • Electronic forms (Adobe) • Domain-specific use cases: • Electronic medical records (eclipse foundation open healthcare framework / HIMSS IHE / IBM) • Geological information systems (Open GIS) • Managing debt statistics for the IMF and World Bank (sdmx.org)

  21. Eric Reed, Oracle BPEL & SOA

  22. BPEL and Composite Applications Business Process Need for new or redesigned process Middleware Business people easily combine services into a new application Orchestration Applications are built as a modular set of re-usable services Applications Services Leverage existing infrastructure Infrastructure Existing Applications Registry DB

  23. BPEL Process ManagerArchitecture Enterprise-strength infrastructure for designing, Deploying, and managing BPEL business processes • Comprehensive and native BPEL implementation • Easy-to-use modeling tool • Scalable and reliable engine • Flexible binding framework • Rich management and monitoring • Support for Oracle AS, WebLogic and WebSphere • Get up and running in less than 15 minutes! Eclipse, JDeveloper BPEL Designer BPEL DEHYDRATE BPEL Process Manager Built-in Integration Services WSDL Binding Web Service ORACLE DB User Tasks JMS XQuery XSLT BPELJ JCA Core BPEL Engine Email BPEL Console MANAGE J2EE Application Server (WebLogic, Oracle AS, JBoss, WebSphere)

  24. Manage ServicesWeb Services Management Service Auditing Service Level Monitoring Security Management Event Management Policy Management Oracle Web Services Manager Enterprise Service Bus WSIF & JBI In Memory REST JCA COM+ SOAP

  25. Rex Brooks, Starbourne Communications Design Emergency First Response Scenario

  26. Emergency First Response Demo Based on Actual Train Derailment, Chlorine Tank-car Rupture Incident from Jan. 2005. Connects Emerging Sensor Network to Nation wide Emergency Alerting Framework using Common Alerting Protocol (CAP) and Emergency Data Exchange Language (EDXL). Shows Several Alerting Services Connected in Nationwide Network—Sirens, Radios, Reverse-911, Geocoded Telephone Warning Application Systems, etc. Uses Web Services Registries to Allow Services to be Connected & Aggregated.

  27. Registry Augments Emergency Alerting

  28. Registry Augments Health Informatics Support Services

  29. Portal Aggregates Geospatial Location Services

  30. Current Commercial Participants Cory Casanave, Data Access Technologies Demonstration of Business Architecture through Technical Architecture using Model Driven Architecture Farrukh Najmi, Sun Microsystems Registry implementation for Community    Joseph Chiusano, Booz Allen Hamilton DRM Mapping and integrations    Chuck Mosher, Metamatrix Implementation of services connected to back-end Data   Rex Brooks, Starbourne Communications Design Emergency Response Scenario    Eric Reed, Oracle BPEL Process design and execution

  31. More Information SOA Community Wiki Demo: http://tinyurl.com/qcvkd Contact: cory-c (at) enterprisecomponent.com

More Related