...

This section deals with the way in which the dataloader accesses SalesForce, and the creation of a new authorisation token.

Create a User in SalesForce with Access to the Dataloader

Use the normal Salesforce administration procedures to achieve this. You will need the following from the user account to proceed from here:

• SalesForce User Login Name
• Password
• SalesForce Security Token

Update the jtel Dataloader to use the new credentials

This is a complicated process, requiring access to the command line of the system.

1. Login to the telephony / application server of your system, as the local administrator.

2. Map a drive to the location of the dataloader, and change to the directory.

Change (CustomerName) to the name of the customer directory. 

net use z: \\acd-lb\shared
z:
cd \(CustomerName)\SalesForce\jteldaloader-0.3

3. Create a secret key

Issue the following command. SecretKeyString can be changed to anything you desire.

java -cp dataloader-40.0.0-uber.jar com.salesforce.dataloader.security.EncryptionUtil -g SecretKeyString

 4. Note the output

The output from the command above is saved to a file "key.txt" saved in the current directory. 

5. Create a token

Copy the following command, and replace <password> with the password of the account, which should be used to access SalesForce, and <token> with the security token from the user account (obtained from SalesForce before this procedure was started).

...

4ff73dc5ea5350cb92be28ad021c633dc62fa0cf735d00c06c4ec0a63c1eecd28c059b80df1541

6. Modify process-conf.xml 

The token from the step above, and the user name, are now changed in the file config\process-conf.xml.

...

...
                <entry key="sfdc.username" value="test.user@example.com"/>
                <entry key="sfdc.password" value="7687a73934af24359a27577534b81c5beed32fa0cf735d00c06c4ec0a63c1eecd28c059b80df1541"/>
...

7. Done

That's it. The next time the dataloader process runs, it will use the new account data.

...