Hi,

this is most likely due to the cookie mechanism used to store the credentials. I think once you log in to the other server the current cookie gets overwritten which would force you to log in again and again.

To avoid this in our PoC we set the servers up to have different URI roots with aliases for the machine for examlple rtc.example.com and rqm.example.com for the two servers, even if they run on the same machine. This would also allow to move the single servers to different machines, provide the DNS would support the "logical" host names.

Please be aware that you can not change the URI Root anymore after you have used it without ill effects. All cross references in the system refer to the URI Root. If you change it links will break, I believe.

Ralph

Setup:
RTC 2.0.0.2 ifix 6 - machine1 port 9444
RQM 2.0.1.1 ifix 1 - machine1 port 10444

RTC and RQM are friends
Project are linked between RTC and RQM

Each time a user traverses a link or opens a defect in RTC from RQM it logs the user out of one application and make them log into the other.

This does not happen on linked projects between different machines

Thoughts?

We used different ports for each tool. RRC, RTC, RQM. 9443, 9444, 9445. Of course you have do changes to the host files (ask your network guy), team server properties under jazz folder for each tool as well (9444 and 9445 guys). In the cross server communications user the new urls with the new port extensions. Now you wont jump into confusing the jazz tomcat server (Or WAS if you are using that) by accessing different tools on the same windows (or unix) server where the tools are installed.