Assuming you have successfully installed the Salesforce Suite module on Drupal (as per my previous post Integrating Salesforce.com and Drupal) and you have a Salesforce account (Developer or Enterprise), then the next logical step is to connect the two together.
Luckily doing so is fairly simple, and largely done through the Drupal front end.
First, in your Drupal Admin suite, you need to navigate to the
Salesforce settings page (admin/config/salesforce/).
This is where you will provide an account username and password, as
well as a generated API security token. Security tokens can be generated
in Salesforce (and e-mailed to the registered address) through: Your name > Setup > My Personal Information > Reset My Security Token.
you must (optionally) supply the module with your Salesforce WSDL definition. This
contains (among other things) the object structure of your Salesforce
implementation, and the connection end point URL. You can obtain your
WSDL by clicking through and selecting the relevant link to download the Enterprise WSDL. If you don't do this, you will only have access to the standard Salesforce.com objects, and you may also experience trouble connecting to Developer or Sandbox accounts, by virtue of their different EndPoint URLs for login.
The module provides a couple of mechanisms for uploading your WSDL to Drupal, via the WSDL tab in the module configuration (admin/config/salesforce/wsdl).
You can either directly upload the file, or point the module to the
system folder containing the XML file. I did find, during development at
this point, that if I needed to update my WSDL definition, I had to go
through a fairly trial-and-error combination of clearing caches and
reloading pages to get the
new details properly installed.
Once the WSDL definition
is set though, you are basically ready to go! All you need to do now is
click through to the Object Setup tab (admin/config/salesforce/object)
to choose the objects you wish to synchronise with Salesforce.com,
and then define the mappings between the fields in Salesforce.com and
the fields in your Drupal installation. I will cover the complexities of
field mappings in a later post, but for now, you should at least have an operational connection between Salesforce.com and Drupal.