SOAP Client Using Visual C++

Environment: Visual C++ 6.0, Windows 98/NT/2000

Section 1: Introduction

In this article, I’ll show you how to build a SOAP client using Visual C++. This tutorial gives you a hands-on introduction to using the SOAP API. SOAP is emerging as a very popular protocol for exchanging information. It’s relatively simple and designed to work with HTTP, SMTP, and other such protocols.


You should be familiar with using COM, specially using Smart Pointers in COM as I used an import directive to convert COM interfaces to Smart Pointers. You must have the Microsoft SOAP Toolkit installed on your system. For information on downloading the toolkit, see the Resources section later in this article.

Section 2: Fundamentals of SOAP Programming

I’ll start with the introduction of the classes involved in a basic SOAP Application. Before that, we have to import the required type libraries so that our program can use the SOAP classes.

Importing Type libraries:

All the objects and interfaces used in SOAP are found in mssoap1.dll. This file is installed with the Microsoft SOAP Toolkit 2.0. You can find this file in “C:Program FilesCommon FilesMSSoapBinariesMSSOAP1.dll”. All you have to do is to import this file into your source using the #import directive, which is used to incorporate information from a type library. The contents of the type library are converted into COM smart pointers, describing the COM interfaces. Because SOAP relies completely on XML, the Microsoft XML Parser is also needed for XML processing. The Microsoft XML parser is included in msxml#.dll where # is the version number. Again, you need to import this file before importing mssoap1.dll.

#import “msxml3.dll”
using namespace MSXML2;
#import “C:Program FilesCommon FilesMSSoapBinariesMSSOAP1.dll”
exclude(“IStream”, “ISequentialStream”, “_LARGE_INTEGER”,
using namespace MSSOAPLib;

That is all that is needed to include all class definitions required to develop a SOAP program. There are three steps that are necessary to make a SOAP client.

  • Specify and connect with the Web Service

  • Prepare and send the message

  • Read the response back from the Service

Now, let’s take a look at the classes involved. Following are the classes that are used to develop a basic SOAP client.

Class 1 — SoapConnector:

The first thing that is required for any client in a client/ server application is to connect with the server. The SoapConnector class implements the protocol that is used as a transport between the client and the server. SoapConnector acts as an abstract class for defining the interface for implementing other protocols. That is because SOAP is not limited to a specific protocol; you’ll see that some implementation supports MSMQ, MQ Series, SMTP, and TCP/IP Transports. For the sake of simplicity, I am demonstrating the use of HTTP Transport, which is implemented by the HttpConnector class available with the Microsoft SOAP Toolkit 2.0.

The steps involved in using SoapConnector class

a) Creating an object to SoapConnector:

ISoapConnectorPtr connector;

b) Specifying the Web Service Address:

Next, we have to define the Web service that we are using as a client. The service is specified using the Property (an attribute of HttpConnector). There are two things to specify when dealing with this attribute:

  • Which property are we referring to
  • the value of the respective property type

Here, for specifying the Web service, we use the EndPointURL property.

Connector->Property [“EndPointURL”] =
“some url pointing to web service”;

The following table provides a list of properties. (The property names are case sensitive.)

The password used for end point authentication.
The user name used for end point authentication.
The end point URL.
The password used for proxy authentication.
The port of the proxy server to use.
The IP address or host name of the proxy server.
The user name used for proxy authentication.
The value used in the "SoapAction" HTTP header. This property can be set only from the low-level API. It is ignored if the property is set using the ConnectorProperty property of the SoapClient interface (high-level API).
A string identifying the client certificate to use for the Secure Sockets Layer (SSL) protocol, if any. The syntax is:
[CURRENT_USER | LOCAL_MACHINE[store-name]]cert-name with the defaults being CURRENT_USERMY (the same store that Microsoft Internet Explorer uses).
The timeout for HttpConnector. This timeout is in milliseconds.
A Boolean property that specifies whether a to use a proxy server. By default, this property is set to False, indicating that a proxy server should not be used. Set this property to True if you want to use a proxy server.
If you set this property to True and don’t specify the ProxyServer property, the HttpConnector uses the proxy server set in the default settings of Microsoft® Internet Explorer. In this release, the HttpConnector ignores the "Bypass Proxy" settings in Internet Explorer.
A Boolean value (True or False) that specifies the use of SSL.
If this property is set to True, the HttpConnector object uses SSL connection regardless of whether HTTP or HTTPS is specified in the WSDL. If this property is set to False, the HttpConnector object will use SSL connection only if HTTPS is specified in the WSDL.

( The above table is taken from MSDN )

c) Connecting with the Web Service:

The connect method of HttpConnector is used to initialize the SoapConnector object and actually prepares a connection with the service.


d) Specifying the action:

After connecting with the server, we need to specify the action that we are going to perform on the Web service. To specify the Action, we again use the Property attribute of the soapConnector.

Connector->Property [“SoapAction”] = “some uri”;

e) Message handling:

After connecting with the service and specifying other details, we signal the start of a SOAP message being sent to the server. The function must be called before calling any other method of SoapSerializer ( which is used to prepare the message).


After finishing the message, we must call the EndMessage() function to actually send the message to the service.

[ message preparation code ]


This is all that is needed to actually connect with the service. The next part shows you how to create and prepare a message.


The SoapSerializer is used to build a SOAP message to be sent to the service. The SoapSerializer object must be connected with the SoapConnector object before communicating with the server. To interconnect these two objects, we need to call the Init method of the SoapSerializer object. This method takes a single argument, which is the InputStream (the stream the sends data to the server).

// creating a SoapSerializer object and initializing it
// with InputSTream

ISoapSerializerPtr Serializer;

Before looking into other functions of SoapSerializer, let’s take a look at a sample SOAP request to get an idea of what we are building in our code.

Simple Soap Request:

<SOAP: Envelope xmlns_SOAP=”soap namespace”>
<m:someMethodName xmlns_m=”some namespace”>
<someParameter> </someParameter> </SOAP:Body></SOAP: Envelope>
<SOAP: Envelope xmlns_SOAP="soap namespace">
<m:someMethodName xmlns_m="some namespace">
<someParameter> someParameterValue </someParameter>
</SOAP: Envelope>

A SOAP request is simply encapsulated into tags. The <Envelope> tag is the main tag of this SOAP Document. A SOAP message is always encapsulated in an envelope. The envelope contains a message body, which is specified by a <Body> Tag. The body contains the actual request. In C++, we have the appropriate methods to create these tags and specify any values in these. The following code piece demonstrates the use of these methods.

// Begins an <envelope> element in a SOAP message, first
// the argument defines the namespace. If it is empty, SOAP-ENV
// is used by default.
// The second and the third argument define the URI and the
// Encoding Type, respectively. Serialzier->startBody(“”);
// begins the <Body> element in the message. The first
// argument defines the encoding style Uri; by default it is NONE.

// Begins a child element into the body element of a SOAP message.
// The first parameter is the element name; the second parameter is
// the Uri; the third is the encoding style; and the last element
// is the namespace for the element.

// Writes the value of an element.

All the preceding startXXX functions have their equivalent endXXX function to end the element. After finishing the message, the connector’s endMessage() method is called to actually send the message as described above.

Until here in this tutorial, we have connected with the service, prepared our request, and sent it to service. The next and the final step is to read the response from the server.


This object reads the response from the service and parses the incoming message into DOM for further processing. Following is a sample SOAP Response from the service.

Simple SOAP Response:

<SOAP: Envelope xmlns_SOAP="soap namespace">
<m:someMethodNameResponse xmlns_m="some namespace">
<return> someResult </return>
</SOAP: Envelope>

Before calling any functions to get the result, we connect with the OutputStream to actually read the response in a SoapReader object. ( An OutputStream receives data from the service ).

// code to create a SOAPReader object and connecting with
// the outputstream

ISoapReaderPtr Reader; Reader.CreateInstance(_uuidof(SoapReader));

// the load method can also accept a XML Document File or String

After loading the response into our SoapReader object, we get the result by calling the RPCResult property of SoapReader object. But RPCResult doesn’t return the actual result; it returns the first child element of the first entry in the <Body> element. We get the result by calling the text property.


Section 3: Demonstrating a Sample SOAP Client

For demonstrating the use of above SOAP classes, I used one of the services listed on The service indicates Yahoo Messenger’s online presence. You can find the required details by following this URL: The only thing it expects is a method parameter, such as the Yahoo user’s login id. The result returned is a Boolean value indicating 0 for offline and 1 for online. Other details are available on the site or by viewing the wsdl at

Section 4: Resources

The SOAP specification Simple Object Access Protocol (SOAP) 1.1 – W3C Note

Microsoft SOAP Toolkit Download

Source Code:

#include <stdio.h>

#import “msxml3.dll”
using namespace MSXML2;

#import “C:Program FilesCommon FilesMSSoapBinariesMSSOAP1.dll”
exclude(“IStream”, “ISequentialStream”, “_LARGE_INTEGER”,
using namespace MSSOAPLib;

void main()

ISoapSerializerPtr Serializer;
ISoapReaderPtr Reader;
ISoapConnectorPtr Connector;

// Connect to the service
Connector->Property[“EndPointURL”] =

// Begin message
Connector->Property[“SoapAction”] = “uri:allesta-YahooUserPing”;

// Create the SoapSerializer

// Connect the serializer to the input stream of the connector

// Build the SOAP Message

// Send the message to the web service

// Read the response

// Connect the reader to the output stream of the connector

// Display the result
printf(“Answer: %sn”, (const char *)Reader->RPCResult->text);



Download demo project — 3.18 KB

More by Author

Get the Free Newsletter!

Subscribe to Developer Insider for top news, trends & analysis

Must Read