Rolling back a third-party integration to the previous version

To roll back an integration

1. Run the following command to verify the BMC Helix Developer Tools connector status: 

   docker ps | grep <connectorNname>

   Sample output

   CONTAINER ID    IMAGE           COMMAND      CREATED        STATUS       PORTS                NAMES
   deed817ccb72    57e8da5cb8ac    "/run.sh"    5 hours ago    Up 2 hours   5140/tcp,24224/tcp   tsom_test_connector

2. (Optional) If the connector is up and running, run the following command to stop the connector: 

   docker stop <containerID>

   Example

   docker stop deed817ccb72

3. Back up the /opt/bmc/connectors/<connector-name>/data directory.

   Best practice
   Name the backup directory with the integration build details. For example, if you are taking a backup of the integration build 80, name the backup directory as Integration_backup_build80.

4. Extract and copy the backup data directory of the previous integration version and paste it in the /opt/bmc/connectors/<connector-name>/data directory. 
5. Confirm the file replace operation.

6. Restart the container by running the following command:

   docker exec -it <containerID> bash

   Example

   docker exec -it deed817ccb72 bash

To verify the rollback operation

On the Configured Integrations tab, check the build number on the third-party integration tile, and ensure that the integration version is rolled back to its previous version. For example, before the rollback, if the build number is 108, after the rollback, the build number displayed on the tile would be 107, as shown below: