Client and server version compatibility

Edit online

You can connect to a newer version server by using an older version client, but you cannot connect to an older version server by using a newer version client.

The same principle applies between servers. Jazz® Team Server must be at the same level as or newer than the applications that are registered with it, but the applications cannot have a newer version than Jazz Team Server. If the Global Configuration Management application is deployed, it must be at the same level as the Jazz Team Server.

Client N-1 compatibility is supported, which means that you can upgrade a server to the next release without upgrading the clients. This compatibility with previous versions applies to the following clients:
  • Client for Eclipse IDE
  • Client for Microsoft Visual Studio IDE
  • SCM command line
  • ISPF client
  • Jazz Build Engine
  • Windows shell

Clients are also compatible across fix packs for a release. When combined with N-1 compatibility, this means that client R works with all future fix packs for server R in addition to server R+1 and all future fix packs for server R+1. Note that servers must always be at the same level as or newer than clients. For example, client 6.0 can connect to server 6.0.5, but if client 6.0.5 attempts to connect to server 6.0 a message informs you that the versions do not match.

Engineering Workflow Management repository workspaces are compatible from version 2. This means that if you have a version 2 repository workspace, you can still use it with your upgraded Engineering Workflow Management Eclipse client.

The following table shows the client and server compatibility for version 5.0 and later. The table applies to the clients that are listed earlier in this topic.

Table 1. Client and server compatibility
Client version Server version
  5.0 5.0.1 5.0.2 6.0 6.0.1 6.0.2 6.0.3 6.0.4 6.0.5 6.0.6 6.0.6.1 7.0 7.0.1 7.0.2
5.0 YES YES YES YES YES YES YES YES YES YES YES No No No
5.0.1 No YES YES YES YES YES YES YES YES YES YES No No No
5.0.2 No No YES YES YES YES YES YES YES YES YES No No No
6.0 No No No YES YES YES YES YES YES YES YES YES YES YES
6.0.1 No No No No YES YES YES YES YES YES YES YES YES YES
6.0.2 No No No No No YES YES YES YES YES YES YES YES YES
6.0.3 No No No No No No YES YES YES YES YES YES YES YES
6.0.4 No No No No No No No YES YES YES YES YES YES YES
6.0.5 No No No No No No No No YES YES YES YES YES YES
6.0.6 No No No No No No No No No YES YES YES YES YES
6.0.6.1 No No No No No No No No No No YES YES YES YES
7.0 No No No No No No No No No No No YES YES YES
7.0.1 No No No No No No No No No No No No YES YES
7.0.2 No No No No No No No No No No No No No YES
The following table shows the version compatibility between different servers.
Note:

The IBM® Internet of Things Continuous Engineering Solution and Rational® solution for Collaborative Lifecycle Management products were renamed in version 7.0. For details on the name change, see Renaming the IBM Continuous Engineering Portfolio.

You can install JRS and the JTS at a higher level than the applications themselves, but JRS and the JTS must be at the same level. For example, JRS 7.0 and JTS 7.0 works with CCM 6.0.6.1.

Rhapsody® Model Manager first became available in version 6.0.5, so the compatibility for that product begins with that version.

Table 2. Server and server compatibility
Server version  
  JTS 5.0 JTS 5.0.1.x JTS 5.0.2.x JTS 6.0 JTS 6.0.1 JTS 6.0.2 JTS 6.0.3 JTS 6.0.4 JTS 6.0.5 JTS 6.0.6 JTS 6.0.6.1 JTS 7.0 JTS 7.0.1 JTS 7.0.2
RTC, RQM, DNG, JRS, RELM 5.0 YES YES YES YES YES YES YES YES YES YES YES No No No
RTC, RQM, DNG, JRS, RELM 5.0.1.x No YES YES YES YES YES YES YES YES YES YES No No No
RTC, RQM, DNG, JRS, RELM 5.0.2.x No No YES YES YES YES YES YES YES YES YES No No No
RTC, RQM, DNG, JRS, RELM 6.0 No No No YES YES YES YES YES YES YES YES YES YES YES
RTC, RQM, DNG, JRS, RELM 6.0.1 No No No No YES YES YES YES YES YES YES YES YES YES
RTC, RQM, DNG, JRS, RELM 6.0.2 No No No No No YES YES YES YES YES YES YES YES YES
RTC, RQM, DNG, JRS, RELM 6.0.3 No No No No No No YES YES YES YES YES YES YES YES
RTC, RQM, DNG, JRS, RELM 6.0.4 No No No No No No No YES YES YES YES YES YES YES
RTC, RQM, DNG, JRS, RELM, RMM 6.0.5 No No No No No No No No YES YES YES YES YES YES
RTC, RQM, DNG, JRS, RELM, RMM 6.0.6 No No No No No No No No No YES YES YES YES YES
RTC, RQM, DNG, JRS, RELM, RMM 6.0.6.1 No No No No No No No No No No YES YES YES YES
EWM, ETM, DOORS® Next, JRS, ENI, RMM 7.0 No No No No No No No No No No No YES YES YES
EWM, ETM, DOORS Next, JRS, ENI, RMM 7.0.1 No No No No No No No No No No No No YES YES
EWM, ETM, DOORS Next, JRS, ENI, RMM 7.0.2 No No No No No No No No No No No No No YES
Note: Jazz Team Server must be at the same level as or newer than the applications that are registered with Jazz Team Server. Even if you are upgrading to the next fix pack level, you must first upgrade Jazz Team Server.

Server compatibility for distributed Source Control Management (SCM)

Compatibility with previous versions is not supported in a distributed SCM setup. This means that there is no guarantee that distributed SCM works between different versions, as there could be comprehensive changes in how SCM manages its data between versions.

It is recommended that all servers involved in a distributed SCM setup be at the same version level. For more information about flowing changes across repositories, see this Jazz.net article.

Acronyms used in this topic

  • DCC: Data Collection Component
  • DNG: Rational DOORS Next Generation
  • DOORS Next: Engineering Requirements Management DOORS Next
  • ENI: Engineering Insights
  • ETM: Engineering Test Management
  • EWM: Engineering Workflow Management
  • JRS: Jazz Reporting Service
  • JTS: Jazz Team Server
  • LQE: Lifecycle Query Engine
  • RELM: Rational Engineering Lifecycle Manager
  • RMM: Engineering Rhapsody Model Manager
  • RQM: Rational Quality Manager
  • RRC: Rational Requirements Composer
  • RTC: Rational Team Concert®