When integrating any non native application (JAVA or NET or ..) with salesforce, you need to have the salesforce API library in place that can be referred/used as a referenced library in project being developed. This library is the the one that acts as face to salesforce i.e., intermediary between your application and salesforce.
Simple yet important step of such type of integration is to generate stub code (jar file) from wsdl (salesforce enterprise or partner wsdl) and though such a simple step, we (at least I) always forget (or I should say cant recall easily) the step on how to generate same.
Below are three easy steps to generate stub code (jar) from a wsdl:
- Download Enterprise (Partner) WSDL by navigating to Setup -> API – > Enterprise (Partner) WSDL (right click and save file as “abc.wsdl”, ensure extension “.wsdl” is there).
- Download Force.com Web Service Connector (WSC) . The Force.com Web Service Connector (WSC) is a high performing web service client stack implemented using a streaming parser. WSC also makes it much easier to use the Force.com API (Web Services/SOAP or Asynchronous/REST API). You can download a pre-built WSC jar file from: http://code.google.com/p/sfdc-wsc/downloads/list
Now generate Stub Code from a WSDL. Run wsdlc on the WSDL you have downloaded:
java -classpath wsc-xx.jar com.sforce.ws.tools.wsdlc *wsdl* *jar.file*
java -jar wsc-23.jar *wsdl* *jar.file*
wsdl is the name of the WSDL file
jar.file is the name of the output jar file that wsdlc generates
You can include an optional argument: -Dpackage-prefix=myprefix
- Now write your client application. Add wsc-xx-min.jar and jar.file (generated by wsdlc) to your classpath, then compile and run your client application.
With this you are all set with stub code / library and ready to make soap API calls to Salesforce.
Author : Chirag Mehta & Angelica Buffa
Using FTP servers to store and share files is very common now at days. Most language programs let you develop FTP clients and consume their services.
With Apex, there are three possible approaches to resolve the integration with this kind of file servers:
I – Data Loader CLI – Windows approach.
- Download Salesforce Data Loader Command Line Interface (Read more at http://wiki.developerforce.com/index.php/Using_Data_Loader_from_the_command_line)
- Write a Widows Batch file (.bat file)
- First command in the batch file will be connect to FTP server (ms-dos command ‘ftp’) and then get the necessary files from ftp server to the local folder.
- Second set of commands execute the Data Loader CLI jar and loads step3 retrieved file into Salesforce.
- To automate the execution of the batch, we can schedule the bat file execution using scheduled task feature of Windows operating system.
II – Java Web Service
- Write a Java FTP client, expose it as a Web Service
- Consume above WS into your Salesforce Org using Apex “Browse WSDL” functionality
III – Http Request
- Create a Http Request to the FTP server
- Handle the response using either of HttpRequest and HttpResponse Apex Class
- Ps: The problem that you can face is the size of the files. Please remember that HTTP Request size are currently limited to 100Kb of data, so larger exports would fail unless a mechanism was created to utilize multi-part transmissions.
Apache Axis2 Eclipse Plugins allow Web service developers to easily and speedily expose the available plain old Java applications as Web services.
wso2.org lists a tutorial by Lahiru Sandakith which consists of two parts, with two examples that walk you through developing and deploying a sample Web service using the Top-down (Contract First) and Bottom-up (Code First) approach using Axis2 Eclipse Plugins.
The tutorial is written for Eclipse SDK v3.2 and Axis2 Eclipse Plugin v1.3.
Read the tutorial at http://wso2.org/library/1719