By Juergenkress-Oracle on Mar 09, 2014
Some time ago I had a request to connect a file with salesforce.com. The tool of choice was Oracle Service Bus, first without any special adapter. So I had to investigate into the salesforce.com way of using web services and how I can approach this challenge.
First of all we need an account with salesforce.com. With this account we can access the Web Services API through Profile -> Setup -> API. Here we need to download the Enterprise WSDL.
You can find more details to this here salesforce.com Documentation.
Now we import the WSDL into the Oracle Service Bus. As written in the docs Before invoking any other calls, a client application must first invoke the login() call to establish a session with the login server, set the returned server URL as the target server for subsequent API requests, and set the returned session ID in the SOAP header to provide server authorization for subsequent API requests.
This means for Oracle Service Bus
that we have to use an additional "Service Callout" before calling any
other operation. With this in mind, it might be a good idea to store the
session information for subsequent calls. As the Oracle Service Bus is
stateless, this job could be achieved by using a java callout with a
class variable storing the SF session ID. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.