It's all about the answers!

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

×6,110
×6,034
×864

question asked: Jul 07 '14, 3:28 a.m.
question was seen: 4,879 times
last updated: Aug 11 '14, 1:05 p.m.

Related questions

Design Management. registering to JTS

0
Don Max (24●1●17●34) | asked Jul 07 '14, 3:28 a.m.
edited Jul 07 '14, 3:51 a.m.

Hi,

  I am trying to register the Design managent to a JTS server installed in a different machine. I have installed the DM without JTS .  I am getting the below error while registering.. I tried by going to jts/setup and also in manage server register application options. both giving same error.

I am able to access the /dm and /vvc in url from both machines. DM deployed in WAS setup and JTS runs on tomcat. both clm and DM version 4.0.6...

ERROR!

The applications could not be registered with Jazz Team Server.ID CRJAZ1726E

hide details

Request to service https://192.168.2.8:9443/dm/handleSetup failed with status code 503 and response body: An error occurred while making a discovery request to "https://flame:9443/jts/discovery?type=http%3A%2F%2Fjazz.net%2Fxmlns%2Fprod%2Fjazz%2Fdiscovery%2F1.0%2FApplication". The nested exception should contain more details.
com.ibm.team.repository.common.TeamRepositoryException
com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.checkHttpResponse(FriendsAdminRestService.java:820)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService$UpdatingFriendResponseHandler.handleResponse(ApplicationRegistrationFriendRestService.java:468)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService$UpdatingFriendResponseHandler.handleResponse(ApplicationRegistrationFriendRestService.java:1)
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:945)
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:919)
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:910)
com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.executeHttpRequest(FriendsAdminRestService.java:772)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService.notifyAppRegistrationHandler(ApplicationRegistrationFriendRestService.java:361)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService.postRegisterApp(ApplicationRegistrationFriendRestService.java:201)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:611)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
com.sun.proxy.$Proxy408.postRegisterApp(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:611)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:530)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2359)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:2153)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1963)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165)
com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:581)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:336)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
java.lang.Thread.run(Thread.java:761)

Please suggest.

Thanks

Comments
Ralph Schoon commented Jul 07 '14, 3:42 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Why is there an IP address in one of the URI's and a host name in another?

"to service https://192.168.2.8:9443/dm/handleSetup failed with status code 503" ....
"An error occurred while making a discovery request to "https://flame:9443/jts/discovery?type=http%3A%2F%2Fjazz.net%2Fxmlns%2Fprod%2Fjazz%2Fdiscovery%2F1.0%2FApplication". The nested exception should"

First make sure DNS/host name resolution works. And remember you should use full qualified domain names for the Jazz servers, that can be relocated if you move to a different hardware later.

Francois-xavier Panaget commented Jul 07 '14, 4:23 a.m.

Hi,

In addition to Ralph's comment, make sure that the URLs
https://<servername>:9443/dm/scr
https://<servername>:9443/vvc/scr
are not giving any errors when accessed from your web browser. Instead it should return the rdf resource document for DM and VVC.

Regards,
François

Don Max commented Jul 07 '14, 8:37 a.m.

Hi, 

Thanks for the suggestions. I have made the changes . Still  getting the same error. am able to see the rdf resource documnet for DM and vvc when accessed from web browser.

My test setup :  The DM (4.0.6) is deployed on Linux+ WAS..(firewall /iptabes is disabled)  JTS(4.0.6) is on Windows + Tomcat express setup (antivirus /firewall diabled)

Request to service https://ibmtools.testing:9443/dm/handleSetup failed with status code 503 and response body: An error occurred while making a discovery request to "https://flame:9443/jts/discovery?type=http%3A%2F%2Fjazz.net%2Fxmlns%2Fprod%2Fjazz%2Fdiscovery%2F1.0%2FApplication". The nested exception should contain more details.

com.ibm.team.repository.common.TeamRepositoryException
com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.checkHttpResponse(FriendsAdminRestService.java:820)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService$UpdatingFri

Francois-xavier Panaget commented Jul 07 '14, 8:48 a.m.

Hi,

I would suggest you to open a PMR so that the support team could investigate further looking at the jts.log and dm.log and vvc.log etc...
Regards,
François

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
LUIZ DE ALMEIDA (230●1●61●91) | answered Aug 11 '14, 8:34 a.m.
edited Aug 11 '14, 8:34 a.m.
Don,
I am getting the same error...did you open a PMR? Could you install with this topology?
Comments
Don Max commented Aug 11 '14, 9:03 a.m.

Hi Luiz,

    I was using windows + Linux combination in my setup..  i changed to all linux and it worked for me.. i have not raised any PMR for this. one thing i noticed generally  is most of the issues regarding the design manager like JTS integration  can be resolved  by reinstalling the DM. 

LUIZ DE ALMEIDA commented Aug 11 '14, 12:52 p.m. | edited Aug 11 '14, 1:05 p.m.

Don, in my scenario, JTS and RTC are in a server1 and RSA-DM in server2. Both servers are linux, with the same configuration.
During setup, I can register the vvc and dm in JTS, but in the moment of configuring applications, an error is raised.
I think the problem is with certificates, but I do not know how to solve the problem.

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.