Soap receiver configuration

Hi Everybody,
I am mplementing a RFC to SOAP scenario.
1)Could someone pls tell me how to configure receiver?
2) I have a wsdl provided by the receiver system company, the issue is how do i find out the target url from the wsdl given.
3) Also what is SOAP action field in the soap receiver adapter. Is it a mandatory field?
Regards,
Ashish

Hi Ashish,
I hereunder answer you point by point:-
1. Link for SOAP Adapter configuration....
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
2. You can find the target URL you need to specify in the SOAP adpater in the WSDL file. Locate the wsdl-port in the wsdl-binding. There you find a soap:address location. That's the target url.
For the method you need to fill in the SOAP action of your SOAP adapter. The SOAP action is also defined in the WSDL. Find the correct wsdl-operation, there you can find the <soap:operation soapAction ="" />
3. You can open wsdl in notepad and find soapAction then you will get http://www.webserviceX.NET/ConversionRate as SOAP action.
Regards.
Praveen

Similar Messages

SOAP receiver configuration and ESR part

Hi,
Could you Please help me out?
I have a scenario like IDOC to SOAP in that they are not giving the WSDL structure I have to prepare and have to use.
Please tell me how to create wsdl and then how to proceed with Data Types, Message Types, Service interfaces and mappings and ID configuration.
Thanks & Regards,
L N Venkata Praveen Gade.

Basically you are using target system using soap adapter as receiver.
Import the WSDL In ESR as external definition.
use external message type in the message type tab to choose mesg from WSDL.
create receiver service interface as usual and specify wsdl message as message type.
Message Mapping again choose source message your sender message type and receiver as reciever mesg type(one you picked from the WSDL)
Operation mappping is pretty same
Configure soap receiver channel.
two things
specify wsdl url (find out soap address location tab in the wsdl)
and action (if required) other leave blank.
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
check this [link |http://www.riyaz.net/blog/xipi-a-guide-to-using-sap-xi-soap-adapter/technology/sap/113/]too
hope that helps.

SOAP receiver: configure URL on runtime

Hi experts:
I have an RFCs --> XI --> SOAPs scenario. The URLs for SOAPs are always like "http://server:port/directory/xxxxxxx" and only changes "xxxxxxx". The user/passord is the same for all URLs.
My question:
There is some way to configure dynamically the URL? I have tried to use DynamicConfiguration but I must write all the URL in each (java) mapping. Server and port will change when I transport to the productive systems so I'm interested in maintaining the basis URL on the communication channel by adding the last part dynamically
Thanks

Valero Lázaro wrote:
> My question:
> There is some way to configure dynamically the URL? I have tried to use DynamicConfiguration but I must write all the URL in each (java) mapping. Server and port will change when I transport to the productive systems so I'm interested in maintaining the basis URL on the communication channel by adding the last part dynamically
>
> Thanks
use dynamic configuration itself.
in your case you will have different values for different env. i.e Dev, Qa and PRD so in the code you can check what is the current sap system (based on SID) and write the logic
ex.
// Assume XID is Dev, XIQ is QA etc
String sysName = (String) System.getProperty("SAPSYSTEMNAME");
if(sysName.equals("XID"))
//your logic here
else if(sysName.equals("XIQ"))
//your logic here
else
// your logic
the above code will help you get the SID and based on it you can set the url via dynamic conf.

Issue in Dynamic configuration in SOAP receiver channel

Hi All,
My scenario is file to SOAP. At receiver side I want to generate URL dynamically.
To proceed step by step, I started with passing a constant URL to Dynamic configuration UDF.
mapping:
Dynamic conf. UDF
Channel Configuration:
From testing, I found that channel always takes the url given in Target URL field and dynamic URL in TserverLocation is been ignored by the channel.
That is dynamic configuration is not working completely.
I went through a lot of blogs and also tried a lot of trial and error methods, but none helped. Every thing I configured looks perfect for me, but still not working. I don't understand where I went wrong. Please help me.

Hi Experts,
I am facing similar issue,
URL --> UDF --> @dynamicvariable
I have created a variable underparent node eg: DESADV-->dynamicvariable
passed complete URL to UDF, below is the UDF
& configured SOAP Receiver Channel as well. This is IDOC to IDOC scenario, using IDOC_AAE on sender side and SOAP on receiver in single stack.
--> Checked ASMA
--> Checked Variable Transport Binding and given "TServerLocation" without quotes in XHeaderName1
--> Target URL: http://
But when I am running this interface, nothing is coming in Dynamic configuration.
Ref: Message Log:
MM and OM is also perfect in ESR.
Any suggestions? Please advice.
Regards
Singh

"Configure Proxy in SOAP Receiver"

Hi ,
Can some one help in providing me the information regarding "Configuration of proxy in SOAP receiver adapter (PI 7.1).
Thanks ..

Hi Stefan,
I have my Proxy Values ,the Host and the Port ...even then i am facing some issues., I want to know are there any other details which needs to provided inorder to configure proxy ...(My receiver is a 3rd party Webservice outside the firewall.)
Do i need to check the conversion parameters.
Error:
SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: "*********************************". at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</SAP:AdditionalText>
<SAP:Stack />
Edited by: Madhusree Nagalla on Oct 28, 2010 3:28 PM
Edited by: Madhusree Nagalla on Oct 28, 2010 3:29 PM

SOAP Receiver : Dynamic URL configuration vs. TAuthKey capability

Hello all,
I plan to use dynamic URL configuration of web service URL in SOAP Receiver CC. I got an idea, which is more or less described on SDN already. But one thing bothers me a lot.
In my scenario we talk about 10 and more WebServices' URLs to be called dynamically. The WS call will include also authorization username:passwd and it is expectable, that each WS will have different uname:passwd definition to be authorized with.
I made a capability analysis of SOAP Receiver CC - tab Advanced - Authetication keys and there are prepared only 10 possibilities to define password for authentication key (which I'll handle to CC via TAuthKey parameter).
In the help page http://help.sap.com/saphelp_nw04s/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm there is a note regarding authentication key:
If authentication is required for the receiver system, you can enter a password with confirmation for each key value. This means that you do not need to write passwords in the enhanced message header.
So in other words there should be a way, how to send to CC even the password with other adapter-specific message attributes. (or maybe I miss the meaning of this comment, like the other way is to develope own module for CC and process additional attribs from enhanced message header)
Does anyone have some experience with handling the authentication data in "enhanced message header" ?
Thanx for you info in advance.
Regards
Tom

Hi all,
I got an idea that the solution could be to use "Enhanced receiver determination" and use a set of Services-CommChannels with special naming convention. With this (little bit complicated) scenarion I'll get a possibility to define more then one SOAP Receiver CC => I'll get more than 10 options to store the logon password.
What do you think ?
Points for ideas guaranteed.
Tom

Configure User Authentication on SOAP Receiver Adapter

Hi,
I am calling a WebService that is available over the internet. We are on PI 7.1 and I am using a Soap Receiver Adapter. The configuration was downloaded from SAP in a partner package. The development in the package was done on XI3.
I need to call the WS with user authentication. I've selected the "Configure User Authentication" radio button and entered the username and password. The message fail with "HTTP 401 Unauthorized" and it is because the user details are not being send from the adapter. If I copy the XML payload to a XML tool, like Stylus Studio, I can call the webservice successfully. I've read through numerous blogs and messages on this Forum, including adding the adapter module (MessageTransformBean) and changing the Conversion Parameters without any luck.
Any suggestions please?
Thanks

I am calling a WebService that is available over the internet.
I copy the XML payload to a XML tool, like Stylus Studio, I can call the webservice successfully.
normally the webservices that we use (from internet) are freely available...meaning they dont require any username/ password.
if no credentials are required then do not select Configure User Authentication...uncheck it....if user-details are provided by the Webservice, then use these details (not your XI/ PI user details) in the channel.
Are you using any user-name/ password while testing from SOAP tools?
Regards,
Abhishek.

No Payload in the soap receiver call adapter ?

Hi Guys,
configured Proxy-SOAP Asynchronus process and in the sxmb_moni, i am unable to see the payload under call adapter in sxmb_moni, but i am able to see the payload under RWB in MDT. The message is checked successful in monitor.
I am not understanding why i am unable to see the payload under call adapter in sxmb_moni. I am not getting the data into my receiver system.
Do i need to mention the QOS as EO in the soap url in the soap receiver adapter configuration ?
any help would be really appreciated
Thanks,
srini

Hi,
You can only see the Payload(both with and without transformation) in MONI. message that is handling by adapter can only seen in Adapter Framework using RWB-Message Monitoring or using Communication Channel Monitoring.
Regards,
Farooq.

Rewards points if you find it usefull.

Using adapter specific message attributes in SOAP adapter configuration

Hi,
Can you please let me know how to use adapter specific message attributes in receiver and sender SOAP adapter configuration. If possible , with example.

See here:
Adapter-Specific Message Attributes in the Message Header
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/frameset.htm
Sender Soap Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
Receiver Soap Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm

SOAP Receiver Adapter Proxy Settings

Hi Guys,
I am trying to send a SOAP message to an external webservice. I was able to get the message to arrive at the webservice when I used a proxy without user authenication.
I now need to get the SOAP adapter to use a proxy with user authenication. I have added the username and password on the communication channel, but I keep getting the following response error:
com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
Has anyone got a suggestion as to how I may go about fixing this problem? Is there somewhere else that I need to configure the proxy server and user to allow the SOAP Receiver to send a message out?
Thanks very much,
Miguel

Hi Abhy,
I have checked the settings and they appear to be correct according to the help files.
I know that it has something to do with the authenication in the proxy server because the only thing that I have changed is the proxy server from a server that required no authenication to one that requires authentication. I have added the username and password and am getting this error.
According to the sap help, it is either a wrong target URL or invalid authentication. But the url worked previously, so it is definitely something to do with the authenication.
I have added this info on the communication channel. Is there somewhere else that I should add the proxy settings?
Thanks,
Miguel

SOAP receiver adapter digest authentization

Hallo,
I have scenario with SOAP receiver adapter configured as follow:
Adapter Type: SOAP
Transport Protocol: HTTP
Message Protocol: SOAP 1.1
Adapter Engine: Integration Serer
Target URL: http://localhost:8099/webservices/test_v1_1_2
Configure User Authentication
User: ****
Pasword:****
but WS need digest HTTP authentication and SOAP adapter send in header Authentication: Basic.
Hou can I change authentication method for SOAP protocol?
Thx

Hallo,
I solved this problem by using AXIS framework. I hope that this short instruction help to someone.
1. In SOAP receiver CC you have to set up Transport Protocol to HTTP(AXIS) and Message protocol to AXIS
2. Now you can switch Authentication to Digest (NOW adapter will still send Basic!!! Digest Authorization is Supported only by the following handler: com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender)
3. On Module tabs in section Module configuration change type HTTPSender to CommonHTTPSender:
(trp handler.type java:com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender)
4. Save and Activate
Before you start to use AXIS framefork you have to deploy necessary library.
This thread help:
Re: How to install SOAP Axis adapter and where is it available ??
Be carefull, for digest authorization you have to linked Optional library "Jakarta-Commons HttpClient" too.
Good luck.
JK

SOAP Receiver Adapter / Scenario calling WebServices

Hi Experts,
I am trying to call a web service. Configured a SOAP Receiver adapter. Message to Web Service goes fine but not shown with Checkered flag, but with icon with description "Log Version".
In response message for the request Error Category - MAPPING and Error ID "Cannot Read Payload".
Any ideas to clear this problem. I do have response mapping assigned to Message Interface. Message Interface is Synchronous.
Thanks in advance for any solutions.

can you verify that you are getting a response..try re-routing that to tcpgw and check if content is in line with expected response.
Regards
Ravi Raman

Soap receiver adapter payload with certficate signature

I have a requirement.. where XI calls external webservice using SOAP.
I have configured SOAP receiver adapter, but the webservice wants the certificate authentication.. From XI we sent the certficate to external webservice and then in the comm channel I did activate the 'certficate' check box. It did not work.
For test purpose now they have deactivated the certficate authentication in their end.. it works if they deactivate. It means there is no issue with request structure.. purely the issue is when I use the certficate.
External webservice sent me the copy of the soap request which works for them.. that has security signature inside the payload. ( I have atteched below).
If anybody has done it have an idea how to do it please let me know.
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Header>
- <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="CertId-62149565">MIIGOzCCBaSgAwIBAgIQIKVRaj76KNaG5Dl6P5X7wzANBgkqhkiG9w0BAQUFADCBnjEPMA0GA1UEChMGaHAuY29tMRowGAYDVQQLExFJVCBJbmZyYXN0cnVjdHVyZTELMAkGA1UEBhMCVVMxIDAeBgNVBAoTF0hld2xldHQtUGFja2FyZCBDb21wYW55MUAwPgYDVQQDEzdIZXdsZXR0LVBhY2thcmQgUHJpbWFyeSBDbGFzcyAyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MDMyMzAwMDAwMFoXDTA4MDMyMjIzNTk1OVowUDEgMB4GA1UEChQXSGV3bGV0dC1QYWNrYXJkIENvbXBhbnkxEDAOBgNVBAsUB1NlcnZlcnMxGjAYBgNVBAMTEWl0Zy5lcHJpbWUuaHAuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDVGa1x5j/RJHHkqYzEb9NIQGChffTb1D0LiYAP5arbxz0trCp8ZeG4FCH71jc6x9Ks3gC4YdWgQbOCz64wnpM8NvEVCZBHuxvdnPZpziPWQqDr0yvwSoCXg8mkeJrHql0MSm7TNiyhzCAzlmB9JgmoHrRtArJdXMRpHjdZQK3QIDAQABo4IDxTCCA8EwDAYDVR0TAQH/BAIwADAOBgNVHQ8BAf8EBAMCBaAwHwYDVR0jBBgwFoAUSlYfvIpRj/SDE8naXHlUyAK6q58wHQYDVR0OBBYEFE99o7D6AITUcqWVmeYzu/2k66VEMIIBKAYDVR0fBIIBHzCCARswggEXoIIBE6CCAQGUWh0dHA6Ly9vbnNpdGVjcmwudmVyaXNpZ24uY29tL0hld2xldHRQYWNrYXJkQ29tcGFueUlUSW5mcmFzdHJ1Y3R1cmUvTGF0ZXN0Q1JMLmNybIaBuWxkYXA6Ly9sZGFwLmhwLmNvbS9DTj1IZXdsZXR0LVBhY2thcmQlMjBQcmltYXJ5JTIwQ2xhc3MlMjAyJTIwQ2VydGlmaWNhdGlvbiUyMEF1dGhvcml0eSxPPUhld2xldHQtUGFja2FyZCUyMENvbXBhbnksQz1VUyxPVT1JVCUyMEluZnJhc3RydWN0dXJlLE89aHAuY29tP2NlcnRpZmljYXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5MCoGA1UdJQEB/wQgMB4GCCsGAQUFBwMBBggrBgEFBQcDAgYIKwYBBQUHAwQwggEWBgNVHSAEggENMIAwgAYKKwYBBAELBAMCATCAMCkGCCsGAQUFBwIBFh1odHRwOi8vZGlnaXRhbGJhZGdlLmhwLmNvbS9jcDCABggrBgEFBQcCAjCAMB4WF0hld2xldHQtUGFja2FyZCBDb21wYW55MAMCAQIagZVBdXRob3JpdHkgdG8gYmluZCBIZXdsZXR0LVBhY2thcmQgQ29tcGFueSBkb2VzIG5vdCBjb3JyZXNwb25kIHdpdGggdXNlIG9yIHBvc3Nlc3Npb24gb2YgdGhpcyBjZXJ0aWZpY2F0ZS4gSXNzdWVkIHRvIGZhY2lsaXRhdGUgY29tbXVuaWNhdGlvbiB3aXRoIEhQLgAAAAAAAAAAAAAwge4GCCsGAQUFBwEBBIHhMIHeMCsGCCsGAQUFBzABhh9odHRwOi8vb25zaXRlLW9jc3AudmVyaXNpZ24uY29tMIGuBggrBgEFBQcwAqSBoTCBnjEPMA0GA1UEChMGaHAuY29tMRowGAYDVQQLExFJVCBJbmZyYXN0cnVjdHVyZTELMAkGA1UEBhMCVVMxIDAeBgNVBAoTF0hld2xldHQtUGFja2FyZCBDb21wYW55MUAwPgYDVQQDEzdIZXdsZXR0LVBhY2thcmQgUHJpbWFyeSBDbGFzcyAyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MA0GCSqGSIb3DQEBBQUAA4GBAMB3vOFZYe26MaZ8mpnoZwhWbLBFV/lxtefZT1uT7mKZiaHjVqwu3tN1eAYAUXtJQHVJTnCnbDm9zFunlvuEzGMt9PwXS61MK6GwPmtjEsevRnGIA7arvpjSJ1/EQlD620I7icM9BNXbElYFfsnZjlWKFTZz3VX1OT2qmJtVWpD</wsse:BinarySecurityToken>
- <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
- <ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
- <ds:Reference URI="#id-24819136">
- <ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<ds:DigestValue>6Mzpm7P8k3f8UuxbBMP4ZTC83Yc=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>HcqMChOzlHFXTRRAf7kyTSQ5Jd53Yiu7oFLjkh5P3vayo2G4sjFv/qFKHX0E6a5xkBMTIRrW+30t7IdB4X0x35FPO1dTulz37KM1/jpLSGVxnjnWWeFZvseVjJsk5NTPiSE6GAjO7rFW/Vled2djATTmZsIgJCIfhLYVp112Uis=</ds:SignatureValue>
- <ds:KeyInfo Id="KeyId-21369792">
- <wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="STRId-29015968">
<wsse:Reference URI="#CertId-62149565" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" />
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>
</wsse:Security>

go through this webinar and follow the steps...It will solve your problem..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1b657d59-0c01-0010-4fa8-f792fa412823
Regards,
Ravi

SOAP Receiver Adapter issue

Hello there,
I am using a SOAP receiver adapter. The URL contains the format - https://<XYZ.com>/car/soap/Sync?login=username&pass=password
Now, if I configure the channel by using the "Configure User Authentication", the data is not getting posted at target.
But if I provide the user id / pwd in the URL, it gets posted.
I don't want to use the user id / pwd in the URL but at the sametime, the WS team is not ready to change the format of the URL.
Can I use "Query String" to handle that? If yes, how? If no, what options I have?
Thanks for your precious input and time.
Abhi

Thanks Suraj!
Have you tried this:
url : https://<XYZ.com>/car/soap/Sync
and Configure User Authentication option set
I haven't tried it that way. I am not sure whether that will work, as WS team told me that I am required to put in the whole URL. But thanks for your suggestion, I will give it a try that way.
also try specifying the SOAP action as per your wsdl file
SOAP Action is not Mandatory, so I am not using that.
Thanks,
Abhi

Soap receiver adapter exception

Hi,
I am using SOAP receiver adapter to access a web service that is hosted on SAP Web AS (in this case it is the integration server Web AS). I use the web services navigator to test the web service and the web service works fine. The name of the web service is 'RemoteCrossReferenceProcessor' and it has one operation 'crossReference'.
But with the soap adapter, I am getting OperationNotFoundException in the logs and my web service is not getting accessed. Here is the server log:
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:RemoteCrossReferenceProcessor'; Key name:'SoapRequestWrapper' key value:'crossReference'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
#1.5#0003BA0FF9EA0022000000840000688D0003F9349A3C2D61#1118429251382#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######b40aca80d9be11d994360003ba0ff9ea#SAPEngine_System_Thread[impl:5]_47##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:#http://sapsand1:8000/sap/xi/engine?type=entry#
Here is adapter configuration:
Transport Protocol:HTTP
Message Protocol:SOAP 1.1
Adapter Engine:Integration Engine
Target URL: http://<server_name>>:50000/RemoteCrossReferenceProcessor/Config?style=document
User:
Password:
Default SOAP Action:
I imported the WSDL into the external definition and used the messages from the WSDL for defining my interface mappings.
I am using XI 3.0 SR1 (SP 09).
I am out of ideas as to why the SOAP adapter is not calling my web service. Please help me with your suggestions.
Thanks and Regards.

HI Dani,
I was looking for this error and I found this post AXIS SOAP Receiver. This post says about other errors, but sugests many ideas to found the soluction, like:
1- non-deployed all AXIS jars; (but in this case it deployed all)
2- Exists this note for one erro in AXIS: (https://service.sap.com/sap/support/notes/1028961).
3- this document (http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f) that have sets for header parameters. This is interesting becouse one of this parameters is obligatory but isn't filled, can occur error like "null object".
By the way, you can check if have update to AXIS (http://ws.apache.org/axis/), becouse isn't a SAP application and in other systems can have this error.
I hope this helps,
Romerito Silva

Soap receiver configuration

Similar Messages

Maybe you are looking for