Migrating to a data store (Using the drawing tool)

A store is a location used to store state data from the Boomi Flow platform externally. Having an external data store, outside the realms of where the Flow platform stores state data, gives you even more granular control over your flow state data. For example, you can have the data reside on your favorite cloud, or even on-prem, if you like.

An external data store can be used for specific data residency and compliance requirements, giving you the freedom to decide where your state data ultimately resides, based on your unique business needs.

Setting up migration using the Flow drawing tool:

  1. Click External Storage to open the data stores tab. All the data stores that are present in the tenant are listed here.
  2. Click the Migrate icon next to the data store you want to use.

    This opens the Migrate to Store screen.

    You can see which data store you are migrating the data to from here, as well as the endpoint URL.
  3. Select the number of states you want to migrate at a time from the dropdown menu. We recommend you migrate 50 states at a time.
  4. Click Start Migration. This sends a request to the Flow engine to start the migration to the selected store. You will get a success message confirming the migration request.
You’ve got mail!

The Flow platform would have sent you an email on the migration – with details on whether the migration has gone through; or not. Every builder associated with the tenant will get this email.

When the migration is successful the email will list the number of flows (and subflows) and the number of states that were migrated. Going forward, now the external data storage will be used along with the Boomi Flow internal runtime data storage to store your state data.

If the migration was not successful, you may want to make sure that your external state storage service is working, and try the procedure again.

The migration operation (successful for not), will always:
  • Associate the store with the tenant and enable it – so it will be used in saving state data.
  • The replication mode is set to “ON” – meaning that state data are stored internally (as before the migration) and in the service (if it works; if it doesn’t work, we will be still trying to save state data there).
NOTE // 

Wondering what you need to do additionally, if you have flows in production? Nada. Absolutely nothing! The elves of the Flow platform will do all the work! The end-users of your Flow apps will not even realize the backend of their apps have gotten an update!