SOAP
SO-S-6 WSDL service
Generating HTML based Service interactions from a WSDL file
Web services architecture
- Service providers deploy and publish services by registering them with the Service broker.
- Service requesters find services by searching the Service broker's registry of published services.
- Service requesters bind to the Service provider and consume the available services.
Technology Uses
In the world of Web services, each of these three operations involves three complimentary yet distinct technologies:- Publishing services uses the Universal Description, Discovery and Integration (UDDI) API
- Locating services uses a combination of UDDI and the Web Services Description Language (WSDL)
- Binding to services leverages WSDL and the Simple Object Access Protocol (SOAP).
At the most basic level, the Binding operation is the most important of the three.
Example
- The example will create a SOAP based interface and WSDL description for searching an existing Customer Order
- New orders can be added into the demo database.
- The first page renders the WSDL as an HTML form for selecting the SOAP method.
- The second page renders the WSDL again to make a form for input parameters. Note that on this entry form needs to be entered valid _CustomerID (for example ALFKI) and _ProductID (for example is 1). Otherwise the servce will generate SOAP Fault message. Also _ShipVia needs to have a correct value to be entered (for example 1,2 or 3).
- Final page displays the result from the SOAP call.
| View the source | Action |
|---|---|
| 1. so_s_6.sql | Set the initial state |
| 2. so_s_6_sample_1.vsp | Run |
| 3. so_s_6_sample_2.vsp | |
| 4. so_s_6_sample_3.vsp | |
| 5. wsdl_call.xsl | |
| 6. wsdl_oper.xsl |
OpenLink Home
Technical Support