Where is the SOAP Payloads of XI Message in host?

Hi to all,
   I'm trying to find the XML documents(SOAP Payloads of XI Message) in PI host.
Anybody knows which file include this files?
   Look forward your help!
   Thanks!

Jean ,
Same query came early morning ...
Information is stored in the table SXMSPMAST (or SXMSPMAST2 ).
This will help you : /people/alessandro.guarneri/blog/2008/09/15/xipi-message-payload-from-java
Regards ,

Similar Messages

Capture the file name in the payload from the SOAP payload

Hi ,
We have a scenario , a file to RFC , we need the file name which is coming the SOAP payload . This file name needs to be captured in the payload . Please tell me is there any way capture this .
Thanks
Anita

Anita,
If SP14 and above , do this,
Sender File adapter --> Adapter Specific Identifiers --> Select File name
Then in your mapping, you can use this piece of code to access / get the file name,
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String FileName = conf.get(key);
Regards,
Bhavesh

Where is stored xml payload of XI messages

Hi to all,
where can I find the XML payload of each XI Message that I see in the SXI_MONITOR? I want to find the table or the FUNCTION MODULE that contains/retries the XML Payload.
Thanks to all!

Hi,
The messages are stored in the Table.
SXMSPMAST---->Integration Engine: Message Queue (Master)
SXMSSYERR---->XMS: System Error Error Codes
SXMSCLUP -
>XMB: Property Cluster
SXMSCLUR -
>XMB: Resources Cluster
Regards
San

Where is the SOAP Method in XI generated WSDL?

Hi Experts,
I have generated a WSDL from XI for the outbound interface. The web application developer is using this WSDL to send a SOAP request from the web application, but he is not finding a SOAPMethod in the WSDL. Could someone please tell how the XI generated WSDL is to be used from a web application?
Thanks,
Shobhit

Thanks Prateek, but could you send me some document / link on how to send a SOAP request to an XI generated webservice. Is it in any ways different to a regular webservice deployed on a http server.
We are trying to send a SOAP request using a .Net based application. Any clues / leads on how to send the request using the XI generated WSDL.
Appreciate your help.
Thanks,
Shobhit
p.s. i have the following in my WSDL:
     <wsdl:binding name="OB_NP_WorkOrderDetails_MIBinding" type="p1:OB_NP_WorkOrderDetails_MI"
                  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"
                                  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
          <wsdl:operation name="OB_NP_WorkOrderDetails_MI">
               <soap:operation soapAction="http://sap.com/xi/WebService/soap1.1"
                                                    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
               <wsdl:input>
                    <soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
               </wsdl:input>
               <wsdl:output>
                    <soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
Edited by: Shobhit Swarup Mathur on Aug 4, 2008 10:51 AM

Where is the configuration file for my message server ?

Hi:
I am in charge for a message server version upration from 5.1 to 5.2, My question is very simply , I can not find configuration file for message server,when I execute start-msg [smtp | imap | pop | store | http] which configuration file it will read ?
and /usr/iplanet/server5/slapd-www/config/slapd.conf
is my ldap server configuration file ?
and the following three file is mta related file ?
/usr/iplanet/server5/msg-www-1/imta/config/dispatcher.cnf
/usr/iplanet/server5/msg-www-1/imta/config/job_controller.cnf
/usr/iplanet/server5/msg-www-1/imta/config/imta.cnf
My question is very simple and I am a new junior for ims . Anyway Thanks !!
$ imsimta version
iPlanet Messaging Server 5.2 (built Feb 21 2002)
libimta.so 5.2 (built 15:07:23, Feb 21 2002)
SunOS ctidml 5.8 Generic_108528-27 sun4u sparc SUNW,Ultra-5_10

There is NO ONE messaging server configuration file.
The store configuration is read from the configuration ldap server on startup, and cached in temporary files, msg.cnf and local.cnf. Do not attempt to edit these files, as that won't work.
Use the configutil utility to see what the store configuratin is

Enabling to see the Source payload for synchronous Interface

Hi Experts,
Am working on a SOAP <-> RFC synchronous interface and PI version is 7.4 dual stack. Am unable to see the source payload when a
message is triggered from the Source Webservice. I can only see the receiver payload in RWB for request msg i.e the RFC payload.
Even for Response, I can only see the receiver payload which is sent to webservice and not the source payload from ECC on the RFC.
I have built the interface using ICO. I have made the changes in NWA, by setting the RemoveBody field to false.
Please let me know if any other settings are required. I have checked all other threads related to this issue and could not find the solution
to my issue where only the source payload in the synchronous interface is missing. In case of Asynchronous interface, the source payload
is visible.
Please assist me how can I enable this.
Regards,
Vish...

Hi Vishwanath,
Please check the below blog
Message Staging and Logging Options in Advanced Adapter Engine of PI 7.3x
regards,
Harish

Issue after Migration: ID and Content-ID are different in SOAP Payload

Hi Experts,
I am facing a strange issue in the PI landscape after the migration from XI 3.0 to PI 7.1.
The scenario is from R/3 system to TIBCO System (Proxy-to-SOAP). The TIBCO system receives the file in SOAP Format. The message is sent from PI via SOAP adapter to TIBCO System.
There is a attachment coming from the R/3 System along with the main message and the main payload/message has a "attachment-ID" as a field. Earlier what used to happen in XI 3.0 that the "Attachment-ID" used to equal to the "Content-ID" when the SOAP payload was generated at the TIBCO end. Now after migration, in PI 7.1 the "Attachment-ID" and "Content-ID" are different. We have control over the "Attachment-ID" as it is coming from the source payload but we do not have any control over the "Content-ID" as we are not creating it.
Can anyone of you please let me know how the SOAP Payload is created and how the content-ID gets populated in the Header of the SOAP Envelope? Also, can anyone help me to fix this issue? Is it something which needs to be handled by us or the BASIS Team?
Thanks,
Arkesh
Edited by: Arkesh Sharma on Dec 16, 2011 12:53 PM

Hi Ramesh,
Thank You for the very Helpful Answer. Before I proceed and close this thread, I have one more question which comes to my mind:
I create my own SOAP Header if I apply the solution provided by you then will the rest of the details in the SOAP Header payload will change or do I need to customize it for myself? For e.g., there is a field named MessageId in the SOAP Header. If I write a Java Mapping, do I need to manually populate the MessageId field in the SOAP Header of my java code or will it be automatically populated?
My requirement is to change only the content ID of the SOAP Header Payload and the rest of the fields should remain the same as it is. Is it possible with the approach that you mentioned above?
Thanks,
Arkesh

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.

How to XI error message will mapped to the SOAP faul message-SOAP(Axis)

Hi,
Receiver end I am using SOAP (Axis) adapter and I am getting the system error and I am not getting the payload in SXMB_MONI.
What ever the error message how do MAP as a SOAP Fault message in SXMB_MONI.
I found the Solution from OSS note 1039369 but did not explain where to set what parameter and what modules...
SOAP Fault code
If parameter Category is XIAdaptger, Area SOAP, Code FAULT
In this case, parameters P1 and P2 may be set to the fault namespace and fault name. If these parameters are set, the SOAP fault code is set to namespace P1 and name P2. Otherwise, it is set as in other cases.
For all other cases
In this case, the SOAP fault code is set to namespace "http://sap.com/xi/XI/Message/30" and name category.area.code, where category, area, code represent the XI error category, area, and code values, respectively.
SOAP detail
If parameter ApplicationFault is set
The SOAP detail child is set to the XI application payload. If, however, the payload extraction mode is set to Envelope, the application payload is taken as the SOAP envelope and the SOAP detail content is set to its body content. Similarly, if the extraction mode is set to Body, the application payload is taken as the SOAP body and the SOAP detail content is set to its content.
Otherwise
No SOAP detail content is set in this case.
Examples
XI error element
<sap:Error ...>
<sap:Category>XIAdapterFramework</sap:Category>
<sap:Code area="MESSAGE">GENERAL</sap:Code>
<sap:AdditionalText>Failed to determine a receiver agreement for the given message.</sap:AdditionalText>
</sap:Error>
SOAP fault element
<soapenv:Fault>
<faultcode xmlns:ns1="http://sap.com/xi/XI/Message/30">ns1:XIAdapterFramework.MESSAGE.GENERAL</faultcode>
<faultstring>Failed to determine a receiver agreement for the given message.</faultstring>
<detail/>
</soapenv:Fault>
Help appriciated
Regards,
Venu.
Edited by: Venugopalarao Immadisetty on Sep 24, 2009 3:39 PM

Using Receiver SOAP Axis adapter and I am getting the below exception
XI error element
<sap:Error ...>
<sap:Category>XIAdapterFramework</sap:Category>
<sap:Code area="MESSAGE">GENERAL</sap:Code>
<sap:AdditionalText>Failed to determine a receiver agreement for the given message.</sap:AdditionalText>
</sap:Error>
and above exception how do I convert as a SOAP Fault message..
SOAP fault element
<soapenv:Fault>
<faultcode xmlns:ns1="http://sap.com/xi/XI/Message/30">ns1:XIAdapterFramework.MESSAGE.GENERAL</faultcode>
<faultstring>Failed to determine a receiver agreement for the given message.</faultstring>
<detail/>
</soapenv:Fault>
Any idea what modules need to add in Receiver SOAP Axis adapter.

Proxy to SOAP Scenario, payload with the SOAP envelops

Hi ,
We have Scenario like Proxy to SOAP,As per Business requirement they are asking payload with ENVELOP . Like below message
================================================================
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding">
     <SOAP-ENV:Header>
          <nseps:endpoints xmlns:nseps="urn:schemas-IBX:/docs/endpoint.nsendpoint" SOAP-ENV:mustUnderstand="true">
               <nseps:to>
                    <nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
               </nseps:to>
               <nseps:from>
                    <nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
               </nseps:from>
          </nseps:endpoints>
          <nsprop:properties xmlns:nsprop="urn:schemas-IBX:/docs/property.nsproperty" SOAP-ENV:mustUnderstand="true">
               <nsprop:identity>3198841w-fa4d-dafa-2797-89029c15255b</nsprop:identity>
               <nsprop:sentAt>2010-01-18T02:42:08Z</nsprop:sentAt>
               <nsprop:topic>CostObjectInformation</nsprop:topic>
          </nsprop:properties>
     </SOAP-ENV:Header>
     <SOAP-ENV:Body>
//Payload of the message to be added here.
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I am trying out this in XSLT, but I am not sure how to add the SOAP Envelops and these Envelops are Static.
Can someone help me out in this.
Joe

But if you look at the SOAP Envelop Structure below it is not XI generated SOAP Envelop. IBX (3rd party) has its own standards, so XI has to Produce the SOAP Envelop according to their standards.
I have created the XSD with SOAP Envelop stucture with what ever structure 3rd party wants, but the problem is when Creating the SOPA Envelp tag, where it has a ":" where its not allowing me to create the valid XSD. And at the same time 3rd party is not in position to give us even WSDL file and we are not using Webservice call and they are not able to provide the XSD with SOAP envelop structure.
I thought of going for XSLT and started doing as well with what ever XSD 3rd party has provided, which does not have the SOAP Envelop structure and has only payload XSD structure.
80% of the SOAP Envelop structure is Static, it does not change. Only 2 fields keeps changing. IS there any solution that we can create XSD with the SOAP structure with Special Character ": "or is there any way in doing in XSLT.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding">
<SOAP-ENV:Header>
<nseps:endpoints xmlns:nseps="urn:schemas-IBX:/docs/endpoint.nsendpoint" SOAP-ENV:mustUnderstand="true">
<nseps:to>
<nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
</nseps:to>
<nseps:from>
<nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
</nseps:from>
</nseps:endpoints>
<nsprop:properties xmlns:nsprop="urn:schemas-IBX:/docs/property.nsproperty" SOAP-ENV:mustUnderstand="true">
<nsprop:identity>3198841w-fa4d-dafa-2797-89029c15255b</nsprop:identity>
<nsprop:sentAt>2010-01-18T02:42:08Z</nsprop:sentAt>
<nsprop:topic>CostObjectInformation</nsprop:topic>
</nsprop:properties>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
its a high priority issue.
Thanks in Advance.
Joe.

How to send the SOAP Fault Message to the Web Service Consumer

Hi,
I have configured SAOP to Proxy Syncronous Scenario in PI 7.1 and using XML Validation in Adapter Engine to Validate the Structure of the Message Payload.The scenario is working fine.When some of the Filed's Length increses the maxLength specified in the Data Type . We are getting the Following error.
<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>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: XML Validation for payload with root element name MT_Out_CustomerMaster_FPMReq , target namespace http://Pegasystems.com/I06_Customers Failed!Errors Encountered During Parsing
1.cvc-maxLength-valid: Value '123456789' with length = '9' is not facet-valid with respect to maxLength '8' for type 'null'.
2.cvc-type.3.1.3: The value '123456789' of element 'CompanyCode' is not valid.
3.cvc-maxLength-valid: Value 'asdf' with length = '4' is not facet-valid with respect to maxLength '1' for type 'null'.
4.cvc-type.3.1.3: The value 'asdf' of element 'OperationType' is not valid.
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1164)
My question is How does the Web Service Consumer can handle this Soap Server Error in the SOAP Fault.Or How can we provide a specific information like 'The value '123456789' of element 'CompanyCode' is not valid.It exceeds the Maximum Length'.
I read this /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client blog .Where it is mentioned that the Web Service Consumer can handle while calling the Web Service.Is there any other solution?
Kindly appreciate your help.

Thank You Stefan for your kind reply.
So you mean to say if we use the XML Validation .we cannot provide proper error information to the calling Web Service Consumer .And While calling a Web Service they cannot Extract the Exact Message in the Text Filed(<text>) present under the Detail Element (<detail>) in the <SOAP:Fault> node. as
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: XML Validation for payload with root element name MT_Out_CustomerMaster_FPMReq , target namespace http://Pegasystems.com/I06_Customers Failed!Errors Encountered During Parsing
1.cvc-maxLength-valid: Value '123456789' with length = '9' is not facet-valid with respect to maxLength '8' for type 'null'.
2.cvc-type.3.1.3: The value '123456789' of element 'CompanyCode' is not valid.**
3.cvc-maxLength-valid: Value 'asdf' with length = '4' is not facet-valid with respect to maxLength '1' for type 'null'.
4.cvc-type.3.1.3: The value 'asdf' of element 'OperationType' is not valid.
That is why we have to use the Fault messages and Field Lengths has to be Validated in the Server proxy.
Please Correct me If I am wrong.

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.
<b>
Rewards points if you find it usefull.</b>

SOAP receiver adapter - payload inside the soap envelop

Hi,
We have to send a SOAP message to 3rd party from PI 7.1. Using SOAP receiver adapter - we are trying to achieve this. 3rd party software is unable to accept payload as an attachment of the main envelop - they want it enside the main envelop.
I tried with "Keep attachment" option - but PI still keping the payload as an attachment. I think this option is for handling "extra" attachment.
Is there any way we can keep the payload inside the envelop?
In run-time WB, at the moment envelop looks like
<SOAP:Envelope xmlns:SOAP="http://schemas....
<SOAP:Body>
<sap:Payload xlink:type="simple" xlink:href="cid:payload-d6518670ca1311debbd9ca347000800b...">
</SOAP:Body>
</SOAP:Envelope>
And the payload d6518670ca1311debbd9ca347000800b... ( again viewed from RWB) - contains the data.
<?xml version="1.0" encoding="UTF-8" ?>
<ns2:Order> ....
</ns2:Order>
Can we insert this payload directly inside the SOAP:Envelope body instead of a link there?
Regards,
Sudhin

Hi!
It seems to me that this 3rd party is expecting only XML not SOAP.
If this is the case, you should use the HTTP Receiver adapter instead of SOAP.
Some systems 'say' they can speak SOAP but they can only speak XML. Not to blame, it's a mistake many make these days.
The only way you use SOAP Receiver adapter with this 3rd party, is that if someone from the 3rd party hands you a WSDL file.
Ricardo Sancio Lóra
Brazil

How to send back the soap fault message without details tag to the sender

Hello Expert,
Is it possible to send the soap fault message(fault String element value) without details tag as shown below to the sender in synchrounous scenario.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soapenv:Body>
          <soapenv:Fault>
               <faultcode>soapenv:Client</faultcode>
               <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.arrayOtrosTributos.otroTributo(1).codigo - El Código de Tributo es obligatorio.</faultstring>
               <detail></detail>
          </soapenv:Fault>
     </soapenv:Body>
</soapenv:Envelope>
I have to send the faultstring element value in one of the element in response message back to sender? Is it possible using BPM?The above fault response does not have a fault payload (no detail element) and would result in a system error message.So how to handle this?
If yes .Please tell me the BPM design
faultstring value will be dynamic.
Thanks in advance

Thanks Yzanagi,
I have gone through the index.htm file.
In my scenario that is RFC -PI-soap(using http(Axis) protocol).when the webservice provider is sending the soap fault as.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soapenv:Body>
          <soapenv:Fault>
               <faultcode>soapenv:Client</faultcode>
               <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1</faultstring>
               <detail></detail>
          </soapenv:Fault>
     </soapenv:Body>
</soapenv:Envelope>
In PI sxmb_moni it is converting to the error (system not application error)as shown below when using receiver soap adapter with https(Axis) transport protocol and Message protocol:Axis.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1></SAP:P1>
<SAP:P2></SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1.</SAP:AdditionalText>
<SAP:Stack></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
As my requirement was (I have mentioned in my first question) that I want to pass
SAP:AdditionalText tag
value back to sender in one of the elements of response message payload or handle using fault message mapping if this error could be converted to application error and map to the RFC exception but unfortunately which is not possible even using AXIS adapter.
so other option to inform the sender RFC is mentioned here http://help.sap.com/saphelp_nw70/helpdata/en/22/0425e0488911d189490000e829fbbd/content.htm
but while handling the SYSTEM_FAILURE exception from PI at sender in report program and displaying the msg variable ,I am not getting complete error message..It is getting truncated.Is there a limit to the no of character the msg variable contains which is set by system.Even if we declare msg variable with more length(for example char length 500) it is just displaying part of the error message from PI.
Any Idea to read complete system error message from PI in report program at RFC sender..
Kind Regards,
Kubra fatima

How to view the payload of a Message if it processed through AAE

Hi All,
Can anybody please tell me how to view the payload if the message processed through Advance Adapter Engine.
I have developed a SOAP to SOAP interface by using Advance Adapter Engine and it is working fine I can see the messages in Runtime Work Bench(RWB) but when I clicked on the Sender and Receiver Adapter I can't see the payload so I am wondering if anyone knows how to view the payload or it is possible to view the payload if the message was processed through Advance Adapter Engine (AAE).
Is there any setting or properties available in NWA to enable or disable the payload of AAE?
Thanks,
Iqbal

Hi All,
Unfortunately I can only see the SOAP Document but no Payload.
here is what I can see
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
- <sap:Main xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" soap:mustUnderstand="1">
<sap:MessageClass>ApplicationResponse</sap:MessageClass>
<sap:ProcessingMode>synchronous</sap:ProcessingMode>
<sap:MessageId>75e50f37-9bef-11e0-af98-000027d151a6</sap:MessageId>
<sap:RefToMessageId>7597008d-9bef-11e0-a027-000027d151a6</sap:RefToMessageId>
<sap:TimeSent>2011-06-21T10:15:59Z</sap:TimeSent>
- <sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<sap:Service>Srv_xxxxx__Sender_SOAP_AAE_BS</sap:Service>
</sap:Sender>
- <sap:Receiver>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<sap:Service>Srv_xxxxx_Sender_SOAP_AAE_BS</sap:Service>
</sap:Receiver>
<sap:Interface namespace="urn:xxxxxxxx.com:pi:A_TEST:HTTP_TO_SOAP_AAE">SI_OS_xxxx_Request_AAE</sap:Interface>
</sap:Main>
- <sap:ReliableMessaging xmlns:sap="http://sap.com/xi/XI/Message/30" soap:mustUnderstand="1">
<sap:QualityOfService>BestEffort</sap:QualityOfService>
</sap:ReliableMessaging>
<sap:System xmlns:sap="http://sap.com/xi/XI/Message/30" soap:mustUnderstand="1" />
- <sap:HopList xmlns:sap="http://sap.com/xi/XI/Message/30" soap:mustUnderstand="1">
- <sap:Hop timeStamp="2011-06-21T10:15:59Z" wasRead="false">
<sap:Engine type="AE">af.dgx.dbdgx66</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>75e50f37-9bef-11e0-af98-000027d151a6</sap:MessageId>
</sap:Hop>
</sap:HopList>
</SOAP:Header>
- <SOAP:Body xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink">
- <sap:Payload xlink:type="simple" xlink:href="cid:payload-75e51c499bef11e0a13a000027d151a6atsap.com">
<sap:Name>maindocument</sap:Name>
<sap:Description>main document</sap:Description>
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Do I need to do anything in NWA to enable the payload for Sender and Receiver?
Thanks,
Iqbal

Where is the SOAP Payloads of XI Message in host?

Similar Messages

Maybe you are looking for