RQM 2.0.0.2 service conflict with RTC 3.0iFix001
Hi,
A customer has RQM 2.0.0.x installed on its own local install of WAS and connecting to DB2 on an AIX box. A RTC 3.0iFix001 -RAM 7.5.0.2 PoT was deployed on a different machine with its own local WAS installation and using the same DB2.
After the RTC setup, RQM now has a problem in that users cannot log in to the RQM project areas. When the RQM admin tries to view the Client Access License Management or Active Users page in the admin web UI, they get a "CRJAZ1173I Service "com.ibm.team.reposiotry.service.internal.ILicenseAdminRestService" is not available." error msg.
I am waiting for WAS logs from the customer but any thoughts/help would be appreciated on what might be the cause of the problem. The customer suspects something in the database used by RQM was overwritten during the RTC install.
Cheers,
Hollis
A customer has RQM 2.0.0.x installed on its own local install of WAS and connecting to DB2 on an AIX box. A RTC 3.0iFix001 -RAM 7.5.0.2 PoT was deployed on a different machine with its own local WAS installation and using the same DB2.
After the RTC setup, RQM now has a problem in that users cannot log in to the RQM project areas. When the RQM admin tries to view the Client Access License Management or Active Users page in the admin web UI, they get a "CRJAZ1173I Service "com.ibm.team.reposiotry.service.internal.ILicenseAdminRestService" is not available." error msg.
I am waiting for WAS logs from the customer but any thoughts/help would be appreciated on what might be the cause of the problem. The customer suspects something in the database used by RQM was overwritten during the RTC install.
Cheers,
Hollis
3 answers
See https://jazz.net/forums/viewtopic.php?t=4079 for similar discussion
-|- Pramod Chandoria
-|- Pramod Chandoria
Hi,
A customer has RQM 2.0.0.x installed on its own local install of WAS and connecting to DB2 on an AIX box. A RTC 3.0iFix001 -RAM 7.5.0.2 PoT was deployed on a different machine with its own local WAS installation and using the same DB2.
After the RTC setup, RQM now has a problem in that users cannot log in to the RQM project areas. When the RQM admin tries to view the Client Access License Management or Active Users page in the admin web UI, they get a "CRJAZ1173I Service "com.ibm.team.reposiotry.service.internal.ILicenseAdminRestService" is not available." error msg.
I am waiting for WAS logs from the customer but any thoughts/help would be appreciated on what might be the cause of the problem. The customer suspects something in the database used by RQM was overwritten during the RTC install.
Cheers,
Hollis
Hi,
I have read through the forum discussion (https://jazz.net/forums/viewtopic.php?t=4079) but there is no further information on how to resolve the problem.
I have read through the forum discussion (https://jazz.net/forums/viewtopic.php?t=4079) but there is no further information on how to resolve the problem.
See https://jazz.net/forums/viewtopic.php?t=4079 for similar discussion
-|- Pramod Chandoria
Hi,
A customer has RQM 2.0.0.x installed on its own local install of WAS and connecting to DB2 on an AIX box. A RTC 3.0iFix001 -RAM 7.5.0.2 PoT was deployed on a different machine with its own local WAS installation and using the same DB2.
After the RTC setup, RQM now has a problem in that users cannot log in to the RQM project areas. When the RQM admin tries to view the Client Access License Management or Active Users page in the admin web UI, they get a "CRJAZ1173I Service "com.ibm.team.reposiotry.service.internal.ILicenseAdminRestService" is not available." error msg.
I am waiting for WAS logs from the customer but any thoughts/help would be appreciated on what might be the cause of the problem. The customer suspects something in the database used by RQM was overwritten during the RTC install.
Cheers,
Hollis
I suspect we're missing some pieces of information here. RTC was installed on a completely different server and this problem arose? Even if the same DB server was used, you isolated the RTC and RQM DBs, right? In the RQM /admin page, everything look OK under "Database Connection"?
Were you using the RTC server as a floating license server, perhaps?
What else changed on the RQM side from when it was working to when it was not? Did it just get restarted and was "all of a sudden" broken? No updates were made?
I think the log file will likely hold the most useful piece of information. During startup or shortly after we should see the "service failed to activate" message referring to the license service and we should be able to work back from that.
If a RQM update was applied (even though it was not mentioned here) then be sure to do a "requestReset" to get all of the updated content.
Were you using the RTC server as a floating license server, perhaps?
What else changed on the RQM side from when it was working to when it was not? Did it just get restarted and was "all of a sudden" broken? No updates were made?
I think the log file will likely hold the most useful piece of information. During startup or shortly after we should see the "service failed to activate" message referring to the license service and we should be able to work back from that.
If a RQM update was applied (even though it was not mentioned here) then be sure to do a "requestReset" to get all of the updated content.