3.0.1 client to 4.0.3 server

Kim Soederhamn (1.5k●2●38●42) | asked Nov 08 '13, 9:41 a.m.

Hi we are upgrading a server from 3.0.1 to 4.0.3. They client however will stay on 3.0.1 for a while.
Now when all the users start using their client after the upgrade will they then run into problems using the existing workspace and repository connection or can they just reuse it as if nothing had happened ?
(The server does not change uri its just being upgraded)

Comments

sam detweiler commented Nov 08 '13, 9:49 a.m.

they will continue to work fine. of course they won't get any of the newer features or client fixes.

Accepted answer

permanent link

Rosa Naranjo (2.9k●1●14●23) | answered Nov 08 '13, 10:03 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

Kim
An RTC 3.0.1 eclipse client will continue to work with a server that has been upgraded to 4.0.3. Once you choose to upgrade the eclipse client to 4.0.3, you can still reuse your existing workspace. Thus, you will not need to create a new workspace and will not need to recreate repository connections.

Check out this topic: http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/topic/com.ibm.jazz.install.doc/topics/c_n-1.html
and this reference in the Deployment wiki: https://jazz.net/wiki/bin/view/Deployment/UpgradeCompatibility

Kim Soederhamn selected this answer as the correct answer

Comments

Kim Soederhamn commented Nov 10 '13, 8:47 a.m.

Hi Rosa,

I'm not sure this is fully the case. Multiple users have seen that they are not able to expand their project areas (they click the twistie but nothing happens) after the upgrade. Disconnecting and connecting seems to solve the problem at least for now.
expand not possible

Kim Soederhamn commented Nov 10 '13, 9:37 a.m.

in the .log from the workspace .metadata I find this problem all over:
eclipse.buildId=unknown
java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows Server 2008 R2 amd64-64 jvmwa6460sr13-20130114_134867 (JIT enabled, AOT enabled)
J9VM - 20130114_134867
JIT - r9_20130108_31100
GC - 20121212_AA
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=da_DK
Framework arguments: -product com.ibm.team.concert.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.ibm.team.concert.product
!ENTRY org.eclipse.equinox.security 1 0 2013-10-31 12:22:05.569
!MESSAGE New keyring password generated.
!ENTRY com.ibm.team.repository.client.login.KeyStoreLoginInfo 1 800 2013-10-31 12:22:23.320
!MESSAGE CRJAZ1887I The list of certificates available in the Windows-MY KeyStore could not be read. If you'd like to access the certificates from that keystore, make sure that you are running with a JVM that supports reading from that keystore.
!STACK 0
com.ibm.team.repository.transport.client.AuthenticationException: Error initializing the keystore.

Kim Soederhamn commented Nov 10 '13, 9:37 a.m.

So to me it seems there is a problem with the keystore finding certificates after the server was upgraded(to be fair its also located on a new server´with the same dns name)

Karl Weinert commented Nov 12 '13, 3:16 p.m.

JAZZ DEVELOPER

Kim the keystore messages can be ignored. RTC uses it's own keystore
As for the other issue you might want to test a 4.x client. Just because it is supported doesn't necessarily mean there won't be any issues.
If it works ok with the 4.x client you may want to open a defect or a PMR

It's all about the answers!

Related questions

3.0.1 client to 4.0.3 server

Accepted answer

Your answer