Tallan's Technology Blog

Tallan's Top Technologists Share Their Thoughts on Today's Technology Challenges

30 minutes to iPAAS with Dell Boomi

Cesar Cordero

Dell Boomi Basics

Tallan has recently started providing 30 minute Lunch and Learn type of webinar recipes for basic iPaaS integration solutions using Dell Boomi’s Atomsphere development platform.

For this quick demonstration we’ve broken the main points into the following bullet points:
• Creating a free account
• Logging in to the Dell Boomi environment
• Creating Processes
• Connector Review
• Process features
• Understanding Profiles
• Building Maps
• Test Mode Overview

 

 

Let’s start by starting a free trial from Dell Boomi’s home page:

 

boomi1

 

You will fill out a very short web form and then receive an email confirmation with your credentials, etc.

Once logged in you should see the AtomSphere component explorer screen:

 

boomi2

 

Process Overview

boomi3

 

 

 

 

 

 

 

 

 

 

Boomi Process is the core integration component and typically represents a discrete workflow moving a given type of record from one application/system to another. They are what is built, deployed and managed and contain all steps and components in a full integration flow.

There are several ways to create a new Dell Boomi Process:

1. From the create new:

boomi4CreateNew

 

 

 

 

 

 

 

 

This will auto-open a new build tab with the ability to choose some runtime configuration options:

BoomiProcessOptions1

 

BoomiProcessOptions2

 

2.Directly into you project/solution folder:

BoomiNewComponent1

 

Provide a name for the process and clicking create:

BoomiProcessCreate1

 

boomi7

In addition from the welcome tab we can review the help file for process creation:

boomi8

Every new process contains a start sheet by default and is the main entry point for one to many documents:

 

BoomiProcessOptions3

 

Documents Overview

boomiDocumentOverview

 

 

 

 

 

 

 

 

A Dell Boomi document is what powers the execution and flows thru the process!

Documents are presented in a number of different Formats (data set organizational units or record set for a given instance of an execution of a process or integration interface)

boomidocumentformat

 

 

 

 

 

 

 

 

Records-flat file and database instances

Transactions for xml and EDI

File instances for communications between systems that does not require structure analysis (email attachments, pdf, etc.)

Empty document to serve as a trigger for other processes.

Connector

boomiconnector1

 

 

 

 

 

 

 

boomiconnector2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

boomiconnector2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

boomiConnectorTypes

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Dell Boomi’s AtomSphere contains a huge library of connectors that provide access to an infinite number of software systems and data standards.

The standard connector types are mostly used for file based integrations. Where you need to get or send data to and from a common data repository such as a network share or on-premise database. These connectors support connectivity over communication protocols. So if you need to send or retrieve document to say email, soap or http client, etc you can use our pre-packed connectors to achieve your custom integration goals

Application Connectors refer to the packaged integration services where there is a branded atomsphere connector built thru the connector SDK.

Here is the list of application connectors which are predominantly API based  you can also open a start shape and review the connector drop down list:

boomiConnectorList

Process Features

Any new process starts as a blank canvas for configuring your business work flow. In order to maximize screen real estate here are the major characteristics:

  • Hide the component explorer or side bar
  • Click on full screen mode up right corner
  • Browser f11 button to enter full screen mode
  • Execution and logic tabs on the far left are your pallet
  • The goal is to drag and drop each new step on to the canvas to build your work flow from left to right
  • You can hover over each step to either configure or remove it from your work flow
  • Note that any referenced components will only be removed and not completely deleted from your account.
  • Also you can click on any white space and drag to create a box around one to many process steps. This will allow you to either move or remove objects from the canvas in bulk.
  • In order for your steps to execute sequentially, you need to click on the end of an arrow and connect the object to the next step so it turns green meaning it’s connected. Objects must be connected or they will be ignored. If an object is not linked it will be ignored. It is a common practice to disconnect some objects in order to unit test particular components and parts of a given process or a certain series of steps. You can also unlink steps…
  • There is a navigation view at the bottom right for more complex process views
  • And note the Add Note button on the top left hand side for adding comments to more complex process flows

Example of a more complex process flow with quick links and the navigation view

boomiComplexProcessFlow

Dell Boomi Profile

BoomiProfile

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

In order to structure a document that interacts with a connector and list out its individual fields we need to understand the reusable profile component

Profile Components – wrapper for filetypes with column/data type definition.

Profiles describe the layout or format of the various documents read into or sent out of AtomSphere. To describe a flat file, for example, the profile would contain field names, delimiters or column positions, data types, min/max lengths, etc.

Profiles are most notably used in maps. For example, to map an XML document to a flat file, you would need to set up one profile that matches the layout of the XML file, and another profile that matches the flat file. Additionally, profiles are used in various places throughout the application whenever the document data must be inspected. Individual profile elements are commonly referenced as parameters for the Decision, Cleanse, Program Command, Message, Route, Document Properties and Exception steps.

Here are the profile types used in AtomSphere.

Name Description
Database Database profiles are separated into two types: Read and Write. A Read database profile can execute SELECT statements or stored procedures against a target database. A Write database profile can execute an INSERT, UPDATE, DELETE or stored procedure against a database.
EDI An EDI profile describes a delimited or positional file that meets ASC X12, HL7, EDIFACT or User Defined standards.
Flat File A flat file profile describes a file that contains either delimited or positional data. An example of a flat file is a comma separated file (CSV).
XML An XML profile describes a file that meets the W3C Standard for eXtensible Markup Language.
JSON A JSON (JavaScript Object Notation) profile describes a file that represents simple data structures and associative arrays. JSON files are based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition – December 1999.

Related Concepts

Related References

Each document type available has a dedicated profile type.

You can create a profile from the component explorer:

BoomiCreateProfile

It is common to configure the base options first on the second tab defining data standards or global file settings and there is also an import wizard associated with each profile which will help auto-list all of the elements.

You can click on import to access tables, files, schemas. Some connectors will auto build a profile for you when configuring the connector operation.

Within the data element view the main tab contains setting unique to each profile type:

boomiProfileTypeSettings

Boomi Maps

Maps allow you to convert data from one layout or format to another. On the left side of a map is a source profile and on the right side is a destination profile. You can drag and drop fields from the source profile into the destination profile in order to indicate how the data should be moved. In addition, you can add functions to data maps, which allow complex conversion logic to be applied to the data as it is moved from source to destination.

boomiMap1

 

 

 

 

 

 

 

 

 

 

 

 

 

Another Map example below:

BoomiMap2

 

Map functions allow the developer to execute transformational logic within the Boomi Map;

boomiMapFunctions

Dell Boomi Suggest is another core feature for “linking fields” in a map.

boomiSuggest

// // Boomi Suggest takes the guesswork out of data mapping – The Dell Boomi Blog

We can also export maps to excel for documentation purposes and team sharing!!!

boomiexport

 

BoomiTestOvervioew

Obviously test mode is a critical feature during process development. It allows you to unit test the process changes purely within the build tab and it displays a real-time view of your steps along with data visibility and enhanced logging.

When choosing to run a test the latest version of your process will be saved you will then be prompted to select an atom.

boomiRunTest

Note that once testing is started the shapes will turn green or red based on success or failure as the Boomi process executes:

 

boomiTestRunGreen

boomiTestRun2

Process properties example tab for more detailed information

boomiProcessPropertyexamples

This menu also allows to retry previous test:

boomitest99

Once the process is closed you will then lose the ability to retry previous tests.

boomiTestClosed

 

 

 

 

 

 

boomiTestModeSupport

 

 

 

 

 

 

 

 

 

 

Anything exceeding this limits will throw an error in the process and in AtomSphere.

 

Please Visit us at Tallan.com for more information and let Tallan be your go-to Integration Partner!

 

No comments

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>