Versions Compared

Old Version 15

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
maxLevel3
typeflat

...

Importing the Salesforce Certificate

To use the Salesforce connector, add the  <salesforce.init>  element in your configuration before carrying out any other Salesforce operations.

Before you start configuring the Salesforce connector, make sure to import the Salesforce certificate to your ESB client keystore.

Follow the steps below to import the Salesforce certificate into the ESB client keystore:

  1. Log in to your Salesforce account in your browser (e.g., https://login.salesforce.com), and click the lock on the address bar to view the certificate.

  2. Export the certificate to the file system.

  3. Import the certificate into the ESB client keystore using the Management Console or by using the following command:

    Code Block
    keytool -importcert -file <certificate file> -keystore <ESB>/repository/resources/security/client-truststore.jks -alias "Salesforce"

  4. Restart the server and deploy the following Salesforce configuration:

...

Info
  • Users can obtain the security token by changing the password or resetting the security token using the Salesforce user interface. The new security token will be sent to the email address recorded in the user's Salesforce record.
  • The response of this operation is attached to the message body and is used for subsequent Salesforce operations.
  • The session ID is saved into the property salesforce.sessionId, and the server URL is saved into salesforce.serviceUrl. If the given login details are invalid, the specified fault sequence will be triggered.
Tip

Secure Vault is supported for encrypting passwords. See, Working with Passwords on integrating and using Secure Vault.

Re-using Salesforce configurations

You can save the Salesforce connection configuration as a local entry and then easily reference it with the configKey attribute in your operations. For example, if you saved the above <salesforce.init> entry as a local entry named MySFConfig, you could reference it from an operation like getUserInfo as follows:

 

Code Block
<salesforce.getUserInformation configKey="MySFConfig"/>

 

The Salesforce connector operation examples use this convention to show how to specify the connection configuration for that operation. In all cases, the configKey attribute is optional if the connection to Salesforce has already been established and is required only if you need to specify a different connection from the current connection.

...