It's all about the answers!

Ask a question

Error while regestering application in jts setup


Deepak soora (156) | asked Jul 07 '17, 3:57 a.m.

I have two servers
S1 : WAS,CCM,JTS - clmtest  - configured deployed and ready to use.
S2 : LDAP,WAS,QM - adserver

I am trying to setup a distributed topology and i am trying to register QM to JTS setup of server1 and having the following error while jts setup for QM
discovery URL is successful
https://adserver:9443/qm/scr is accessible from both servers. 

Request to service https://adserver:9443/qm/service/com.ibm.team.repository.service.internal.setup.IRegistrationHandlerService failed with status code 500 and response body: Error 500: CRJAZ1938E The consumer key and secret could not be validated for the following Jazz Team Server: https://clmtest.deep.dom:9443/jts Caused by: Connection timed out: connect Caused by: Connection timed out: connect



Comments
Donald Nong commented Jul 07 '17, 5:52 a.m.

If you check the content of https://adserver:9443/qm/scr, do the URLs in there have the same host as request?


Deepak soora commented Jul 07 '17, 8:11 a.m.

yes all the URLs inside the file has below format.
<oslc:publisher rdf:resource="%server-URL%/application-about"/>;
<jd:rootServices rdf:resource="%server-URL%/rootservices"/>;

QM is on Server2 so the host that we are requesting from S1 to S2 should be host name os S2 ?

One answer



permanent link
Krupa Gunhalkar (3312) | answered Jul 17 '17, 9:41 a.m.
JAZZ DEVELOPER

Hi Deepak,

It is recommended to use the full qualified host name while doing the JTS setup. Let it be QM, CCM or any other CLM application.

couple of points to cross check,

1) Map the IP address of both the machines with the fully qualified hostnames on both the machines. It is just like handshaking.
2) Ping the IP address and confirm that it matches the fully qualified hostname.
3) Ping the machines from each side.
4) See if you have any pop up blockers blocking the registration .

All these are important factors since the error thrown in 500 connection timeout, which generally means S1 is unable to contact S2 for some reason.

Hope this helps,
Krupa

Your answer


Register or to post your answer.