Updating ItemPath (ItemPath 3)
ItemPath updates do not install automatically. Use the itempath-deploy utility to check the current version, apply the target version, and confirm the update completed.
Note: These instructions are for updates from ItemPath from 3.0.0 to later versions. If you are updating from ItemPath 2 to ItemPath 3, use these instructions instead.
Before You Start
- Docker must be installed and running.
- Docker Compose v2 must be available through
docker compose. - The Docker engine must run Linux containers.
- The operator must have permission to run Docker commands.
- The host must be able to pull ItemPath images from the registry, unless the images are already loaded locally.
- Save the installer file on the ItemPath host.
In the instructions below, replace
<target-version>with the ItemPath version being installed, such as3.4.7.
Follow These Steps to Perform the Update
- Make note of the current version of ItemPath installed in your environment.
- Confirm the Deployment Manager is installed and on the latest version before continuing.
Linux:
bash install-deployment-manager.sh <target-version>Windows:
cd $HOME .\Install-ItemPathDeploymentManager.cmd <target-version>
- Apply the Update. The
upgradecommand will back up the current deployment and apply the update to the specified version.Linux:
itempath-deploy upgrade <target-version>Windows:
cd $HOME .\itempath-deploy.cmd upgrade <target-version>
- If prompted
INSTALL_TYPE is not set in .env. Is this a cloud or on premise install?enteron premise. Follow any additional confirmation prompts that appear. - Confirm that the current version is now the specified version of ItemPath 3.
Linux:
itempath-deploy statusWindows:
cd $HOME .\itempath-deploy.cmd status
- Open your ItemPath application and confirm it loads as expected.
Rollback the Update
If for any reason, you need to roll back the upgrade, use the following command to restore the earlier deployment state.
Linux:
itempath-deploy rollbackWindows:
cd $HOME
.\itempath-deploy.cmd rollbackNote: the rollback command does not preserve changes made after the migration. It will restore the backup of your environment prior to the upgrade.
If your ItemPath environment is not loading after the rollback, use the following command to restart the environment.
Linux:
itempath-deploy restartWindows:
cd $HOME
.\itempath-deploy.cmd restartWhat Not To Do
- Do not manually edit ItemPath deployment files.
- Do not stop, start, or update ItemPath with manual Docker commands as the migration path.
- Do not move or delete ItemPath data while updating.
- Do not remove deployment backups unless support confirms it is safe.
- Do not roll back without understanding that changes made after the migration will be discarded.