Upgrade Process Astonishingly Poor

OK, partial success.

I tried James' procedure, but it ultimately failed. When I looked in the logs it was complaining that the database has not been migrated properly. My bad, I told James I was using RC3, but when I rechecked I realized it was RC1.

I then tried the procedure by ejodet which seemed to work better - although I modified it slightly more along the lines of what James gave me. I did not run the validation step.

However, when I ran jts/setup, it failed on step 14 with

CRRRS3008E Unexpected error occurred, see the log file for a possible cause. The response code for the error is '500'

Looking in the rm.log file I can see

2011-06-22 09:06:41,484 [         http-9443-Processor23] ERROR er.services.servicedocument.ProjectResourceService  - Server Error: Entry [e9ff5dc134f8403e]

com.ibm.team.jfs.app.oauth.OAuthInvalidConsumerKeyException: CRJZS0033E The consumer key is not valid and the consumer may not be registered. The service provider is "https://ekolotyluk-3500.creo.com:9443". The consumer key is "622...977".

Does anyone have any idea how I can get around this problem?

Cheers, Eric

OK, partial success.

I tried James' procedure, but it ultimately failed. When I looked in the logs it was complaining that the database has not been migrated properly. My bad, I told James I was using RC3, but when I rechecked I realized it was RC1.

I then tried the procedure by ejodet which seemed to work better - although I modified it slightly more along the lines of what James gave me. I did not run the validation step.

However, when I ran jts/setup, it failed on step 14 with

CRRRS3008E Unexpected error occurred, see the log file for a possible cause. The response code for the error is '500'

Looking in the rm.log file I can see

2011-06-22 09:06:41,484 [         http-9443-Processor23] ERROR er.services.servicedocument.ProjectResourceService  - Server Error: Entry [e9ff5dc134f8403e]

com.ibm.team.jfs.app.oauth.OAuthInvalidConsumerKeyException: CRJZS0033E The consumer key is not valid and the consumer may not be registered. The service provider is "https://ekolotyluk-3500.creo.com:9443". The consumer key is "622...977".

Does anyone have any idea how I can get around this problem?

Cheers, Eric

Hi Eric

So the problem is that the JTS and CCM apps can't talk to each other because the keys are invalid. You can try and add keys manually later - but I expect it to work.

Just so we are all clear - what was step 14? Which app was being set up? This may sound like a strange question, but depending on whether your original install had RTC only, or RRC/RTC and RQM, or some combination - step 14 might be a different step.

anthony

So the problem is that the JTS and CCM apps can't talk to each other because the keys are invalid. You can try and add keys manually later - but I expect it to work.

Just so we are all clear - what was step 14? Which app was being set up? This may sound like a strange question, but depending on whether your original install had RTC only, or RRC/RTC and RQM, or some combination - step 14 might be a different step.

anthony

You will have to tell me how to add keys manually.

Step 14 is trying to set up the RM application, which is why I found the error in the rm.log file. I originally had RTC, RM and QM installed.

Cheers, Eric

So the problem is that the JTS and CCM apps can't talk to each other because the keys are invalid. You can try and add keys manually later - but I expect it to work.

Just so we are all clear - what was step 14? Which app was being set up? This may sound like a strange question, but depending on whether your original install had RTC only, or RRC/RTC and RQM, or some combination - step 14 might be a different step.

anthony

You will have to tell me how to add keys manually.

Step 14 is trying to set up the RM application, which is why I found the error in the rm.log file. I originally had RTC, RM and QM installed.

Cheers, Eric

Apologies, I didn't register the fact that it was rm.log. So now this is going to be a whole heap of fun because I am pretty sure there where schemas changes between RC1 and GA. You where ok with RC3, but maybe not with RC1. That is probably why the verifier tool is failing.

However, lets at least try...

There is a help topic entry

Administering > Administering the Jazz Team Server > Configuring the server > Configuring OAuth consumers

that talks about registering keys. Do you have access to this from your installation, or you can try the help files here on jazz.net.

You generally do not have to do this manually (in fact I have never had to do this manually - so not quite sure how it should work for the RRC app).

I also suggest we stop for a minute and check if anyone knows if it is even possible to migrate from RC1 to GA given you have RRC involved

anthony

Apologies, I didn't register the fact that it was rm.log. So now this is going to be a whole heap of fun because I am pretty sure there where schemas changes between RC1 and GA. You where ok with RC3, but maybe not with RC1. That is probably why the verifier tool is failing.

However, lets at least try...

There is a help topic entry

Administering > Administering the Jazz Team Server > Configuring the server > Configuring OAuth consumers

that talks about registering keys. Do you have access to this from your installation, or you can try the help files here on jazz.net.

You generally do not have to do this manually (in fact I have never had to do this manually - so not quite sure how it should work for the RRC app).

I also suggest we stop for a minute and check if anyone knows if it is even possible to migrate from RC1 to GA given you have RRC involved

anthony

I don't know that the verifier tool is failing. I just said I did not run it.

I tried following the Configuring OAuth consumers help, and went to the Jazz server admin for consumers, but nothing makes sense to me in terms of the error message. I do not know what it is I am supposed to do.

Cheers, Eric

Unfortunately, it's a bit hard to tell exactly what state you are in given it's not entirely clear the complete set of steps you went through (and in what order) up to this point. But based on the info it does sound like there is an issue with a key mismatch.

Can you do the following?

1. Login to the JTS (/jts/admin) and go to the server administration area
2. Click on the "Consumers (inbound)" in the left-nav and look at the list of keys. There should be one there for RM. Note that key
3. Go to the server/conf/rm directory and look at the friendsconfig.rdf file and see if the XML element named jfs:oauthConfigKey has the same key value.

Please reply with whether the keys from 3 match or not so we can confirm the issue one way or the other and determine the right next steps.

Sorry to take so long to respond - dealing with network problems...

OK, the key in the Admin UI does not match the key in the file.

Cheers, Eric

Hi,

The next step is to repair the key and secret in the friendsconfig.rdf to match that in the database.

Here is the relevant technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21502286

Also, here is a page the describes the steps:
https://jazz.net/wiki/bin/view/Main/OAuthConsumerIssues

Mark

Success!

Things seem to be working now. I had to repair the keys in rm and admin.

I can see my project and all its data. I'll test things a bit more to be sure everything is working correctly.

Much thanks to everyone who helped out here - thank you!

OK, I'll just recap what happend:

(1) Originally I stared off using 3.0.1 RC1

(2) I installed 3.0.1 GA parallel to RC1

(3) I tried following the instructions at http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp which copied the settings over but not the databases.

(4) Intuitively I tried copying over the Derby databases, but that did not work, at which point I was very frustrated and asked for help.

(5) Eventually I followed the export/import process which seemed to work, but jts/setup failed because of key issues.

(6) Finally I was able to repair two of the OAuth consumer keys, and now things seem to be running properly.

Afterthoughts

The server product I work on at Kodak is architected such that we can easily upgrade from any old version to any new version. While this makes things easy for our customers, it is mostly a huge aid to our developers who need to make changes and test new versions easily. Basically our installer handles the upgrades and data migration automatically so we don't have to think about it.

My experience with the Jazz server was surprising in how little automation there was regarding upgrades. However, compared to version 2, it has dramatically improved. It is particularly frustrating to be faced with a huge amount of complex, confusing and incomplete documentation when attempting an installation or upgrade.

More recently I have started implementing a completely new server architecture from scratch, using Jazz, and I have been trying to incorporate the lessons learned from our previous server product, and experiences with other people's technologies.

At one point I found myself writing some very detailed instructions for our developers on how to set up the development environment for the new infrastructure. Eventually I realized I had created a beast of a document that had so many manual steps I had trouble following it myself - and it was increasingly insane to test the document. I had created one of the things I despise most - a complex manual process document.

I then changed my software design so that the server installs and configures all the infrastructure it needs (PostgreSQL, SQL Spaces, Hibernate, etc). To set up the development environment basically you just do

java -jar service.jar

and the rest just gets done automatically - it can take a while - but it is all automated. In the end the service is up and running. Some other benefits are that while testing you can just blow away parts of the infrastructure, and the service with reinstall and reconfigure them - it's self healing.

The best part is I could throw out the stupid document I wrote. The other great part is testing. It is hundreds of times easier to test an automated installer than to test a document for a complex manual process.

My feelings about Jazz are that it is like a five star meal served on a paper plate. From using Jazz it is apparent that IBM has fostered some amazing talent at understanding software development methodology, and leveraged it with some first-class technology like Eclipse. However, deployment is Astonishingly Poor! I really hope that IBM rethinks how Jazz is deployed.

Cheers, Eric