Invoke a SOAP API written in Salesforce using Axis

I had to consume an API written by someone else in Salesforce. I got the WSDL and the EndPoint.

Essentially what I had to do is to replace existing code I wrote a year ago to perform User Provisioning in Salesforce and rely on this API to perform that logic.

Now the interesting part is how to write my client, the obvious answer was to use WSDL2Java (Axis), because I don't want to write much code. And this is my final code: public void executeAccountUserProvisioningOnSalesforce(){ log.debug("Execute Account, Contact and User Provisioning (using single API on Salesforce) for "+this.kaptestRegistrationFields.getEmail()); com.sforce.soap.schemas._class.SSOprovisioningFunctionCall.Details details = null; this.login(); //Invoke Login //Create a sessionHeader object and set its sessioId property to sessionId SessionHeader sessionHeader = new SessionHeader(); sessionHeader.setSessionId(this.connection.getSessionHeader().getSessionId()); SSOprovisioningFunctionCallService service = new SSOprovisioningFunctionCallServiceLocator(); details = this.transformKaptestRegistrationFields(this.kaptestRegistrationFields); try { SSOprovisioningFunctionCallPortType port = service.getSSOprovisioningFunctionCall(new URL(provisioningEndPoint));//Use the service to get a stub which implements the SDI log.debug("Invoking "+provisioningEndPoint); ((Stub)port).setHeader("SessionHeader", "SessionHeader", sessionHeader); port.executeAccountUserProvisioning(details);//Invokes API } catch (Exception ex) { log.error("Error while invoking "+provisioningEndPoint+" for "+this.kaptestRegistrationFields.getEmail(),ex); } log.debug("Provisioning call to Salesforce completed for "+this.kaptestRegistrationFields.getEmail()); } .... private Boolean login() { Boolean success = false; try { ConnectorConfig config = new ConnectorConfig(); config.setUsername(username); config.setPassword(password); log.debug("AuthEndPoint: " + authEndPoint); config.setAuthEndpoint(authEndPoint); connection = new EnterpriseConnection(config); // Set the SOAP header to roll back the create unless // all contacts are successfully created. connection.setAllOrNoneHeader(true); printUserInfo(config); success = true; } catch (ConnectionException ce) { log.error("Error while executing login",ce); }catch (Exception ex) { log.error("Other Error occurred while executing login",ex); } return success; } This is a simple Cooking recipe with the exception of these lines: this.login(); //Invoke Login ... //Create a sessionHeader object and set its sessioId property to sessionId SessionHeader sessionHeader = new SessionHeader(); sessionHeader.setSessionId(this.connection.getSessionHeader().getSessionId()); ... ((Stub)port).setHeader("SessionHeader", "SessionHeader", sessionHeader); Things to keep in mind (otherwise you'll get "INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session"):

1. Open a session in Salesforce (that's how get permission to invoke the API)
2. Populate SessionHeader object (with Salesforce sessionId)
3. Set the Header to your Port before making your call

WebServices with CXF - Configuration files III

Now I'll cover my Apache CXF configuration file

<?xml version="1.0" encoding="UTF-8" ?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:cxf="http://cxf.apache.org/core" xmlns:jaxws="http://cxf.apache.org/jaxws" xmlns:aop="http://www.springframework.org/schema/aop" xmlns:tx="http://www.springframework.org/schema/tx" xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd http://cxf.apache.org/core http://cxf.apache.org/schemas/core.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd"> <!-- =========================== Useful Imports ===========================--> <import resource="classpath:META-INF/cxf/cxf.xml" /> <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml" /> <import resource="classpath:META-INF/cxf/cxf-servlet.xml" /> <!-- =========================== Aegis data binding ===========================--> <bean id="AegisDatabindingBean" class="org.apache.cxf.aegis.databinding.AegisDatabinding" scope="prototype"/> <bean id="JaxWsServiceFactoryBean" class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean" scope="prototype"> <property name="dataBinding" ref="AegisDatabindingBean"/> <property name="serviceConfigurations"> <list> <bean class="org.apache.cxf.jaxws.support.JaxWsServiceConfiguration"/> <bean class="org.apache.cxf.aegis.databinding.AegisServiceConfiguration"/> <bean class="org.apache.cxf.service.factory.DefaultServiceConfiguration"/> </list> </property> </bean> <!-- =========================== Web Services ===========================--> <jaxws:endpoint id="libraryService" implementorClass="mx.com.mylibrary.core.business.service.impl.LibraryServiceImpl" implementor="#LibraryService" address="/LibraryService"> <jaxws:serviceFactory> <ref bean='JaxWsServiceFactoryBean' /> </jaxws:serviceFactory> </jaxws:endpoint> </beans>

As I said before this is not rocket science. It follows the same logic used in every Spring configuration file, everything is based on Beans tags

If you remember my serviceApplicationContext, I declared a Bean called LibraryService

<!--================== Business Objects/Service Objects =============--> <bean id="LibraryService" class="mx.com.mylibrary.core.business.service.impl.LibraryServiceImpl"/>

Well, we're going to make reference to this particular Bean on our CXF configuration file, so we can expose it (We already changed our Interface & Implementation using annotations)

Now if you analyze carefully my CXF configuration file, this section links my Spring Bean (Service) with my endpoint on CXF through implementor & implementorClass attributes, which basically link my Java Code (implementorClass) and my Spring Bean (implementor);
The only thing you must add is "#" character before Spring's Bean name: #LibraryService

<!-- =========================== Web Services ===========================--> <jaxws:endpoint id="libraryService" implementorClass="mx.com.mylibrary.core.business.service.impl.LibraryServiceImpl" implementor="#LibraryService" address="/LibraryService"> <jaxws:serviceFactory> <ref bean='JaxWsServiceFactoryBean' /> </jaxws:serviceFactory> </jaxws:endpoint>

Finally, I'm using another attribute called address to declare the address for this WebService, by declaring it as address="/LibraryService", this will be my URI for this WebService: http://localhost:8080/little-library-lite/services/LibraryService

Why /services/LibraryService?? I declared on my web.xml that URL Pattern.

In my next and last entry I'll test this WebService using JUnit, if you want to see the WSDL file for all your available WebServices, you can do it by going to http://localhost:8080/little-library-lite/services

There you'll see a list of available WebServices and by clicking them you'll see each one's WSDL