Local Atom Migration

Last updated Wed Aug 03 2022

This recipe acts as a guide to migrate from one local atom to another, which includes:

  • Updating the destination atom name, hostname and purge settings.
  • Migration of the process schedules and Listener statuses.
  • Migration of the persisted properties.
  • Migration of the Atom counter.
  • Use of error handling to roll back changes if the migration fails at any point.

Overview:

A Local Boomi Atom is a single-tenant, single-node AtomSphere runtime engine installed on your local network to access the local resources (file read/write, database, on-premise applications or servers) reachable within the network.

As your company learns of new requirements, you may need to move from one local atom to another or from a Boomi Cloud Atom to a local atom.

This solution provides you a seamless way to execute this migration. By making use of the atmosphere API, we automate all the parts of the migration process.

This solution serves as a checklist of all the things you need to migrate when you are migrating fromone atom to another.

Within a matter of minutes, you can migrate from one local atom to another, also migrating all the atom settings, process schedules, listener statuses, persisted properties and atom counter.

This automation not only saves you time, it also helps you avoid any manual errors.

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.

Learn More

Related Solutions

Accelerator

Boomi EDI Dashboard

Simplify EDI with End-to-End Visibility

Recipe

Cloud Atom Migration

Kick start your cloud atom migration process using this recipe. By utilizing Atomsphere API, various parts of the migration are automated.
Learn more

Recipe

Start Encrypting Single Fields

Easily encrypt a single field's value within a given document. Field values are encrypted, temporarily stored in a Document Cache, and then re-incorporated with the rest of the document using a Map shape.
Learn more