The Salesforce Bulk API is optimized for loading large sets of data asynchronously by submitting batches of data that are processed in the background. It’s possible to use the Bulk API from the Data Loader using CSV files, however handling large CSV files and dealing with errors during loading can be quite daunting even for couple thousand records.
- sfdc:upsert-bulk service call to submit the records to be uploaded
- sfdc:batch-result service call to asynchronously check bulk upload completion
- basic exception handling that retries the completion check (since the connector throws an exception when the batch is not completed)
- processing the returned BatchResult object to match the results with each data record
SAP is one of the leading ERP(Enterprise Resource Planning) tool available in the market today. Customers would like to integrate enterprise (SAP) data with other systems in this changing world. It is a challenge to allow data synchronization between SAP and other systems with a robust integration system. To solve the integration problem, Mule provides a SAP JCo (Java Connector) for integrating SAP data with other tools or systems.
CXF helps to consume a web service when we don’t have the WSDL contract, but have the service class and data objects used to expose the web service.
In this blog I will explain how to consume web service with the CXF JAX-WS code client in Mule 3.4 when we have the service class. Demonstrated in this post is the service that was used to create the web service.
When we think of consuming a SOAP web service, most commonly we will have the WSDL Contract for the service that we are trying to consume. CXF framework enables us to consume a SOAP service very easily when we have the WSDL Contract. Also CXF provides simple APIs to build code first services, Maven plugins, JAX-WS support, Spring XML support and so forth. In this blog I would like to consume web service with CXF JAX-WS Client when we have the WSDL contract.
Web Application Description Language (WADL) is a machine-readable XML description of a REST webservice. WADL is platform and language independent. WADL is REST equivalent of SOAP’s WSDL. Each service is described by a set of resource elements. Each resource element has a set of param and method elements. Method elements has request and response elements which describe the request and response attributes of the service.
WADL is very useful in generating client code which can be used to call or consume a REST service. Also it is an easier way to document your REST API. WADL appeals to people coming from SOAP world where WSDL is used to generate client code.
CXF is a services framework which helps to build and develop web services using programming APIs like JAX-WS & JAX-RS. CXF supports a variety of web service standards including SOAP, WSDL, WS-Addressing, WS-Security, WS-Policy. For REST services CXF supports JAX-RS.
From time to time, I have wished I had an example of a particular technique I wanted to use in Mule ESB. Those wishes never seemed to come true. So some of the Confluex developers and I decided to make one, and begin creating a series of example projects – a Mule cookbook.
Our first example is the Imperial Manufacturing example. (See our quick guide for help using git with Mule Studio) It is a Mule 3.3 CE application that exposes a simple RESTful web service using the Jersey module. It validates requests using an XML schema, then calls a java SDK, and updates a database using JDBC.