Source
Hosting options & portability — found from sitemap — Boomi
Checked for Boomi on 10 Nov 2026
- Page
- https://help.boomi.com/docs/Atomsphere/Integration/Deployment/c-atm-Deployment_4e723d20-3e2b-41b7-8d57-010dccb940b8
- Checked
- 10 Nov 2026, 18:30 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:9fef9cfe76d9ccd7e1859059b5474363c57e83e117ff6b923c39e9707218a9e9
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Deployment purpose Report an error
“Deployment is the means by which you prepare your processes and deployable components to run and operate in a test or production environment.”
-
Versioning audit Report an error
“Provides full audit history for versioning and deployments.”
-
Scheduled batch Report an error
“batch processes can be scheduled for automated execution”
-
Deployable components Report an error
“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”
-
Deployment steps Report an error
“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.”
-
Packaged component isolation Report an error
“This packaged component version is isolated from future changes on the Build page, so ongoing configuration changes to the process or other component do not affect it.”
-
Process library sharing Report an error
“After you create a packaged component in preparation for deployment, you can share that same packaged process component in the Process Library or add it to an integration pack.”
-
API service integration pack Report an error
“You can also add packaged API Service components to an integration pack.”
-
Deployment replacement behavior Report an error
“When you deploy a new version of a process to an environment, the new version replaces the previous version currently running on the associated runtimes. Any in-progress executions will complete with the previous version but future executions will use the new version.”
-
Deployment tools Report an error
“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.”
-
Doc updated Report an error
“Updated 18 March 2026”
Scores citing this record
- The Data Protection Officer Process design, forms & approvals
- The Data Protection Officer Governance, credentials & audit trail
- The Data Protection Officer Hosting options & portability
- The Head of IT Process design, forms & approvals
- The Head of IT Governance, credentials & audit trail
- The Head of IT Hosting options & portability
- The Integration Engineer Process design, forms & approvals
- The Integration Engineer Governance, credentials & audit trail
- The Integration Engineer Hosting options & portability
- The Operations Analyst Process design, forms & approvals
- The Operations Analyst Governance, credentials & audit trail
- The Operations Analyst Hosting options & portability
- The Process Owner Process design, forms & approvals
- The Process Owner Governance, credentials & audit trail
- The Process Owner Hosting options & portability
- The Skeptic Process design, forms & approvals
- The Skeptic Governance, credentials & audit trail
- The Skeptic Hosting options & portability