Publishing Enterprise Services

Hi, folks i have to search in all EHP if there es an SAP enterprise service that works just like an SAP MM ERP transaction. I have a list of all MM trx and i don´t know where to search. if they exist, is there an easy way to search those enterprise services?
Hope you can help me.
thanks in advance and Regards,
Diego

Hi Diego,
Try browsing the [ES Workplace |http://www.sdn.sap.com/irj/sdn/esworkplace;jsessionid=(J2EE3417700)ID1691934950DB01981249436239136538End]-> ERP Process Components -> Product Data Maintenance (process component) -> Manage Material In (service interface)
Hope it helps
Regards,
Eduardo

Similar Messages

Error while publishing enterprise service from ES builder.

Hi Friends
I am not able to publish my service from ES builder. I am getting this error after publishing.
Please let me know if anyone has faced similar problem and has solution for it.
Thanks
-Mitesh
This is the error log generated.
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 com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean@c8c9bc 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] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; 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] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. 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] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; 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] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. 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] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) 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 $Proxy61_10002.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:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) 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 $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) 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: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 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] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. 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 $Proxy61_10002.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:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) 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 $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) 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: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) 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) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 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] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; 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] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. 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 $Proxy61_10002.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:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) 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 $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) 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] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. 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) ... 50 more Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) 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) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 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 com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean@c8c9bc 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] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; 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] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. 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 $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) 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] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; 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] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. 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 $Proxy61_10002.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:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) 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) ... 31 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] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxy~ejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. 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) ... 50 more Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) 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) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more

Hi ,
try to change the ServiceRegistry Logical Port
In NetWeaver Administrator under SOA Management _Business Administration _Web Services Administration
Client Proxy Name: ServicesRegistrySi
Authentication: User name/password
Role: SERVICES_REGISTRY_READ_WRITE
Should help u out

ESW: Publishing Enterprise services in PI 7.1

Hi,
My Scenario was Webservices to ID
Is WS Navigator is necessary for testing the Enterprise Services.
How to define a service interface in the service registry and if i need to create any purchase order how do and where do i need to import the WSDL file ..
What is Service Registry and what is the differeince b/w the WS Navigator and Service Registry.
Where this comes into picture in PI
regards
Kishore

Hi Gourav,
Thanks Gourav for your valuable reply,
Still i am facing the problem,
When i give the values as of for the above case i am facing with the below error
An error has occurred. Maybe the request is not accepted by the server:
SRT: Authorization denied
The below is the request message
POST /sap/bc/srt/xip/sap/ecc_purchaseorder005qr/310/ecc_purchaseorder005qr/ecc_purchaseorder005qr_binding HTTP/1.1
Host: scc10ykf.rim.net:8010
Content-Type: text/xml; charset=UTF-8
Connection: close
Authorization: <value is hidden>
SAP-PASSPORT: 2A54482A0200B900007363633130796B665F4543445F31303337333037353000000000000000000000000147756573740000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000017363633130796B665F4543445F3130333733303735300000000000000000000063663133383632303838303931316465626338333030316632393665396464322A54482A
Content-Length: 877
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Header><sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/"><enableSession>true</enableSession></sapsess:Session></SOAP-ENV:Header><SOAP-ENV:Body><ns1:PurchaseOrderERPByIDQuery_sync_V1 xmlns:ns1='http://sap.com/xi/SAPGlobal20/Global'><PurchaseOrderSelectionByID><SelectionByPurchaseOrderID><IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode><LowerBoundaryPurchaseOrderID>0000205000</LowerBoundaryPurchaseOrderID><UpperBoundaryPurchaseOrderID>0000205132</UpperBoundaryPurchaseOrderID></SelectionByPurchaseOrderID></PurchaseOrderSelectionByID></ns1:PurchaseOrderERPByIDQuery_sync_V1></SOAP-ENV:Body></SOAP-ENV:Envelope>
This is the response message which i got
HTTP/1.1 500 Internal Server Error
Set-Cookie: <value is hidden>
content-type: text/xml; charset=utf-8
content-length: 1762
accept: text/xml
sap-srt_id: 20090813/090413/v1.00_final_6.40/4A8356473B0B55C5E10000000A51143C
server: SAP Web Application Server (1.0;701)
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Header></soap-env:Header><soap-env:Body><soap-env:Fault><faultcode>soap-env:Server</faultcode><faultstring xml:lang="en">SRT: Authorization denied</faultstring><detail><ns:SystemFault xmlns:ns="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/"><Host>Provider</Host><Component>SECURITY</Component><ChainedException><Exception_Name>CX_SOAP_CORE</Exception_Name><Exception_Text>SRT: Authorization denied</Exception_Text></ChainedException></ns:SystemFault><ns:SystemFault xmlns:ns="http://www.sap.com/webas/711/soap/runtime/abap/fault/system/"><Host>Provider</Host><Component>SECURITY</Component><ChainedException asx:root="asx:abap" version="1.0" xmlns:asx="http://www.sap.com/abapxml"><asx:values><EXCEPTION href="#o201"></EXCEPTION></asx:values><asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary"><cls:CX_SOAP_CORE id="o201"><CX_ROOT><TEXTID>0018FE864EEE1DECA69CF9C71ACB337F</TEXTID><PREVIOUS></PREVIOUS><KERNEL_ERRID></KERNEL_ERRID><INTERNAL_SOURCE_POS><PROGID>99</PROGID><CONTID>1077</CONTID></INTERNAL_SOURCE_POS></CX_ROOT><CX_NO_CHECK></CX_NO_CHECK><CX_SOAP_CORE><E_LOCATION><CLASS>CL_WS_SECURITY_PROTOCOL</CLASS><METHOD>AUTHORITY_CHECK</METHOD><ID>0</ID></E_LOCATION><E_TEXT>SRT: Authorization denied</E_TEXT><E_ID>1100</E_ID><E_FAULT_LOCATION>1</E_FAULT_LOCATION><E_AREA>SECURITY</E_AREA><E_HOST>1</E_HOST><E_PROCESS_CONTROL></E_PROCESS_CONTROL></CX_SOAP_CORE></cls:CX_SOAP_CORE></asx:heap></ChainedException></ns:SystemFault></detail></soap-env:Fault></soap-env:Body></soap-env:Envelope>
i am giving the purchase order number lowerbound and upperbound of the range but i am getting this error
Request you to help on this..
Is there any issue with SRT: Authorization error.. (Any Configurations to be avoid this)
regards
Kishore

Procedure to publish an enterprise service to ESR

Hi,
I know the creation of a web service from the abap end through sproxy transaction.
After the creation of web service... what is the procedure to publish it in ESR.
Thanks & Regards,
Aleem.

Hi Aleem,
Now WSCONFIG and WSADMIN are obsolete and SAP has come up with new Transaction SOAMANAGER just check the blog.
/people/bv.pillai/blog/2007/09/18/configuring-publishing-enterprise-services-from-sap-business-suite-system-into-nwce-netweaver-composition-environment-services-registry
Venkat

Problems While Publishing a Service in Service Registry

Hi folks,
while I was following the diffrent steps that were described in this blog:
/people/bv.pillai/blog/2007/09/18/configuring-publishing-enterprise-services-from-sap-business-suite-system-into-nwce-netweaver-composition-environment-services-registry
i´ve get an error.
After execute the trx a pop up window asking me the mndt user and pass of the '/ESRegistryWS/BasicAuthConfig' path. I ´ve insert the user and pass of the administrator´s account in the CE. is that ok? .
I get this error Msg.
"Exception raised during physical system publication. Code : '10150'"
Can anyone help me with this problem please?
Thanks for all.
Diego.
Thanks for all,
Diego.

Lei Ji, you can do what Mohd Tauseef told me.
try to change the ServiceRegistry Logical Port
In NetWeaver Administrator under SOA Management _Business Administration _Web Services Administration
Client Proxy Name: ServicesRegistrySi
Authentication: User name/password
Role: SERVICES_REGISTRY_READ_WRITE
have you done it? this is the only role that i used in CE.
Greatings.
Diego.

SICF and SOAMANAGER for using enterprise services

Hi,
I need to publish enterprise services from my ERP backend to the Services Registry on my PI server.
According to the tutorial (https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20b723f8-a422-2c10-aca5-fe64eeda1ff2), I have to first activate the services in SICF and create endpoints for the corresponding services in SOAMANAGER.
I suppose, only after that I could publish the configured services in SR using WSPUBLISH, right?
Now, if let say I want to publish all enterprise services in my ERP backend, I have to select all the services in the WSPUBLISH, as stated in the instructions of the tutorial (http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/108ef7ba-8abd-2a10-f787-d5f29c5f1b88). But the problem is, do I need to configure every single enterprise services using SOAMANAGER? If not, only the service definitions would be published?
Hopefully someone could clear my doubts.
Thanks.
Regards,
Joon Meng

Hi Venu,
I could not see any nodes for end points in the SICF. So I manually created a service endpoint in SOAMANAGER and then published it to the Services Registry via WSPUBLISH. However, I was surprised to see two endpoints (one was created by me) in the Services Registry.
The service is "ECC_PURCHASEORDERCRTRC" and there are two endpoints for it in the Services Registry:
1. ECC_PURCHASEORDERCRTRC_Binding (created by me)
2. PurchaseOrderCreateRequestConfirmation_InSoapBinding
When I open the service in SOAMANAGER and navigate to the "Configuration" tab, I only see the endpoint from me (with "Manually Created" for Creation Type).
I wonder if the 2nd endpoint was created automatically during the service publishing?
Regards,
Joon Meng

Comsume enterprise service from service registry

HI guys, now I want to consume enterprise services form ECC6 in NWDS, should me publish enterprise services to service registry? and then I consume services from service registry. How should i do?thanks

Hi lei,
If u can access the ES workplace u can directly consume the service by downloading the wsdl either locally or through the service registry.To use the SR u would have to use the S user ID of ES workplace.
Just check this blog by Boris.It is a step by step approach to consume an ES wsdl through a simple java client using NWDS.
Remember to uncheck wsdl validator in NWDS before u dwnld wsdl in NWDS,else it might give an error.
How-To-Guide for consuming a Web Service with a standalone client using SAP NetWeaver Application Server Java(TM) EE 5 Edition
Once u have tried this, go through this link
http://help.sap.com/saphelp_nwce10/helpdata/en/46/7ffe4b393650d1e10000000a155369/content.htm
here is a link that will help u conf NWDS for the same:
http://help.sap.com/saphelp_nwce10/helpdata/en/46/7ffdb4393650d1e10000000a155369/content.htm
Should help u out

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.

How can i easy to publish multiple enterprise services

Hi All,
I'm trying to use an enterprise service at multiple clients.
Now, When create a new enterprise service, I create end point and publish service all the time.
If we'd like to use multiple enterprise services at multiple clients,
Do I have to create end point & publish services to each of multiple enterprise services?
(For instance, 3 clients * 10 enterprise services = 30 creates and publishes ??)
Could you tell me an easy way to it.
Thanks
Masahiro

We can achieve multiple enterprise services publishing by configuring Service registry between client server and esr.
Edited by: Murthy Karaka on Feb 3, 2010 1:49 PM

Enterprise Service publish in SR with "Not Released State".

Hi guys,
i need someone who can help me with this problem, please.
I've model an Enterprise Service in the ESR, then i´ve implement it in an Ecc 6.0 ( Generating the Proxy and inserting the business logic ).
Note : When i´m trying to generate de proxy the state of the Service Interface is "Not released", but i can´t change this status, but when i save and activate it no errors appear.
Then in the Service Registry i search this Service published, The crazy thing is that i can see it published in the SR but i can´t consume it in the Visual Composer because it not appears in the Service Registry search menu. I can only see the WS that i published manually without modeling it directly from the Ecc 6.0.
Regards,
Diego Rodriguez.

Hi
You can change this in the Enterprise Services repository. Please go to the Service Interface > Mark it editable > From the menu options on top, choose Properties > and one of the properties there is Status, which will be not released.
Mark it as released.
regards
Rathish

Publish BUS1065 object to Enterprise Service Bus (Tibco)

Dear forum members,
We are trying to find out if a concept we designed will work. Our goal is to publish a full business object e.g. BUS 1065 (Employee) to the Enterprise Service Bus (Tibco JMS technology).
We plan to customize change pointers to the BUS object, which will trigger a replicate of the BUS object. We hope to create an outbound iDoc which will contain the full BUS object. The ESB solution will trigger a JMS publish on receiving the iDoc.
Does anybody has experience with replicating a business object for a non SAP receiver? Will our concept work?
kind regards,
Richard

Dear forum members,
We are trying to find out if a concept we designed will work. Our goal is to publish a full business object e.g. BUS 1065 (Employee) to the Enterprise Service Bus (Tibco JMS technology).
We plan to customize change pointers to the BUS object, which will trigger a replicate of the BUS object. We hope to create an outbound iDoc which will contain the full BUS object. The ESB solution will trigger a JMS publish on receiving the iDoc.
Does anybody has experience with replicating a business object for a non SAP receiver? Will our concept work?
kind regards,
Richard

What is causing my "Publish Enterprise Summaries" in Global Scheduled Services to fail

We are a relatively new P6 installation. Publish Enterprise Summaries has failed from the beginning. The only error I see in the log file is below. Any clue to what we need to fix?
2014-10-21 06:37:57:[TASK]:[PxEpsSpread]: [4] CORE(SQL): Errors occurred when executing following statement: DECLARE vupdate_date varchar2(20); msg varchar(2000); vspid number; vtotal pls_integer := 0; vupd pls_integer := 0; vins pls_integer := 0; i_start pls_integer; i_end pls_integer; vsec number; vrate number; start_time timestamp; end_time timestamp; vmsg varchar2(1000); vmsg_cnt pls_integer := 0; df varchar2(22) := 'yyyy-mm-dd hh24:mi:ss'; vparent_wbs_id projwbs.parent_wbs_id%type; vobs_id obs.obs_id%type; vobs_name obs.obs_name%type; BEGIN vupdate_date := :update_date; vspid := sys_context('USERENV', 'SID') ; i_start := dbms_utility.get_time; execute immediate 'select current_timestamp from dual' into start_time; for erec in (SELECT distinct eh.parentobjectid FROM project p, projwbs pw, epshierarchy eh WHERE p.project_flag='Y' and p.proj_id = pw.proj_id and pw.proj_node_flag ='Y' and eh.childobjectid = pw.parent_wbs_id and p.orig_proj_id IS NULL and p.px_last_update_date > to_date(vupdate_date,'yyyy-mm-dd hh24:mi:ss') ) LOOP select parent_wbs_id, pw.obs_id, o.obs_name into vparent_wbs_id, vobs_id, vobs_name from projwbs pw, obs o where pw.obs_id = o.obs_id and pw.wbs_id = erec.parentobjectid; DELETE /*+ INDEX(EPSSPREAD NDX_EPSSPREAD_OBJID) */ FROM EPSSPREAD where ObjectID = erec.parentobjectid; INSERT INTO EpsSpread (OBJECTID ,ID ,NAME ,PARENTOBJECTID ,PROJECTOBJECTID ,OBSOBJECTID ,OBSNAME ,STARTDATE ,ENDDATE ,ACTUALLABORUNITS ,ACTUALNONLABORUNITS ,ATCOMPLETIONLABORUNITS ,ATCOMPLETIONNONLABORUNITS ,BASELINEPLANNEDLABORUNITS ,BASELINEPLANNEDNONLABORUNITS ,EARNEDVALUELABORUNITS ,ESTIMATEATCOMPLETIONLABORUNITS ,ESTIMATETOCOMPLETELABORUNITS ,PLANNEDVALUELABORUNITS ,REMAININGLABORUNITS ,REMAININGNONLABORUNITS ,ACTUALCOST ,ACTUALEXPENSECOST ,ACTUALLABORCOST ,ACTUALMATERIALCOST ,ACTUALNONLABORCOST ,ACTUALTOTALCOST ,ATCOMPLETIONEXPENSECOST ,ATCOMPLETIONLABORCOST ,ATCOMPLETIONMATERIALCOST ,ATCOMPLETIONNONLABORCOST ,ATCOMPLETIONTOTALCOST ,BASELINEPLANNEDEXPENSECOST ,BASELINEPLANNEDLABORCOST ,BASELINEPLANNEDMATERIALCOST ,BASELINEPLANNEDNONLABORCOST ,BASELINEPLANNEDTOTALCOST ,EARNEDVALUECOST ,ESTIMATEATCOMPLETIONCOST ,ESTIMATETOCOMPLETECOST ,PLANNEDVALUECOST ,REMAININGEXPENSECOST ,REMAININGLABORCOST ,REMAININGMATERIALCOST ,REMAININGNONLABORCOST ,REMAININGTOTALCOST ) SELECT a.objectid, a.id, a.name, a.parentobjectid, a.projectobjectid, a.obsobjectid, a.obsname, a.startdate, a.enddate, a.ACTUALLABORUNITS, a.ACTUALNONLABORUNITS, a.ATCOMPLETIONLABORUNITS, a.ATCOMPLETIONNONLABORUNITS, a.BASELINEPLANNEDLABORUNITS, a.BASELINEPLANNEDNONLABORUNITS, a.EARNEDVALUELABORUNITS, a.ESTIMATEATCOMPLETIONLABORUNITS, a.ESTIMATETOCOMPLETELABORUNITS, a.PLANNEDVALUELABORUNITS, a.REMAININGLABORUNITS, a.REMAININGNONLABORUNITS, a.ACTUALCOST, a.ACTUALEXPENSECOST, a.ACTUALLABORCOST, a.ACTUALMATERIALCOST, a.ACTUALNONLABORCOST, a.ACTUALTOTALCOST, a.ATCOMPLETIONEXPENSECOST, a.ATCOMPLETIONLABORCOST, a.ATCOMPLETIONMATERIALCOST, a.ATCOMPLETIONNONLABORCOST, a.ATCOMPLETIONTOTALCOST, a.BASELINEPLANNEDEXPENSECOST, a.BASELINEPLANNEDLABORCOST, a.BASELINEPLANNEDMATERIALCOST, a.BASELINEPLANNEDNONLABORCOST, a.BASELINEPLANNEDTOTALCOST, a.EARNEDVALUECOST, a.ESTIMATEATCOMPLETIONCOST, a.ESTIMATETOCOMPLETECOST, a.PLANNEDVALUECOST, a.REMAININGEXPENSECOST, a.REMAININGLABORCOST, a.REMAININGMATERIALCOST, a.REMAININGNONLABORCOST, a.REMAININGTOTALCOST FROM (select /*+ INDEX(EH NDX_EPSHIER_PARENTOBJ) INDEX(PS NDX_PROJSPREAD_PARENTEPSID) */ eh.parentObjectid objectid, eh.parentid ID, eh.parentname NAME, vparent_wbs_id ParentObjectId, eh.parentprojectid ProjectObjectId, vobs_id ObsObjectId, vobs_name ObsName, ps.startdate,ps.enddate, SUM(ps.ACTUALLABORUNITS) ACTUALLABORUNITS, SUM(ps.ACTUALNONLABORUNITS) ACTUALNONLABORUNITS, SUM(ps.ATCOMPLETIONLABORUNITS) ATCOMPLETIONLABORUNITS, SUM(ps.ATCOMPLETIONNONLABORUNITS) ATCOMPLETIONNONLABORUNITS, SUM(ps.BASELINEPLANNEDLABORUNITS) BASELINEPLANNEDLABORUNITS, SUM(ps.BASELINEPLANNEDNONLABORUNITS) BASELINEPLANNEDNONLABORUNITS, SUM(ps.EARNEDVALUELABORUNITS) EARNEDVALUELABORUNITS, SUM(ps.ESTIMATEATCOMPLETIONLABORUNITS) ESTIMATEATCOMPLETIONLABORUNITS, SUM(ps.ESTIMATETOCOMPLETELABORUNITS) ESTIMATETOCOMPLETELABORUNITS, SUM(ps.PLANNEDVALUELABORUNITS) PLANNEDVALUELABORUNITS, SUM(ps.REMAININGLABORUNITS) REMAININGLABORUNITS, SUM(ps.REMAININGNONLABORUNITS) REMAININGNONLABORUNITS, SUM(ps.ACTUALCOST) ACTUALCOST, SUM(ps.ACTUALEXPENSECOST) ACTUALEXPENSECOST, SUM(ps.ACTUALLABORCOST) ACTUALLABORCOST, SUM(ps.ACTUALMATERIALCOST) ACTUALMATERIALCOST, SUM(ps.ACTUALNONLABORCOST) ACTUALNONLABORCOST, SUM(ps.ACTUALTOTALCOST) ACTUALTOTALCOST, SUM(ps.ATCOMPLETIONEXPENSECOST) ATCOMPLETIONEXPENSECOST, SUM(ps.ATCOMPLETIONLABORCOST) ATCOMPLETIONLABORCOST, SUM(ps.ATCOMPLETIONMATERIALCOST) ATCOMPLETIONMATERIALCOST, SUM(ps.ATCOMPLETIONNONLABORCOST) ATCOMPLETIONNONLABORCOST, SUM(ps.ATCOMPLETIONTOTALCOST) ATCOMPLETIONTOTALCOST, SUM(ps.BASELINEPLANNEDEXPENSECOST) BASELINEPLANNEDEXPENSECOST, SUM(ps.BASELINEPLANNEDLABORCOST) BASELINEPLANNEDLABORCOST, SUM(ps.BASELINEPLANNEDMATERIALCOST) BASELINEPLANNEDMATERIALCOST, SUM(ps.BASELINEPLANNEDNONLABORCOST) BASELINEPLANNEDNONLABORCOST, SUM(ps.BASELINEPLANNEDTOTALCOST) BASELINEPLANNEDTOTALCOST, SUM(ps.EARNEDVALUECOST) EARNEDVALUECOST, SUM(ps.ESTIMATEATCOMPLETIONCOST) ESTIMATEATCOMPLETIONCOST, SUM(ps.ESTIMATETOCOMPLETECOST) ESTIMATETOCOMPLETECOST, SUM(ps.PLANNEDVALUECOST) PLANNEDVALUECOST, SUM(ps.REMAININGEXPENSECOST) REMAININGEXPENSECOST, SUM(ps.REMAININGLABORCOST) REMAININGLABORCOST, SUM(ps.REMAININGMATERIALCOST) REMAININGMATERIALCOST, SUM(ps.REMAININGNONLABORCOST) REMAININGNONLABORCOST, SUM(ps.REMAININGTOTALCOST) REMAININGTOTALCOST FROM projectspread ps,epshierarchy eh WHERE eh.childobjectid = ps.parentepsobjectid AND eh.parentobjectid = erec.parentobjectid group by eh.parentObjectid, eh.parentid, eh.parentname, vparent_wbs_id, eh.parentprojectid, vobs_id, vobs_name, ps.startdate, ps.enddate ) a; vins := vins+SQL%ROWCOUNT; commit; END LOOP; vtotal := vins; i_end := dbms_utility.get_time; execute immediate 'select current_timestamp from dual' into end_time; vsec := round(( (i_end-i_start) * 0.01), 3); if vsec > 0 then vrate := round( vtotal / vsec , 3); else vrate := 0; end if; vmsg := 'Success[true],' || ' Start[' || to_char(start_time, df) || '], End[' || to_char(end_time, df) || '], ' || ' Elapsed[' || trim(to_char(vsec, '99999.99')) || 's], ' || ' Count[' || trim(to_char(vtotal, '999999999')) || '], ' || ' Throughput[' || trim(to_char(vrate, '99999999.99')) || '/s], ' || ' Pages[1], ' || ' Inserted[' || trim(to_char(vins, '999999999')) || '], ' || ' Updated[' || trim(to_char(vupd, '999999999')) || ']'; vmsg_cnt := vmsg_cnt + 1; DBMS_OUTPUT.PUT_LINE(vmsg); EXCEPTION when others then ROLLBACK; vmsg := 'Success[false]'; vmsg_cnt := vmsg_cnt + 1; DBMS_OUTPUT.PUT_LINE(vmsg); vmsg := SQLERRM; vmsg_cnt := vmsg_cnt + 1; DBMS_OUTPUT.PUT_LINE(vmsg); raise; END;

>
Efstratios Karaivazoglou wrote:
> Which version of BOBJ (incl. SP and FP) are you using?
>
> Regards,
>
> Stratos
BusinessObjects XI 3.1 SP2
FixPack 2.6
Edited by: Erika Atencio on Sep 1, 2010 8:46 PM

XML Publisher Enterprise error

Dear all:
When I create and run the report in the "XML Publisher Enterprise Release 5.6.2" ,shows the error as follow, how can I solve the problem?
javax.servlet.ServletException: Attribute missing in : 'url'
     at oracle.apps.xdo.servlet.XDOServlet.handleRequest(XDOServlet.java:211)
     at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:138)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:52)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:629)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
my environment is : XML Publisher Release 5.6.2
Platform is : Windows XP 32bit
Regards
Terry

Hi Helios:
What is the error?
javax.servlet.ServletException: Attribute missing in : 'url'
at oracle.apps.xdo.servlet.XDOServlet.handleRequest(XDOServlet.java:211)
at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:138)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:52)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:629)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)

How to get the UDDI Key to publish a service provider system in SR?

Hi,
I am following instruction in appendix 1 & 2 of the white paper at https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1079b1af-dcb7-2b10-9ebb-eafcaa3cbbea?overridelayout=true
trying to publish a service provider system into the service registry. One thing not clear to me is how to get the uddikey as needed in step 6 in appendix 1.
My service registry is in a PI 7.1 SP4 system. I followed the instruction in appendix 2 but there is no uddi key displayed in the General tab. Please help.
Regards,
Jiannan
Paragraph extracted from the whitepaper:
There may be cases in which the NWA logical settings do not match the Services Repository
settings when Visual Composer is trying to locate the enterprise services. Such cases can occur
when there is no SLD ID definition of the physical system in the Services Repository.
Currently, Visual Composer cannot search for services on a physical system with an empty SLD ID
(which is not a valid one).
To obtain this capability, the following steps should be performed to generate the necessary data
for each system with a non-valid SLD ID, so that Visual Composer can search for services over it.
1.Log on to http://<serverName>:<serverPort>/WSNavigator.
2.Select the Services Registry radio button.
3.In the Find field, enter sr and choose Go.
4.Select the ServicesRegistrySi line and choose Next.
5.Under the Operation Name, search for the publishPhysicalSystems operation, select it and choose Next.
6.Fill the service information parameters with the following (see Appendix 2 for details on how to get this information) :
6.1.Click the + icon in the physical system[].
6.2.Deselect the Classifications checkbox.
6.3.Click the + icon in the classificationReferenceGroups[].
6.4.Click the + icon in the classificationReferences[].
6.5.Deselect the classificationSystemKey checkbox.
6.6.Deselect the uddiKey checkbox and enter the value <localUddiKey>.
6.7.Deselect the value checkbox and enter the value <localSystemHostName>.
6.8.Deselect the host checkbox and enter the value <localHostName>.
6.9.Deselect the physicalSystemKey checkbox.
6.10.Deselect the logical key checkbox and enter the value <System name>.<SystemHome>.<host name>.
6.11.Deselect the systemName checkbox and enter the value <system name>.
6.12.Deselect the type checkbox and enter the value 2.

Hi Jiannan,
No worries, you can go to UDDI client from the main page of PI i.e. http://<serverName>:<serverPort>/
And you use the search function for the TModel for your Physical System. Search parameters can use the % wildcard.
Hit the search and you find the UDDI Key for the Physical System.
Cheers.
Hemant Chahal

RFC WSDL need to publish in Service Registry or not?

Hi,
I have created a webservice(WSDL) using SOAMANAGER for Remote Function Call(RFC) developed in R/3 System. This WSDL will be used in Enterprise Portal for our Web Application. Is it required to publish the Webservice in Service Registry? What is the importance of publishing webservice in Registry? If it is required, who will be responsible for publishing it(ABAP Technical person or Basis or Enterprise Portal person)?
Thanks and Regards,
Vimala P

Hi Nidhi,
>My Scenario is I need to publish one RFC as a webservice in PI 7.1 and provide an endpoint URL to user to use.
As per my understanding, you are trying to expose an RFC as webservice. If yes, have a look at this [link|http://help.sap.com/saphelp_nw04/Helpdata/EN/e9/ae1b9a5d2cef4ea4b579f19d902871/frameset.htm] to ensure you have done it properly.
> I have done the configuration but when I try this option Tools-> display WSDL it gives me following error-- ``Object Service Interface Z_QMNC_SAVE_CORRECTIONS | urn:sap-com:document:sap:rfc:functions not found in Enterprise Services Repository``
I am not clear with configuration you have done. Can you describe a bit more?
Regards,
Sunil Chandra

Publishing Enterprise Services

Similar Messages

Maybe you are looking for