Course Outline
When constructing a modern, flexible company business architecture, web Services are often considered the lingua franca for obtaining a loosely coupled integration between heterogeneous applications. There is a considerable temptation to apply web services in an ad-hoc fashion, even when their usage is in fact not justified. Our training will therefore start with an overview of the pro and cons of webServices as well as a justification process for services.
In addition to the current technology used for implementing Web Services (SOAP, WSDL, UDDI, REST / RESTful Web Services...), we will also study how specific service functionality can be mapped to the corresponding business requirements. What is the appropriate level of granularity of a service? Do patterns exist that we can apply to services? The most up to date developments such as service choreography, WS-CDL, WS-Transaction, WS-Addressing and many others will be covered in reasonable depth. After taking this course, the participants will have a thorough understanding of webServices’ capabilities and insight into tools and techniques that enable a more agile organization.
Course Content
Available as a public or closed course at our London training centre, or can be tailored to your team's requirements and delivered onsite as a bespoke, customised training course.
This course has been developed for real-world, commercial scenarios by our expert instructors. See below for detailed syllabus. If you have a technical question, please email sales@jbinternational.co.uk
Web Services Training Course Outline
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
A closer look
Creating XML
Validating XML
Viewing XML
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 / RESTful Web Services
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
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
