Skip to Content
author's profile photo Former Member
Former Member

Access to service registry from Netweaver developer center

Hi,

I've installed the SAP Netweaver 7.3 trial version on a VMWare instance on my computer. I managed to get the server running and a few sample processes. I'm currently trying to complete the tutorialCreate a Process-driven Composite Application with CE 7.2 - Part 1 found athttp://scn.sap.com/docs/DOC-7712

But i'm stuck at the visual composer step where i should connect to the service registry. I tried a lot of different thing but i can't access the registry through the sr_central shortcut in the browser and in the developer studio it just says it can't connect to the service registry.

I've configured the nd point URL to http://[host]:[port]/ServicesRegistrySiService/ServicesRegistrySiPort, which in my case ishttp://192.168.0.194:50000//ServicesRegistrySiService/ServicesRegistrySiPort.

I've given the administrator the following roles SERVICES_REGISTRY_READ_WRITE and the UDDI role UDDI_TierN.

I can access the sr central from the browser, but i get the following error when trying to access via eclipse.

Hope someone is able to help.

com.sap.ide.es.sr.runtime.ex.ErConnectException: The IP address of the configured services registry host sapnwce73 could not be determined at com.sap.ide.es.sr.runtime.internal.ConnectionIntercepter.createConnectException(ConnectionIntercepter.java:146) at com.sap.ide.es.sr.runtime.internal.ConnectionIntercepter.handleInvalidResponseCode(ConnectionIntercepter.java:210) at com.sap.ide.es.sr.runtime.internal.ConnectionIntercepter.checkWebServiceCommunicationError(ConnectionIntercepter.java:190) at com.sap.ide.es.sr.runtime.internal.ConnectionIntercepter.access$600(ConnectionIntercepter.java:40) at com.sap.ide.es.sr.runtime.internal.ConnectionIntercepter$SrCommunicationHandler.communicationError(ConnectionIntercepter.java:340) at com.sap.ide.es.sr.runtime.internal.ConnectionIntercepter$SrCommunicationHandler.handleCustomExceptions(ConnectionIntercepter.java:312) at com.sap.ide.es.core.core.importer.AbstractCommunicationHandler.handleComunicationException(AbstractCommunicationHandler.java:28) at com.sap.ide.es.sr.runtime.internal.ConnectionIntercepter$1.run(ConnectionIntercepter.java:102) at com.sap.ide.discovery.util.longop.CurrentThreadOperationRunner.run(CurrentThreadOperationRunner.java:29) at com.sap.ide.discovery.util.longop.recoverable.RecoverableOpRunner.run(RecoverableOpRunner.java:57) at com.sap.ide.es.sr.runtime.internal.ConnectionIntercepter.invoke(ConnectionIntercepter.java:71) at com.sap.ide.es.sr.runtime.internal.SecurityInterceptor.doInvocationWithSecureStoreCredentials(SecurityInterceptor.java:68) at com.sap.ide.es.sr.runtime.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:44) at com.sap.ide.es.sr.runtime.internal.InterceptorChainHead$ErManagerIH.invoke(InterceptorChainHead.java:46) at $Proxy38.getClassificationSystemInfos(Unknown Source) at com.sap.ide.es.sr.core.internal.lookup.LookupManager.getClassificationValueTree(LookupManager.java:123) at com.sap.ide.es.sr.ui.internal.lookup.updater.SearchPageUpdater$3.run(SearchPageUpdater.java:153) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: com.sap.ide.es.sr.runtime.internal.ConnectionIntercepter$SrCommunicationHandler$WebServiceCommException: com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 404: Not Found ... 13 more Caused by: com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 404: Not Found at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:196) at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:168) at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:83) at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:105) at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:587) at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:546) at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:531) at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:428) at com.sun.xml.internal.ws.client.Stub.process(Stub.java:211) at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:124) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107) at $Proxy37.getClassificationSystemsGreaterThanVersion(Unknown Source) at com.sap.ide.es.sr.runtime.internal.invocations.GetClassificationSystemInfosInvocation.getClassificationSystemInfos(GetClassificationSystemInfosInvocation.java:41) at com.sap.ide.es.sr.runtime.internal.invocations.GetClassificationSystemInfosInvocation.invoke(GetClassificationSystemInfosInvocation.java:24) at com.sap.ide.es.sr.runtime.internal.invocations.MethodDispatcher.invoke(MethodDispatcher.java:89) at com.sap.ide.es.sr.runtime.internal.ConnectionIntercepter$1.run(ConnectionIntercepter.java:98) ... 10 more

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 02, 2012 at 05:59 AM

    I ended up reinstalling the trial version and that helped

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.