SOAP Adapter nosoap mode !

Hi we have a Http to File scenario. PI will be getting Multipart Http post requests, xml file and pdf files through Http post request, I am using SOAP adapter in nosoap mode, how do I retain the original file name of the pdf while creating the file?

Were you able to send Multipart data to XI from sender? In my opinon, you have to write an adapter module to handle multiple messages as attachment, and soap sender does not support module.
Regards,
Prateek

Similar Messages

Sender SOAP adapter: access Header fields (dont use envelope and nosoap=1)

Hi,
I've just been going through various blogs regarding the SOAP adapter and receiving the actual unconverted content being sent to xi. Trying this out I dont get the exptected result.
What I have done is simply created a web service in XI - added '&nosoap=true' to the url and set the flag in 'Do not use SOAP envelope'.
After this I send synchronous message via xmlspy and receive error 'XIServer:CANNOT_READ_PAYLOAD'.
When checking data received in MDT I only see the envelope containing my additional header info (provided in the request) + some XI headers + a body. The body however pretty much only contain a manifest. The actual payload data that I sent in my request a gone (hence the error message).
When looking i SXMB_MONI i (naturally) also only see the header and body info - no payload. So when mapping step is reached it complains.
I'm aware I should use mapping like xslt/java to map the message. But first I need to see the payload.
Anybody got any clues?
For information I'm running 2004 SP 19.
Best Regards,
Daniel

Hi,
This is not a matter of logging or trace levels - all these thing a set as needed.
I do see the messages but I don't see the actual payload (the body-part sent with my request) in neither the AFW or IE.
Regards,
Daniel

HTTP Header fields in SOAP adapter - Part 2

Hi All,
With regards to my previous thread HTTP Header fields in SOAP adapter
my header issue is solved and hence I have closed the thread but still I am not able to make the connection successful. The new problem is below
My vendor requirement is to specify the header as "Ent-sender" but when we give the same in XI in communication channel it automatically convets into uppercase "ENT-SENDER". Due to case-sensitive in vendor server the connection is not gettingestablished.
Please help me out how to solve the problem.
Note: Sorry for the new thread as it was created due to new problem and also the previuos thread is already too long.
Regards,
Dhill

Hi Neaves,
Thank you, I jave seen the note and find the below solution will be some what realated to my prblem.
The nosoap mode lets the adapter send the XI payload directly without wrapping it in the SOAP envelope. Although the main use of this mode is to send some plain text content directly to some web server, one can use this mode to send their own SOAP message (e.g., with arbitrary headers) to an external web service (See related questions). In this case, the XI payload must be formatted in the SOAP envelope.
To use the nosoap mode, the channel must be configured to use no SOAP envelope.
If yes, can you please let me know how to use nosoap mode otherise let me the other possibilities. I am already using tcpg2.zip to trace the SOAP adapter in which it was confirmed that XI is changing the header automatically into CAPS whatever case we give,
Regards,
Dhill

How to Send Multiple Attachment by SOAP Adapter

Hi,
How to send multiple attachment by SOAP Adapter.
I am able to send single attachment but at the time of sending multiple attachment i am not able to see in SXMB_moni.
Regards,
Anurag

On the communication channel, please check the 'Do Not Use SOAP envelope' option. Also, please, add the "nosoap" attribute to the SOAP adapter caller. Check the note below for more information
#856597 FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
> "How does the nosoap mode work for the SOAP sender adapter?"

How to use Basis Authentication in Sender SOAP Adapter

We implemented one Sender SOAP Adapter and we had to implement the modified WEB.XML method to remove the security specification. We have now asked the developer to correct this situation so we can remove this modification. The Interface developer would like to use Basic Authentication. If you have an automated interface sending in a SOAP Message, how do you do Basic Authentication?
I've tried using:
http://host:port/XISOAPAdapter/MessageServlet?channel=:<Service>:<Channel>&sap-user=xiappluser&sap-password=<Password>&sap-language=EN&sap-client=<Client>
When I do this, I still get the Authentication Pop-Up Window.
How does the Sending Interface either supply the ID and Password on the incoming SOAP Message or respond to the Authentication Pop-Up?
Thanks,
Anne

By Defualt the web service exposed by you will use Basic Authentication mode only.
But the way you do Basic Authentication in the web client is platfrom dependent.
This is not the way to do Basic authentication
http://host:port/XISOAPAdapter/MessageServlet?channel=:<Service>:<Channel>&sap-user=xiappluser&sap-password=<Password>&sap-language=EN&sap-client=<Client>
I am providing you a code snippet on how to Basic Authentication in Java when making the Web Service Call.
If the client is on some other platform just look for the corresponding api.
Please award points if you find this answer useful.
Code Snippet
URL url = new URL(URL);
URLConnection connection = url.openConnection();
if( connection instanceof HttpURLConnection )
((HttpURLConnection)connection).setRequestMethod("POST");
 //connection.setRequestProperty("Content-Length",Integer.toString(content.length()) );
 connection.setRequestProperty("Content-Type","text/xml");
 connection.setDoOutput(true);
 String password = User + ":" + Password ;
 //Where con is a URLConnection
 connection.setRequestProperty ("Authorization", "Basic " + encode(User + ":"+ Password));
 connection.connect();
Encode Method
public static String encode (String source) {
BASE64Encoder enc = new sun.misc.BASE64Encoder();
return(enc.encode(source.getBytes()));

SOAP Adapter + asynchronous message + Runtime Workbench

Hi
I have problem with error monitoring in Runtime Workbench -> Message Monitoring
I have SOAP adapter deployed on Apache Axis.
I have flow SOAP->XI->SOAP (asynchronous mode)
It works great until receiver adapter generate error.
I can see error message in defaultTrace log but in
Message Monitoring-> Details I see only "SOAP: response message
contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault".
SOAP message from receiver adapter (with error) looks like that
<?xml version="1.0" encoding="UTF-8"?>
<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:Body>
 <soapenv:Fault>
 <faultcode>Client</faultcode>
 <faultstring>Internal Server Error</faultstring>
 <detail>
 <myfaultmessage>
 <type>RABAX_STATE</type>
 <message>Divide by 0 (type 1).</message>
 </myfaultmessage>
 <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">pslupkowski</ns1:hostname>
 </detail>
 </soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
I'm think that this message is not well formated and
Adapter Engine can't find some tags during parsing this
message. Any ideas how to solve this problem?
I'm just want to see error description from <myfaultmessage> tag in Message Monitoring

Hi,
Did you check the log on adapter engine?
http://<host>:<port>/MessagingSystem/monitor/monitor.jsp
Take a look to this monitor, here you can see both messages (request and response).
Cheers,
Ricardo.

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

SOAP Adapter: Content Type Issue in WebServices via HTTP

Hi,
I have configured a Receiver SOAP adapter. When i had to test the message i had an HTTP 415 error.
i found that the sender SOAP adpater that received this message is not capable of handling Content-Type: Application/XML i.e. which is being transmitted by the Receiver SOAP Adapter.
Please let me know how to configure in the Receiver SOAP adapter so that the HTTP Content-Type would be TEXT/XML instead of Application/XML .
Thanks in Advance,
Venkatesh

Hi Michal,
I have created a Web service for a RFC function Module. The webservice is available in SOAMANAGER.
It got activated also . But whenever I tried to test, I am getting the below error,
"Message Envelope not found. Probably Empty SOAP message"
 Request:
 POST /sap/bc/srt/rfc/sap/yotci_i015_linkp8sap/100/yotci_i015_linkp8sap/yotci_i015_linkp8sap HTTP/1.1
Host: sapkrftewd01.krft.net:8030
Content-Type: text/xml; charset=UTF-8
Connection: close
Authorization: <value is hidden>
Content-Length: 657
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:YotciI015Linkp8sap xmlns:ns1='urn:sap-com:document:sap:soap:functions:mc-style'><IvParam1>POD</IvParam1><IvParam2>00006095</IvParam2><IvParam3>01/14/2009</IvParam3><IvParam4>PDF</IvParam4></ns1:YotciI015Linkp8sap></SOAP-ENV:Body></SOAP-ENV:Envelope>
 Response:
 HTTP/1.1 500 Message E 1S 406 cannot be processed in plugin mode HTTP
content-type: text/xml; charset=utf-8
content-length: 0
accept: text/xml
sap-srt_id: 20090224/141936/v1.00_final_6.40/49A4677A2D0736EDE10000000A3597E9
server: SAP Web Application Server (1.0;700)
Is this because of "do not use SOAP envelope" check?
I didn't check this check box.
If that is the error could you please tell me how to see the "do not use SOAP envelope"?
Where can I find SOAP channel?
I am very new to SOAP concept.
One JAVA application is going to invoke this Webservice from SAP.
Please help me.
Thanks,
Bala.

SOAP Adapter doesn't find channel

Hi all,
I currently have XI 3.0 SP11 running and I'm trying to set up a simple <SOAP> -> <XI> -> <SOAP> scenario with it. Therefore I configured a Business Service called "WSClient" without associating it to a party. This service contains a Communication Channel called "SOAPClient" that is configured to use the SOAP Adapter and to act as a sender.
When i now try to send data to XI using a simple web service client i get the following error:
SystemError:
 <context>XIAdapter</context>
 <code>ModuleUnknownException</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#7 $)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:497)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at ...
</text>
Therefore I tried to use the HelperServlet to see if the channel is available. When invoking the HelperServlet with the parameters action=FindChannel&channel=:WSClient:SOAPClient
I get the following error:
<SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError>
 <context>XIAdapter</context>
 <code>ADAPTER.SOAP_EXCEPTION</code>
 <text>
java.lang.Exception: Channel not found for SOAPClient in http://sap.com/xi/XI/System^SOAP
 at com.sap.aii.af.mp.soap.web.HelperServlet.processFindChannel(HelperServlet.java:408)
 at
Somehow the Adapter Engine seems not to recognize the channel I have configured.
Any ideas how to solve this problem?
Thanks for your help.
Christian

Hi,
I have observed that when the SOAP sender channel is not activated, and a request is posted to XI, u will get "ModuleUnknownException".
When the Sender SOAP Adapter is created in BE mode and "no receiver determination" is created, you will encounter "DeliveryException" while testing using XMLSPY. U will find that the message has failed in XI with an error "NO_RECEIVER_CASE_BE"
When the Sender SOAP Adapter is created in EO/EOIO mode and "no receiver determination" is created, you will not encounter any error while testing using XMLSPY. But you will find that the message has failed in XI with an error "NO_RECEIVER_CASE_ASYNC"
Also make sure you defined the correct
"Default Interface NameSpace" and
"Default Interface Name"
in the Sender SOAP Channel. Else the message will fail b'cos it will not find the correct receiver Determination.
Cheers,
Siva Maranani

SOAP adapter not working - say No adapter registered??

Hello experts,
I have configured a receiver SOAP adapter to call a web service from my UDF for a SOAP Lookup. But in my RWB's Channel Monitoring the status of all my SOAP adapters configured in the system is "????" with the short text "No adapter registered for this channel".
When i run my UDF, there is no technical error in the code by the SOAP adapter which i call in the UDF is not gtting called with the error as "The channel cound not be found in the Integration Server Java Cache. Check if the channel exists in the Integration Builder Directory and execute a refresh of the Java Cache".
The channel does exists in the ID and when when i see the cache status, it saws all green though in channle monitoring i am not able to see anystatus.
Please help.
Regards,
Yash

Make sure that the channel name is exactly similar. Edit the channel, just description, save and activate again. Then perform CPACache refresh using PIDIRUSER and this url.
http://XIHost:JavaPort/CPACache/refresh?mode=full
Regards,
Prateek

SOAP Adapter and plain HTTP

Hello,
what does the option
"Do not use SOAP envelope" on a SOAP SENDER adapter mean?
Does this mean, that only the payload from the soap message is sent to the integration server? (without the soap envelope)
Or does this mean, that I can send a XML message without SOAP envelope to the adapter from a HTTP client?
Which means, I can use the SOAP adapter like the standard PLAIN HTTP adapter, but I can implement a adapter module!
How knows more details on that?
Best regards
Werner Magerl

Hi Werner,
> When I use the option nosoap=true and the setting "Do
> not use SOAP envelope" then it works.
> So both things must be used together.
> Is this correct?
Yes. In your scenario you need both parameters.
> What does this mean, that the XI message is created
> after the self-defined modules?
When you write a module for sender file-adapter, you have to deal with an XI message, as the file adapter fisrt creates the XI message, then calls the customer module.
When you write a module for sender SOAP adapter, you have to deal with the incoming message, as the SOAP adapter first calls the customer module, then creates the XI message.
> We just want to check the incoming XML message
> against a local XSD. If there is an error against the
> XSD, we do not want to receive the message, we want
> to send back a specific HTTP error code.
> This is the reason, why we just want to send a
> plainHTTP message and not a SOAP Message.
> In my opinion this should work?!
> We do not want to use other modules.
Yes, that should work.
> Do you have experience on adapter modules for SOAP
> adapter?
No, I have no experience with adapter modules for sender SOAP adapter.
Regards
Stefan

Prolog with soap adapter in PI

Dear All,
We run a scenario Proxy=>PI=>HTTP
The remote service accepts messages POSTed using either the form-encoded format (name, value pairs)
or the multi-part mime format which enables the files to be passed to the web service.
In both cases, the external service replies with a multi-part message.
We are going to use the SOAP adapter (plain HTTP does not support attachments)
with nosoap flagged.
What is best approach to add a prolog before the actual XML with SOAP adapter,
to simulate the form-encoded format?
Example :
USER=USER1&PASS=PASS1&DB=DB1
In the 2nd situation, how to create the different documents before the actual XML?
Example :
7d924f5b0464
Content-Disposition: form-data; name="USER"
USER1
7d924f5b0464
Content-Disposition: form-data; name="PASS"
PASS1
7d924f5b0464
Content-Disposition: form-data; name="DB"
DB1
Best regards,
KR,
Laurent

Dear All,
We run a scenario Proxy=>PI=>HTTP
The remote service accepts messages POSTed using either the form-encoded format (name, value pairs)
or the multi-part mime format which enables the files to be passed to the web service.
In both cases, the external service replies with a multi-part message.
We are going to use the SOAP adapter (plain HTTP does not support attachments)
with nosoap flagged.
What is best approach to add a prolog before the actual XML with SOAP adapter,
to simulate the form-encoded format?
Example :
USER=USER1&PASS=PASS1&DB=DB1
In the 2nd situation, how to create the different documents before the actual XML?
Example :
7d924f5b0464
Content-Disposition: form-data; name="USER"
USER1
7d924f5b0464
Content-Disposition: form-data; name="PASS"
PASS1
7d924f5b0464
Content-Disposition: form-data; name="DB"
DB1
Best regards,
KR,
Laurent

Synchronous messages for SOAP adapter.

Hi All,
I wanna expose an interface in XI as a WebService.My requirement is to invoke a webservice which takes some input and hands it over to a DataBase and gets something from it(DB) and hands it over to the application which had called this WebService.Both the request and response have to go and come through the WebService.Is it possible to design an Outbound Intf in Synchronoues mode with both the input and output messages types and expose that Intf as a WebService.
Clarification and help on this wud b appreciated.
Thanx in Advance.
Anil Kumar Veepuri

Hi Anil,
You can definitely make an outbound Interface as a webservice.For this create two message
types(Request & Response) and make a synchoronous Message Interface out of it.This will be
our Outbound Interface. You will Definitely have JDBC Request and response.
Map the outbound Resquest type-> JDBC Request.
JDBC Response->Outbound Response.
Go to Tools->Define Web service, mention the Outbound Interface you have created.Now you save the WSDL created out of it and make a call to this interface through the SOAP Adapter.
Cheers,
Rashmi

SOAP Adapter with application/x-www-form-urlencoded

You can use the content type "application/x-www-form-urlencoded" in a SOAP adapter?
Thank you.

I did the configuration below:
"Here you have to use below configuration parameters for Module
Transform.Class = com.sap.aii.messaging.adapter.Conversion
Transform.ContentType = application / x-www-form-urlencoded "
However, got the following error:
=======================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.ClassNotFoundException: com.sap.aii.messaging.adapter.Conversion -
Loader Info -
ClassLoader name: [sap.com/com.sap.aii.af.mod.trans.app] Living status: alive Direct parent loaders: [system:Frame] [service:servlet_jsp] [service:ejb] [library:engine.j2ee14.facade] [library:com.sap.base.technology.facade] [library:com.sap.aii.af.lib] [library:com.sap.aii.af.sdk.lib] [service:com.sap.aii.af.cpa.svc] [service:com.sap.aii.af.svc] [service:com.sap.aii.adapter.xi.svc] [library:com.sap.aii.adapter.lib] Resources: C:\usr\sap\PI1\DVEBMGS04\j2ee\cluster\apps\sap.com\com.sap.aii.af.mod.trans.app\EJBContainer\applicationjars\com.sap.aii.af.mod.trans.ejb.jar -
</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
=======================================================================================================
Any suggestion?
Thank you.
Regards,
Bruno

HTTP or SOAP Adapter Can't Reach "Outside"

Does anyone have any direction or could anyone point me to some SAP docs on how to configure your network to allow the adapters to get out to the "wild internet". I have tried configuring the SOAP adapter to hit our normal web browsing proxy/port along with my user name/password but that isn't working. When I go to the web service URL I can reach it fine from my browser but not from the XI box ( adapter ).
Thanks!
Andrew

Hi Andrew,
Try to use HTTP Destination mode and create a RFC Destination in sm59 (HTTP Type=G).
Specify all the connection parameters - proxy details, authentication details etc. Use Test RFC (F8) there and try to figure out if it is working. If so, then XI can use that RFC destination and connect to the internet.
regards,
Pops V

SOAP Adapter nosoap mode !

Similar Messages

Maybe you are looking for