1. Docs
    2. arrow-right
  2. Updating Overview
    3. arrow-right
  3. Updating from ItemPath 2 to ItemPath 3

Updating from ItemPath 2 to ItemPath 3

Updating from ItemPath 2 to ItemPath 3 is a special migration path. If you are updating from ItemPath 2 to a later version of ItemPath 2, use these instructions. If your software version is already ItemPath 3, update using these instructions.

Note: Before updating to version 3.0.0.0 and later, ensure you are running the latest version of ItemPath 2 (2.25.4.11).

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. In the event of a firewall issue preventing this, please reach out to ItemPath support.
  • Save the installer file on the ItemPath host.

Note: Replace <target-version> with the ItemPath version being installed, such as 3.3.1. 

Follow These Steps to Migrate from ItemPath 2 to ItemPath 3

Step 1: Make note of the current version of ItemPath installed in your environment

Step 2: Follow the instructions to Install the Deployment Manager.

Step 3: Confirm the Deployment Manager is installed and that the current version is the expected ItemPath 2 version (noted in step 1) before continuing. Note: The terminal may indicate the version as "Latest". If so, you can proceed to the next step.
Linux:

itempath-deploy status
Windows:
cd $HOME
.\itempath-deploy.cmd status

Step 4: Bring the docker containers down by running the command: docker compose down

Step 5: Run the Migration. The upgrade command will back up the current deployment and apply the ItemPath 3 migration.

Linux:
itempath-deploy upgrade <target-version>
Windows:
cd $HOME
.\itempath-deploy.cmd upgrade <target-version>

Step 6: If prompted INSTALL_TYPE is not set in .env. Is this a cloud or on premise install? enter on premise. Follow any additional confirmation prompts that appear.

Step 7: Confirm that the current version is now the specified version of ItemPath 3. 

Linux:
itempath-deploy status
Windows:
cd $HOME
.\itempath-deploy.cmd status

Step 8: Open your ItemPath application and confirm it loads as expected.

Rollback the Update

If for any reason, you need to roll back from the ItemPath 3 upgrade, use the following command to restore the earlier deployment state of ItemPath 2.

Linux:
itempath-deploy rollback
Windows:
cd $HOME
.\itempath-deploy.cmd rollback

Note: the rollback command does not preserve changes made after the migration. It will restore the backup of your environment prior to the upgrade.

What 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.

Release Notes

Software release notes can be found online here.

Resources

To learn more about ItemPath and see it in action, please book a demo with our sales team. In the meantime, here are some of our popular articles and key topics.

Book a Sales Demo arrow icon
Updating

Product Updates

Updating

Install or Update the Deployment Manager Tool for On-Premise Software Updates (ItemPath 3)

Updating an On-Premise installation of ItemPath to version 3.0.0.0 and later requires ItemPath's Deployment Manager Tool. This tool is used to update, start, stop, and check an ItemPath deployment.The ItemPath ...

Updating

Updating Overview (ItemPath 2)

ItemPath pushes out regular ItemPath Docker image updates, but the images do not update automatically. Here's how to perform an ItemPath software upgrade. ...