Start Automating your Integration Deployments
Last updated Mon May 23 2022
Use this recipe to migrate your Integration deployments across environments. The recipe includes:
- Quick steps for setting up the AtomSphere API Connector.
- A mechanism to check whether the target environment already has the packaged component deployed.
- A logging mechanism to track deployments and skipped packages.
There are many reasons you might want to bulk-migrate your Boomi deployments from one Integration environment to another. It might serve as a portion of an ALM (Application Lifecycle Management) design, or it might simply be a one-off migration to new infrastructure. For folks that will need to shift away from the Boomi API Management Authentication Broker when it reaches its planned retirement in mid 2022, this recipe will streamline the migration process.
The first branch of the process queries all of the currently-deployed packaged components in the target environment. It then adds those documents to a cache. The second branch queries all of the currently-deployed packaged components in the source environment. It checks each against the cache to determine whether the target environment needs the component, and deploys it if so.
Once the pattern is set up, the possibilities are endless for where you can automate the your cross-environment Integration deployments. Get started today!
The recipe qualifies for Boomi’s Recipe Program
This Recipe is eligible for Boomi’s Recipe Program – that bundles free expertise from the Boomi PSO team included in the price of this prebuilt offering. The Boomi experts will help you get set up faster than ever, allowing you to get the most out of the Boomi AtomSphere Platform.