What is payload, xi-soap message and xml payload....

can any 1 explains abt What is payload, xi-soap message and xml payload....

Hi Shiva,
see this abstract from messages file:
"The SOAP header of a message contains all the important information that the Integration Server requires to forward the message, while the payload contains the actual business data (such as <PurchaseOrder> in the example above). <b>You can also append an unlimited number of attachments to the message before it is sent. Attachments typically comprise non-XML data, for example, pictures, text documents, or binary data."</b>
Check this link for more info:
http://help.sap.com/saphelp_nw04/helpdata/en/b6/0b733cb7d61952e10000000a11405a/content.htm
Regards,
Subhasha

Similar Messages

How to get Payload of SOAP Message in Advance Adapter Engine

HI All,
I am wondering if anybody can tell me how to view the Payload of SOAP Sender and Receiver Message in Advance Adapter Engine?
Does Anybody know how to check mapping payload in Advance Adapter Engine because in ABAP you can see the mapping payload under Request Message Mapping but when you use AAE you can't see the Request Message Mapping Payload.
I have a SOAP to RFC Scenario in which I can't see the SOAP Sender and RFC Receiver Mapping Payload.
When I am sending incorrect data to an RFC I am getting this error which is very strange and new to me.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Unable to split a synchronous message
Any comments would be much appreciated.
Thanks,
Iqbal

HI All,
I have managed to find Michal's Blog which is talking about getting the mapping payload but unfortunately I don't know how to create Adapter Module so I am wondering if somebody can please provide me EAR file so that I will request the Basis guys to deploy the code and hopefully this will solve my query.
Michal's Blog
As you all probably know while using local Advanced Adapter Engine (AAE) processing in SAP PI 7.1 the message is logged only once (during processing by sender adapter). This is great in terms of performance but what if we need to check the mapping output? Is there a way do do it somehow? It turns out that we don't have such an option in standard yet. Is there any alternative then?
It turns out there is - a simplest adapter module there is...
Local AAE works in such a way that from the sender adapter it executes the receiver adapter so in the outbound message to PI processing you can see the adapter info logs of the receiver adapter and this is what we can use. The idea is to add an adapter module to the receiver adapter which will put the content of the message into the audit log of PI message processing. We can do it by writing a few lines of code:
PI/XI: target message logging with local AAE not possible ? not anymore...
*Please upload the file in any free site or <REMOVED BY MODERATOR>
<READ RULES OF ENGAGEMENT>
Thanks,
Edited by: Prateek Raj Srivastava on Jan 6, 2012 9:10 PM

SOAP body and XML

Hi,
how can I get the body content of SOAP messages in XML format?
I have a service that get as input a XML string, I want to create a Web Service, with this service, without change all but I have not understand how take the XML to give it to the old service.
TIA
Aslas

You should check out the following in details. It
explains to you how soap works and how you can
implement a listener to retrieve the XML doc in
the body.
http://xml.apache.org/soap/docs/index.html
Amlan

Transform payload to SOAP message using XSLT

Hello,
I'm working with e-invoice for Finland (called Finvoice) and is supposed to send a soap message as a file via file/ftp adapter.
The output from SAP is an INVOIC idoc that is mapped to a given output structure. This works fine.
The soap envelope is created via xslt transformation.
The Envelope is created correctly but I'm struggling with how to add the payload to the message. It needs to look as shown below, (I'm just showing the essential part).
My problem is that I don't know how to add the doctype part via xslt:
<?xml version="1.0" encoding="ISO-8859-15"?>
<!DOCTYPE Finvoice SYSTEM "Finvoice.dtd">
I get validation errors when adding this in the xsl. The content of the payload looks good.
Does anyone know how this can be solved?
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<eb:Manifest eb:id="Manifest" eb:version="2.0">
<eb:Reference eb:id="Finvoice" xlink:href="1017000018">
<eb:schema eb:location="http://www.pankkiyhdistys.fi/verkkolasku/finvoice/finvoice.xsd" eb:version="2.0"/>
</eb:Reference>
</eb:Manifest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<?xml version="1.0" encoding="ISO-8859-15"?>
<!DOCTYPE Finvoice SYSTEM "Finvoice.dtd">
<?xml-stylesheet type="text/xsl" href="Finvoice.xsl"?>
<Finvoice Version="1.2">
<SellerPartyDetails>
<SellerPartyIdentifier>SellerPartyIdentifier23456789012345</SellerPartyIdentifier>
<SellerOrganisationName>SellerOrganisationName3456789012345</SellerOrganisationName>
// Best regards Hans

hI,
How to add the the below soap frame thru XSLT mapping.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">
<SOAP-ENV:Header>
<eb:MessageHeader xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" SOAP-ENV:mustUnderstand="1" eb:version="2.0">
<eb:From>
<eb:PartyId>0037123456678</eb:PartyId>
<eb:Role>Sender</eb:Role>
</eb:From>
<eb:From>
<eb:PartyId>NDEAFIHH</eb:PartyId>
<eb:Role>Intermediator</eb:Role>
</eb:From>
<eb:To>
<eb:PartyId>FI2757800750155448</eb:PartyId>
<eb:Role>Receiver</eb:Role>
</eb:To>
<eb:To>
<eb:PartyId>OKOYFIHH</eb:PartyId>
<eb:Role>Intermediator</eb:Role>
</eb:To>
<eb:CPAId>yoursandmycpa</eb:CPAId>
<eb:ConversationId/>
<eb:Service>Routing</eb:Service>
<eb:Action>ProcessInvoice</eb:Action>
<eb:MessageData>
<eb:MessageId>20081228-010142</eb:MessageId>
<eb:Timestamp>2008-12-28T01:01:42+03:00</eb:Timestamp>
<eb:RefToMessageId/>
<eb:RefToMessageId>XS1027.LPTF82/268</eb:RefToMessageId>
</eb:MessageData>
</eb:MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<eb:Manifest eb:id="Manifest" eb:version="2.0">
<eb:Reference eb:id="Finvoice" xlink:href="XS1027.LPTF82/268">
<eb:Schema eb:location=" http://www.finvoice.info/yrityksen_verkkolasku/ladattavat/Tekniset tiedostot/schemat/Finvoice.xsd" eb:version="2.0"/>
</eb:Reference>
</eb:Manifest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<?xml version="1.0" encoding="ISO-8859-15"?>
<!DOCTYPE Finvoice SYSTEM "Finvoice.dtd">
<?xml-stylesheet type="text/xsl" href="Finvoice.xsl"?>
Thanks and Regards,
Hymavathi

Payload of SOAP-Message cannot be read

Hi,
I'm sending an easy message to the XI 3.0 soap-adapter:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
     <SOAP:Header/>
     <SOAP:Body>
          <plain>test</plain>
     </SOAP:Body>
</SOAP:Envelope>
Unfortunately I get always the error:
<SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
Thank you for reading und help,
Udo

Hi Stefan,
Yes, I go from Client to XI to R/3 via SOAP.
I don't know how the wsdl can solve my problem.
I use wfetch to send the message. I sent to
http://host:port/XISOAPAdapter/MessageServlet?channel=
:service:channel
as described in sap bibliothek.
Without the right namespace in the channel the receiver determination runs to an error but it works fine.
We are on XI 3.0 SP 9.
The error message coming from XI back to wfetch:
[code]<?xml version='1.0'?>\r\n
\r\n
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>\r\n
<SOAP:Body>\r\n
    <SOAP:Fault>\r\n
      <faultcode>SOAP:Server</faultcode>\r\n
      <faultstring>failed to call the adapter engine</faultstring>\r\n
      <detail>\r\n
        <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>\r\n
          <context>XIAdapter</context>\r\n
          <code>DeliveryException</code>\r\n
          <text><![CDATA[\r\n
com.sap.aii.af.mp.module.ModuleException\r\n
\tat com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:697)\r\n
\tat com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)\r\n
\tat com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:221)\r\n
\tat com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)\r\n
\tat com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:513)\r\n
\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:760)\r\n
\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:853)\r\n
\tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)\r\n
\tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)\r\n
\tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:339)\r\n
\tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:317)\r\n
\tat com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:810)\r\n
\tat com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)\r\n
\tat com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)\r\n
\tat com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)\r\n
\tat com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)\r\n
\tat com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)\r\n
\tat com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)\r\n
\tat java.security.AccessController.doPrivileged(Native Method)\r\n
\tat com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)\r\n
\tat com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)\r\n
Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception used by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:\r\n
\tat com.sap.aii.af.mp.soap.ejb.AFCallerApplication.perform(AFCallerApplication.java:122)\r\n
\tat com.sap.aii.messaging.srt.ApplicationBubble.onMessage(ApplicationBubble.java:29)\r\n
\tat com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:56)\r\n
\tat com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:576)\r\n
\t... 20 more\r\n
Caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:\r\n
\tat com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:366)\r\n
\tat com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:123)\r\n
\tat com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:419)\r\n
\tat com.sap.engine.frame.core.thread.Task.run(Task.java:60)\r\n
\tat com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)\r\n
\tat com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)\r\n
          ]]></text>\r\n
        </s:SystemError>\r\n
      </detail>\r\n
    </SOAP:Fault>\r\n
</SOAP:Body>\r\n
</SOAP:Envelope>\r\n
[/code]
Regards (and thanks for your help), Udo

Read payload for error messages and throw a red flag in SXMB_MONI

Hello All,
I am calling a synchronous web service from PI ccBPM and getting a response back to PI ccBPM itself.
So the steps in BPM are receive(from CRM), sync step (to call web service) and a control step (to end the BPM process).
The requirement is to check if error_list node in the response from web service call has a value in it and throw an error in SXMB_MONI so that they can easily identify how many messages errored out out of thousands of messages.
This is the response structure for web service if there are errors.
<manageResponse>
<result>
                <ErrorList>
                    <object>
                        <hyatt>partnerupdate--NR</hyattt>
                        <Message />
                        <Operation>jukio</Operation>
                        <User>atuser</User>
                    </object>
                 </ErrorList>
</result>
</manageResponse>
Again I only need to see if error_list is not empty and throw a red flag error in SXMB_MONI.
Thanks
Mike

Hi Mich,
In Response map when Error segment appear's fail the maping so that you can see the list of message in MONI. and do not need to put any conditions in MONI.
I mean in your Respoinse when ERROR_LIST segment coman under that one manatory field you select and take that field length say 20 characters.
source field->Substring (0,100) get the 100 characters from source in that case case from source it won't get 100 characters mapping will fail so that you can see the Error messages in SXMB_MONI.
Finally what I am saying do the wrong condition mapping in the response mapping so that mapping will fail.
Regards,
Venu.

What is the difference between message and multipart message?

Does the multipart message type provides the flexibility that the schema assigned to it can be changed later on?
Suppose if a message is assigned with the schema directly, can it not be changed(adding, deleting elements,etc)
once deployed.
If the receive port is set to message box, should the receive shape be assigned with multi part message type or just with a message where a schema is assigned directly.
what should be done if the input schema which is not a multipart message type changes after deployed?

Thread Question: Technically, there is no difference. All messages are multi-part. The 'single part' type in the Orchestration Designer is just a convenience offered by the Orchestration Designer, the underlying type is the same for both.
First Question: The difference you see is that the Orchestration Designer does not enforce the Body part Type on Port bindings because it it abstracted by the Multi-Part Type, which, yes, means you can change Body Part Type without having to unhook the Port
and Receive/Send Shapes.
Second Question: You can make any change to a Schema, except the Root Node Name and Namespace, without affecting the Message variables or Port types at all. So yes, you can add/remove/change elements without even opening an Orchestration.
Third Question: There's really no difference because outside of the Orchestration Designer, there is no difference between the 'single' and Multi-Part Message type. You will always get a filter on the Body part MessageType.

What is DTD (related to BC and XML)?

Hi all,
Could you please refer me to links/documents, after giving a brief overview of <b>DTD</b>
Thanks,
Charles.

Hi,
The purpose of a DTD is to define the legal building blocks of an XML document. It defines the document structure with a list of legal elements. A DTD can be declared inline in your XML document, or as an external reference.
Internal DTD
This is an XML document with a Document Type Definition: (Open it in IE5, and select view source)
<?xml version="1.0"?>
<!DOCTYPE note [
><!ELEMENT note (to,from,heading,body)>
<!ELEMENT to (#PCDATA)>
<!ELEMENT from (#PCDATA)>
<!ELEMENT heading (#PCDATA)>
<!ELEMENT body (#PCDATA)>
]>
<note>
<to>Tove</to>
<from>Jani</from>
<heading>Reminder</heading>
<body>Don't forget me this weekend!</body>
</note>
The DTD is interpreted like this:
!ELEMENT note (in line 2) defines the element "note" as having four elements: "to,from,heading,body".
!ELEMENT to (in line 3) defines the "to" element to be of the type "CDATA".
!ELEMENT from (in line 4) defines the "from" element to be of the type "CDATA"
and so on.....
External DTD
This is the same XML document with an external DTD: (Open it in IE5, and select view source)
<?xml version="1.0"?>
<!DOCTYPE note SYSTEM "note.dtd">
<note>
<to>Tove</to>
<from>Jani</from>
<heading>Reminder</heading>
<body>Don't forget me this weekend!</body>
</note>
This is a copy of the file "note.dtd" containing the Document Type Definition:
<?xml version="1.0"?>
<!ELEMENT note (to,from,heading,body)>
<!ELEMENT to (#PCDATA)>
<!ELEMENT from (#PCDATA)>
<!ELEMENT heading (#PCDATA)>
<!ELEMENT body (#PCDATA)>
Why use a DTD?
XML provides an application independent way of sharing data. With a DTD, independent groups of people can agree to use a common DTD for interchanging data. Your application can use a standard DTD to verify that data that you receive from the outside world is valid. You can also use a DTD to verify your own data.
For more information, please check this links.
http://help.sap.com/saphelp_nw04/helpdata/en/64/0bee3da7138e5be10000000a114084/content.htm
http://help.sap.com/saphelp_46c/helpdata/en/dc/6b827c43d711d1893e0000e8323c4f/content.htm
Regards,
Ferry Lianto

Payload to field of a XML / Payload to XML tag

https://wiki.sdn.sap.com/wiki/display/XI/WholePayloadtoaXML+field
Posted a Wiki that will handle copying a payload to a field of an XML. Encourage others to enhance this wiki by posting alternative ways. Ex. XSLT code

Hi Experts
I have not got any solution for this issue. Can any of you get me some clue to work on this issue with sorting news based on a date field in a XML form?
I removed the property link from the screen field Input field.
Thank you
Best Regards
Ramamoorthy D

How to bind xml generated by guide in Soap request message and then unbind it?

Hi
I have issue in "invoke web service" in adobe LC process ?
Actually , i have process, a long lived, which take input as xml . this xml(data) it get from guide data submission in browser by user?
Now , what i need to achieve here is that i have to invoke this long lived process in one of my other process via "invoke web service" option.And to do that, i need to bind the xml into Soap message and then it unbind to back same xml in the other process to use it?
so, my question here is how can i achieve that?

Hello Iñaki
Thanks for your reply.
I had read the blog about the XMLAnonymizerBean. It looks very straightforward, and in theory should do just what I need.
I've added the anonymizer bean as the first module as the SOAP message is asynchronous, and I want to remove the namespaces from the request.
I want to exclude all namespaces so I haven't set any parameters.
The SOAP channel in Communication Channel monitor has a status of 'Channel Started but inactive'. I cannot see any messages in the Processing Details for this channel, even though I have sent test messages from Java code and from RWB (the message from RWB without the namespace does reach the receiver). This makes me wonder if I have not configured the interface to use the new SOAP channel correctly, although I can see it in the Receiver Determination configuration overview.
I can see the messages in SXMB_MONI but can't find which communication channel is being used by the sender.
I'm using PI 7.1.
regards
Steve

PI 7.1 SOAP Adapter - Message Payload for Failed Messages - Where to find

We are exposing a webservice through SAP PI. Occassionaly we have customers calling our webservice and some failure occurs. The error is usually the way that the customer is calling the webservice (missing elements, misnamed tags, bad content in the WS payload..). Generally in these cases we can see the error in communication channel monitoring.
Here is an example:
12/12/11 4:39:07 PM com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-complex-type.2.4.b: The content of element 'SupplierInvoice' is not complete. One of '{"":Invoice}' is expected. at line 1, column 227
12/12/11 4:39:06 PM request received for a channel
I understand the issue, but it would be extremely helpful to have the full SOAP Envelope and Payload of a request when it fails. The communication channel will show a SUCESSFUL message payload with a link to it. But it does not show a failed one.
Where can I find the FAILED payload that accompanies this message? These failures occurs before any mapping or being seen in RTWB Adapter Engine message monitoring... I did some searching around, but did not find anything offhand. I would greatly appreciate any pointers from anyone who has crossed this bridge.

Hi,
When the web service is being called by external application, the first point of contact would be the sender communication channel which converts the SOAP message into XML message and pass to integration engine ( In case of success )
But if the web service call fails due to WSDL validation, Authentication issue, Bad content, invalid content type, you would not see the payload in the sender communication channel or in Adapter engine. You can just see error message in the sender communication channel . I have experienced this many times and i always ask the web service team to provide the SOAP message for validation/investigation purpose.

Testing XML Payload of Message Mapping in RWB

Hi All,
Is there any way where we can test the XML payload of Message Mapping bypassing the usual testing of messages thorugh IE .
What i mean here is passing tge XML payload of Message Mapping directlyy to Adapter Engine...
Regards
Vinay P.

Hi Vinay
As said above
You can use Testing the Runtime feature to do this task
RWB -> Component Monitoring -> Integration engine Test tab
You can also use this feature for Adapter engine and J2SE adapter - File & JDBC
http://help.sap.com/saphelp_nw70/helpdata/EN/33/b99eebd9261b4886d6f6a354b8dcdf/content.htm
Follow michal blog give above for screen shots
Thanks
Gaurav

There is no payload in Soap request

Hi Expert,
I am testing Soap to RFC scenario. I am firing the soap request using Altova xmlspy. I am getting the response as cannot read payload. I checked in the Moni, no payload is coming to xi. but i am sending data through soap request. Below the response wat i am getting
<?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>RecoverableException</code>
                         <text><![CDATA[
com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:919)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:258)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
     at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:167)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:424)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
          ]]></text>
                    </s:SystemError>
               </detail>
          </SOAP:Fault>
     </SOAP:Body>
</SOAP:Envelope>
Please help me out in this issue
Thanks,
Venky

Hi,
Check whether your payload message which you are passing in HTTP Client tool is correct or not, try to copy the payload from Integration Repository while testing your mapping program.
Also check the Integration Engine Configuration runtime parameters,
Open Transaction SXMB_ADM -> Integration Engine Configuration -> Change Specific Configuration
Check the values of below given parameters for runtime category, these values must be maintained:
LOGGING, LOGGING_SYNC, LOGGING_PROPAGATION, TRACE_LEVEL and TRACE_LEVEL_PROPAGATION.
Look into this thread ... it seems something similar with your problem.
Payload of SOAP-Message cannot be read Try these solutions.
Regards
Aashish Sinha

Soap message with Attachment

Hi All,
I have a requirement wherin I have to send an attachment(image) along with the soap payload.i.e. the soap message contains the payload and an attachment.For eg. the soap message is as shown below:
<?xml version="1.0" encoding="UTF-8" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
    <ns1:MT_Soap xmlns:ns1="http://www.adc.com/sample">
         <Record>
            <FieldXML>abc</FieldXML>
            <FieldAthmt />
         </Record>
      </ns1:MT_Soap>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
How can I include the attachment(which is on a local machine) in the above soap message?
Is it posssible to send the attachment in the field "FieldAtthmt"?
If it is possible to send an attachment with the soap message then how can that attachment be handled in XI?
Thanks in advance,
Vikram

Hi,
A SOAP message may need to be transmitted together with attachments of various sorts, ranging from facsimile images of legal documents to engineering drawings. Such data are often in some binary format. For example, most images on the Internet are transmitted using either GIF or JPEG data formats. In this document we describe a standard way to associate a SOAP message with one or more attachments in their native format in a multipart MIME structure for transport.
yes it is possible to send attachment with the SOAP.
SOAP Message Packages
A "SOAP message package" contains a primary SOAP 1.1 message. It may also contain additional entities that are not lexically within the SOAP message but are related in some manner. These entities may contain data in formats other than XML. The primary SOAP 1.1 message in a message package may reference the additional entities. Such additional entities are often informally referred to as "attachments." This section describes how to construct SOAP message packages and how SOAP processors will process them.
A SOAP message package is constructed using the Multipart/Related media type, which is defined in RFC 2387. The rules for the construction of SOAP message packages are as follows:
The primary SOAP 1.1 message must be carried in the root body part of the Multipart/Related structure. Consequently the type parameter of the Multipart/Related media header will always equal the Content-Type header for the primary SOAP 1.1 message, i.e., text/xml.
The MIME Multipart/Related encapsulation of a SOAP message is semantically equivalent to a SOAP protocol binding in that the SOAP message itself is not aware that it is being encapsulated. That is, there is nothing in the primary SOAP message proper that indicates that the SOAP message is encapsulated .
For more details you can refer these links
http://www.w3.org/TR/SOAP-attachments
http://www.w3.org/TR/soap12-af/
regards
Aashish Sinha
PS : reward points if helpful

Http Header for SOAP message.

Hello,
I need to set some custom HTTP Header when i send the SOAP message to an endpoint.
I tried this..but doesn't solve my requirement.
SOAPMessage soapmsg = messageFactory.createMessage();
MimeHeaders mime = soapmsg.getMimeHeaders();
mime.addHeader("SOAPAction", "xxxx");
mime.addHeader("Sender", "yyy");
SOAPMessage reply = connection.call(soapmsg, destination);
Can anyone please guide me how to set HTTP headers for SOAP?
Thanks,

The following snippet is some code froma stand-alone web service client that I use for testing. It picks up an XML as the payload of the web service, wraps it in a SOAP message and fires it at the web service endpoint.
     System.out.println("Create the SOAP message.\n");
     MessageFactory messageFactory = MessageFactory.newInstance();
     SOAPMessage message = messageFactory.createMessage();
     System.out.println("Creating a DOM object from the JAXB payload.");
     DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
          factory.setValidating(false);
             factory.setNamespaceAware(true);
     DocumentBuilder parser = factory.newDocumentBuilder();
     Document doc = parser.parse("file:payload.xml");
     // Add the HTTP headers.
     message.getMimeHeaders().addHeader("User-Agent", "Mozilla/4.0 [en] (WinNT; I)");
     message.getMimeHeaders().addHeader("Host", "localhost:9080");
     message.getMimeHeaders().addHeader("Content-type", "text/xml");
     message.getMimeHeaders().addHeader("SOAPAction", "http://www.xxx.com.au/wsdl/someWebService");
     message.setProperty(SOAPMessage.CHARACTER_SET_ENCODING, "utf-8");
     SOAPEnvelope envelope = message.getSOAPPart().getEnvelope();
     envelope.addNamespaceDeclaration("n", "http://xxx/webService");
     envelope.addNamespaceDeclaration("xsd", "http://www.w3.org/2001/XMLSchema");
     envelope.addNamespaceDeclaration("xsi", "http://www.w3.org/2001/XMLSchema-instance");
     System.out.println("Adding the payload to the SOAP body.\n");
     SOAPBody body = message.getSOAPBody();
     SOAPBodyElement docElement = body.addDocument(doc);
     System.out.println("This is the SOAP message.\n");
     message.writeTo(System.out);
     System.out.println("\nPutting the payload on the wire.\n");
     SOAPConnectionFactory conFactry = SOAPConnectionFactory.newInstance();
     SOAPConnection connection = conFactry.createConnection();
     URL endpoint = new URL("http://localhost:9080/xxx/services/yyy-webservices");
     SOAPMessage response = connection.call(message, endpoint);
     System.out.println("Payload sent. Closing the connection.\n");
     connection.close();

What is payload, xi-soap message and xml payload....

Similar Messages

Maybe you are looking for