Question about set up the configuration of the integration
Hi,
Here is another question about setting up the configuration of the integration in RQM v1.0.1.
I try to set up the RTC as the defect provider for the RQM. But when I completed the RTC repository configuration dialog in RQM and click the "next" button, it stays in "Fetching Project Areas"... No errors return and no pass this step...
My environment is:
RQM 1.0.1 on server1 (repository URI - https://10.10.10.1:9443/jazz)
RTC 2.0M2D1 on server2 (repository URI - https://10.10.10.2:9443/jazz)
Both these servers use the derby DB inside them.
I've set the com.ibm.team.repository.service.internal.xdomain.DynamicProxyFrameService in RTC and its value is:
https://10.10.10.1:9443/jazz (RQM's repository)
Also I've set Adapter for RTC Component in RQM to set the ADMIN account and password.
Is there any mistake in my configuration? Thanks for your help!
Here is another question about setting up the configuration of the integration in RQM v1.0.1.
I try to set up the RTC as the defect provider for the RQM. But when I completed the RTC repository configuration dialog in RQM and click the "next" button, it stays in "Fetching Project Areas"... No errors return and no pass this step...
My environment is:
RQM 1.0.1 on server1 (repository URI - https://10.10.10.1:9443/jazz)
RTC 2.0M2D1 on server2 (repository URI - https://10.10.10.2:9443/jazz)
Both these servers use the derby DB inside them.
I've set the com.ibm.team.repository.service.internal.xdomain.DynamicProxyFrameService in RTC and its value is:
https://10.10.10.1:9443/jazz (RQM's repository)
Also I've set Adapter for RTC Component in RQM to set the ADMIN account and password.
Is there any mistake in my configuration? Thanks for your help!
4 answers
Hi,
Here is another question about setting up the configuration of the integration in RQM v1.0.1.
I try to set up the RTC as the defect provider for the RQM. But when I completed the RTC repository configuration dialog in RQM and click the "next" button, it stays in "Fetching Project Areas"... No errors return and no pass this step...
My environment is:
RQM 1.0.1 on server1 (repository URI - https://10.10.10.1:9443/jazz)
RTC 2.0M2D1 on server2 (repository URI - https://10.10.10.2:9443/jazz)
Both these servers use the derby DB inside them.
I've set the com.ibm.team.repository.service.internal.xdomain.DynamicProxyFrameService in RTC and its value is:
https://10.10.10.1:9443/jazz (RQM's repository)
Also I've set Adapter for RTC Component in RQM to set the ADMIN account and password.
Is there any mistake in my configuration? Thanks for your help!
This use case was broken in RTC 2.0 M2D1 but recovered in RTC 2.0 Beta1.
Do you already have a project in your RTC server?
This causes the same problem for me. After creating a project in RTC, the problem got solved. Let me know if it helps...
Yes, there are some projects in RTC already but it still didn't work for me...
Today I try to deploy both RTC and RQM to the same server and configure the integration for them. Then it can work well... but to do this I have to change the server and application port number for either RQM or RTC or both to let these two servers can run on the same server.
In this case, I also use env described above..
Hi,
Here is another question about setting up the configuration of the integration in RQM v1.0.1.
I try to set up the RTC as the defect provider for the RQM. But when I completed the RTC repository configuration dialog in RQM and click the "next" button, it stays in "Fetching Project Areas"... No errors return and no pass this step...
My environment is:
RQM 1.0.1 on server1 (repository URI - https://10.10.10.1:9443/jazz)
RTC 2.0M2D1 on server2 (repository URI - https://10.10.10.2:9443/jazz)
Both these servers use the derby DB inside them.
I've set the com.ibm.team.repository.service.internal.xdomain.DynamicProxyFrameService in RTC and its value is:
https://10.10.10.1:9443/jazz (RQM's repository)
Also I've set Adapter for RTC Component in RQM to set the ADMIN account and password.
Is there any mistake in my configuration? Thanks for your help!
This use case was broken in RTC 2.0 M2D1 but recovered in RTC 2.0 Beta1.
Thanks for you response. I'll try to do this in RTC 2.0 beta1 when available...
Now it can work well when I installed RTC 2.0 M2D1 and RQM 1.0.1 on the one server.