Integration

Dell Boomi Platform Overview

Dell Boomi Platform Overview

In the first blog post „Dell Boomi first steps“ we learned the general basics of Boomi. In this post I will give an overview of the platform and components to make a deep dive in the next posts.

AtomSphere Platform Overview

Development and Monitoring

The modules are already explained in the previous blog post about first steps. The usage of Boomi doesn’t require a deep knowledge about software engineering (however I think it’s extremely helpful to know more about that topic). Boomi provides a web-based development environment. The IDE is hosted in the cloud only. So there isn’t extra effort needed by the developer on their local machine. The developer can start building integrations right after successful logged in the IDE (https://platform.boomi.com/). Also important to know that Boomi doesn’t require the setup of a version control system or build server. Everything is in place and integrated in the web-based IDE.

Web-based IDE

Furthermore monitoring and tracing of process executions are also completely done in web-based dashboards. There are no additional infrastructure required for that purpose. The monitoring and tracing features are accessible in the same way as the development features.

Monitor Executions

So at the end starting a development of a new integration is a task that only needs some minutes and no additional infrastructure.

Runtime

The Boomi runtime uses Java as general infrastructure to run integrations. However there exists several deployment options which can be adopted to your special needs and requirements:

  1. Atom
    Atom is the smallest runtime unit. It includes a single Java Runtime and anything else to run an integration and also to communicate with the Boomi platform. The Atom exchanges runtime (e.g. heartbeat) and configuration data with the Boomi platform (monitoring). Data processed by an integration isn’t transferred to the Boomi platform!
  2. Molecule
    A Molecule is a cluster configuration of Atoms and contains of several nodes which can be distributed to multiple machines. It enables high availability when executing mission-critical integrations. All other aspects of an Atom applies to a Molecule also. A Molecule defines a head node which is responsible to exchange runtime and configuration data with the Boomi platform.
  3. Atom Cloud
    Boomi provides a Molecule infrastructure in their data center’s which can also run integrations. This runtime option has some characteristics which can be found in detail here. The current status of the environment can be seen using the url https://status.boomi.com/

The interesting part is that the runtime options can be mixed depending on your needs. You can run for example some of the integrations in the Atom Cloud whereas highly secure data can be integrated running on an Atom in your own data center. Management of the entire infrastructure will be done in one place on https://platform.boomi.com. No data will be transferred to the Boomi platform.

In the next blogpost I will show how to setup and use a local Atom. The Atom runs in a virtual machine on my local desktop machine.

References