Tag Archives: dell boomi

Tip of the Week – Dell Boomi Connector Design

Looking at developing a Dell Boomi Connector?  here’s our tips to get you started:

  1. Understand what type of Web Services API the app is using. For example: REST or SOAP, etc. What about the supported document format? XML or JSON?
  2. Most applications have an authentication layer. Some authenticate using BasicAuth, some  use an API Key in the HTTP Request Header, some use OATH. This information should ideally be captured in the Connector Connection. It is highly recommended to encode any password related field for security best practice.
  3. Decide the supported operations. Does the API support QUERY? UPDATE? CREATE?
  4. The browser and schema generation. A Boomi Connector is capable of generating the schema each operation supports. Some applications provide a metadata API that you can connect to and describe the schema on the fly. Some  use a fixed schema.
  5. The final step is to design the Operation. When your Connector receives a response from the API, how do you want to process it? Serve it raw as is or does it need any further manipulation. Error handling should also be considered here.

Boomi Integration Tip: Working with dynamic and static database parameters

In boomi if you want to run an INSERT/UPDATE/QUERY operation in a connector shape you probably will need to use a ‘?’ as a dynamic parameter. In figure 1 we can see that the number of ‘?’ is exactly the same as the number of the fields (highlighted in blue).  In this situation the SQL statetment will work without any error.

If we need to use both dynamic and static parameters at the same time, and we use the same technique as above, with a static parameter, we get the following:

This will result in the error “First document failure: Invalid column index” :

The solution is to remove the static ‘CREATED_TAD’ field from the parameter but leave it in the SQL statement:


New Boomi feature – Document cache

Today Dell Boomi released a great new feature – Document Cache. 

You can configure a cache on any profile (say a Flat File of all your accounts). You can read in that file in one branch and map it to the cache, and set a key, say account ID.

If for example, you have a process that reads an order from a database or an app such as salesforce.com, you can, in the map step where you are mapping that, add the Cached Data, choose which field in the Order profile to link to the Key in the Cache (Account ID) and it will bring in that profile into the source map.  You can then map directly from any of the Order, or matched Account profiles to your target.


WDCi becomes one of the first certified Dell Boomi partners

Dell Boomi has just launched a certification program for their partners.  If you’re asking yourself is this an attempt at shameless self promotion, you’re right, WDCi is one of the first certified partners.  Boomi announced the list of initial certified partners in their Spring Product Release announcement.

Details on the certification program can be found here: http://help.boomi.com/display/BOD/AtomSphere+Certification+Program.