Hello Trailblazers,

Welcome to the 13th tutorial of the Salesforce Integration Tutorial Series. In the previous tutorial, we created a SOAP web service in apex. You can have a look at that tutorial by clicking here. In this tutorial, we're going to create a test class for a SOAP web service.

Let's have a look at the below code:-

As  you can see above, we have a webservice method in our ContactResource class. This method takes an integer which is the limit of contacts. Then, we query some contacts from our org using that limit and return the list of contacts in the response.

Now it's time to create a test class for the same. The test class for this web service will be exactly the same as we make a test class for a normal apex class. We just have a method which is accepting an integer as a parameter and returning a list of contacts. I created a new test class for our ContactResource class named as ContactResourceTest. Let's have a look at the code below:-

As you can see above, we have a TestSetup method which is creating 5 contacts with name Rahul Malhotra. This is our test data. Then, we have a testGetContactIdAndNames method which is simply calling the getContactIdAndNames method of our ContactResource class by giving the integer 1 in the parameter. That method is returning a list of contacts which we have stored in returnedContacts variable. Finally, we're just checking that our returnedContacts list is not null, has a size of 1 and the contact inside that list has a name of Rahul Malhotra. So, we just checked that our method is working as expected and when you'll run this test class, you'll find that our ContactResource class is covered with 100% coverage as shown below:-


That's all for this tutorial. You have successfully created a test class for a SOAP Web Service class in apex. You can find the code for the web service and test class in the soapapi branch of my SFDC-Integration-Tutorial github repository by clicking here.

Tired of reading or just scrolled down, don't worry, you can watch the video too.



Do checkout the other tutorials in this whole integration tutorial series by clicking here. If you liked this tutorial, make sure to share it in your network and let me know your feedback in the comments section down below.

Happy Trailblazing..!!

Hello Trailblazers,

Welcome to the 12th tutorial of the Salesforce Integration Tutorial series. In the previous tutorial, we created a mock class and a test class for our SOAP API callout. You can find that tutorial by clicking here. In this tutorial, we're mainly going to create a web service i.e. a custom SOAP API in Salesforce.

Remember the 2nd tutorial of Integration Tutorial Series in which we created a custom REST API and explored GET method in detail ? Let's recall that code by having a look below:-

As you can see above, we have a method named as:- getContactIdAndNames() which is called when we make a get request to this API. Inside this method, we're getting the contactLimit i.e. the number of contacts to be queried as a URL parameter and we're returning a list of contacts in the response.

Creating a custom SOAP API

Now, I am going to convert the same method into a webservice method so that it's converted into a SOAP API and then we'll generate a WSDL file for it and call it from SOAP UI client. If you're not aware of SOAP UI, please have a look at this tutorial first and then you can come back to the current tutorial as we're going to use SOAP UI client to hit our custom SOAP API and get the response.

Let's have a look at the updated code below:-

As you can see above, I removed all the annotations like:- @HTTPPost @RestResource etc. as we don't need them in case of defining a SOAP API. All we need is a global class with a static method defined with webservice keyword. The number of contacts to query that we were giving previously as a URL parameter are now given in the method parameter named as:- contactLimit. After that we're simply querying the contacts and returning the list of contacts in the response.

And that's all. You have successfully created a custom SOAP API in Salesforce. SOAP APIs basically support GET and POST HTTP Methods according to the w3 specifications defined here:- https://www.w3.org/TR/2007/REC-soap12-part0-20070427/#L26854 but we mostly use POST in case of SOAP requests as we have messages encoded in XML format. So, whenever you need to create a SOAP webservice in Salesforce, all you need to do is to define a static method in a global class with the keyword webservice. You can take the input as a parameter in method and the data returned by the method will be given in the response.

Generating a WSDL file

Now, it's time to test our custom SOAP API that will return the contact id and names of contacts present in salesforce and we can limit those contacts by giving the contactLimit in the input request XML. Remember, when we wanted to consume a SOAP API we used WSDL2Apex to generate an apex class from WSDL. In the same way you can generate a WSDL from your custom apex class. All you need to do is go to setup and search for apex classes. Click on Apex Classes under Develop and you'll see the below page:-


As you can see above in the ContactResource class I have an option of WSDL. Either you can click this or when you open the ContactResource class, you'll see a Generate WSDL button as shown below:-

You can provide this XML to the 3rd party who wants to consume your custom SOAP API and it'll be able to connect with Salesforce.

Testing our SOAP API using SOAP UI

Now we have the WSDL for our custom SOAP API. So, it's time to test our SOAP API. I have already imported the Enterprise WSDL into the SOAP UI and got the session id. If you want to learn that, you can have a look at another tutorial by clicking here. I am going to add our new WSDL to the existing project. To do that, just right click on the project and click on Add WSDL as shown below:-

You'll see a dialog as shown below:-


Choose your custom WSDL file and click on OK. When I tried to import the WSDL and clicked on OK button, I got some errors as shown below:-


These errors are coming because the WSDL file that we downloaded from Salesforce has some tags missing. For ex:- The first error is regarding the ChangeEventHeader which is not found in our WSDL file. However, I checked Enterprise WSDL and I was able to find the ChangeEventHeader as shown below:-


The other errors are related to some other type tags like:- json, stringList. You can find all the missing data in the enterprise wsdl and can copy from there to update your actual wsdl file.

I tried and added the ChangeEventHeader, json, and stringList xml types that were missing in my custom WSDL file below the schema tag as shown below:-


Please note that I have added xsd: namespace also along with the parent tag name for consistency, as all the other tags were having this namespace in the custom xml file I am trying to import. I tried to import my WSDL file in SOAP UI again and found that those 3 errors are resolved and I have some of the remaining errors that I need to resolve.


So, I updated the the custom API xml file again adding the missing contents and tried to import that file again. Finally, I got my XML imported into SOAP UI and our method getContactIdAndNames is available with the input XML request as shown below:-


I am also sharing the XML changes I did below, so that you can just add-on the same elements in your custom XML in case the error is exactly same. Otherwise you'll find all the missing elements in Enterprise XML from Salesforce.

Now, It's time to test our API. As you can see in the image below, I commented out the XML tags that I am not using, added the session id received from login request between the con:sessionId xml tag. Between the con:getContactIdAndNamesTag I have another tag named as con:contactLimit, which is nothing but the parameter of our apex method. I have specified the limit as 2 here as I just want to fetch 2 contacts from my org with Id and Name.


As you can see above, on the left hand side I have the request XML that I sent using the green play button above and on the right hand side, I have the response xml with 2 contacts queried from my Salesforce Org with Id and Name of each contact.

Tired of reading or just scrolled down, don't worry, you can watch the video too.



That's all for this tutorial. Today, you learned about creating a custom SOAP API in Salesforce and testing it using SOAP UI. You can find the code used in this tutorial in the soapapi branch of my SFDC-Integration-Tutorial github repository here. If you liked this tutorial, make sure to share it in your network and let me know your feedback in the comments down below.

Happy Trailblazing..!!

Hello Trailblazers,

SOAP UI is a very popular API testing tool specially when we talk about SOAP APIs. So, in this tutorial, we're going to see how we can connect with Salesforce Org using SOAP UI and we will call a standard salesforce soap api and have a look at the response. If you want to learn about connecting with Salesforce using REST APIs you can have a look at this tutorial. So, let's begin:-

Download SOAP UI

Salesforce Enterprise WSDL

Connecting with Salesforce using SOAP UI

Executing a Query using SOAP UI

Hello Trailblazers,

Welcome to the 11th tutorial of the Salesforce Integration Tutorial series. In the previous tutorial, we performed a callout to a SOAP API by importing a WSDL file in Salesforce. You can find that tutorial by clicking here. In this tutorial, we're mainly going to create a test class for the same callout that we performed before. So, make sure you've completed the previous tutorial before you begin with this one.

If you remember, in case of REST APIs, when we have to create a test class for an api callout, we used to create a mock class that implements HTTPCalloutMock interface and that mock class was used to create a mock response for the API callout that is going to initiate from our test class. In this case, we're going to do the same.

This time, we're going to create a mock class and implement a different interface which is known as WebServiceMock. This interface consists of a doInvoke() method which we need to override in our mock class. The doInvoke() method will receive request and response in the parameters and we can set the response parameter with the fake response that we're going to send for our soap api callout while running a test class.

If you remember, we named our auto-generated class for SOAP API callout as CalculatorService. So, let's name our mock callout class as:- CalculatorServiceMock. The code for the mock class is given below:-

As you can see above, our calculator service soap api basically peforms 4 mathematical operations:- Addition, Subtraction, Multiplication and Division. So, we've setup 4 macros named as:- ADD_MODE, SUB_MODE, MUL_MODE, DIV_MODE. These 4 macros basically define 4 modes in which our mock class will run to generate different responses when different methods of CalculatorService class are called. We've also declared another string variable named as mode which is setup using a constructor of this mock class.

Inside our doInvoke() method, we're checking the mode of our callout and setting up the fake response by using the responsewrapper provided by our auto-generated calculatorservice class.For ex:- When we have to generate a response for addition, we're using AddResponse_element response wrapper from CalculatorService class to setup the result of addition and finally setting up the response using the response map in which we have the key as:- response_x and the value as the instance of AddResponse_element class which is addResponse. Each response wrapper has a result variable like:- AddResult in case of addition and SubtractResult in case of subtraction where we can set the result of operation.

We've setup the result of operations accordingly by assuming that our input elements are:- 6 and 3. We'll be sending these numbers from our test class to the api callout so that we get the correct response from the mock.

Now, it's time to create our test class for SOAP API callout. We've created a test class with name:- CalculatorServiceTest. The code for the same is given below:-

As you can see above, first of all we've setup two integers as x and y with values 6 and 3 as we know that our mock class will send the correct response for any operation that we call using the soap api for these inputs. After that we've 4 test methods defined, one for each operation i.e.:- Addition, Subtraction, Multiplication and Division that can be performed by our CalculatorService class. So, we basically need to cover the Add(), Subtract(), Multiply() and Divide() methods which are defined in the CalculatorSoap inner class of our CalculatorService class that we were using to make callouts in our previous tutorial.

Let's have a look at testAddCallout() method. In this method, first of all we set the mock using our Test.setMock() method. This time we pass the instance of WebServiceMock.class in the first parameter and an instance of our CalculatorServiceMock class in the second parameter with the mode as CalculatorServiceMock.ADD_MODE in the constructor. Remember, ADD_MODE was one of the macros that were defined in our mock class and is used to check the mode in order to define the addition response. That's why we're passing the same variable in the constructor to setup the correct response for our additon SOAP callout.

After that, we simply created an instance of our CalculatorService.CalculatorSoap class named as calculator. We called the Add() method and passed our x and y variables with values:- 6 and 3. You can checkout the mock class again to see that we've setup the mock response as 9 in AddResult which is the sum of 6 and 3. We got the result from add method i.e. the actual api callout and that result is stored in result integer variable. We've also setup another variable expectedResult which is x+y. So, this expectedResult also has a value 9 and the result variable also receives 9 from our mock api. At last, we check that our expectedResult and result variables have same value using System.assertEquals() method and our test method for addition is complete.

Similarly, we've made different methods to cover subtraction, multiplication and division operations in our test class. You can run this test class and you'll see that the CalculatorService class is covered with 100% coverage as shown below:-


Congratulations..!! You've successfully created a test class for SOAP API callout with 100% coverage.

Tired of reading or just scrolled down, don't worry, you can watch the video too.



All the code for this tutorial is present in our soapcallouttest branch of the SFDC-Integration-Tutorial github repository that can be accessed by clicking here. That's all for this tutorial, if you liked it, do share it in your network and let me know your feedback in the comments section down below.

Happy Trailblazing..!!

Hello Trailblazers,

Welcome to the 10th tutorial of the Salesforce Integration Tutorial series. In the previous tutorials, we mainly worked on creating custom REST APIs and performing callouts to REST web services. In this tutorial, we're mainly going to perform a callout to SOAP API.

I am going to use the calculator SOAP API for this tutorial available at:- http://www.dneonline.com/calculator.asmx. The actual web service WSDL is available here:- http://www.dneonline.com/calculator.asmx?WSDL. However, Salesforce was not able to parse that WSDL.

Blog Update: Most of the people were not able to parse WSDL because of the same error i.e. more than one binding so I am specifying how I removed that error from the WSDL I am using.

I got the below error on importing the calculator WSDL in Salesforce.


It says:- Error: Failed to parse wsdl: Found more than one wsdl:binding. WSDL with multiple binding not supported

When I had a close look at the WSDL file, I got to know that it consists of multiple WSDL binding tags as shown below:-


So, I modified it a little bit i.e. removed the second binding tag and it's references from the WSDL. You can see the changes below:-

1. Removed the second WSDL binding.


2. Removed the binding references.



And that's it. My WSDL is now ready to be parsed by Salesforce and it was parsed succesfully without any errors and warnings. You can use the modified WSDL for this tutorial which you can see below:-

You can copy and paste the above xml in a new file or save it directly from here. Once you have the WSDL file ready, it's time to import that in Salesforce and call our Calcuator API from apex to perform some of the basic arithmetic operations. Salesforce has a built-in WSDL2Apex generator and we're going to use that only.

Importing WSDL to Salesforce using WSDL2Apex