Welcome > Upgrade tenants

Upgrade tenants

This section describes the steps for upgrading the TotalAgility tenants from version 7.5.0 or (7.5.X.X) to version 7.9.0.

Note When upgrading a tenant in on-premise multi-tenancy which is installed with the Integration Server, you must stop all the services; otherwise, the tenant upgrade fails.

You can perform capture data migration in on-premise multi-tenancy. The capture data migration process is performed when upgrading a tenant from previous versions of TotalAgility to 7.8.0. The migration process of each tenant database is done from the Tenant Management System. The migration process can migrate only consistent data. If for some reason (due to custom scripts or TotalAgility failures) some folders in database are in not in a consistent state, these folders cannot be migrated and appear as broken folders.

If any broken root folders are found during tenant's upgrade, a "Complete with Warnings" is displayed for that tenant's status. You can review the warnings and associated broken root folder IDs. You can acknowledge each tenant individually, or acknowledge all tenants at once. Acknowledging a tenant in this case will mark the tenant's upgrade as complete.

Perform the following steps to upgrade a tenant:

  1. In the Upgrade Tenants page, on the Disable for Upgrade list, select one of the following:

    • Disable All Developments
    • Disable All Productions
    • Disable All

    Note

    • The Disable Dev and Disable Production options are available only if you select a tenant.

    • When a specific environment (production or development) for a tenant is inactive, you can still log on to TotalAgility Designer or Workspace.

  2. Backup all the databases. This includes Master Tenants, Data Center Tenants and each tenant specific database.
  3. On the Tenant Management System page, click Upgrade Tenants.

    The Upgrade Tenants page appears.

  4. On the Upgrade Actions list, select one of the following options.

    • All Environments: The upgrade scripts run on all the Development and Live environments for all tenants.

    • Production Environments: The upgrade scripts run on all the Production environments for all tenants.

    • Development Environments: The upgrade scripts run on all the Development environments for all tenants.

      Note There can be multiple development environments per tenant.

    Upon confirming to upgrade, the upgrade scripts run on the selected environment.

  5. Click Refresh.

    Note:

    • The Result column shows the data migration upgrade progress visualization for the tenants, for example, Inprogress (35%), ETA :0h 25min for tenant A. After the capture data migration process, the Result column displays the tenant upgrade status, such as completed, failed or completed with warnings.

    • The migration process can migrate only consistent data. If for some reason (due to custom scripts or TotalAgility failures) some folders in database are in not in a consistent state, these folders cannot be migrated and appear as broken folders. During tenants upgrade, if any broken folders are found, the upgrade status is changed to "Completed with Warnings" and the Review Warnings tab is enabled. This status does not allow to enable the tenant until the warnings are not explicitly reviewed.

  6. To view the warnings and fix them, click the Review Warnings tab.

    During upgrade of one or more tenants, if some root folders are found broken, the names of the tenants and the broken root folder IDs are displayed in the Review Warnings dialog box. You can acknowledge each tenant individually, or acknowledge all tenants at once. Acknowledging a tenant will mark the tenant's upgrade as complete. Do either of the following to acknowledge:

    • Select a tenant and click Acknowledge to Acknowledge individual tenant. This marks selected tenant upgrade status as succeeded and removes it from the list. If it was the last tenant with broken folders, the Review Warnings dialog box is closed.

    • Click Acknowledge for All to Acknowledge all tenants. This changes all found tenants upgrade status as succeeded and closes the Review Warnings dialog box.

  7. Click Close.
  8. Ensure that the system is working as expected. For example, you can login and check if the system is running properly.

Zero downtime upgrade process

In the non-zero downtime upgrade process, you must close the current running application for all the tenants, install new version and upgrade all the tenant databases and start the new version of the application after all the tenants are upgraded. This involves application being down for a while. With zero down time upgrade, you can upgrade TotalAgility by introducing a new version of your application to production during the upgrade process, the application is never completely down or in an unstable state and the system need not be down until all tenants to be upgraded.

To upgrade with zero downtime on Azure via Tenant Management System, do the following:

  1. Manually run 7.8 to 7.9 conversion scripts (pre-upgrade) on Master Tenants and DataCenter Tenants databases, if any.
  2. Upgrade the current (7.8) Tenant Management System Azure deployment to the latest version (7.9).
  3. Deploy the latest version (7.9) Azure datacenter into staging deployment. You must deploy without running the worker task roles. For this, you must set the "IgnoreWorkerTasks" setting in the Azure Configuration.cscfg file to true. This setting when set to true will not be running any worker tasks.

    When you use a staging deployment that users cannot access, there is no need to disable the tenant Designer as the production will still be running 7.8.0.

  4. Logon to Tenant Management System and navigate to the Datacenter screen and update the Datacenter with the new staging datacenter details in the Live Host Name and Dev Host Name fields. The staging datacenter hostname can be derived from Azure portal similar to how you get it from production in current deployment.
  5. Navigate to the Upgrade Tenants page, select single tenant, multiple tenants or all tenants to upgrade and click Convert DB- Pre Upgrade to pre upgrade the database scripts.
    This will upgrade the tenant databases which will be backward compatible. The tenant will be Inactive during this upgrade. Make sure the upgrade is successful and the tenant is working fine, that is, the tenant DB is upgraded and running the old version binaries.
  6. Revert the Datacenter via the datacenter screen in Tenant Management System with the original production datacenter details.
    Note: You can only start doing this after all the tenant databases are upgraded.
  7. From the Azure portal, you can now change the IgnoreWorkerTasks setting in the configuration file to false and swap the staging into production.
    The Tenant Management System and datacenter databases are upgraded to latest version(7.9) which is backward compatible.
  8. Make sure the tenant is working fine. If not, swap back the deployment and restore databases to previously backed up state.
  9. To run the post upgrade database scripts to cleanup old data, navigate to the Upgrade Tenants page, select single tenant, multiple tenants or all tenants to upgrade and click Convert DB- Post Upgrade.
    The postscripts are executed. Each tenant will be inactive during its upgrade.
    Note It is not be possible to upgrade to the next version of TotalAgility until the Post Upgrade DB scripts are executed.
  10. Manually run the post-upgrade scripts for Master Tenants and DataCenter Tenants databases.

    The tenants are now upgraded to latest version (7.9).