After recently finishing my first small business focused Boomi integration here at SFCG, here are the top five things that are totally cool about the Boomi Atomsphere Platform:
Unique Data Processing: Boomi processes a single record at a time. This sounds similar to the way the current integration products work but it’s actually not quite the same. Most tools process a whole file (with multiple records) thru each step. Boomi’s methodology runs the record (or row of data), which is a basic unit of work, thru the process up and until you decide to combine it into a multi-record document. One reason a development engineer might find this interesting is that the developer designs a process to handle a single unit of work. Boomi handles the looping. Totally Cool!!!
Branching Processes: Branching allows you to start over with the source data to accomplish something else in your process. Only one source read is required to process a record thru multiple branches. Above we process all the source records into an Account entity, and then we start over with the original source data and process it into Contacts.
Storing Results for Error Handling: Result info easily captured. We can capture results and store them into a Dynamic Process Property.
And the TOP COOLNESS Reason. Every Integration methodology concept we configured into this integration helps builds a template for starting on the next. Some of the artifacts will even be re-usable.
Another cool feature is using the Email feature to email of process results is fairly simple and straightforward. I have written a blog article about this:
The last cool feature I have actually written about is the Flow Control feature.
Boomi handles many integration tasks at a high level without the need for scripting pretty much at all. However, there comes a time when you just need to alter/manipulate/examine the document by groups, and most of the Step components generally cannot do that. However, you can use the Flow Control step.
The Flow Control Step is one component that is totally awesome. For example when using the process batch web-services in Oracle CX – Sales Cloud you can group the XML payloads in batches of 500. In your Boomi data Integrator process you can easily handle this issue with the Flow Control Step.
This step takes individual documents flowing into this step, and batches them in whatever is configured as a Batch parameter. It is typically followed by a combined step.
Say Quickbooks as a source has 1800 records in their database. Through web-services we are provided with 1800 XML documents, one at a time. These documents flow thru the Flow Control Step, and only 500 (or less) at a time are processed. Then the next step combines the 500 that flowed into the step and creates a single document with combined information of the 500 records.
This would happen for document 501 thru 1000, and then 1001 thru 1500, and then 1501, thru 1800.