It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×3,951

question asked: Dec 30 '09, 9:49 a.m.
question was seen: 18,621 times
last updated: Dec 30 '09, 9:49 a.m.

Related questions

Trouble establishing cross server communication with RRC

0
Ales Koprivnikar (116●3●5●2) | asked Dec 30 '09, 9:49 a.m.
Hello,
I was experimenting with creating a CALM scenario with RRC, RQM and RTC but I ran into some problems. I was following the instructions from this article: http://jazz.net/library/techtip/304
I successfully connected RTC with RQM and vice versa. Also creating cross server communication between RRC and RTC/RQM worked. What failed was connecting RTC/RQM with RRC.

When trying to establish cross server communication from RTC/RQM to RRC I get the following error. 

An error occurred while requesting an OAuth consumer key from server "https://rrc:9443/rdm/rootservices".Hide Details

CRJAZ1341E The remote server responded to the request to generate a provisional OAuth consumer key with a HTTP status code 403 error.

com.ibm.team.repository.common.TeamRepositoryException

com.ibm.team.repository.service.internal.oauth.OAuthRestService.postRequestRemoteProvisionalKey(OAuthRestService.java:154)

sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

java.lang.reflect.Method.invoke(Method.java:618)

org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)

org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)

org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

$Proxy126.postRequestRemoteProvisionalKey(Unknown Source)

sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

java.lang.reflect.Method.invoke(Method.java:618)

com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:571)

com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1752)

com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1623)

com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1536)

javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)

org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)

org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)

org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)

javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)

com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54)

javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)

org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)

org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)

org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)

org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)

org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)

org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)

org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)

org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)

org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)

org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)

java.lang.Thread.run(Thread.java:811)

A bit about my environment. I have the following installed 



IBM Rational Quality Manager

V 2.0.0.1 Standard Edition (2.0.1.20091024_1915) 



IBM Rational Requirements Composer Server

V 2.0.0 (2.0.0.20091110_0711) 



Jazz Team Server Standard Edition

V 2.0.0.2 (2.0.2002.I20091211-1048)


It is all running on a single machine, with changed ports (RRC - 9443, RTC-9444, RQM-9445) and appropriate entries into hosts file so all the team servers are available with the following names: rrc, rtc, rqm. The Public URI root property is changed appropriately, so that the https://server:port/jazz/rootservices and https://server:port/rdm/rootservices are available. The servers function normally and I can access them without problems, just the cross server communication does not work.

I tried removing all the server entries, restarting and retrying the procedure, did not work. Only thing I found that is a bit peculiar is that in RRC the is server friend entry named Rational Requirements Server which has a Root services URI property set to localhost:9443/rdm/rootservices and i can not remove it. Also in the rootservices xml there is an entry of <jfs>https://localhost:9443/rdm, https://rrc:9443/rdm</jfs>. is this normal that there is a localhost entry inside?

Anyone had any similar problems? Any ideas on how to solve this?

Any and all ideas are very welcome.

Happy new year 2010 :)

20 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Joe Barnes (53●1●4●5) | answered Dec 30 '09, 11:15 a.m.
Hi,
I am running into a problem at project link time. Can you add a snippet from your hosts file and even what the entries look like in the Public URI property so I can be sure I am tackling those options correctly? I really appreciate the help.

I am receiving a 403 error when I go to link the projects. It happens in both Firefox and IE 8. I'm stuck.

Any help is greatly appreciated.

Happy New Year

- Joe
0
permanent link
Ales Koprivnikar (116●3●5●2) | answered Dec 31 '09, 5:59 a.m.
Hi,
hosts:

127.0.0.1       localhost

127.0.0.1	RRC	#9443

127.0.0.1	RTC	#9444

127.0.0.1	RQM	#9445


public URIs 
public URI for RRC

https://rrc:9443/rdm

for RQM:

https://rqm:9445/jazz

for RTC:

https://rtc:9444/jazz


For me it breaks down when creating cross server comm, cant even get to project area linking. Also to add to this, this was all installed fresh. Am thinking about reinstalling RRC again to see if that helps. Also this is running on Tomcat and DB2 9.5. Tomcat is the default app server that comes with the web install.

Bye
0
permanent link
Greg Hodgkinson (209●21●20) | answered Dec 31 '09, 7:43 a.m.
I have the same issue.

I installed RRC and RQM on one machine, and RTC on another.

I followed the instructions for configuring CALM integrations...

http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.help.common.jazz.calm.doc/topics/r_calm_cfg_roadmap.html

...and I get the same issue in that the RRC server always reports back localhost in it's rootservices as opposed to the hostname I configured in the Public URI.
0
permanent link
Paul Verrone (136●1●12●7) | answered Dec 31 '09, 11:19 a.m.
I have the same issue.

I installed RRC and RQM on one machine, and RTC on another.

I followed the instructions for configuring CALM integrations...

http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.help.common.jazz.calm.doc/topics/r_calm_cfg_roadmap.html

...and I get the same issue in that the RRC server always reports back localhost in it's rootservices as opposed to the hostname I configured in the Public URI.


Same exact thing here. RRC and RQM fresh installs on separate machines. RRC always reports back https://localhost:9443/ instead of the server name in it's rootservices.
0
permanent link
Robin Bater (3.4k●4●7) | answered Dec 31 '09, 2:18 p.m.
JAZZ DEVELOPER
I am not sure that this helps but when I successfully installed RRC, RTC, and RQM on the same machine, using different port numbers and using the local host aliases I needed to make the following change, to get C/ALM to work, in the Jazz Admin advance properties for each tomcat server:


https://jazz.net/wiki/bin/view/Main/CALMSmokeInstall (look towards the bottom)


If it says localhost, you have to configure the server's host name in the advanced properties:

1. Start the server
2. Launch the Web UI
3. Login as ADMIN/ADMIN
4. Choose Admin -> Jazz Server Administration Server props...
5. Click Advanced Properties
6. Change the Host Name to rtc (rqm=/=rrc)
0
permanent link
Ales Koprivnikar (116●3●5●2) | answered Jan 04 '10, 2:11 a.m.
Hi,
tried to set the hostname to RRC, like suggested but it makes no difference. In rootservices is says localhost. Not sure if that was the case before, but it still doesnt work...

Any ideas?
0
permanent link
Ales Koprivnikar (116●3●5●2) | answered Jan 04 '10, 8:22 a.m.
Some more additions,
if I reinstall and try to set the hostname during setup (set jazz root services URL to https://rrc:9443/... and so on) the setup procedure fails. When i come the step #3 in the setup the configure button does not work (you can click it, there is a internal error in the Error console in firefox - error 500) and i cant finish the setup...).

Any ideas ?
0
permanent link
Marc Baumbach (131●1) | answered Jan 04 '10, 12:01 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
We were able to troubleshoot aleskoprivnikar's problem and it consisted of two problems:

1. The friendsconfig.rdf files in server_root/conf/jazz and server_root/conf/rdm had "localhost" in them, which they should have had the correct HOSTS defined hostname. In this case, "rrc".

2. For some reason which I'm unsure of at the moment, the RRS OAuth key had been removed and needed to be re-added and matched with what was in the friendsconfig.rdf files. After manually doing this and restarting the RRC server, the problems seem to be resolved.

As a general rule of thumb, it's best to run the Custom Path setup for RRC and specifically state the hostname you plan to use from the other servers in all cases where you are asked.
0
permanent link
Joe Barnes (53●1●4●5) | answered Jan 04 '10, 1:58 p.m.
All,
I tried the fixs mentioned below and they still don't seem to work. At this point, I have my RTC/ RQM servers communicating and the cross project linking established in those two platforms.

I get the 403 error when trying to establish a connection between my RTC server and the RRC server (when I go from RRC to RTC the connection is established).

My RRC /conf/jazz/friendsconfig.rdf looks like this:

<jd>
<jd>
<dc>Rational Requirements Server</dc>
<jfs>https://rrc:9443/rdm,https://rrc:9443/jazz</jfs>
<jfs>339a727942cb41ffbeed909b8d398463</jfs>
<jfs>swshuLZz/HG76L79hvAQh7Dyqgvjq+FGdFatlGuPZGw=</jfs>
<jfs>true</jfs>
</jd>
<jd>
<jfs>false</jfs>
<jfs>bigmac</jfs>
<jfs>fcfaa5632d4245f79ed44dfa47800bb7</jfs>
<jfs>https://rtc:9433/jazz</jfs>
<dc>My RTC Friend</dc>
<jd>
</jd>


My conf/rdm/friendsconfig.rdf looks like this:

<jd>
<jfs>false</jfs>
<jfs>swshuLZz/HG76L79hvAQh7Dyqgvjq+FGdFatlGuPZGw=</jfs>
<jfs>339a727942cb41ffbeed909b8d398463</jfs>
<jfs>https://rrc:9443/jazz</jfs>
<dc>RRS_JFS</dc>
<jd>
</jd>

Any help is greatly appreciated.

Thanks,
Joe
0
permanent link
Hugh Cushing (21●3●1) | answered Jan 04 '10, 5:33 p.m.
One step that's left out of that technote: if you originally set up the server with a certain server name or port, then later changed it to non-default values, you have to edit two friendsconfig.rdf files in order to update the internal friends list.

Open up \server\conf\jazz\friendsConfig.rdf (after making a backup!) and change the names ports to the appropriate ones. Then do the same with server\conf\rdm\friendsConfig.rdf.

I've told support about the gap in the note above and they've put in a fix to update it.

Your answer

Register or to post 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.