You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Things to consider before starting software upgrade:

  • Partial migration
    Starting from version 17.0.4, Teamwork Server supports multiple project versions. Different teams can work with the same Teamwork Server with different project versions, e.g. 17.0.5 and 18.1. So with Teamwork Server migration, only part of the projects could be migrated into the newest version. However within a project, the same version client application must be used.
    Floating server allows connecting all older versions clients starting from version 16.9.
  • Downtime
    Please dedicate at least one day downtime for products and data migration.
  • Custom artifacts (i.e. plugins, report templates) upgrade
    After migration, custom artifacts could be incompatible. Please check compatibility in advance. Note: we can help to test compatibility, and also upgrade custom artifacts.
  • Recommended upgrade workflow
    Upgrade: Teamwork Server, floating server license, client applications, plugins, required project on Teamwork Server. Before production environment migration we suggest to check Teamwork Server project upgrade and custom artifacts compatibility on test environment.
  • System requirements
    Check that new hardware and software conforms to the system requirements.

 

Floating license upgrade

Upgrade your floating license. See detailed instructions.

Modeling tool upgrade

Upgrade your modeling tool. See detailed instructions.

Plugin upgrade

Upgrade your plugins, for example, SysML plugin. Check compatibility tables to find compatible versions of the plugins you need to upgrade. See detailed plugin upgrade instructions. If you're using your own or third-party developed plugins, contact their developers/owners for new versions and update instructions.

Teamwork Server upgrade

Upgrade your Teamwork Server. See detailed instructions.