Deployment is the means by which you prepare your processes and deployable components to run and operate in a test or production environment.
Boomi Deployment is similar to traditional software development concepts of building and releasing product. The deployment functionality performs several important functions:
- Controls the deployment of specific versions to different runtime environments as part of the development life cycle (for example, “stage” vs. “production”).
- Manages versioning of processes and other deployable components.
- Isolates the version of processes running in runtime environments from ongoing changes made in the Build tab.
- Provides full audit history for versioning and deployments.
After you configure and test processes and components in the Build tab, the next step is to deploy them to one or more environments. Deployed processes can accommodate full production-scale data volumes, batch processes can be scheduled for automated execution, and listener processes such as API Services and event-driven connectors are activated to receive incoming requests.
Deployable components
In addition to processes, the following types of components can also be packaged and deployed independently:
- API Proxy
- API Service
- Certificate (public X.509)
- Custom Library
- Flow Service
- Process Route
- Processing Group
Though an independent component may have been included in a process’ or another component’s configuration, they are stand-alone in nature and are not included during the packaging stage of deployment. Due to this, they must be packaged and deployed independently, and as a result, provide you more granular control over deployment versioning.
How deployment works
There are two steps to deployment:
- Create and manage point-in-time versions of processes or other deployable components. These are called Packaged Components.
- Assign those specific versions to one or more environments to be available to run. This is called a Deployment.
The creation of a packaged component is a “snapshot” of the current revision of a process and all its included components (such as maps, profiles, connections, etc.). This packaged component version is isolated from future changes in the Build tab so ongoing configuration changes to the process or other component do not affect it. That version can then move through a development life cycle, such as promoting from a “test” environment to a “production” environment.
The Deploy menu provides access to the following deployment tools:
- The Packaged Components option lets you create and manage packaged components for the processes and components that you build.
- The Deployments option lets you monitor existing deployments and create new deployments.