Web Service Error - no service endpoints found

[Former Member]

Hi,

I tried to create a web service deployable proxy project to consume an external third party web service url. There were no files generated for Logical Ports and Proxy Classes, though there are files generated for WSDL and SEIs. A further test on http://ip:port/index.html -> web service -> Enter the WSDL URL of the Web service -> No Service Endpoints Found, prove that something wrong with the url.

Any idea for me to check what goes wrong with the web service url? or could it due to firewall?

[Former Member]

Hi,

Another question, while generating web service, i picked Simple SOAP as configuration type, can it be used to send over internet, or just constrained to intranet?

[Former Member]

Hi Julius!

I wonder if you have resolved your error, because I have the same problem. I want to invoke a web service published in webAS server, the client is programmed with Axis api and I get a security protocol error:

#1.5#001321FC8AE700690000026300001F600004190D37BC6C7B#1153444467623#com.sap.security.core.server.ws.service.ServerSecurityProtocol#sap.com/ProveedoresWS#com.sap.security.core.server.ws.service.ServerSecurityProtocol.handleRequest#anon1#0####411ceb70185611db9c53001321fc8ae7#SAPEngine_Application_Thread[impl:3]_8##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'http://10.49.96.232:50000/ProveedorNombresWS/Config1?style=document'; Key name:'SoapRequestWrapper' key value:'getNombreCompleto'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#

I'll really apreciate any help!!

Thnks a lot!

[Former Member]

In the meantime, there are also consuming my java-created web service using the test tool from http://www.soapclient.com/soaptest.html.

Error given as below, from the

wsse:InvalidSecurity0012BF1423AB0047000000350000065C00041741F13F5CDC : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; 0012BF1423AB0047000000350000065C00041741F13F5CDC : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext';

From my application log, error shown as below:

#1.5#0012BF1423AB0047000000360000065C00041741F13F5DA5#1151471894671#com.sap.security.core.server.ws.service.ServerSecurityProtocol#sap.com/AdapterWSTabEAR#com.sap.security.core.server.ws.service.ServerSecurityProtocol.handleRequest#J2EE_GUEST#230####800311f0066511dba3770012bf1423ab#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]# #1.5#0012BF1423AB0049000000370000065C00041741F475BD3F#1151471948578#com.sap.security.core.server.ws.service.ServerSecurityProtocol#sap.com/AdapterWSTabEAR#com.sap.security.core.server.ws.service.ServerSecurityProtocol.handleRequest#J2EE_GUEST#230####a024a020066511db954d0012bf1423ab#SAPEngine_Application_Thread[impl:3]_9##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#

Anyone has any idea what's the rootcause of all the incompatibility?