SOAP Adapter without SOAP envelope sets contenttype to application/xml

Hi,
I wrote a adaptermodul for the SOAP adapter to create a SOAP:HEADER.
I disable the SOAP envelope in the communication channel.
Now I get a error from the WebService Provider because the SOAP Adapter sends with Content-Type application/xml and not text/xml. I set the content-type in the adapter module but it seens to not work.
How can I correct this ?
Regards,
Gerald

Hi
Simple answer is NO, it is not possible (without party/channel/ service etc to process the request)
but it is worth a try to check if the URL encoding works.. though I have not tried..
for example sending the hex value of the "?" - %3F%
URL is a generic topic, you can search that to get more information
(ex : http://www.blooberry.com/indexdot/html/topics/urlencoding.htm)
Regards
Vishnu

Similar Messages

How to make PI 7.0 soap adapter support SOAP 1.2

hi all:
Is there some idea make PI 7.0 soap adapter support SOAP 1.2?
I have look the document about soap adapter,and it specified that soap adapter only support SOAP 1.1.
http://help.sap.com/saphelp_nw70/helpdata/EN/ae/d03341771b4c0de10000000a1550b0/frameset.htm.
my scenario:
external system send message via soap 1.2 to xi.

for more detail about axis soap adapters refer this link[http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm]

SOAP adapter without any querystring

Hi,
I have to configure communication from an Axis2c client to PI soap adapter. Unfortantly the Axis2c application strips the url after the question mark, it is thereby not possible to specify a service and channel.Are the any alternatives to use SOAP or HTTP without a question mark like defining the url without it?
I know it is a bit weird, so we migth find an other solution.
/daniel

Hi
Simple answer is NO, it is not possible (without party/channel/ service etc to process the request)
but it is worth a try to check if the URL encoding works.. though I have not tried..
for example sending the hex value of the "?" - %3F%
URL is a generic topic, you can search that to get more information
(ex : http://www.blooberry.com/indexdot/html/topics/urlencoding.htm)
Regards
Vishnu

Sender SOAP adapter: get soap header data

Hi,
I've been going through various posts and blogs here on SDN + looked in the how to guide for SOAP adapter, but still find it quite difficult to actually find out how to do it. I've tried to follow recommendations seen, but it doesn't add up.
So can someone please tell me how to get an element situated in the SOAP header of the request sent to XI via sender soap adapter?
Let's for instance say the request looks like this:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <SOAP-ENV:Header>
 <SSN>1234567890</SSN>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 <event>
 <elem1>data 1</elem1>
 <elem2>data 2</elem2>
 <elem3>data 3</elem3>
 </event>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
How can I get the data in the SSN-header element at mapping time?
I'm sure this can be done by using adapter modules as the first step adapter, but I prefer doing it at mapping time if possible.
Best Regards,
Daniel

I solved it on my own now. My missing link was the fact that I'm using XMLSPY to send request and thus need to replace all '&' with & in Connection Endpoint.
Message was edited by:
 Daniel Engsig-Karup

Receiver SOAP Adapter Problem-soap fault: Server did not recognize the valu

I have a scenario for service orders using async call : IDOC-XI-SOAP.
I used the XML Spy tool to test the Service order's web services and it works fine. I imported the same WSDL file in XI. When I send a SOAP message from XI, I get a following error in the adapter engine.
MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: AddUpdateCostObjectLevel1.
Can someone please help me...
Thanks in advance!
Mrudula

This problem is resolved by me by passing the "http://company's URL/AddUpdateCostObjectLevel1" in the SOAP action.
Thanks to all for your input.
Mrudula

Sender SOAP adapter without authentication

Dear All,
I am working on one of our customer requirement where i need to send data to SAP ECC 6.0 using SOAP (Sender) and RFC (Receiver).
My scenario is SOAP (Sender) to RFC (Receiver). While configuring the SOAP sender adapter i am selecting 'HTTP' and my QOS is 'Best Effort' as it is a synchronous call.
The Web service URL looks like as follows :
http://xiserver:50000/XISOAPAdapter/MessageServlet?channel=:BS_WROUTE:SOAP_SEN_ROUTE_DATA&version=3.0&Sender.Service=BS_WROUTE&Interface=http%3A%2F%2Fxxx.com%2Froute%5EMI_WROUTE_ROUTE_OUT
The problem i am facing is while testing this web service {generated by PI 7.0 (in ID)} it is asking for user name and Password.
Can somebody suggest me while testing :
1) how can we avoid user name and Password?
2) Can we attach user name and Password in our SOAP URL? if yes so please suggest me how to attach this.
Thanks
Honey

Dear Stefan,
Thanks for your reply.
If I am using ABAP Port 8000 for my scenario and my URL is as follows :
http://xiserver:8000/XISOAPAdapter/MessageServlet?channel=:BS_WROUTE:SOAP_SEN_ROUTE_DATA
Can i not use this additional string &sap-user=user&sap-password to provide the user name and password in wsdl??
my new URL would be like this:
http://xiserver:8000/XISOAPAdapter/MessageServlet?channel=:BS_WROUTE:SOAP_SEN_ROUTE_DATA&sap-user=user&sap-password
Please suggest how can i avoid the credentials.
Thanks
Honey

HTTPS Port for SOAP Adapter PI 7.1 (XI)

Hello Colleagues,
we plan to configure an Sender SOAP Adapter (without SOAP envelope) as HTTPS message receiver with HTTP Security Level "HTTPS with Client Authentication".
Does anyone know if this works and which port will be used. For my understanding it must be 443.
If not, it's possible to change the port to 443?
Regards,
Jochen

Hi Prateek,
many thanks!
Where can i do the port change?
Many thanks in advance!
Regards,
Jochen

Base64 encoding in SOAP adapter

Hi,
Is it possible to transform outgoing messages to Base64 encoding format in XI using module processors and security encryption? I'm using receiver SOAP adapter (without SOAP header) and using PayloadZipBean module processor to zip the outgoing message. Also I need to add digital signature and base64 encryption to the zipped message. Please let me know how this can be achieved.
Thanks,
Dipankar

hi dipankar
check the below blog
How to use Digital Certificates for Signing & Encrypting Messages in XI
How to use Digital Certificates for Signing & Encrypting Messages in XI
hope this resolves your issue
additionally check this
How to use Client Authentication with SOAP Adapter
How to use Client Authentication with SOAP Adapter
also
How XML Encryption can be done using web services security in SAP NetWeaver XI
How XML Encryption can be done using web services security in SAP NetWeaver XI
reward points if helpfull
regards
kummari
Edited by: kummari on Jul 19, 2008 7:24 AM

Sender SOAP Adapter, inconsistent behavior

Hi,
We are using XI 3.0 SP17. We have noticed some inconsitent behavior with the sender SOAP adapter:
When sending a valid SOAP message to the adapter, it will reply with:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body/></SOAP:Envelope>
To me this seems errornous, becuase it is missing "<?xml version='1.0'?>" in the beginning, and thus is not valid XML. This leads to errors on the Client that is sending messages to the Sender SOAP adapter.
When sending an errornous SOAP message from the client to the XI Sender SOAP adapter, the error message does include the "<?xml version='1.0'?>" + the corresponding error message, so the behavior seems inconsitent and errournous.
Can someone tell me how the get the Sender SOAP Adapter to include "<?xml version='1.0'?>" in the reply for valid SOAP messages?
Thanks for any help on this subject!
-Hans
PS: Here is an example of an error message from the Sender SOAP adapter, that does include the xml header:
<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>MalformedMessageException</code>
 <text><![CDATA[Unexpected content in SOAP:Body; nested exception caused by: com.sap.aii.messaging.util.XMLScanException: Unexpected content in SOAP:Body\tat com.sap.aii.messaging.mo.Message.reparseRootDocument(Message.java:1014)\tat com.sap.aii.messaging.net.MIMEInputSource.readSOAPPart(MIMEInputSource.java:619)\tat com.sap.aii.messaging.net.MIMEInputSource.decodePart(MIMEInputSource.java:611)\tat com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:379)\tat com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)\tat com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:378)\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:760)\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:853)\tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)\tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)\tat com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)\tat com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)\tat com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)\tat com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)\tat com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)\tat java.security.AccessController.doPrivileged(AccessController.java:180)\tat com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)\tat com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>

Hi,
"Do not use SOAP Envelope" is not really an option for us.
From help.sap.com:
If the indicator is set, the adapter expects a message without a SOAP envelope.
If you have set the indicator, you must also enter nosoap=true in the URL.
The adapter then puts the whole message in the XI payloads
So this also requires heavy changes to the client side. It would almost make more sense to use the plain HTTP adapter in that case..
-Hans

XI 2.0 Standalone J2SE SOAP Adapter as client - SOAP:encodingStyle

Hi,
We're setting up the J2SE SOAP Adapter of XI 2.0 to talk to a synchronous web service provided by a webmethods platform.
When we generate the Request message using the WSDL and post it directly via the HTTP test tool the message is understood and a response message is returned.
Here is the Request:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <SOAP-ENV:Body>
 <m:callFP091 xmlns:m="http://destserver/FP091.flows" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
 <iw1_RECTPE xsi:type="xsd:string">String</iw1_RECTPE>
 <iw1_DLRCODE xsi:type="xsd:string">String</iw1_DLRCODE>
 <iw1_FRNCODE xsi:type="xsd:string">String</iw1_FRNCODE>
 <iw1_JOBNUM xsi:type="xsd:string">String</iw1_JOBNUM>
 <iw1_CHASIS xsi:type="xsd:string">String</iw1_CHASIS>
 <iw1_COLOUR xsi:type="xsd:string">String</iw1_COLOUR>
 <iw1_DESCRIP xsi:type="xsd:string">String</iw1_DESCRIP>
 <iw1_INVNUM xsi:type="xsd:string">String</iw1_INVNUM>
 <iw1_CAPAMT xsi:type="xsd:string">String</iw1_CAPAMT>
 <iw1_INTFRE xsi:type="xsd:string">String</iw1_INTFRE>
 <iw1_LOC_IND xsi:type="xsd:string">String</iw1_LOC_IND>
 <iw1_REGISTRATION xsi:type="xsd:string">String</iw1_REGISTRATION>
 <iw1_ENGINE_NUM xsi:type="xsd:string">String</iw1_ENGINE_NUM>
 <iw1_VIN_NUM xsi:type="xsd:string">String</iw1_VIN_NUM>
 </m:callFP091>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
When we try to use the SOAP Adapter and pass it the following message from XI:
<m:callFP091 xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:m="http://destserver/FP091.flows"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" >
 <iw1_RECTPE xsi:type="xsd:string">E1</iw1_RECTPE>
 <iw1_DLRCODE xsi:type="xsd:string">3009838</iw1_DLRCODE>
 <iw1_FRNCODE xsi:type="xsd:string">333</iw1_FRNCODE>
 <iw1_JOBNUM xsi:type="xsd:string">123</iw1_JOBNUM>
 <iw1_CHASIS xsi:type="xsd:string">2</iw1_CHASIS>
 <iw1_COLOUR xsi:type="xsd:string">3</iw1_COLOUR>
 <iw1_DESCRIP xsi:type="xsd:string">4</iw1_DESCRIP>
 <iw1_INVNUM xsi:type="xsd:string">5</iw1_INVNUM>
 <iw1_CAPAMT xsi:type="xsd:string">6</iw1_CAPAMT>
 <iw1_INTFRE xsi:type="xsd:string">7</iw1_INTFRE>
 <iw1_LOC_IND xsi:type="xsd:string">8</iw1_LOC_IND>
 <iw1_REGISTRATION xsi:type="xsd:string">9</iw1_REGISTRATION>
 <iw1_ENGINE_NUM xsi:type="xsd:string">1</iw1_ENGINE_NUM>
 <iw1_VIN_NUM xsi:type="xsd:string">2</iw1_VIN_NUM>
</m:callFP091>
The SOAP adapter wraps the envelope and body around this message, provides an empty header but changes the SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" attribute to SOAP:actor='http://schemas.xmlsoap.org/soap/encoding/'.
The generated SOAP message is:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Header/>
<SOAP:Body>
<m:callFP091 xmlns:m='http://196.11.134.83/FP091.flows'
SOAP:actor='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
 <iw1_RECTPE xsi:type='xsd:string'>E1</iw1_RECTPE>
 <iw1_DLRCODE xsi:type='xsd:string'>3009838</iw1_DLRCODE>
 <iw1_FRNCODE xsi:type='xsd:string'>333</iw1_FRNCODE>
 <iw1_JOBNUM xsi:type='xsd:string'>123</iw1_JOBNUM>
 <iw1_CHASIS xsi:type='xsd:string'>2</iw1_CHASIS>
 <iw1_COLOUR xsi:type='xsd:string'>3</iw1_COLOUR>
 <iw1_DESCRIP xsi:type='xsd:string'>4</iw1_DESCRIP>
 <iw1_INVNUM xsi:type='xsd:string'>5</iw1_INVNUM>
 <iw1_CAPAMT xsi:type='xsd:string'>6</iw1_CAPAMT>
 <iw1_INTFRE xsi:type='xsd:string'>7</iw1_INTFRE>
 <iw1_LOC_IND xsi:type='xsd:string'>8</iw1_LOC_IND>
 <iw1_REGISTRATION xsi:type='xsd:string'>9</iw1_REGISTRATION>
 <iw1_ENGINE_NUM xsi:type='xsd:string'>1</iw1_ENGINE_NUM>
 <iw1_VIN_NUM xsi:type='xsd:string'>2</iw1_VIN_NUM>
</m:callFP091>
</SOAP:Body>
</SOAP:Envelope>
This message has no SOAP:encodingStyle attribute and is therefore not understood by the WebMethods web service. Here is the error message from the web service:
[B2BCORE.0076.9201] SOAP Message Coder cannot decode message; no encoding style is specified
How do I configure the outbound SOAP adapter within the XI 2.0 J2SE adapter engine to add the SOAP:encodingStyle attribute to the outbound message?
I have tried playing around with the XMBWS.* parameters outlined in the adapter engine documentation but these don't seem to have any influence on the way the SOAP request message is formed.
Any suggestions would be appreciated.
Regards,
-Derek

Hi,
You could use the webMethods XI adapter to create the connection.
Best Regards,
Sander

SOAP adapter redirecting 50000 port posts to 50001 automatically

Hi,
We have the SSL provider activated because we do encrypted messaging with external partner, but we also have internal systems posting via the SOAP adapter without SSL. They are trying to do this via port 50000, but since SSL is active, the message is redirected to 50001. This normally would not be an issue, except, they do not have port 50001 open on the firewall of the internal system sending the message and it is blocked, is there a config setting to NOT automatically redirect messages to 50001?
But acept them via 50000 and 50001.
Thanks,
Chris

Its technically possible to use same port but it may give usability issues in long run. It would be better if you could opt for different ports. During https enabling, the SSL port is identified and the traffic will always use that port. You Might need to disable and re-enable the settings.
Regards,
Prateek

Receiver SOAP Adapter error

Hi All,
 I am getting this response error message in my receiver SOAP Adapter while invoking a synchronous webservice.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <ProcessMessageResponse xmlns="http://Sleek.Integrator.Messaging" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProcessMessageResult>Value cannot be null. Parameter name: Request string is a null reference.</ProcessMessageResult>
</ProcessMessageResponse>
Thx in advance
Ravijeet

Hi All,
 I am still getting the same error value is null. I am not able to track what could be the cause of the error. If I am taking the message from SXMB_MONI and using it in a client tool it is successfully calling the webservice.
Do we need to explicitly mention in some configuration that content type is soap/xml. SOAP header is omitting the content type or is not specifying "soap/xml" as the content type.
I am interacting with a WAF websevice, is there any compatibilty issue with Windows Webservice and SAP XI?
Also what should I pick as the SOAP Action from this wsdl file definition
<wsdl:portType name="IMessageProcessor">
 <wsdl:operation name="ProcessMessage">
 <wsdl:input message="tns:IMessageProcessor_ProcessMessage_InputMessage" wsaw:Action="XXX.Messaging/ProcessMessage"/>
 <wsdl:output message="tns:IMessageProcessor_ProcessMessage_OutputMessage" wsaw:Action="XXX.Messaging/ProcessMessageResponse"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:service name="MessageProcessor">
 <wsdl:port name="BasicHttpBinding_IMessageProcessor" binding="i0:BasicHttpBinding_IMessageProcessor">
 <soap:address location="http://XXX.com/cardax/provisioningservice"/>
 </wsdl:port>
Thx in advance
Ravijeet

Remove authentication in sender soap adapter pi 7.1

Hello
Did anyone manged to remove authentication in PI 7.1 sender soap adapter?
I have updated file web.xml in the file com.sap.aii.adapter.soap.war
and now I want to deploy it,but I dont have any sda in the folder
thx
Shai

hi Shai,
just something to try in case:
you don't need any java parameters of SOAP sender
you can try approach from Stefan:
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
and then:
1. in SICF copy the engine service to a new one
2. put the credentials for this new service inside SICF
then you will have sender SOAP adapter without a password right?
I didn't try it but I guess it would work without
crashing the whole original SOAP sender adapter by
making changes into web.xml
Regards,
Michal Krawczyk

SOAP Adapter: java.io.IOException: unable to create a socket

Hi,
I am trying to use the soap adapter to connect to a URL and post a document. When I try, the adapter throws the following
java.io.IOException: unable to create a socket
Does anyone know what causes this?
I get it both with the SOAP Envelope turned on and off.
I am trying to post to a URL that is usually used for straight HTTPS posts, could this cause an issue? The only reason we are using the SOAP adapter is to be able to send attachments! Hence, SOAP adapter, no SOAP envelope.
Kind Regard,
Chris

Hi,
Had faced the same issue. The possible reasons were :
1. Either the target server might not be responding.
2. The Target URL configured in the communication channel might be wrong.
3. The port to which the message is being sent might not be opened which you need to cross-verify.
For me the issue was the port, which wasn't enabled from our end. The messages went past successfully once it was enabled.
Cheers!!
Jithin James.

Urgent ---- SOAP Adapter

Hai,
The scenario that we are working now is IDOC-XI-SOAP.
We are having problem at SOAP Adapter.
SOAP Adapter Receiver configurations:
TargetUrl : .net webservice
proxy settings : done
soap action : given
In the audit log error code is : General Error
giving error that : soap call failed
any inputs would be highly appreciated.
Thanks
Sri Krishna Charan

Hai All,

How can i check whether my .net webservice is accessible or not in xi server....
bcause xi server is runnig on remote host
Audit log information in message monitor is:
Success The message was successfully received by the messaging system. Profile: XI URL: http://iccxi.sap.com:58000/MessagingSystem/receive/AFW/XI
Success Using connection AFW. Trying to put the message into the receive queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the receive queue.
Success The message status set to DLNG.
Success Delivering to channel: TEST_VONDELSOAP_DEMO
Success SOAP: request message entering the adapter
Success SOAP: call failed
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack

SOAP Adapter without SOAP envelope sets contenttype to application/xml

Similar Messages

Maybe you are looking for