• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Austrian Government Nov 18 2003 - Morning One

Austrian Government Nov 18 2003 - Morning One






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Austrian Government Nov 18 2003 - Morning One Austrian Government Nov 18 2003 - Morning One Presentation Transcript

    • Service Oriented Architecture Wien, Osterreich 18 November 2003 Sprecher: Duane Nickull [email_address]
    • Sprecher – Duane Nickull
      • Aus Kanada – Executive Vice-President f ü r Yellow Dragon Software.
      • Abeitet - UN/CEFACT eBusiness Architecture Group (UEB Architecture)
      • Co-lead /Chief Editor - ebXML Technical Architecture v 1.0
      • ebXML Steering Committee Member
      • [email_address]
    • Tagesordnung
      • 9:15 – 11:00 Introduction – Service Oriented Architectures
      • History of Service Oriented Architectures (SOA).
      • Messaging: SOAP and ebXML MS
      • Business Service Interfaces – WSDL, CPP and CPA
      • Agents for Discovery – UDDI Directory and ebXML Registry
      • Process and Choreography – BPSS, BPEL
      • Modeling Methodology and Framework – BCF/ UMM / UML
      • Information – Core Components, BIE’s Semantics, XML schema.
      • 11:00 – 11:30 - BREAK
    • Tagesordnung
      • 11:30 – 13:00 Service Oriented Architectures in practice
      • The Canadian Government’s IJI Data Dictionary work + ebXML registry
      • eForms scenario
      • Harmonizing Data models for international integration of justice and security data.
      • - Questions and Answers
    • An Introduction to Service Oriented Architectures Understanding the technological and cultural factors driving their adoption 09:30
    • Business factors for Services Business to Customer System Integration Internet Based Delivery SOA eBusiness Processes over WWW Cultural Shift Computers Protocols / Standards Local Networks WAN’s
    • Business Interaction Models B to C Disintermediation B to B Collaboration Infomediary Malls EDI HTML XML
    • The Shift to N-Tier 1-Tier 2-Tier N-Tier Mainframe Apps Mini-Computer Apps Corporate Applications (Often departmental) Distributed Production Web Aware/Web Scale eCommerce Client/Server Internet/ Enterprise Monolithic/ Automation 1988 1990 1994 1999 2001 2003
    • Before Object Oriented Programing…
      • A program often resided on one system.
      • Old style -> Spaghetti code: no structure, no classes – procedural and linear execution.
      • GWBasic, early cobol, Pascal, Fortran
      • Object-Oriented programming is the early roots of Service Oriented Architecture.
      • Classes (encapsulation) call each other as services (accessor + mutator)
    • A simple program (object-oriented)
      • public class HelloWelt{
      • public static void main(String[] args){
      • System.out.println("Hello Welt!");
      • }
      • }
      Import HelloWelt; public class WieGehtsAllesDieWelt{ public static void main(String[] args){ HelloWelt(); System.out.println(“Wie geht es Dir?"); } } Imports another class Calls a method() of the class Returns something (optional)
    • A simple program (object-oriented)
      • public class HelloWelt{
      • public static void main(String[] args){
      • System.out.println("Hello Welt!");
      • }
      • }
      Import HelloWelt; public class WieGehtsAllesDieWelt{ public static void main(String[] args){ HelloWelt(); System.out.println(“Wie geht es Dir?"); } } This class uses the service This class offers a service
    • Service Oriented Architecture expanded
      • What if the two classes are not on the same machine? Network!
      • How can one class find another? Service Description
      • How can a class send its’ information to the other class? XML serialization.
      • Do the two classes have to be on the same network? TCP/IP + HTTP
    • Calling a service (RPC)
      • Remote Procedure Call (RPC)
      • Calling a functional piece of logic that resides elsewhere.
      Multiply() class ConvertCurrency() class ConvertCurrency(5.45, USD, CAD) Multiply (5.45, 1.63) Result comes back
    • XML used to pass values
      • <parameters>
      • <service>Multiply</service>
      • <integer value=‘5’/>
      • <integer value= ‘4’/>
      • </parameters>
      Service publisher Service User <answer> <integer value=‘20’/> </answer>
    • The ebXML SOA Architecture By UN/CEFACT and OASIS 11:05
    • ebXML
      • Started in 11/1999 in San Jose, USA
      • UN/CEFACT and OASIS joint project.
      • Goal to develop one global electronic marketplace.
      • Architecture team decided to write a large Service oriented Architecture.
      • 2,000 + participants worldwide.
      • Seven teams
      • Version 1.0 delivered May 2001, Wien (sponsored by AustriaPro)
    • ebXML Service Oriented Architecture
      • 1.  Business processes and associated information models (in XML)
      • 2.  A mechanism for registering and storing artifacts (Registry)
      • A mechanism for declaring a Trading Partners capabilities and services (CPP)
      • A way to convey semantics and agree on meanings of Business Payloads (Core Components, BIE’s)
      Architecture Concepts…
      • 5.  A mechanism for describing a bilateral Trading Partner Agreement (CPA).
      • 6.   A standardized messaging service (ebXML MS)
      • 7. A standardized methodology/process for modeling the real world business and translating it into XML. (UMM)
      Architecture Concepts…
    • ebXML FSV – implementation
    • ebXML
      • Is a framework / architecture
      • Does not mandate specific payloads
      • Is service oriented and event driven
      • Is being continually developed
      • Is a SOA specific for eBusiness but works well for other information sharing (eGovernment, security, data)
    • The W3C Web Services SOA Architecture A generic SOA.
    • Web Service – simple model
    • Web Service Architecture – expanded
    • WSAG principles
      • An interoperability architecture.
      • Not intended for individual Web Services
      • Not dependant on WSDL, SOAP, ebXML MS or any other technology.
      • Provides a global perspective on the networked service architecture.
      • Other specifications, such as SOAP 1.2 and WSDL give detailed recommendations for specific requirements
    • WS Relationships
    • The UN/CEFACT Architecture Building on top of ebXML and Web Services SOA’s.
    • Key Architecture Principles
      • Platform independence.
      • Event driven and Service Oriented Architecture.
      • Facilitation of multiple concurrent and/or different implementations.
      • Component based architecture allowing eBusiness components to be added, deleted or modified.
      • Allows proprietary protocol support, including custom extensions for industry standards. This refers to, but is not constrained by, electronic message payloads.
      • Custom workflow, information and syntax definitions are allowed in support of unique business rules and requirements, as may be defined by users.
      • Incremental phased implementation.
    • UN/CEFACT eBusiness Architecture Registry/Repository Business Collaboration Framework Business Processes Business Information Trading Partner “A” Trading Partner “B”
    • EDI Reference Model B U S I N E S S T R A N S A C T I O N S * UML Models Viewed as Information technology aspects of business transactions Business Operational View Functional Service View Business aspects of business transactions Comply with Covered by BOV related standards* Comply with Covered by FSV related standards
    • SOAP and ebXML Messaging Communication layer in SOA’s
    • SOAP
      • Simple Object Access Protocol.
      • XML over http
      • Work by W3C; moving to v 1.2
      • A simple and lightweight messaging standard designed as replacement for XML-RPC.
      • Synchronous and Asynchronous.
      • Can use other low level transport protocols
    • Ebxml Messaging Service
      • Built on top of SOAP and HTTP (can also use other low level protocols like FTP, SMTP)
      • Requires a service level agreement.
      • Advanced security features
      • Advanced reliable messaging features.
      • If message does not get through – sender is advised.
      • Once and once only receipt by receiver.
      • Non-repudiation of sender.
      • Can carry any payload, 0, 1 or * attachments.
      • Conversation ID tracks differents threads.
    • ebXML - Secure and Reliable Messaging
    • Business Service Interfaces Using WSDL, CPP and CPA to describe services 09:30
    • How do I describe services? Unsere Computer ? ? ? ? ? ? ? ?
    • Service descriptions ? ? ? ? ? ? ? ? Eco.xml CPP WSDL WSDL WSDL Eco.xml CPP + BPSS CPP + BPSS Focus: Web Services Description Language (WSDL) Collaboration Protocol Profile (CPP)
    • Web Service Description Language
      • WSDL provides a simple description of the service offered.
      • WSDL is missing items – semantics, trading partners agreement references, constraints on who can use the service, etc.
      • WSDL is a very lightweight, works well for web service descriptions.
      • Minor binding to Messaging layer (SOAP only)
    • Business Service Interface (BSI)
      • UN/CEFACT Architectural term.
      • An abstract architectural component containing all aspects of an interface to a business including technical and business terms of use.
    • ebXML – CPP and CPA
      • Trading Partner Profiles and Agreements.
      • Tells you Business Service Interfaces, bindings etc.
      • Provide a list of Business Processes or Web Services.
      • NOT designed to be a legal agreement.
      • example
    • Registry and Directory Functionality in SOA’s A look at UDDI, ebXML and ISO/IEC 11179 Registry and Directory Systems 13:00
    • Discovery - Registry/Repository ? ? ? ? ? ? ? ? Eco.xml CPP WSDL WSDL WSDL Eco.xml CPP + BPSS CPP + BPSS REGISTRY
    • What is a Registry?
      • An XML registry is an infrastructure that enables the registration and discovery of services, ontology's or other artifacts for information sharing.
      • It is a neutral third party that facilitates dynamic and loosely coupled interactions.
      • A registry is available to organizations as a shared resource, often in the form of a web-based service.
    • Relationship of Registry standards
    • UDDI Directory Data Businesses register public information about themselves White Pages Yellow Pages Green Pages Standards bodies, programmers, businesses register information about their service types Service type registrations (“tModels”)
    • UDDI and SOAP
      • The Registry is the heart of ebXML.
      • Powerful system of Registries and Distributed Repositories.
      • Loosely coupled.
      • Registries contain pointers and meta information. Meta information constrained by Registry Information Model (RIM)
      • The Registry Services exposed by the interfaces have set metadata for expressing queries and returns.
      Repository Registry Synchronization API I / O RIM ebXML Registry / Repository
    • ISO Registry Metamodel
    • Business Process and Choreography BPSS and BPEL
    • Process = State Management
    • ebXML Business Process Specification Schema
      • BPSS instances are Runtime and Design Time artifacts.
      • Captures particulars of process in an XML schema controlled instance.
      • References Business Information used in each step of process.
      • Contains conditions to guard against improper execution of a specific process.
      • Controls Business Signals
      • Lacking support from software vendors
    • Business Process Execution Language (BPEL)
      • Similar to BPSS in concept.
      • Designed for Web Services.
      • Work is advancing rapidly – strong support from major vendors.
      • Choreographs service use
      • Controls Business Signals
    • Information Core Components, BIE’s, Semantics, XML schema
    • ebXML Business information Service Description 1.. Supported Process <<References>> DTD’s Schemas? DTD’s Schemas? DTD’s Schemas? <<Constructed From>> 1.. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp Business Information Entities <<Constructed From>> <<Constructed From>> XML Representations Bridge to Legacy Data
    • Core Components:
      • A Core Component captures information about a real world (business) concept. 
      • A Core Component can be atomic or aggregate.
      • It is ‘Core’ because it occurs in many different areas of industry/business information exchange.
      • Think ISO 11179 Data Elements!
    • Core Components & BIE’s are like… Name Address email Phone # Company Company Phone # email Address Name Party Party ID Invoice PO # Line Item Cost
    • Core Components – driven by UMM
    • The UN/CEFACT Modeling Methodology An integral part of the UN/CEFACT Business Collaboration Framework (BCF)
    • The UMM Meta-model
    • UMM - expanded
    • What can UMM give us?
      • Data in payloads, transport details in message envelope and verbs in BP* artifacts.
      • Higher probability of interoperability between vocabularies.
      • Alignment of semantics.
      • Smart, re-useable processes.
      • A complete view of choreography and state.
      • A statement of intent.
    • Q & A SOA’s
    • BREAK TIME!!!
      • Back by 11:30 please.