Earliest server version compatible with RTC 6.0.6.1 client?
Xavier Nodet (22●4●6)
| asked Jul 26 '19, 11:10 a.m.
retagged Jul 29 '19, 3:31 p.m. by Ken Tessier (841●1●7)
Hello,
I just installed the RTC 6.0.6.1 client on macOS, and I get this error when connecting to our server:
Exception constructing editor input
CRJAZ0056I There is a version mismatch for the "com.ibm.team.repository" service. The server version is "39" while the client version is "43".
Could you please let me know which is the latest client version that can work with this server?
And, alternatively, what is the earliest server version that would work with this client?
I find this issue very surprising, because I had already an RTC 6 client on my previous machine...
Thanks.
|
Accepted answer
See the help topic for client and server compatibility: Xavier Nodet selected this answer as the correct answer
|
One other answer
Ralph Schoon (63.5k●3●36●46)
| answered Jul 26 '19, 11:33 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Jul 26 '19, 12:33 p.m.
The RTC 6.0.6.1 client is compatible with RTC 6.0.6.1 server. That is it. The clients are compatible with the same version server and clients potentially are compatible with higher versions up to a major version - that is the aim, might not be possible. This is called N-1 client to server capability.
See the summary at the end of https://rsjazz.wordpress.com/2013/07/09/new-version-and-now-experiences-with-sdk-and-plain-java-api-across-tool-versions/or open the system requirements or the product documentation for the details.
Get the server version and download the matching client.
Comments 
Geoffrey Clemm
commented Jul 26 '19, 11:51 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Note that the key point here is that you can never use a client that is a later version than the server. So you always first deploy a new version of the server, and then you can start deploying the new version of the client. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.