Client and server version compatibility
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.
- Client for Eclipse IDE
- Client for Microsoft Visual Studio IDE
- SCM command line
- ISPF client
- Jazz Build Engine
- Windows shell
- Rational Software Architect Design Management client
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 5.0.1 can connect to server 5.0.2, but if client 5.0.2 attempts to connect to server 5.0.1 a message informs you that the versions do not match.
Rational® Team Concert™ 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 Eclipse client.
The following table shows the client and server compatibility for version 4.0 and later. The table applies to the clients that are listed earlier in this topic.
Compatibility between version 4.x to 6.0 is not supported. You must first upgrade your version 4.x server to the latest version 5, then upgrade to version 6.
Client version | Server version | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
4.0 | 4.0.1 | 4.0.1.1 | 4.0.1.2 | 4.0.2 | 4.0.3 | 4.0.4 | 4.0.5 | 4.0.6 | 4.0.7 | 5.0 | 5.0.1 | 5.0.2 | 6.0 | |
4.0 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
4.0.1 | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
4.0.1.1 | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
4.0.1.2 | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
4.0.2 | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
4.0.3 | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
4.0.4 | No | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
4.0.5 | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | No |
4.0.6 | No | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | No |
4.0.7 | No | No | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes | No |
5.0 | No | No | No | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes |
5.0.1 | No | No | No | No | No | No | No | No | No | No | No | Yes | Yes | Yes |
5.0.2 | No | No | No | No | No | No | No | No | No | No | No | No | Yes | Yes |
6.0 | No | No | No | No | No | No | No | No | No | No | No | No | No | Yes |
Jazz Reporting Service which includes DCC, LQE, and JRB first became available in version 5.0, so the compatibility for those products begins with that version.
RELM became available in version 4.0.3, so the compatibility for that product begins with that version.
As of version 5.0, IBM® Rational Requirements Composer is renamed to IBM Rational DOORS Next Generation. For more details, read this Jazz.net blog post.
Server version | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
JTS 4.0.0.x | JTS 4.0.1.x | JTS 4.0.2.x | JTS 4.0.3.x | JTS 4.0.4.x | JTS 4.0.5.x | JTS 4.0.6.x | JTS 4.0.7.x | JTS 5.0 | JTS 5.0.1.x | JTS 5.0.2.x | JTS 6.0 | |
RTC, RQM, RRC, DM 4.0.0.x | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
RTC, RQM, RRC, DNG, DM 4.0.1.x | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
RTC, RQM, RRC/DNG, DM 4.0.2.x | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
RTC, RQM, RRC, DNG, DM, RELM 4.0.3.x | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
RTC, RQM, RRC, DNG, DM, RELM 4.0.4.x | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
RTC, RQM, RRC, DNG, DM, RELM 4.0.5.x | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | No |
RTC, RQM, RRC, DNG, DM, RELM 4.0.6.x | No | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | No |
RTC, RQM, RRC, DNG, DM, RELM 4.0.7.x | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes | No |
RTC, RQM, DNG, DM, JRS, RELM 5.0 | No | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes |
RTC, RQM, DNG, DM, JRS, RELM 5.0.1.x | No | No | No | No | No | No | No | No | No | Yes | Yes | Yes |
RTC, RQM, DNG, DM, JRS, RELM 5.0.2.x | No | No | No | No | No | No | No | No | No | No | Yes | Yes |
RTC, RQM, DNG, DM, JRS, RELM 6.0 | No | No | No | No | No | No | No | No | No | No | No | Yes |
Server compatibility for distributed Source Control Management (SCM)
- Rational Team Concert 4.0.4 is not compatible with Rational Team Concert 4.0.5 and beyond.
Also future releases might not support backwards compatibility with respect to distributed SCM, if there are significant changes to how SCM manages its data.
If you need to perform distributed SCM operations between a server that is running Rational Team Concert 4.0.4 or earlier and a server that is running Rational Team Concert 4.0.6 or higher, you must upgrade your version 4.0.4 server to version 4.0.6 or higher.
In general, it is a good practice that all servers involved in a distributed SCM be at the same version level. For more information about flowing changes across repositories with Rational Team Concert, see this Jazz.net article.
Acronyms used in this topic
- JTS: Jazz Team Server
- RTC: Rational Team Concert
- RQM: Rational Quality Manager
- RRC: Rational Requirements Composer
- DNG: Rational DOORS Next Generation
- DM: Rational Software Architect - Design Management
- JRS: Jazz Reporting Service
- DCC: Data Collection Component
- LQE: Lifecycle Query Engine
- RELM: Rational Engineering Lifecycle Manager
Watch videos CLM playlistJazz.net channel User Education channel |
Learn more CLM learning circleAgile learning circle Learning circles |
Ask questions Jazz.net forumdeveloperWorks forums |
Get support Support PortalDeployment wiki Support blog |