RRC V2 beta / Jazz co-existance problem - all V2
I am installing RTC, RQM and RRC on one win2003 server (sp2). I have allowed RTC to use the default ports 9080/9443. I have configed RQM to use 9081/9444 and RRC to use 9082/9445. RTC and RQM work fine (all clients).
RRC works fine using the web UI. But not the RRC eclipse client. Using Web Ui I created a project from a template, added users with admin/author rights and can use all web UI functions with those usersID's. WeB URL is:
https://rrc:9445/jazz/web (NOTE: rrc is an alias to localhost, in my images "hosts" file, this is as per instructions)
RRC eclipse yields message "The connection does not work" and some times changes the URL back to localhost:9443 ?
The RRC eclipse URL that is not working is:
https://rrc:9445/jazz/rdm/
(client seems to require "rdm" to be in the address or the OK button stays gray-ed out). ( I also tried : https://rrc:9445/rdm/ - no good )
Any ideas??????
:shock:
RRC works fine using the web UI. But not the RRC eclipse client. Using Web Ui I created a project from a template, added users with admin/author rights and can use all web UI functions with those usersID's. WeB URL is:
https://rrc:9445/jazz/web (NOTE: rrc is an alias to localhost, in my images "hosts" file, this is as per instructions)
RRC eclipse yields message "The connection does not work" and some times changes the URL back to localhost:9443 ?
The RRC eclipse URL that is not working is:
https://rrc:9445/jazz/rdm/
(client seems to require "rdm" to be in the address or the OK button stays gray-ed out). ( I also tried : https://rrc:9445/rdm/ - no good )
Any ideas??????
:shock:
One answer
The url used by the client should be of the form https://rrc:9445/rdm/ (it should not include 'jazz'). The corresponding url for the web client should be https://rrc:9445/rdm/web/rrc (/jazz/web is for accessing the JFS server). Does accessing the RRC web client work (rdm/web/rrc)?
What happens if you actually use "localhost" in place of "rrc"? I know the is code in the connection logic that if the server comes back claiming a different address than you entered, we will switch to that instead to ensure a match.
Other than that, I'd have to assume there is a configuration problem somewhere related to changing the port.
What happens if you actually use "localhost" in place of "rrc"? I know the is code in the connection logic that if the server comes back claiming a different address than you entered, we will switch to that instead to ensure a match.
Other than that, I'd have to assume there is a configuration problem somewhere related to changing the port.