It's all about the answers!

Ask a question

Cannot finalize setup


Scott Hurd (124) | asked May 11 '15, 6:27 p.m.
 We want to 're-register' /rm & qm/ in CLM 5.0.2 (CCM is setup and running)
Both apps were working before in our 'dev' env. We decided to refresh ccm + jts DBs from prod.
Naturally /rm and /qm were not registered after that since they are not installed in prod.

I created 2 new DBs for each.

-Ran /qm/setup
Got to last page "Finalize Lifecycle Project Administration Setup"
Page says "Please wait while the Lifecycle Project Administration application is being finalized. This may take a minute."
for more then an hour.

-Bounce server.
Tried /rm/setup
Same problem.

/jts/Admin says:
WARNINGS:
   CRJZS5766W Resources cannot be accessed from the com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7 storage area because the 6309ebb9a37a4bbc8a8cd4362c17d196 consumer key does not exist. Create a consumer key, stop the server, and set the new consumer key to the storage area by using "repotools-jts -setStorageAreaKeys list=com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7,new_consumer_key", where new_consumer_key is the name of the consumer key that you created.

I tried what it says for both new keys for qm & rm.

I don't know if this is related to consumer keys or not.

Logs (JTS/RM/QM) say nothing.

I don't know if this is a consumer key issue or not.

How do you re-register qm & rm??

2 answers



permanent link
Donald Nong (14.4k314) | answered May 11 '15, 9:20 p.m.
There should be no "re-register". After you refreshed the JTS and CCM DB from PROD, your DEV environment mimics the PROD environment and you should do a server rename straightaway so that all the resources in the DEV environment point to the DEV correctly, not PROD. Then you will just add QM and RM to this configuration as if they never existed before. You've already created two new DBs for them, which is good. I think it will be easier if you use the original teamserver.properties files as well (find the backup version). Check the JTS admin page to see if QM and RM are registered there (they should not be as you said the PROD environment does not have them). Then run /jts/setup to add QM and RM to the configuration.

Comments
Scott Hurd commented May 12 '15, 10:28 a.m.

We are not doing a server rename. The dev env has a host entry to point dev items back to dev. We had this working before.

RM and QM were added to jts/admin registration.
Then I run qm/setup and rm/setup and all is fine until I get to the last page (finalize) in both cases.

I have tried the original teamserver.properties (blank) and the teamserver.properties when it was working. Same problem.

One thing I did not try was running jts/setup with rm & qm unregistered ..... I'll try that.


permanent link
Scott Hurd (124) | answered Jun 02 '15, 1:06 p.m.
I was able to get through (finalize) the RM & QM Setup.

After removing rm and qm registrations and removing all 'friends' from rm/admin and qm/admin
I noticed strange lines in the properties file for both apps.
The lines had  -random stings-  after the =
I commented the lines out and ran setup for both apps. Unfortunately setup deleted the commented lines from the properties files so I cannot show you what they were.

com.ibm.team.repository.setup.registration.pendingOauthConsumer= [long string....]
com.ibm.team.repository.setup.registration.pendingJtsFriend=  [long string....]

setup did complete with one error but both Qm and RM appear to be working. The only warning in the jts/admin is:

WARNINGS:
   CRJZS5766W Resources cannot be accessed from the com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7 storage area because the 6309ebb9a37a4bbc8a8cd4362c17d196 consumer key does not exist. Create a consumer key, stop the server, and set the new consumer key to the storage area by using "repotools-jts -setStorageAreaKeys list=com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7,new_consumer_key", where new_consumer_key is the name of the consumer key that you created.
   CRJZS5766W Resources cannot be accessed from the com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7.configs storage area because the 6309ebb9a37a4bbc8a8cd4362c17d196 consumer key does not exist. Create a consumer key, stop the server, and set the new consumer key to the storage area by using "repotools-jts -setStorageAreaKeys list=com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7.configs,new_consumer_key", where new_consumer_key is the name of the consumer key that you created.
   CRJZS5766W Resources cannot be accessed from the com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7.index storage area because the 6309ebb9a37a4bbc8a8cd4362c17d196 consumer key does not exist. Create a consumer key, stop the server, and set the new consumer key to the storage area by using "repotools-jts -setStorageAreaKeys list=com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7.index,new_consumer_key", where new_consumer_key is the name of the consumer key that you created.
   CRJZS5766W Resources cannot be accessed from the com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7.projects storage area because the 6309ebb9a37a4bbc8a8cd4362c17d196 consumer key does not exist. Create a consumer key, stop the server, and set the new consumer key to the storage area by using "repotools-jts -setStorageAreaKeys list=com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7.projects,new_consumer_key", where new_consumer_key is the name of the consumer key that you created.
   CRJZS5766W Resources cannot be accessed from the com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7.templates storage area because the 78ef124d7716460d91b198802c5ad165 consumer key does not exist. Create a consumer key, stop the server, and set the new consumer key to the storage area by using "repotools-jts -setStorageAreaKeys list=com.ibm.team.lpa.d196ed72-7a1f-4d98-94c3-87a44ffa77d7.templates,new_consumer_key", where new_consumer_key is the name of the consumer key that you created.

I think this is due to the /admin app not being deployed since it is not part of CLM v5.0. This is the result of upgrading from v3.0.

As said before, setup did complete but I got an error "deploy failed" on the very last step "Deploy Templates"

Your answer


Register or to post your answer.