Skip to content

Salesforce SOAP Connector Example

The Salesforce SOAP Connector allows you to work with records in Salesforce, a web-based service that allows organizations to manage contact relationship management (CRM) data. You can use the Salesforce connector to create, query, retrieve, update, and delete records in your organization's Salesforce data. The connector uses the Salesforce SOAP API to interact with Salesforce.

What you'll build

This example explains how to use the Salesforce client to connect with the Salesforce instance and perform the create sObjects operation. Then execute a SOQL query to retrieve the Account Names in all the existing accounts. All operations are handling as SOAP messages.

  • Create an sObjects in Salesforce.

The user sends the request payload that includes sObjects (any object that can be stored in the Lightning platform database), to create a new Account object in Salesforce. This request is sent to WSO2 EI by invoking the Salesforce SOAP connector API.

  • Execute a SOQL query to retrieve the Account Names in all the existing accounts.

In this example use the Salesforce Object Query Language (SOQL) to search stored Salesforce data for specific information which is created under sObjects.

All two operations are exposed via an salesforce-soap-API API. The API with the context /salesforce has two resources

  • /createRecords: Creates a new Account object in Salesforce.
  • /queryRecords : Retrieve the Account Names in all the existing accounts in Salesforce.

Using Salesforcesoap SOAP Connector

The user calls the Salesforce SOAP API. It invokes the createRecords resource and creates a new account in Salesforce. Then through the queryRecords resource, it displays all the existing account details to the user.

If you do not want to configure this yourself, you can simply get the project and run it.

Configure the connector in WSO2 Integration Studio

Connectors can be added to integration flows in WSO2 Integration Studio, which is the tooling component of WSO2 EI. Once added, the operations of the connector can be dragged onto your canvas and added to your sequences.

Import the connector

Follow these steps to set up the Integration Project and the Connector Exporter Project.

  1. Open WSO2 Integration Studio and create an Integration Project. Creating a new Integration Project

  2. Right click on the project that you created and click on Add or Remove Connector -> Add Connector. You will get directed to the WSO2 Connector Store.

  3. Search for the specific connector required for your integration scenario and download it to the workspace.
    Search Connector in the Connector Store

  4. Click Finish, and your Integration Project is ready. The downloaded connector is displayed on the side palette with its operations.

  5. You can drag and drop the operations to the design canvas and build your integration logic. Drag connector operations

Add integration logic

First create an API, which will be where we configure the integration logic. Right click on the created Integration Project and select, New -> Rest API to create the REST API. Specify the API name as salesforcerest and API context as /salesforcerest.

Adding a Rest API

Configuring the createRecords resource

Now follow the steps below to add configurations to the resource.

  1. Initialize the connector.

    1. Navigate into the Palette pane and select the graphical operations icons listed under Salesforce Connector section. Then drag and drop the init operation into the Design pane.

      Drag and drop init operation

    2. Add the property values into the init operation as shown below. Replace the username, password, loginUrl and blocking with your values.

      • username: The username to access the Salesforce account.
      • password: The password provided here is a concatenation of the user password and the security token provided by Salesforce.
      • loginUrl : The login URL to access the Salesforce account.
      • blocking : Indicates whether the connector needs to perform blocking invocations to Salesforce. (Supported in WSO2 ESB 4.9.0 and later.)
  2. Set up the salesforce.create operation.

    1. Setup the create configurations.

    In this operation we are going to create a sObjects in the Salesforce account. An SObject represents a specific table in the database that you can discretely query. It describes the individual metadata for the specified object. Please find the create operation parameters listed here.

    - **sObjectName** : XML representation of the records to add.
    - **allowFieldTruncate** : Whether to truncate strings that exceed the field length (see Common Parameters).
    - **allOrNone** : Whether to rollback changes if an object fails (see Common Parameters).
    
    While invoking the API, the above three parameters values come as a user input.
    1. Navigate into the Palette pane and select the graphical operations icons listed under Salesforce Connector section. Then drag and drop the create operation into the Design pane.

      Drag and drop create operations

    2. To get the input values in to the API we can use the property mediator. Navigate into the Palette pane and select the graphical mediators icons listed under Mediators section. Then drag and drop the Property mediators into the Design pane as shown bellow.

      Add property mediators

      The parameters available for configuring the Property mediator are as follows:

      Note: That the properties should be add to the pallet before create the operation.

    3. Add the property mediator to capture the sObject Name value. In this example we are going to create a new Account object using the POST method.

      • name : Name
      • expression : //Name/text()
      • type : STRING

      Add values to capture sObjectName value

    4. Add the payload factory mediator to capture the sObject content.

      Add values to capture sObjec value

    5. Forward the backend response to the API caller.

    When you are invoking the created resource, the request of the message is going through the /createRecords resource. Finally, it is passed to the Respond mediator. The Respond Mediator stops the processing on the current message and sends the message back to the client as a response.

    Drag and drop respond mediator to the Design view.

    <img src="../../../../assets/img/connectors/salesforcesoap-respond-mediator.png" title="Add Respond mediator" width="800" alt="Add Respond mediator"/>

Configuring the queryRecords resource

  1. Initialize the connector.

    1. You can use the same configuration to initialize the connector. Please follow the steps given in section 1.1 and 1.2 for setting up the init operation to the createRecords operation.
  2. Set up the salesforce.query operation.

    1. Setup the query configurations.

    In this operation we are going to retrieve data from an object, use salesforce.query and specify the following properties. If you already know the record IDs, you can use retrieve instead.

    • batchSize : The number of records to return. If more records are available than the batch size, you can use the queryMore operation to get additional results.
    • queryString : The SQL query to use to search for records.

    While invoking the API, the above two parameters values come as a user input.

    1. Navigate into the Palette pane and select the graphical operations icons listed under Salesforce Connector section. Then drag and drop the query operation into the Design pane.

      Drag and drop query operations

    2. To get the input values in to the API we can use the property mediator. Navigate into the Palette pane and select the graphical mediators icons listed under Mediators section. Then drag and drop the Property mediators into the Design pane as shown below.

    3. Add the property mediator to capture the sObject queryString value. In this example we are going to create a new Account object using the POST method.

      • name : queryString
      • expression : //queryString/text()
      • type : STRING

    Add values to capture queryString value

    1. Forward the backend response to the API caller.

    When you are invoking the created resource, the request of the message is going through the /createRecords resource. Finally, it is passed to the Respond mediator. The Respond Mediator stops the processing on the current message and sends the message back to the client as a response.

    Drag and drop respond mediator to the Design view.

    Add Respond mediator

    Now you can switch into the Source view and check the XML configuration files of the created API and sequences.

    create.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <api context="/salesforce" name="salesforce-soap-API" xmlns="http://ws.apache.org/ns/synapse">
        <resource methods="POST" url-mapping="/createRecords">
            <inSequence>
                <property expression="//Name/text()" name="Name" scope="default" type="STRING"/>
                <salesforce.init>
                    <username>kasunXXX@wso2.com</username>
                    <password>eiconnectortestXXXnO9Nz4Qpiz5Us4N7ijj9zyA</password>
                    <loginUrl>https://login.salesforce.com/services/Soap/u/42.0</loginUrl>
                    <blocking>false</blocking>
                </salesforce.init>
                <payloadFactory media-type="xml">
                    <format>
                        <sfdc:sObjects type="Account" xmlns:sfdc="sfdc">
                            <sfdc:sObject>
                                <sfdc:Name>{$ctx:Name}</sfdc:Name>
                            </sfdc:sObject>
                        </sfdc:sObjects>
                    </format>
                    <args/>
                </payloadFactory>
                <salesforce.create>
                    <allOrNone>0</allOrNone>
                    <allowFieldTruncate>0</allowFieldTruncate>
                    <sobjects xmlns:sfdc="sfdc">{//sfdc:sObjects}</sobjects>
                </salesforce.create>
                <respond/>
            </inSequence>
            <outSequence>
                <send/>
            </outSequence>
            <faultSequence/>
        </resource>
        <resource methods="POST" url-mapping="/queryRecords">
            <inSequence>
                <property expression="//queryString/text()" name="queryString" scope="default" type="STRING"/>
                <salesforce.init>
                    <username>kasunXXX@wso2.com</username>
                    <password>eiconnectortestXXXnO9Nz4Qpiz5Us4N7ijj9zyA</password>
                    <loginUrl>https://login.salesforce.com/services/Soap/u/42.0</loginUrl>
                    <blocking>false</blocking>
                </salesforce.init>
                <salesforce.query>
                    <batchSize>200</batchSize>
                    <queryString>{$ctx:queryString}</queryString>
                </salesforce.query>
                <respond/>
            </inSequence>
            <outSequence>
                <send/>
            </outSequence>
            <faultSequence/>
        </resource>
    </api>

    Get the project

You can download the ZIP file and extract the contents to get the project code.

Download ZIP

Tip

You may need to update the value of the access token and make other such changes before deploying and running this project.

Deployment

Follow these steps to deploy the exported CApp in the Enterprise Integrator Runtime.

Deploying on WSO2 Enterprise Integrator 7

You can copy the composite application to the /repository/deployment/server/carbonapps folder and start the server. Micro Integrator will be started and the composite application will be deployed. You can further refer to the application deployed through the CLI tool. You can download the CLI tool from here from the Other Resources section. Make sure you first export the PATH as below.

  $ export PATH=/path/to/mi/cli/directory/bin:$PATH
  1. Log in to Micro Integrator using the following command.

    ./mi remote login
  2. Provide default credentials admin for both username and password.

  3. In order to view the APIs deployed, execute the following command.

    ./mi api show
Click here for instructions on deploying on WSO2 Enterprise Integrator 6
  1. You can copy the composite application to the /repository/deployment/server/carbonapps folder and start the server.

  2. WSO2 EI server starts and you can login to the Management Console https://localhost:9443/carbon/ URL. Provide login credentials. The default credentials will be admin/admin.

  3. You can see that the API is deployed under the API section.

Testing

Invoke the API as shown below using the curl command. Curl Application can be downloaded from here.

  1. Create a new Account object in Salesforce.

Sample request

```
 curl -v POST -d '<Name>Engineers</Name>' "http://172.17.0.1:8290/salesforce/createRecords" -H "Content-Type:text/xml"    
```

Expected Response

 ```xml
 <?xml version='1.0' encoding='utf-8'?>
 <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="urn:partner.soap.sforce.com">
     <soapenv:Header>
         <LimitInfoHeader>
             <limitInfo>
                 <current>55</current>
                 <limit>15000</limit>
                 <type>API REQUESTS</type>
             </limitInfo>
         </LimitInfoHeader>
     </soapenv:Header>
     <soapenv:Body>
         <createResponse>
             <result>
                 <id>0012x00000Am4kXAAR</id>
                 <success>true</success>
             </result>
         </createResponse>
     </soapenv:Body>
 </soapenv:Envelope>
 ```
  1. Retrieve the Account Names in all the existing accounts in Salesforce.

Sample request

 curl -v POST -d '<queryString>select id,name from Account</queryString>' "http://172.17.0.1:8290/salesforce/queryRecords" -H "Content-Type:text/xml"    
Expected Response

You will get a set of account names and the respective IDs as the output.

What's Next

Top