Łukasz Sokołowski: /* 2. Service Response Returned ⌘ */

2015-11-04T01:49:46Z

2. Service Response Returned ⌘

New page

{{Cat|Web Services Basics For Non-programmers|06}}

<slideshow style="nobleprog" headingmark="⌘" incmark="…" scaled="true" font="Trebuchet MS" >
;title: Web Services Basics For Non-programmers
;author: Pete George (NobleProg Ltd)
</slideshow>

=Day One Revision ⌘=
# Introduction
# Service-Oriented Architecture
# Web Services Overview
# XML
# SOAP
=SOA & Web Services ⌘=
Service-Oriented Architecture

Without Agreed standards

Atomic

Interoperability

Service Request

Loose coupling

Brittleness

Hide information (service abstraction)

10. Are reusable services: a. used many times b. used in multiple processes

b. Used in multiple processes

=Name the features ⌘=
# <?xml version="1.0" encoding="utf-8"?>
# <mySoap:Envelope
# xmlns:mySoap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsx="http://www.webserviceX.NET">
# <mySoap:Header/>
# <mySoap:Body>
# <wsx:GetAtomicNumber>
# <wsx:ElementName>Oxygen</wsx:ElementName>
# </wsx:GetAtomicNumber>
# </mySoap:Body>
# </mySoap:Envelope>
==Name the features (answers) ⌘==
# <big>Prolog
# Root Element
# SOAP Envelope
# Namespace Declaration
# Attribute
# SOAP Header
# SOAP Body
# Body Block
# Element
# Namespace</big>

=Day Two Schedule ⌘=
# WSDL
# Handling Binary Content
# RESTfull Web Services
# Other Technologies
# Conclusion

=WSDL ⌘=
[[File:WSDL 1.png|600px]]

=WSDL Metaphor ⌘=
*XML = Language of message
-English
*SOAP = Style of message
-Business letter
*WSDL = specific instructions on what to write + what the response will be
11/18/2013
Pete George
NobleProg
Dear Sir

NobleProg
Chiswick
123456789
123456789
someone@nobleprog.com
=Interface Definition Language ⌘=
*Defines language for ORB interfaces (e.g. CORBA)
*Objects have defined contract with outside world
-Methods

-Method parameters

-Return values

*Usually interface investigated during programming

=Web Services Description Language ⌘=
*Standardized way to describe a Web service
*Not language-specific
-Describes data to be passed

-Describes method for passing data
*The basis of the original Web services specification
*WSDL 2.0 Became W3C recommendation 2007
*Originally used in conjunction with UDDI
=UDDI Registry ⌘=
*Universal Description, Discovery, and Integration
*Intended to provide way to discover Web services
-contact information for organisations

-services available from organisations
*<big>Not been widely implemented</big>
=WSDL with UDDI ⌘=
[[File:WSDL 2.png|600px]]

=1. Services Described Using WSDL ⌘=
[[File:WSDL 3.png|300px]]

* Service Provider describes its service using WSDL
* Definition published to registry of services
* Registry uses UDDI

=2. Registry Services Queried ⌘=
[[File:WSDL 4.png|300px]]

*Service Consumer issues one or more queries to registry:
-to locate a service

-to determine how to communicate with service

=3. WSDL Service Details Supplied ⌘=
[[File:WSDL 5.png|300px]]

* Registry provides response to Consumer queries
* i.e WSDL section containing details of the Provider’s requests and responses

=4. Service Request Sent ⌘=
[[File:WSDL 6.png|300px]]

* Service Consumer has WSDL request details passed from UDDI registry
* Service Consumer sends XML request

=5. Service Response Returned ⌘=
[[File:WSDL 7.png|300px]]

* Service Provider sends XML request
* Service Consumer knows from WSDL details (passed from UDDI Registry) what response message should look like

=WSDL without UDDI ⌘=
[[File:WSDL 8.png|600px]]

=1. Service Request Sent ⌘=
[[File:WSDL 6.png|300px]]

* Service Consumer knows WSDL request details
* Service Consumer sends XML request

=2. Service Response Returned ⌘=
[[File:WSDL 7.png|300px]]

* Service Provider sends XML request
* Service Consumer knows from WSDL details what response message should look like

=Obtaining WSDL ⌘=
*Usually by simple request, e.g.
GET

http://www.webservicex.net/periodictable.asmx?wsdl

[[File:WSDL 9.png]]

=<definitions> ⌘=
* Root Element
* Includes Namespace declarations
* Includes WSDL and SOAP declarations
=Periodic Table <definitions> ⌘=
[[File:WSDL 10.png]]

=<types> ⌘=
* WSDL file builds up in levels – starts with data types
* Defined in terms of XML Schema
=Periodic Table <types> ⌘=
<wsdl:definitions xmlns:s="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema
<s:element name="GetAtomicNumber">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ElementName" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
=<messages> ⌘=
*Defines content
-What the message is

-What kind of data it holds
=Periodic Table <messages> ⌘=
[[File:WSDL 12.png]]

=Periodic Table SOAP message ⌘=
*Can be translated into SOAP message, e.g.
[[File:WSDL 13.png]]

=<portType> ⌘=
*Define individual operations provided by service
-Input and Output operations

-Consist of messages
=<portType> ⌘=
[[File:WSDL 14.png]]

=<binding> ⌘=
*Binds operations to protocol, includes:
-<soap:binding>
* specifies binding to SOAP
* Transport type, e.g. HTTP
-<soap:operation>
*Specifies SOAPAction header – redundant
-<soap:body>
* Define how messages are presented
* Literal or encoded
=<binding> ⌘=
[[File:WSDL 15.png]]

=<service> ⌘=
*<port> How to send the information
-Binding information, e.g.
<wsdl:port name="periodictableSoap" binding="tns:periodictableSoap">
*<soap:address> Where to send the information
-Location of the Web service, e.g.

<soap:address location="http://www.webservicex.net/periodictable.asmx" />
=<service> ⌘=
<wsdl:service name="periodictable">
<wsdl:port name="periodictableSoap" binding="tns:periodictableSoap">
<soap:address location="http://www.webservicex.net/periodictable.asmx" />
</wsdl:port>
=Summary Exercise 1 ⌘=
Using the JMeter test tool, create a SOAP Service Request to retrieve the weight of an atom from the Periodic Table Web service.

See:

http://www.webservicex.net/periodictable.asmx?wsdl

(you might like to open the WSDL in a separate JMeter instance while you work)
# Start from PortType = "periodictableSoap"
# Create Message
# Use appropriate Types
=Summary Exercise 2 ⌘=
Confirm Exercise 1 SOAP message is correct:
# Pull Periodic Table WSDL into SoapUI
# Execute Ex1 SOAP message in JMeter. Compare Response Message with expected Response message in WSDL.
# Repeat exercise with own WSDL.

WSDL - Revision history

Łukasz Sokołowski: /* 2. Service Response Returned ⌘ */