4 - Deploy

After you have built a Process, there are two quick steps to begin executing it:

1. Deploy an Atom to your server.
2. Deploy the Process to that Atom.

Once the Atom has been deployed and one or more Processes have been deployed to that Atom, you will be able to execute and manage the Processes from the Manage Tab. Note: Processes do NOT need to be deployed to an Atom to execute them in Test Mode.

By default, once you deploy a Process to an Atom, any changes made to that Process or any of its components are immediately communicated to the Atom upon saving. You do not have to deploy another Atom or do anything to make the changes effective in your Process. This is sufficient for most integration scenarios. However, if you want greater control over when Process changes are "released" to the Atom(s), you can disable the auto-deploy functionality and deploy Process changes manually. This allows a "production" Process to continue running as normal while you make changes for troubleshooting or enhancements. You can toggle the auto-deploy setting for your account from the Account Tab. See Deploying Processing for more information on managing Process deployments manually.

One Atom vs. Multiple Atoms

If your account has been set up to only allow for one Atom, which means your processes will only run in one location, you will need to deploy all of your processes to that Atom in order to run them. If your account allows for multiple Atoms to be deployed, you will be able to select which Atoms will execute each process. This design will allow the same process to execute in multiple locations.

What's Inside an Atom?

A Boomi On Demand Atom is a lightweight, dynamic runtime engine. An Atom is just a runtime engine until you deploy your processes to your Atom. Once your processes have been deployed to your Atom, the Atom will contain all the components required to execute your integration processes from end to end including connectors, transformation rules, decision handling, and processing logic.

Local vs. Hosted Deployment

An Atom can be deployed one of two ways: Locally (to a machine in your network) or Hosted (to the Boomi data center). Which option to choose depends upon your specific integration scenario.

Local - If your integration scenario includes connecting to resources or applications behind your firewall, such as a database, file system directory, or other on-premise applications, you will have to deploy the Atom locally. The Atom must be installed on a machine that has access to all the required resources. This is how the on-premise to SaaS integration problem is solved!

Hosted - if your integration scenario only includes connecting to resources or applications accessible via the Internet, such as web applications and FTP sites, you can choose to deploy the Atom to the Boomi Data Center. The Hosted option provides a "zero-footprint" integration solution, with no software or hardware to be installed.

No matter how your Atoms are deployed, their can all be monitored from the same console on the Manage Tab.