The Anatomy of Your Local Boomi Atom
The Dell Boomi local atom installation directory has within it a number of executables, jar files, logs and settings files, and this post is meant to help a newcomer be able to navigate their way around this collection of files. We plan on targeting a few select folders ( highlighted in the image below) for discussion, because these are the folders that have the files we most frequently need to touch.
This directory contains files that are used by the installer when first installing the atom to your computer, but besides that there are a couple of files that might be of interest to someone after installation is complete. The inst_jre file contains a single file path which points to the jre that was used during the installation process. The installer itself is a java application and therefore needs a jre to be installed on your machine in order to run. The next file that might be of even more interest to someone reading this post is the pref_jre file that contains a single file path to the jre that is being used by the local Atom when it is running. The version of the jre being used at runtime will match the version that is visible in Atomsphere through the web portal.
Also, make note that the uninstaller application is right there under the top level of the installation directory and to remove your local Atom its as easy as just double clicking that file and following the uninstall wizard.
This directory contains the executable files needed to run an atom on your machine. The atom can be run as a windows service using the atom.exe file or as a desktop application using the atomdesktop.exe. Each of these files has a corresponding vmoptions file that allows you to pass flags to your JVM when the atom is launched. This is one of the files that we have accessed the most since starting to work with Boomi. The JVM can be tuned in any number of ways such as altering the algorithm used by the garbage collector, increasing the maximum heap size, increasing the size of each threads stack, etc. So make note of this file as tuning your local atom is something that will likely come up in the future.
This directory contains the container.properties file which contains a few key value pairs after installation is complete and these are responsible for the configuration of your local atom. There are hoewever a large number of key value pairs available to a developer to alter the configuration of their local Atom and their names and uses are documented here
This directory contains all the jar files used by the Atom when it is running. It is these files as well as the jar files supplied by the jre that constitute what is accessible at run time on the class path. We have in the past needed to move jar files from the userlib directory (mentioned below) to this folder in order for them to be visible to our code executing inside of a Data Process Shape’s custom scripting file. Keep this trick in mind if the same issue comes up for you.
This directory is where a new log file is created each day, and this log file captures any execution that occurs on this local atom. These log files are worth looking through even when your Atom is functioning properly just to see how the system starts up.
This directory was only added to the discussion because we thought it was cool that ActiveMQ (which is like the JMS server implementation) is used to provide the Atom queue abstraction to Boomi developers. The directory is filled with the files used by KahaDB to provide persistence to the messages being passed around inside of the running Boomi application.
This directory contains all the resources needed for the Boomi processes to run. The directory is broken down into a folder for all the certificates, the components and for the processroutes. The contents of this directory can be useful when verifying that a deployment has been made successfully.
For local Atoms, you can add in your own jar files to the class path. This has made it possible for us to reference our own custom Groovy code that we developed outside of AtomSphere using any Java IDE of my choice. We were able to create a jar file and then place it into the /<atom_installation_directory>/userlib/script directory (after which restarting my Atom was required), and from then on reference this code from the custom scripting files of a Data Process shape. Another common use case that calls for adding a jar file to this directory is when we needed to use a newer JDBC driver then was provided out of the box by my Boomi installation. So to make some of the newest features of this updated JDBC driver available to me, we added the requisite jar file into the following directory /<atom_installation_directory>/userlib/database and added this driver to my database connector.
Dell Boomi AtomSphere
The Dell Boomi AtomSphere integration platform is a shared-everything, multi-tenant platform that supports cloud-to-cloud, SaaS-to-SaaS, cloud-to-on-premises, on-premises-to-on-premises and B2B integration. Boomi AtomSphere supports real-time integration and elastically scales to meet high-volume needs in mobile, batch (ETL) and EDI environments. Easily accessed via a browser, it delivers an impressive range of integration, master data management (MDM) and platform extension capabilities.
Tallan Integration Solutions for Dell Boomi
Tallan is a certified Dell Boomi Partner specializing in iPaaS platform integrations. We specialize in Integrations using EDI and Dell Boomi as the iPaaS platform of choice. Leverage Tallan’s vast integration experience for your AtomSphere platform needs. Our certified architects and developers provide the expertise, best practices, and guidance to deliver a successful integration solution.
We hope this guide will help you in your use of AtomSphere. If you have any questions or comments, or need assistance with any Integrations or development questions, please contact us at email@example.com.