RTC Plugin development Jetty server version incompatible with client RTC
I started developing RTC plugin. EWM, we have on our system is of version 7.0.1 . I verified earlier these versions are discontinued and server and client sdk for v 7.0.1 not present but other files like p2 repo , plain java libraries are still there for this version. As I can't change or upgrade my RTC to newer version I choose to develop plugin for this version only using workshop setup 7.x and plain java libraries and EWM client of version 7.0.1 but server and client sdk of v6.0.6.1 (Thought one lower version sdk will not cause problem ). But I was wrong while I was following IBM Rational Team Concert 7.x Extensibility this pdf .
My Jazz test development server is up and running at https://localhost:7443/jazz but v6.0.6.1 but while i reached on lab activity 1.10 step 72 creating snippets project in the test server from eclipse it got failed giving error
client 6.06.1 and server 7.0.1 not compatible (Was expecting this) still i procced further skipping this step i tried to create a repository connection to this https://localhost:7443/jazz following activity Lab 2 Create a Simple Build on State Change Operation Participant
Error received You client of version 7.0.1 and server version 6.0.6.1 not compatible
Now I am struck there I'm all new to this so I don't know how to procced further like I can't upgrade to new version and sdk not available for current version any suggestion how can i procced further to create plugin - feature - site than deploying it for testing any guidance highly appreciable or should I create a simple plugin for my https://localhost:9443/jazz (main instance) and directly create feature and site for this
One answer
You can not work with an EWM 7.0.1 client against a 6.0.6.1 server. You can only use an 6.0.6.1 or 6.0.6 or lower version EWM client against such a server.
You should follow the workshop and use the clients and servers as they are described in the workshop.
You should upgrade your production environment to 7.0.2 SR1 or higher immediately.
Comments
I guess that is the only option, upgrading production env from v7.0.1 to 7.0.2/higher.
It might be possible to develop the plugin on a 7.x development system and deploy it on a 6.x production server. But the changes to log4j would make it impossible to enable logging in the plugin.
1 vote