I'm missing the internal key RM Data Collector after an upgrade from 5.0.2 to 6.0.2 and a server rename
After a tedious process of upgrade from 5.0.2 to 6.02, a server rename I found all the internal keys were missing.
Using this forum entry : https://jazz.net/forum/questions/158089/missing-internal-licenses-after-upgrade-to-clm-500 I was able to find almost all the missing internal keys. I'm still unable to find the RM Data Collector key. I also used https://<server-name>/rm/licensekey to retrieve the RM-Application Internal key, but not the RM Data Collector key Does someone have a suggestion of how to recover the RM Data Collector internal key? |
One answer
I found them at:
https://<server-name>/rm/etllicensekey and the other missing key at https://<server-name>/rm/trslicensekey These can be found along with /rm/licensekey in the https://<server-name>/rm/scr output under the node: licenseKeyProvider Would IBM consider making this license key management consistent with the other CLM artifact types - they all store their respective keys in a zip file. Comments
Donald Nong
commented Sep 22 '16, 6:23 a.m.
JTS should pull those license keys automatically when the application is first registered to JTS and when starting up. Can you please contact Support and confirm that whether it is a defect?
This was an upgrade for 602, and so were the keys there after the install? I can' be 100% sure, but I believe they were. I have already contacted support, their response was to do what I had done, described above.
Donald Nong
commented Sep 22 '16, 9:47 p.m.
It may be a rare case. While I "believe" it is a defect, the developers will have to final say.
|
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.