Publish services from ESR to service registry

Hi,
first thanks for reading my question
I have a SAP test environment with a ESR. This ESR holds a lot of enterprise services (SAP's not custom programmed). I want to publish them from the ESR into the service directory to make them available for consumption in the NetWeaver developer studio?
Can anyone help me? I still searched sdn but I was not lucky.
thank you
felix

Hi,
goto windows>preferences>Web services-->Enterprise Service Browser
and give the corresponding details with respect to your server.
then login to ESB(Enterprise Service Builder),there you find all the services that are available to consume.
now goto CAF perspective and create a project in Development Infrastructure-->development component click on NEXT,
select Composite Application under SAP.COM root and give a name to your project.
you find External and Modeled under your project in CAF perspective.
right click on the external and import-->import the web service.
there you find 3 options and among them select ESR and select the corresponding Service and add and develop the application..
Regards
Manohar

Similar Messages

Classification lost in publishing service interface from ESR

Hello All,
I have followed a tutorial to model a service in ESR. Finally I want to publish this service interface in order to avail it from service registry but when I do so from ESR by pressing Publish Button it shows me error that Classification assigned from the Services Registry will be lost after publication. Would you like to continue?
and when I anyway to go publish the service then there is no Endpoint assigned to it. If I go to NWA to assign the endpoint then It does not show me any service in NWA>SOA Manager>Single Service Administration. Nevertheless, I see the service when I go to SR.
Does any one has idea??
Regards,
NK

I am letting you know the process which has worked for me.
Once the service is published there won't be any endpoint in the registry if you try to do it from ESR the way you have done. The default classification will be as Modeled and Not Released. You can add more classification after you find the service by searching for it in the Registry bu using the option "Add Classifications".
To add Endpoint and classification at the same time get the WSDL link from the service interface. You can generate WSDL form Integration Directory. You will have a WSDL URL along with that. You can take the URL and publish it separately in registry add endpoints and have separate classification. You need not go it to NWA.

Publish an Enterprise Service in Service Registry from SOAMANAGER

Dear All,
Can anyone please helpme with the procedure or step-by-step guide to Publish an Enterprise Serive in Service Registry from SOAMANAGER?
Thanks a lot.
Regards

Hi Chanakya,
Please find this help.sap.com link which gives the standard procedure for publishing services.
[Publishing a Service|http://help.sap.com/saphelp_nw70/helpdata/EN/44/b7f7e1354135e7e10000000a1553f7/frameset.htm]
Even this indicates use of WSPUBLISH Transaction.
I'll update if any new information is found.
Regards,
Alka.

Publishing Service in Service Registry from SOAMANAGER/WSPUBLISH

Hi,
When I am trying to publish services from SOAMANAGER to SERVICE REGISTRY all the services are published successfully
I am able see a message in display log.But when i check the services in service regisrty i am not able see any service ...what could be the problem?where i can check the log?
Thanks
Swathi

Hi Chanakya,
Please find this help.sap.com link which gives the standard procedure for publishing services.
[Publishing a Service|http://help.sap.com/saphelp_nw70/helpdata/EN/44/b7f7e1354135e7e10000000a1553f7/frameset.htm]
Even this indicates use of WSPUBLISH Transaction.
I'll update if any new information is found.
Regards,
Alka.

PI 7.1 How to delete a published service from the service registry?

Hello,
I have the same problem in the pi 7.1, like Rahul in CE (Composition Environment) with the deleting of published services.
How to delete a published service from the service registry?
In the WS navigator I found only this operation:
deleteClassificationSystemValues and deleteClassificationSystem
I miss the operation deleteService.
Have you an idea?
Bye
Stefan

Hi all,
I have opened an oss message and now I have an answer:
Use this Service: ServicesRegistrySiService and the operation deleteServices with the logical key of the service as parameter.
The logical key can be seen from the SR UI in the details of the endpoints.
Bye
Stefan

Error publishing WSDL to service registry

Hello,
We have just installed PI 7.1.
I have created a service in ESR.
When I click on the WSDL tab and click on Publish, I get the errors listed below.
My questions are:
1. Do I need to do any specific service registry configuration and what are those?
2. If you look at the errors, it says connection refused to localhost:50100. Where does it get that settings from? We have our instance installed on port 50000 not 50100.
Please help.
javax.ejb.EJBException: Exception raised from invocation of public com.sap.aii.ibrep.core.esregistry.ServicesRegistryPublication com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(com.sap.aii.ib.bom.gen.XiReference) throws com.sap.aii.utilxi.misc.api.ResourceException,java.rmi.RemoteException,com.sap.aii.ib.core.uddi.RegistryClientException method on bean instance [email protected] for bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|ServicesRegistryBean; nested exception is: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused); nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused); nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:173) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64) at $Proxy2731_10000.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy416_10000.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:316) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:173) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1622_10000.publishServiceInterface(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:340) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:964) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:703) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167) ... 68 more Caused by: java.io.IOException: Unable to connect to localhost:50100 - Connection refused at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:666) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:658) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:621) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:499) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:450) at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getRequestStream(ClientHTTPTransport.java:481) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:298) ... 72 more javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy416_10000.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:316) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:173) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1622_10000.publishServiceInterface(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:173) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64) at $Proxy2731_10000.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 58 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:340) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:964) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:703) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167) ... 68 more Caused by: java.io.IOException: Unable to connect to localhost:50100 - Connection refused at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:666) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:658) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:621) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:499) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:450) at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getRequestStream(ClientHTTPTransport.java:481) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:298) ... 72 more javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused); nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:307) at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy416_10000.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:316) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:173) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1622_10000.publishServiceInterface(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) ... 52 more Caused by: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:173) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64) at $Proxy2731_10000.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 58 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:340) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:964) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:703) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167) ... 68 more Caused by: java.io.IOException: Unable to connect to localhost:50100 - Connection refused at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:666) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:658) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:621) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:499) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:450) at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getRequestStream(ClientHTTPTransport.java:481) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:298) ... 72 more javax.ejb.EJBException: Exception raised from invocation of public com.sap.aii.ibrep.core.esregistry.ServicesRegistryPublication com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(com.sap.aii.ib.bom.gen.XiReference) throws com.sap.aii.utilxi.misc.api.ResourceException,java.rmi.RemoteException,com.sap.aii.ib.core.uddi.RegistryClientException method on bean instance [email protected] for bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|ServicesRegistryBean; nested exception is: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused); nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1622_10000.publishServiceInterface(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused); nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:307) at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy416_10000.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:316) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:173) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 32 more Caused by: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]2f for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxy~ejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) ... 52 more Caused by: javax.xml.ws.WebServiceException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:173) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64) at $Proxy2731_10000.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 58 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Unable to connect to localhost:50100 - Connection refused) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:340) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:964) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:703) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167) ... 68 more Caused by: java.io.IOException: Unable to connect to localhost:50100 - Connection refused at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:666) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.createSocket(HTTPSocket.java:658) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:621) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:499) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:450) at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getRequestStream(ClientHTTPTransport.java:481) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:298) ... 72 more

I think I have this figured out for now. I will go through the steps in "Technical Communication at Design Time".
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/5a6d50edc70db7e10000000a1553f6/frameset.htm
Regards
Haseeb

Publishing Service interfaces from SAP PI Repository

Hello All,
I am wondering is it possible to publish service interfaces from ESR in to repository? If so am I able to publish even outboud service interfaces along with inbound service interfaces? As in my ESR for Inbound I am unable to publish services in to Service registry... any reason? I want to get the concept behind it.
Thanks
Rajeev

Hi Rajeev,
The outbound web service invocation doesn't work like that. Refer to the guide below, see the section regarding developing a Web Service Consumer:
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06b6392-cde7-2c10-8f8b-bdea5d781dd9?quicklink=index&overridelayout=true]
You have the option of using SAP PI or not using PI for outbound Sync or Async Web Service calls. If you use PI then you would still need to generate the Consumer Proxy in the back-end & from there proceed with the SOAMANAGER route.
Regards, Trevor

Service Registry documentation URL and deleting published services?

Hello,
We are using SAP NetWeaver PI 7.1 SP 7. Do anyone know how you can control the published Documentation URL for published Service Interfaces in the Service Registry when you publish service interfaces directly from the ESR (from the WSDL tab on a Service Interface)?
Do anyone know if you can delete published service interfaces in the Service Registry if a service interface have been deactivated/deleted/is not used any more?
Regards,
Markus Johansson

Hi Markus,
There is anothre approach to delete services using API's.
Determine the WSDL Url of your Services Registry.
- Open SAP NetWeaver Administrator and choose SOA Management Application and Scenario Communication Single Service Administration .
- Search for ServicesRegistrySi and copy the Services Registry WSDL.
Open WS Navigator.
- In the WSDL Url field, enter the Services Registry WSDL and choose Next.
- All Services Registry API operations are displayed.
- Select operation hideServiceDefinitions and choose Next.
- Enter either the UDDI key or the logical key of the service definition you want to delete and choose Execute.
Both keys are displayed on the General tab in the Services Registry.
In case SR shows you as having no logical key for the service you are interested in removing.
There is another operation, findServiceDefintions, that can be used to search a name that will return the UDDI key. Take that value and plug it into the hideServiceDefintions uddiKey value.
Regards,
Jitender

Where is ESR ,Service Registry in ECC or SAP-PI?

Hi Gurus,
i am trying to develop a custom web service in ECC 6.0 with the end point "Function module' . i went to SE80 and did all the required things.
I want to know where is my ESR and service registry in ECC? Does it only exists in SAP-PI or it also exists in R/3 ECC 6.0 ? I dont know about it and if it exists in ECC 6.0 how does SOAMANAGER helps and what role does it play in that?
so when ECC 6.0 act as a service provider , our WSDL will be generated in R/3 ECC 6.0 so in that case where we register our service and how?
Well I read that SAP Service Registry along with Enterprise Services Repository are shipped with SAP NetWeaver Process Integration 7.1 and SAP NetWeaver Composite Environment 7.1 but then when we create our custom enterprise services in R/3 ECC System how ESR and Enterprise registry comes in to play? how this whole thing works?
Regards,
Mayank

Hi Mayank,
Key message: ESR + SR is part of PI and/or CE and doesn't exist on ECC.
Now regarding your confusion over service created on ECC from FM:
ESR is modeling tool which just model the service, and you can't really execute this service until unless you implement it somewhere (may be ECC). ESR act as central repository of meta-data of all services, however no service execute on ESR and it is just some sort of storage place. Real benefits ESR gives is that you can connect different systems with ESR and extract meta-data (WSDL) to implement webservice in backend (ECC or Java).
On other hand Service Registy act as yellow page where information about actual services is available so if you are looking for some specific service you look into yellopages (Service Registry) and locate the endpoint (actual address) of webservice, again service execute on backend systems not in Service Registry.
When you create service out of FM in ECC then you are still creating service but you are not using ESR, you can also publish service into Yellowpages(Service Registry) so others can locate your service. This approach is called inside-out development, for inside out development you don't need ESR.
You can also design same service in ESR first and then create proxy in ECC and call FM inside proxy, this approach is known as outside-in approach of developing services.
On SCN you can find plenty of information on this subject, and remember outside-in/top down approach is recommended (design first then develop).
Regards,
Gourav

Consume service from esr

HI guys, now i access esr with ESRAdmin from NWDS,but i was denied?what roles should i have to access ESR from NWDS?Thanks

Hi look at this Thread
I think so your quessr is solved here , look at the suggesion given by Jitender
Re: Service Registry documentation URL and deleting published services?
Regards
Abhishek

Publish of a Service over Service Registry - com.sap.esi.uddi.sr.api.exce

Hello
I try to publish a Service over the Service Registry UI but this results in a com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: java.lang.NullPointerException->java.lang.NullPointerException
Is the problem the schema import or the two address locations ?
We use ESR CE 7.1 SP3
Kind regards
Gerald Eder
The WSDL looks like :
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://test.com/soa/" xmlns:i0="http://test.com/soa" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://test.com/soa/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:import namespace="http://test.com/soa" location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx?wsdl=wsdl1" />
- <wsdl:types>
- <s:schema targetNamespace="http://test.com/soa/">
<s:import schemaLocation="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx?schema=schema1" namespace="http://test.com/soa" />
</s:schema>
</wsdl:types>
- <wsdl:service name="CustomerID">
- <wsdl:port name="CustomerIDBinding" binding="i0:CustomerIDBinding">
<soap:address location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx" />
</wsdl:port>
- <wsdl:port name="CustomerIDBinding1" binding="i0:CustomerIDBinding1">
<soap12:address location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:de

Hi Rajesh,
Many thanks for your prompt reply, however this note 1267817 was already applied before posting message.
B/W I have observed that in spite of the error the service published multiple times in the registry (perhaps each try to publish resulted a entry in SR).
Really crazy error, any other suggestion??
Regards, Immy.

Error publishing service in Service Registry

Hi experts.
I've configured Service Registry in a SAP PI 7.11. Everything seems to work correctly but I can't publish services there. When I try to publish from Directory or directly in Service Registry by wsdl I'm getting this error:
com.sap.aii.ib.core.uddi.RegistryClientException: Services registry is not available; for more information, see the log
     at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:440)
     at com.sap.aii.ibdir.server.wsquery.WSQUDDIPSPublishTB.execute(WSQUDDIPSPublishTB.java:91)
     at com.sap.aii.ibdir.core.simulation.DefaultTaskBroker.execute(DefaultTaskBroker.java:171)
     at com.sap.aii.ibdir.server.simulation.TaskQueryService.specialQuery(TaskQueryService.java:33)
     at com.sap.aii.ib.server.query.SpecialQueryServiceProvider$SpecialQueryServiceImpl.specialQuery(SpecialQueryServiceProvider.java:63)
     at com.sap.aii.ib.server.query.QueryServiceImpl.specialQuery(QueryServiceImpl.java:443)
     at com.sap.aii.ib.server.query.QueryServiceBean.specialQuery(QueryServiceBean.java:112)
     at sun.reflect.GeneratedMethodAccessor762.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:592)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
     at $Proxy1646.specialQuery(Unknown Source)
     at sun.reflect.GeneratedMethodAccessor761.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:592)
     at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:362)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
I think is a authorization problem but I have role to read and write in service registry. I can see this error in Service Registry Trace
Invalid Response code (401). Server [http://xxxxxx:50000/uddi/api/publish/] returned message [Unauthorized].
Any idea? Maybe the user you have to fill in Service Registry Configuration Wizard?
Regards
Edited by: Christian Abad Chico on Feb 20, 2012 1:00 PM

Hi,
It looks like you are missing some Services Registry preconfiguration. Please find a description how to configure the Services Registry under the SAP Help document below:
http://help.sap.com/saphelp_nwce711/helpdata/en/47/d391d7b8fc3c83e10000000a42189c/frameset.htm
There is also a wizard that you can use for this purpose:
http://help.sap.com/saphelp_nwce711/helpdata/en/f7/6182bd68434595ba5105a0a346efcc/frameset.htm
Hope this helps,
Greg

Error while publishing service definition in Services Registry

I created a service interface in ESR and published the WSDL to my Services Registry. Now when I go to the "Publish" tab in the Services Registry to provide a definition for this service, after entering the WSDL and clicking on "Next" I get a pop-up for username and password. Neither the ESRAdmin, the user with Services Registry Read Write permissions nor the Administrator credentials seem to work.
I get the following error:
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='WSDL_WSDL_EXCEPTION', Arguments: [' WSDL 'option' can not have child 'wsp:Policy' of namespace 'http://schemas.xmlsoap.org/ws/2004/09/policy' !', 'http://localhost:50000/rep/publicwsdl/ext/?service=publicwsdl&method=serviceinterface&p1=e77cf5e08e7f11dda32c001b77a40d2b&p2=c898d96af94a32fab2382f09c93a975d']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='WSDL_WSDL_EXCEPTION', Arguments: [' WSDL 'option' can not have child 'wsp:Policy' of namespace 'http://schemas.xmlsoap.org/ws/2004/09/policy' !', 'http://localhost:50000/rep/publicwsdl/ext/?service=publicwsdl&method=serviceinterface&p1=e77cf5e08e7f11dda32c001b77a40d2b&p2=c898d96af94a32fab2382f09c93a975d']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationMessage: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='WSDL_WSDL_EXCEPTION', Arguments: [' WSDL 'option' can not have child 'wsp:Policy' of namespace 'http://schemas.xmlsoap.org/ws/2004/09/policy' !', 'http://localhost:50000/rep/publicwsdl/ext/?service=publicwsdl&method=serviceinterface&p1=e77cf5e08e7f11dda32c001b77a40d2b&p2=c898d96af94a32fab2382f09c93a975d']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en
I am using CE 7.1 EHP1.
Please advice.
Regards,
Puja

Hi Puja,
the below blog explains another way how to publish your web services on the services registry:
Publish your Services to ES Registry
Best regards,
Yasar

Error while publishing thru Service registry

Hi friends
While publishing service thru service registry, I am getting this error message.
Any Solution?
Thanks
-Mitesh
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationException: Cannot load WSDL due to "Invalid Response Code: (401) Unauthorized. The requested URL was:"http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1"". Check that the specified WSDL URL "http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1" points to WS-I Basic Profile 1.1 compliant WSDL Definitions file->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationException: Cannot load WSDL due to "Invalid Response Code: (401) Unauthorized. The requested URL was:"http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1"". Check that the specified WSDL URL "http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1" points to WS-I Basic Profile 1.1 compliant WSDL Definitions file->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationMessage: Cannot load WSDL due to "Invalid Response Code: (401) Unauthorized. The requested URL was:"http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1"". Check that the specified WSDL URL "http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1" points to WS-I Basic Profile 1.1 compliant WSDL Definitions file

Hello Mitesh
Would this forum question be interesting for you?
[ESR post-installation tasks are missing|ESR post-installation tasks are missing]
regards
Rathish

Error while importing Web Service from Services Registry

I am trying to import a WebService in NWDS for CE 7.1 EHP1. This webservice is from an ABAP system and is published on the local service registry.
However, during import, I get the following error, what might be the problem:
java.lang.reflect.InvocationTargetException
     at com.sap.caf.designer.ui.actions.es.WSDownloadAction$1.run(WSDownloadAction.java:453)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
Caused by: com.sap.caf.foundation.caf_import.CAFDTImportException: Cannot find imported schema for referred type {n0,char10}
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformReferedTypeDefinition(XSD2CAFTypesTransformer.java:233)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformElementDecaration2Attribute(XSD2CAFTypesTransformer.java:571)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.iterateThroughModelGruop(XSD2CAFTypesTransformer.java:539)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformComplexTypeDefinition(XSD2CAFTypesTransformer.java:490)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformReferedTypeDefinition(XSD2CAFTypesTransformer.java:256)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformGlobalElementDeclaration(XSD2CAFTypesTransformer.java:181)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformGlobalElementDeclarations(XSD2CAFTypesTransformer.java:114)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transform(XSD2CAFTypesTransformer.java:101)
     at com.sap.caf.foundation.caf_import.wsdl.CAFDTWSDLImporter.tranformImportedWSDLs(CAFDTWSDLImporter.java:350)
     at com.sap.caf.foundation.caf_import.wsdl.CAFDTWSDLImporter.doImport(CAFDTWSDLImporter.java:195)
     at com.sap.caf.designer.ui.actions.es.WSDownloadAction$1.run(WSDownloadAction.java:441)
     ... 1 more

I am trying to import a WebService in NWDS for CE 7.1 EHP1. This webservice is from an ABAP system and is published on the local service registry.
However, during import, I get the following error, what might be the problem:
java.lang.reflect.InvocationTargetException
     at com.sap.caf.designer.ui.actions.es.WSDownloadAction$1.run(WSDownloadAction.java:453)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
Caused by: com.sap.caf.foundation.caf_import.CAFDTImportException: Cannot find imported schema for referred type {n0,char10}
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformReferedTypeDefinition(XSD2CAFTypesTransformer.java:233)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformElementDecaration2Attribute(XSD2CAFTypesTransformer.java:571)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.iterateThroughModelGruop(XSD2CAFTypesTransformer.java:539)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformComplexTypeDefinition(XSD2CAFTypesTransformer.java:490)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformReferedTypeDefinition(XSD2CAFTypesTransformer.java:256)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformGlobalElementDeclaration(XSD2CAFTypesTransformer.java:181)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transformGlobalElementDeclarations(XSD2CAFTypesTransformer.java:114)
     at com.sap.caf.foundation.caf_import.xsd.XSD2CAFTypesTransformer.transform(XSD2CAFTypesTransformer.java:101)
     at com.sap.caf.foundation.caf_import.wsdl.CAFDTWSDLImporter.tranformImportedWSDLs(CAFDTWSDLImporter.java:350)
     at com.sap.caf.foundation.caf_import.wsdl.CAFDTWSDLImporter.doImport(CAFDTWSDLImporter.java:195)
     at com.sap.caf.designer.ui.actions.es.WSDownloadAction$1.run(WSDownloadAction.java:441)
     ... 1 more

Publish services from ESR to service registry

Similar Messages

Maybe you are looking for