Author: Ashok Goguboina
Overview
When integration developers perform deployment, runtime attachment(s), or integration pack re-release and install actions, all runtimes connected to the accounts will initiate a download of the relevant components from the platform. To better handle high-volume concurrent downloads at an enterprise scale, we have optimized the download process. These enhancements reduce the load on the platform, ensuring greater stability and enabling faster, more reliable component downloads for customers.
This change will not impact any functionality and will not interfere with process deployments, runtime attachment (either attaching or detaching), or the releasing, re-releasing, or installation of integration packs.
Usages
- We expect that the new download mechanism will greatly improve the process of downloading components. When we re-release integration packs to multiple runtimes, all of them will start downloading and installing components simultaneously. This will enhance scalability and allow users to access details quickly, so they can continue their work without long waits.
- Even for iPacks instances, you can quickly attach to new environments and runtimes. This makes it easy for users to access what they need to modify configurations and run processes. It also helps with troubleshooting logs and errors across different environments and downstream systems.
- Customers can now seamlessly perform key activities, such as deployments, container attachment and detachment, iPack releases, and installations involving large sets of components and runtimes, without facing disruptions or performance slowdowns. This improvement helps users save valuable time and boosts overall productivity by enabling faster and uninterrupted workflows.
- As your business expands, you gain opportunities, not added complexity. This change streamlines component downloads, ensuring consistent ease and efficiency for all your daily tasks, no matter the size of your components or runtimes. This reliable performance supports your growth, without exception.
Additional Considerations
- Customers using local installers, private runtime cloud, and runtime clusters behind a firewall are required to add the new Boomi endpoint https://component.cdn.boomi.com to their network’s DNS allowlist. If customers have previously set the SNI property -Djsse.enableSNIExtension value to ‘false’, customers are required to set it to ‘true’ in order to take full advantage of the upcoming enhancements. Note that, the default value of the -Djsse.enableSNIExtension value is ‘true’ if not explicitly set.
- During the initial download, you may experience slightly slower speeds as the system begins storing a copy of the component XML in the S3/CDN. However, all subsequent download requests will be significantly faster, as components will then be served directly from the S3/CDN.
- For users with only a small number of components or runtimes, performance improvements may not be immediately noticeable.
- A fallback mechanism is in place: if the DNS URL is not added to the allowlist and the SNI property values are not updated, the system will still download the component XMLs without interruption. However, this may cause delays in component downloads during deployments and integration pack releases or re-releases. To prevent such delays, it is recommended to whitelist the URL and update the property details accordingly.
- This new feature will be gradually enabled on all accounts by Boomi during the maintenance window, starting June 14, 2025.
Note:
- The full rollout is completed on Nov 08th 2025.
- The account feature ‘componentDownload’ can be disabled, if required, by contacting the Support or BizOps teams.
- The account feature ‘componentDownload’ will be enabled by default for the new accounts / sub- accounts from the January 2026 platform release.