Integration Friday Episode 1: Boomi and WSDL

August 15, 2014 Appirio

By Matt Ainsworth and Anna Knyazyan

trawka2

Integration is the key to success for many cloud implementations. Getting a handle on data requires a team with clear thinking and technical skills. We challenged our best integration consultants to share some of their insights on this important will be publishing these in regular intervals.

This week Appirio consultant’s Matt Ainsworth and Anna Knyazyan share some of their insights into the technology they use to help our clients handle their data.

Using Boomi to Cleanse Large Data Sets By Matt Ainsworth

Boomi is a great tool to use to transfer data from one platform to another, but another great use of the tool is to cleanse and condition data. Using the MAPPING feature, you can trim whitespace characters, set default values, make calls to other fields, redirect to other files or even split records by a value on a massive scale.

Many times when I have to cleanse data, I go to excel.  Unfortunately, when you start working in records that are in the millions, excel cannot handle the load. At that point you start to notice bugs and the functionality doesn’t work quite as well.  With Boomi, you can easily handle millions of records, and just let it work in the background while you relax with a hot cup of tea.

Important Considerations in Implementing Web Service callouts from Salesforce By Anna Knyazyan

As you may know, Salesforce can consume a WSDL file by converting it to Apex classes for each object, with the API method exposed in the WSDL file.

WSDL files are converted into APEX classes with no issues if they are simple and have one level of reference.  The nested and complex WSDL files can be manually modified to simplify schema references and to have only APIs that are used in callouts.

Test coverage is important for all apex classes including the ones generated from WSDL.  By default, test methods do not support web service callouts.  In order to have adequate code coverage, Apex provides a built-in WebServiceMock interface and Test.setMock method that can be used to receive fake responses in a test method.

One more important consideration that is important for production code and it’s a best practice to use custom settings for the following items:

·      Endpoint URL

·      Service specific timeouts

·      SOAP headers

·      HTTP Headers

Specifying these parameters in custom settings simplifies the process of re-connecting with different endpoints, and allows changes to be done in production without redeploying the code.

Previous Article
Kicking Off our $500K Learn Swift Series
Kicking Off our $500K Learn Swift Series

We are launching a series to help you learn Swift, Apple’s new development language. We are extremely optim...

Next Article
The Dashboard Health Check with Analytics API
The Dashboard Health Check with Analytics API

Contributed by : Asset Library Team Salesforce Dashboards can now be queried using Analytics API. Querying ...