SQL Server R2 Access webservice based on WSDL

Learning and Finishing: WebService Learning and Finishing (i)--three kinds of client call arrangement

Self-generalization:

WebService through HTTP communication, data is transmitted in XML format

SOAP is the Access Protocol (annotated URL to access WebService, method name, parameter, username/password, etc.)

WSDL is the WebService Description Language (how the service is to be called)

. asmx is the. Net WebService suffix name (there are also methods that describe the service invocation and are easier to read). ASMX?WSDL can also view the description language of the service

Body:

Project requirements need to be webservice with a non-. Net development (see the WSDL description document only).

I have only touched the description document of the. asmx I have no connection to WSDL at all.

Specific soap can be seen in. asmx, and WSDL sees me as foggy.

After a while, I found a tool called SoapUI to convert the WSDL into SOAP .

Very smoothly, only the WSDL document's webservice is accessed on SQL Server.

Step 1:

Step 2:

Step 3:

Step four: SQL Server invokes WebService with MSXML through TSQL (stored procedure)

A few parameters that call this stored procedure can be found on the SOAPUI

[Email protected]: The address of the first line in step 3
[Email protected]: In step 3, the first line of the post
[Email protected]: The XML document on the left in step 2
[Email protected]: In step 3 of the SOAPAction, in this case, "", so in the call stored procedure this parameter is written "" "
[Email protected]: empty
[Email protected]: empty
[Email protected]: return results

Reprint please specify the source, by Lazyneal 2017

SQL Server R2 Access webservice based on WSDL