2.1 - Core Concepts

There are several important terms and concepts to understand when working with Boomi AtomSphere:

Atom	Atoms are the lightweight runtime engines that contain Process configuration information and actually do the work. Atoms can be downloaded and installed to a machine behind your firewall to access local resources such as on-premise applications or databases, or deployed to the Boomi data center if only Web accessible applications or data sources need to be integrated. You will typically deploy multiple integration Processes to a single Atom. (More...)
Component	Components are the reusable configuration objects used in Processes. Components are reusable and include Processes, Profiles, Maps, Connections, Operations, Certificates, and Map Functions. They are listed in the Component Explorer and can be created once and referenced by Process Steps across multiple Processes. For example, the same Database Connection representing a customer database can be referenced in every Process that needs to communicate with that database. When you modify a Component, those changes are reflected wherever the Component is referenced. So if that database should ever move to a different machine, you can simply update the single Database Connection Component once and the new settings would be in effect everywhere it is used. (More...)
Connector	Connectors get data into and send data out of processes. Connectors abstract the technical details of communicating with various applications, data sources, and communication protocols. They are actually comprised of two Components, a Connection and an Operation. The Connection represents the "endpoint" and contains the physical connection details, such as an FTP or database host, a web services URL, and/or login credentials. The Operation represents a specific action to perform against that Connection, such as a database SELECT query, an FTP PUT, or a specific web service call. You can think of the Connection as the "where" and the Operation as the "how". For example, when extracting customer records from Salesforce, the Connection represents your Salesforce organization account user name and password and the Operation represents the "query customer" action. (More...)
Document	A Document is a set of data that goes through a Process. A Document can be a single record, a group of records, an EDI transaction, or an entire file. Documents often represent individual files read in, however it is important to understand that a single Document may contain multiple records. In these cases it is often useful to split a Document into multiple Documents (using the Split action within the Data Process step), each containing a single record for processing. For example, a large daily batch file of purchase orders could be split by order number into multiple Documents so each purchase order can be processed and tracked independently.
Execution	An Execution is the results of running a Process. When viewing previous Executions in the Manage Tab, you can view the data passed into and out of the Process, detailed logs, and error messages. In production environments, Processes are typically scheduled to execute at regular intervals but can be run manually ad hoc as well. (More...)
Map	Maps allow data to be transformed from one format to another--or specifically, from one Profile to another. Fields or elements are mapped by dragging-and-dropping a source element to a destination element. Map Functions can be used to perform simple or complex field-level manipulations as values are mapped. (More...)
Process	Processes represent a single type of data to integrate between two or more systems. They are comprised of a series of steps that specify the business logic and transformation requirements. They are the central Components in Boomi AtomSphere. Process steps transform, route, and otherwise manipulate data to attain the desired end result. Every Process begins with a Start shape that gets data from some source and usually ends with one or more Connectors to send the data to the destination(s). (More...)
Profile	Profiles define the structure or layout of the data to be processed. They are used when reading from or writing to a given format. There are three categories of Profiles: Flat File - Flat Files are common, simple formats that typically contain one record per line, like a comma separated value (CSV) file. Each record contains a number of fields or elements that are either delimited or data positioned (fixed width). Flat File Profiles can represent simple structures with a single record type (e.g. CSV file) to moderately complex structures with multiple record types to accommodate parent-child relationships or other repeating record types within the same file (e.g. header and detail records). (More...) Database - When used for reading, the Database Profile represents the fields in the result set of a SELECT statement. When used for writing, the profile represents the values used in an UPDATE, INSERT, or DELETE statement. Database Profiles can also contain elements to be used as parameters in dynamic statements. (More...) XML - XML is a common hierarchical format used in much of the Internet communication today characterized by the use of tags that describe data elements. Tags can be nested within one another to establish parent-child relationships. XML Profiles are used by web services and the majority of Boomi application connectors. (More...)
Step	Process Steps are the shapes linked together to form the business logic for a Process. Steps can perform execution tasks like document splitting and data transformation or logic tasks like decision and routing. Each step has its own configuration settings. Steps often reference Components such as Profiles, Connections, Operations, and Maps. (More...)