Web Services: from design to implementation

• Wat is een WebService, geschiedenis en positionering
• Web Service concepten
• Het service justificatie proces
• Granulariteit van een service
• Het business value contract en SLA
• De foundations van Web Services

• WSDL, REST, SOAP and UDDI
• Betrouwbare berichtuitwisseling
• Coordinatie, orchestratie, choreographie en compositie
• Top-down process-oriented design
• Bottom-up document-oriented design
• Uitvoeren en monitoring van services

Bekijk meer onderwerpenBekijk minder onderwerpen

• Introduction
  • Web Services concepts
  • Standards
  • Interactions are the primary model
  • Use of HTTP, XML and other standards
  • Internet Services
  • The use of the HTTP and XML
  • Providing remote operations
  • Differences from local RPC system
  • Accountability is required
  • Repackage existing capability
  • Interoperable with other systems
  • W3C Web service architecture working group
• Philosophy
  • Service justification process
  • Granularity of a service
  • Coarse grained versus fine grained approach
  • Read/write state
  • Conversations and state
  • Web services architecture requirements
  • Web services architecture
  • Web services glossary
  • Web services architecture
  • Use case scenarios
  • Discovery agencies
  • Determining the business value of a service
• Technologies involved
  • The technical service contract
  • The human readable contract and SLA
  • The foundations of Web Services
  • WSDL, SOAP and UDDI
  • The management layer
  • The “Application semantics” layer
  • WS-Transactions
  • WS-CDL Choreography
  • WS-Addressing
  • WS-Security
  • WS-Routing
• Run Time messaging
  • Run time protocols
  • Descriptions of services.
  • XML-encoded messages
  • Encoding the parameters to a remote operation
  • XML used as the marshalling style
  • Standard marshalling syntax
  • Well-defined input and output parameters
  • SOAP carrying an XML document
  • The XML schema and namespaces
  • The document object model (DOM)
  • XSLT and XML-Query
  • XML encryption
  • The document mode of SOAP
  • The XML mode versus RPC mode
• Functionality at runtime
  • Routing
  • Security
  • Profiling existing security technologies
  • Authentication and key management.
  • Packaging of attachments to messages
  • XML Packaging.
  • Reliable messaging
  • delivery, non-duplication, ordering
  • TCP provided reliability
  • TCP does not provide accountability
  • Representational state transfer (REST)
  • Improving performance
• Description
  • Different models
  • Different levels of abstraction
  • Multiple specs
  • WSDL: modeling at the lowest level
  • The message or request/response interaction
  • The binding to a specific HTTP port
  • Coordination, orchestration, choreography, composition
  • Protocols involving more than two messages
  • Protocols having a common shared state
  • Protocols having more than two parties involved;
  • The protocol as business protocol

• Composability and Choreography
  • Composability of web services
  • Exposing larger web services
  • Various web services working together
  • Orchestration and Choreography
  • Crossing application boundaries
  • Crossing organizational boundaries
  • The master process delegating to other services
  • WSCI, BPML and BPEL
  • WSCI: emphasis on description
  • BPEL focus on executability
  • WS Choreography Group
  • IBM, Microsoft and BEA, under OASIS
  • BPMI, Business Process Modeling Language BPML
  • Sun et al: Web Services Choreography Interface (WSCI)
  • IBM specs ws-coordination, ws-transaction, ws-orchestration
• Message-oriented Design
  • Multi-agent multi-process system
  • Process-oriented attitude
  • Document-, or message-oriented attitude
  • Top-down approach using WSCI and BPL
  • Business rule triggers
  • Top-down process-oriented design
  • Bottom-up document-oriented design
  • BPEL scripts
  • Conditional execution
  • Correlating processes
  • Moving to RDF
  • Web service choreography#Process modeling
  • Business systems with multiple agents
  • Handling multiple concurrent processes
  • example: will the process necessarily terminate?
  • example: will the service respond within a given time?
  • example: will the net gain from a sale always be positive?
  • pi calculus
  • Rule-based systems
  • Limitations on computational power in WSCI and BPEL
  • Petri nets
• Discovery
  • Establishing relationships
  • Trust infrastructure
  • Automatic comparison shopping
  • Working within the corporate firewall
  • The UDDI project
  • Definition of an ontology
  • Single-tree ontology
  • Inter-registry operations
  • The semantic web
  • Location transparency
• Web Services and Semantic Web
  • A semantic web application
  • RDF mapping
  • Potential ambiguity
  • Common semantic web tools
  • The DAML-services coalition
  • Semantic Web agents
• Service design tools
  • Intalio designer
  • Web services composition
  • Component web services
  • Microsoft BizTalk
  • Oracle SOA Suite
  • Tibco
  • BEA Aqualogic
• Runtime System management
  • Commercial environments
  • Downtime is expensive
  • Running and monitoring services
  • Reliable transmission
  • Provisioning and upgrading services
  • BPM tools
  • Clustering and load balancing of services
  • Security requirements