Salesforce Connection

Overview

Salesforce Connection Manager is SSIS Connection Manager for establishing Salesforce connections. Use the API to build components based on Salesforce Connection Manager.

Setup

Use the Salesforce Connection Manager dialog to specify properties for connecting to Salesforce service.

Server Options

User name

Specify user name in email-like format.

Password

Specify password to access Salesforce service.

Time-out (secs)

Specify the number of seconds before timing out session connect. The default value of this property is 60 seconds.

RetainSameConnection

Specify if all clients should use the same connection. This property has the options listed in the following table.

Value Description
True All clients use same connection (default).
False Every client use different connection.

Note: This parameter is not visible in the connection manager dialog.

OrganizationId (1.6 SR-3)

Specify the ID of the organization against which you will authenticate Self-Service users.

Note: This parameter is not visible in the connection manager dialog.

PortalId (1.6 SR-3)

Specify the ID of the portal for this organization.

Note: This parameter is not visible in the connection manager dialog.

Test Connection

Confirm connection manager configuration by clicking Test Connection.

Advanced Options (1.4 SR-1)

Server URL (1.4 SR-1)

Specify Salesforce service URL. This property should be explicitly specified when doing sandbox testing. Sample URLs:

Proxy Options (1.4 SR-3)

Host (1.4 SR-3)

Specify the name or IP address of the proxy server. If not specified, proxy server is not used.

Port (1.4 SR-3)

Specify the port number on the proxy server to use for the connection.

User name (1.4 SR-3)

Specify user name to access the proxy server.

Password (1.4 SR-3)

Specify password to access the proxy server.

How to trace the web services calls in use?

You can use the regular .NET network tracing facilities to trace the web services calls. Follow these steps to enable tracing:

  1. Go to DTS\Binn folder and open DtsDebugHost.exe.config file in your favorite text editor.
  2. Include following settings inside configuration element:
        <system.diagnostics>
          <trace autoflush="true" />
          <sources>
            <source name="System.Net" maxdatasize="1024" tracemode="protocolonly">
              <listeners>
                <add name="MyTraceFile" />
              </listeners>
            </source>
          </sources>
          <sharedListeners>
            <add
              name="MyTraceFile"
              type="System.Diagnostics.TextWriterTraceListener"
              initializeData="c:\System.Net.trace.log" />
          </sharedListeners>
          <switches>
            <add name="System.Net" value="Verbose" />
          </switches>
        </system.diagnostics>
    

initializeData attribute controls where the trace log file is saved. Now when you execute a package inside Visual Studio, "c:\System.Net.trace.log" file will contain the web services tracing information. If you want to trace when you execute packages outside Visual Studio, include the settings above in DTExec.exe.config configuration file.

Make sure you comment or remove the tracing settings after you finish testing. Otherwise this may slow down your package execution speed considerably.