Hi,
I Create a web Service from a function module, with no authentication and also with basic authentication,
But i receive always the same error
Thu Jul 03 17:28:47 BST 2014:DEBUG:<< "www-authenticate: Basic realm="SAP Web Application Server [DEV]"[\r][\n]"
Can anyone help me ?
Thank you in advance.
Resolved bad invocation..
not relevant anymore.
Hi All,
We are trying to consume a web service published by a third party. For that we have created a consumer proxy and logical port in SOAMANAGER. Also we have added custom SOAP header since the header generated by SAP is not in a format understandable by the service provider.
We are getting a SOAP fault exception while trying to invoke the service from SAP system. However we were successful in testing the web service using SOAP UI testing tool. The difference in the requests generated by SAP and SOAP UI is the location of namespace definitions in the SOAP requests. In the request generated by SOAP UI, all the namespace definitions are at Envelope level (just after soap-env:Envelope). We tested the request generated by SAP in SOAP UI testing tool and got the same error. So we edited the same request using SOAP UI and copied all the namespace definitions from SOAP body and pasted it just after soap-env:Envelope like the one shown below and it gave us the correct results.
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:nm="XXXXX"
xmlns:prx="XXXXX"
xmlns:ne="XXXXX"
xmlns:n0="XXXXX">
<soap-env:Header>
Would it be possible to change the SOAP request once it is generated so that we can pass all the namespace definitions just after <soap-env:Envelope or is there any other way to pass the namespace definition at envelope level to solve this problem.
Could you please share your thoughts and ideas on this.
Regards,
Arun
Hi Alviss,
We are facing similar issue like the one you explained above.
Were you able to resolve it?.
Thank you!.
Regards,
Karun
Hello,
I have question around consuming web service via ABAP program.The scenario is consume a operation of a web-service and get the information, based on this information put the data in flat files and send it back in another operation of this web-service. Due to way web-service is implemented I cannot generate proxy class and use SOA manager the reason is web-service is using complex data t
1) Is it possible to consume a web-service via ABAP program directly
I have explored the SAP documentation and came up with this link
Appendix C - SOAP Runtime for the SAP Web AS - SAP Library
Another Link I found was
Using any of the above approaches can SAP program consume a web-service bypassing the SOA manager & send the zipped files in one of the operations.
Hi Karun,
yes, issue has been resolved. since the configuration/architecture is not same, maybe try to check from your end, the step to re-import web service from ESR is it correctly configured? codes in NWDS is it updated (since we're replaced existing web service, existing implemented codes may get overwritten)
for my case, i have incorrectly configured the settings.
try to check in PI as well, for this new field, is it correctly handled? like mapping in PI?
if there is nothing wrong in the configuration, try to restart the Portal. we have done the portal restart when transported the changes to Acceptance/Production Environment.
Thanks,
Alviss
Thanks, i had the same problem as described and your answer helped me a lot.
Regards, Elmar
Hi Alviss,
Appreciate your reply.Thank you so much.
We will try to check the configurations and reimport it if necessary.
Kind Regards,
Karun
This is the complete text of error.
Usually a web service et.c provided by SAP can be reached by an address similar to this:
Now it happend to be that the address has a name of the server machine - and the common wish is to change that address to something more sustainable alias.
The question can the myhost be changed to an alias?
If so, where should it be done? Is it something that can be adjusted in the SOAMANAGER? 'Alternative Access URL' !?
Look at the following linked picture:
Or is it really that something that the basis needs to set up?
Any input on this is appreciated as I could not really find a lot on this.
Thanks,
Chris
Hello Experts,
I have followed the following tutorial to activate webservice using SOAMANAGER transaction in Quality system.
In the attachments, you can find that webservice is activated successfully.
i can also see my Webservice active in SICF as well as I can find Webservice in SE80 under package $WS_BOL_GEN
From the online tutorials and forums, I have understood that Webservice is configured successfully but now I need to Release it.
Now, I don't know how to release the WS using SOAMANAGER. Same i can perform using WSCONFIG and thereafter I see my webservice at runtime inside document template designer. BUT since., WSCONFIG is obselete.
I would really appreciate, if you can suggest solution how to release WS using SOAMANAGER. ?
High points will be given who provides solution
Thanks in advance.
Best Regards,
Ashish
Hello,
i'm facing a Problem calling a Webservice.
The webservice should make a goods Output.
Till now, I have created a Service Definition, a Consumer Proxy, a Transformation (XML-to-ABAP), Logical Ports via T SOAMANAGER, HTTP Request handler Class and a Webservice Calling Report as ABAP.
When I call the Webservice via http, i get the following XML-Output:
I found out, that the handler, which is called when i use my link is in the class CL_SOAP_HANDLER_EXTENSION and in this class, my handler is not in this one.
How can I provide, that he will call my handler?
Regards,
DEnnis
From SAP NW04s SP14 onwards, you no longer transport the runtime definitions between systems, which means you have to use SOAMANAGER in each environment / client. Have a look at SAP message 1318499 for a fuller explanation and/or search SAP messages for "wsconfig soamanager transport". You still transport the underlying Service Definitions etc via the standard mechanisms in ECC, it's just the runtime definition (such as the security settings you want) that are manually defined in SOAMANAGER.
Jonathan
Hi Jonathan,
Than you for your reply.
I checked the note 1318499 and also search on other forums. I got the point that SOAMANAGER doesnot support run-time definitions. But, I am still confused on one point that I have transported the WS service definition from development to quality system. In Quality system, i could see my WS active in SICF and also created endpoint using SOAMANAGER. could download my WSDL file then Why I am not able to see my WS at runtime in WS template designer.
Shall i also need to create endpoint for my WS using SOAMANAGER in development system? am I missing any point!?
Hope for your reply
regards,
ashsih
Hi,
I'm not familiar with "template designer" - is that CRM-specific functionality? If so, you might find some more info in that forum?
Our experience has been with web services in both ECC5 - using the old WSCONFIG / WSADMIN transactions, and then ECC6 using the new framework with development of the Service Definition within SE80 (transportable) and the Runtime Definitions in SOAMANAGER (not transportable).
With ECC6, we develop the Service Definition in SE80 in DEV (typically sitting over an RFC-enabled function module) and the Service Definition is transported to Test and, eventually, Production. We create the Service Definition specifying the lowest level of security (e.g. Authentication = none) because it will be the Runtime Definition in SOAMANAGER that defines what the consumer will need in order to interact with SAP.
For example, in DEV we might create two Runtime Definitions in SOAMANAGER for the same SAP web service Service Definition, one with anonymous login (so the the developer of the consumer to get their code running without worrying about security) and another with X.509 security (to match what we may have in Test and Production). We sometimes need to have different security depending on the SAP client - so we run SOAMANAGER in the relevant DEV client and create the Runtime Definition - these show up in SICF along the lines of:
z_my_web_service_name
201 (SAP client #)
servicename (as per SOAMANAGER)
bindingname (as per SOAMANAGER)
anotherservicename
anotherbindingname
204
yetanotherservice
bindingnumber3
Jonathan
We ended up registering an "incident" with SAP... after working with them, a new Note was created that solved both the "Invalid X509IssuerName" problem and couple of other issues we encountered during testing - we needed SAP Notes 1974624 + 2031917.
Jonathan
Had a stable project using 9 web services, imported a update wsdl, regenerated the web service client, checked in the code, worked in development environment. Then deployed that code into the test enviroment
java.lang.NullPointerException: while trying to invoke the method com.sap.engine.services.webservices.espbase.configuration.ServiceData.getBindingData() of a null object loaded from local variable 'serviceData'
at com.sap.engine.services.webservices.espbase.client.jaxws.metadata.InterfaceMetadata.getBindingData(InterfaceMetadata.java:228)
at com.sap.engine.services.webservices.espbase.client.jaxws.metadata.InterfaceMetadata.createClientConfigurationContext(InterfaceMetadata.java:176)
at com.sap.engine.services.webservices.espbase.client.jaxws.metadata.InterfaceMetadata.getProxy(InterfaceMetadata.java:70)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.getPort(SAPServiceDelegate.java:258)
at javax.xml.ws.Service.getPort(Service.java:92)
at REMOVED.NWDS_GENERATED_WEB_SERVICE_CLIENT.getCreateOrUpdateLeadAndProspectPortTypeSOAP(NWDS_GENERATED_WEB_SERVICE_CLIENT.java:25)
at REMOVED.HELPER.saveLead(HELPER.java:231)
at REMOVED.SERVLET.doRequest(AbstractLeadUpdateServlet.java:182)
at REMOVED.SERVLET.doPost(SERVLET.java:126)
at REMOVED.SERVLET.doGet(SERVLET.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at REMOVED.FILTER.doFilter(FILTER.java:127)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
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:328)
Hi, got the same error message when consuming webservice from 3rd party. does this snote solve your problem?
Error message:
SOAP:1,001 CX_ST_GROUP_MISSING_CASE:.Element 'sys_id' missing
