Upgrading

This page explains how to move MicroB2B to a newer version, and how to go back if something goes wrong.

Before you start

• Read what the new version changes.
• Make sure you have a recent backup of the database and the payload storage.
• Pick a quiet moment. Partners cannot send you messages while MicroB2B is stopped.

MicroB2B creates missing tables when it starts, but it never changes a table that exists. A version that changes the tables needs an empty database.

Upgrade

1. Back up the database. See backup.
2. Stop MicroB2B, for example with systemctl stop microb2b or docker stop microb2b.
3. Replace the binary or the container image.
4. Start MicroB2B again.
5. Check that GET /health answers 200 and that the log shows no errors. See monitoring.
6. Sign in and look at the dashboard and System > Services.

Stopping MicroB2B fails no delivery. Deliveries that were interrupted are sent after the start. See install.

Roll back

If the new version does not work:

1. Stop MicroB2B.
2. Restore the database backup you made before the upgrade.
3. Start the previous version.

Messages that arrived between the backup and the rollback are not in the restored database.

Which version runs

The footer of the web UI shows the version once you are signed in. The log names it when MicroB2B starts.