How to use soapUI to simulate a webservice client to send a request

Tools Raw materials.

SOAPUI software.

Computer. Method steps.

When developing a webservice client, you first need to obtain the webservice service address of the server and create the corresponding client request based on the service address and communication protocol. If the other party provides a service address, you can copy and paste it through your browser. As you can see from the page, this is a webservice server generated based on the AXIS framework.

Add "?" to the end of the server-side addresswsdl" (note that it is an English question mark), you can see various services, namespaces and other information published by the server on the page. As can be seen from element, there are two methods that are advertised on the server side:

sayhello and sayno. The description with the response is the information returned by the server.

Create a WebService client request on the SOAPUI tool based on the address provided by the server. Open the SOAPUI software, click the file file in the upper left corner of the software, and there are three ways in the pop-up page, generally add the first new SOAPUI project to create a new SOAPUI project.

The web service is generally called by the SOAP protocol through HTTP, in fact, it is a WSDL document, and customers can read the WSDL document to use this web service. The customer generates a SOAP request message based on the WSDL description document. The web service is placed behind a web server (e.g. IIS), and the SOAP requests generated by the client are embedded in an HTTP POST request and sent to the web server.

The web server then sends these requests to the web service request handler. The request handler parses the received SOAP request, calls the Web service, and then generates the corresponding SOAP response. When the web server receives a SOAP reply, it sends it back to the client via HTTP reply.

Personally, I think that most of the problems can be handled by using webservice as HTTP as a request and response method.

SOAP uses HTTP to deliver XML, and although HTTP is not an efficient communication protocol, and XML requires additional parse, both of which make transactions much slower than other solutions. However, XML is an open, robust, and semantic messaging mechanism, and HTTP is a broad and avoids many firewall problems, so that SOAP is widely used. But if efficiency is important to you, then you should think about other ways than soap.

In order to better understand how SOAP, HTTP, and XML work, you may want to consider the operation mechanism of COM DCOM, which handles the low-level details of network protocols, such as communication between proxy stubs, lifecycle management, and object identification. When the client interacts with the server, DCOM uses NDR (Network Data Representation) as the data representation, which is a low-level platform-agnostic data bureau representation.