just a collection of ws diagrams… food for thought dave hollander
TRANSCRIPT
Just a collection of WS diagrams…food for thought
Dave Hollander
WS Architecture Today
• Content
• Messaging
• Description
• Discovery
• + + + security, chorography
• W3C Web Services Architecture– a model for Web Services that takes the principles of Web
architecture into account -- interoperability, vendor-independence, and openness
HTTP SMTP IIOP FTP …
ebXML Applications
Messaging Service I nterface
Messaging Service
Authentication, authorization andrepudiation services
Header Processing
Encryption, Digital Signature
Message Packaging Module
Delivery ModuleSend/Receive
Transport Mapping and Binding
Man
agem
ent
S e c u
r i t y
Core XML Standards
Backend Integration
Service Oriented Architectures
Network Transport
Universal Business Processes
Specialized Business Processes
Business Process Instance
Universal Business Content
Specialized Business Content
Business Content Instance
Messaging
Service Description Language Repository
Directory / Registry
Business Content Format Definition Process Description Language
Trad
ing
Partn
er Ag
reemen
t
Source: microsoft.com
WeWe are working on it!
WeWe are working on it!
Reusable Standards
System Standards (enabling)– Data Representation: XML and related standards
– Events and Processes: UML and and other ModelsSyntax, grammar, security and exchange of interoperable data
Community Standards• Semantic Vocabularies• Business PracticesPrototypes/Stereotypes/Archetypes: models for semantic
concepts to be reused in broad business contexts
Community Standards• Semantic Vocabularies• Business PracticesPrototypes/Stereotypes/Archetypes: models for semantic
concepts to be reused in broad business contexts
Business Standards• Branding: Content, Look and Feel• Organization and StructureSpecific to Business Needs
Business Standards• Branding: Content, Look and Feel• Organization and StructureSpecific to Business Needs
More Nuance in Standards
Standards – not all are equal
Mar
ket A
dopt
ion
Open Standardization
JCV Consortia SDO
SGMLISO
XMLW3C
SOAP v1.1
SOAP v1.2W3C
UDDI v2UDDI.org
WSDLW3C
eb MS v2OASIS
eb Reg v2OASIS
WSDL v1.1
Sanction
Traction
Proprietary
Copyright 2002 OASIS
Stacks of stacks
Blue-yellow
Stacks of stacks
HTTP SMTP IIOP FTP …
ebXML Applications
Messaging Service I nterface
Messaging Service
Authentication, authorization andrepudiation services
Header Processing
Encryption, Digital Signature
Message Packaging Module
Delivery ModuleSend/Receive
Transport Mapping and Binding
B2B Conceptual Model
Ma
na
ge
me
nt
S e
c u
r i t y
Core XML Standards
Backend Integration
Service Oriented Architectures
Network Transport
Business Conceptual
Model(Definitions, format,
structure, and choreography)
Technical Conceptual
Model(Standards, protocols
and tools)
Universal Business Processes
Specialized Business Processes
Business Process Instance
Universal Business Content
Specialized Business Content
Business Content Instance
Messaging
Service Description Language
Repository
Directory / Registry
Business Content Format Definition Process Description Language
Tra
din
g P
artn
er A
gre
em
en
t
Another Stack
http://www.zapthink.com/reports/marketmaplg.html
Goals
• Interoperability• Integration• Vendor
Independence• Factorization• Description• Behavioral Description
– One sided description of behavior over extended activity
– Reliable messaging– Multi-phase interaction
Business
Semantics and Process
Transport
Physical
Interoperability Stack
????
UML
XML, ???
SOAP
HTTP, SMTP
Ethernet
Wireless, Phone
TCP/IP
URL/WSDL
Currency
Goals
• Interoperability• Integration• Vendor
Independence
Business
Semantics and Process
Transport
Physical
Interoperability Stack
????
UML
XML, ???
SOAP
HTTP, SMTP
Ethernet
Wireless, Phone
TCP/IP
URL/WSDL
Currency
Transport
Sec
urity
Man
agem
ent
Transactions Context Qualities of Service
Transport services
Routing Caching Referral
Network services
Description Registry Process Flow
Metadata services
Modularity Simplicity Encapsulation
Creation guidelines
XML and the Semantic Web
Transport
Txns Reliability Caching
Registry Flow
Sec
urity
Man
agem
ent
Description
Modularity Components XML
Service Layers
Application Domain Services
• Trading Partner Agreement
• Semantic Web
Design/Meta Services
• Creation Services
Infrastructure Services
• Metadata services
• Network services
• Transport services
• Management
Services
• Security
• XML
Core
MetaData
Infrastructure
ApplicationDomain
Basic
Premium
Advanced
Messaging Description DiscoveryContent
XMLInfoset
SOAP WSDL
UDDIChoreo-graphy*
XMLSchemas
SemanticWeb
Blue-yellow:
Installable Services
Remote Services
Domain Services
Application Services
Infrastructure Services
Core Services
Web Services Technology Stack
zapthink:
Development Tools and Environments
Runtime Platforms
Service-Oriented Integration
Operation Management
Billing and Metering
Orchestration and Workflow
Registry/Repository
Hosting and Delivery
Content Lifecycle• Multi-Channel Publishing• Content Creation• Content Management• Content Syndication
• Infrastructure• Security• Transformation• XML Data Storage
• Value Chain• eCommerce• eProcurment• Collaboration
• Verticals• Community Vocabularies
• Semantic Web
BIC:
Business Content Instance
Specialized Business Content
Universal Business Content
Business Process Instance
Specialized Business Processes
Universal Business Processes
Business Content Format Definition
Process Description Language
Directory / Registry
Repository
Messaging
Core XML Standards
Network Transport
Service Oriented Architectures
Backend Integration
Service Description Language
S e c u r i t y
Management
Trading Partner Agreement
Actors/objects/operations:
Service Registry
Service Description
Service Requester
Service Provider
Service
Service Description
Find
Publish
Bind
Eric2:
XML and the Semantic Web
Creation guidelines• Modularity • Simplicity
Encapsulation
Metadata services• Description • Registry• Process Flow
Network services • Routing• Caching • Referral
Transport services• Transactions • Context • Qualities of Service
Security
Management
Transport
Service Layers
Domain Services
Application Services• Trading Partner Agreement
• Semantic Web
Design/Meta Services
Creation guidelines• Development Tools and Environments • Modularity • Simplicity Encapsulation• Specialized Business Content• Universal Business Content• Specialized Business Processes • Universal Business Processes• Business Content Format Definition• Process Description Language • Content Lifecycle
• Multi-Channel Publishing• Content Creation• Content Management• Content Syndication
Core Services• Security
• XML• Core XML Standards
zapthink:
Runtime Platforms
Service-Oriented Integration
Operation Management
Billing and Metering
Orchestration and Workflow
Hosting and Delivery• Infrastructure
• Security• Transformation• XML Data Storage
• Value Chain• eCommerce• eProcurment• Collaboration
Actors/objects/operations:
Service Registry
Service Description
Service Requester
Service Provider
Service
Service Description
Find
Publish
Bind
Heap
Installable Services
Remote Services
Business Content Instance
Business Process Instance
Service Oriented Architectures
Web Services Technology Stack
Infrastructure Services•Metadata services
•Description •Service Description Language•Verticals - Community Vocabularies•Registry•Process Flow• Directory / Registry• Repository
Network services •Routing•Caching •Referral•Messaging
Transport services–Backend Integration•Transactions •Context
Management
•Qualities of Service
Service Layers
Application Domain Services• Trading Partner Agreement• Semantic Web
Design/Meta Services• Creation guidelines
– Development Tools and Environments – Modularity – Simplicity Encapsulation– Specialized Business Content– Universal Business Content– Specialized Business Processes – Universal Business Processes– Business Content Format Definition– Process Description Language – Content Lifecycle
• Multi-Channel Publishing• Content Creation• Content Management• Content Syndication
Core /Infrastructure Services• Metadata services
– Description – Service Description Language– Verticals - Community Vocabularies– Registry– Process Flow– Directory / Registry– Repository
• Network services – Routing– Caching – Referral– Messaging
• Transport services– Backend Integration– Transactions – Context
• Management – Qualities of Service
• Security • XML
– Core XML Standards
Service Layers
Attributes of Service Layers
• All members share base class of access methods and message types
• Service level interactions rely only upon core services
• Application domain services have direct access to core services
– Access to these core services should be limited Core
MetaData
Infrastructure
ApplicationDomain
Design/Meta Services
• Creation guidelines– Modularity – Simplicity – Encapsulation
• Base Class Services– Find/discover– Publish– Bind
• Examples of class members– Development Tools and Environments – Registry and Repository– Process Description Services
– Process Description Language(s) – Specialized Business Processes – Universal Business Processes
– Content Description Services– Content Definition Language(s)– Specialized Content– Universal Content– Verticals - Community Vocabularies– Multi-Channel Publishing– Content Creation– Content Management– Content Syndication
Core
MetaData
Infrastructure
ApplicationDomain
• Features
• Auditing and logging
Service Layers
Core /Infrastructure Services
• Network services
– Routing
– Caching
– Referral
– Messaging
• Transport services
– Backend Integration
– Transactions
– Context
• Management
– Qualities of Service
• Security
• XML
– Core XML StandardsCore
MetaData
Infrastructure
ApplicationDomain
Features• Basic message exchange
(request/response)• Message enveloping (SOAP)• Routing: point-to-point or intermediaries• Description (WSDL)
• Bindings• Message structure
• Information Access• XML Infoset• ?PSVI Infoset?
Core /Infrastructure Services• Metadata services• Network services
– SOAP• Transport services
– HTTP, SNMP • Management
– Qualities of Service• Security • XML
– Core XML Standards– ???Addressing
– URI, Namespace
Stacks of stacks