Asynchronous SOAP adapter

Hi,
Please let me know under what circumstances would one want to use the SOAP Adapter with asyncrnous interfaces.
Edited by: Jyotika Manghani on Dec 28, 2007 8:48 AM

Hi,
You need to configure the SOAP adapter so that you can exchange SOAP messages between the Integration Engine and remote clients or servers of Web services.
The SOAP adapter provides a runtime environment that includes various SOAP components for the processing of SOAP messages. You can combine these SOAP components with separate components to meet your needs and requirements.
The SOAP adapter uses a helper class to instantiate and control SOAP components. If you want to use your own SOAP processing logic you must make your helper class known to the SOAP adapter.
To configure the SOAP adapter you must specify the following:
● The helper class that implements the following interface:
com.sap.aii.messaging.adapter.ModuleBubbleHelper
● The parameter values for the specified helper class
For example, you must specify the following parameters for the helper class ModuleBubbleHelperXMBWSImpl (instantiates a BubbleBag to integrate remote Web services with the Integration Engine):
○ Information about the Integration Engine destination (when the Integration Engine is acting as a service provider and therefore the SOAP adapter must be configured as a sender adapter).
○ Information about the Web service provider destination (when the Integration Engine is acting as a service client and therefore the SOAP adapter must be configured as a receiver adapter).
○ Various options for controlling the conversion of multi-part Integration Engine SOAP messages and Web service SOAP messages
The following arguments are mandatory:
○ XI.QualityOfService=<QualityOfService>
Specifies how the Integration Engine should process a message. The following values are permitted:
■ XI.QualityOfService=BE (Best Effort, means synchronous processing)
■ XI.QualityOfService=EO (Exactly Once, means asynchronous processing)
■ XI.QualityOfService=EOIO (Exactly Once in Order, means asynchronous processing using queues)
You must also define a queue name for EOIO:
Refer http://help.sap.com/saphelp_nw04/helpdata/en/bf/27fd3b651f6a1ce10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2f/41e641fb6e3f5de10000000a1550b0/content.htm
Hope this will help you in some extend.
Regards
Aashish Sinha
PS : reward points if helpful
Edited by: Aashish Sinha on Dec 28, 2007 9:01 AM

Similar Messages

SOAP Adapter missing payload on receiving web service

Hi there,
I'm having a problem with a File to (asynchronous) SOAP Adapter scenario that is currently baffling me.
I wonder if anyone out there has any troubleshooting ideas for this one?
The source message is being picked up OK and I can see from Communication Channel Monitoring on the Runtime Workbench that it is allegedly being delivered to the Web Service OK.
All the entries in the audit log point to a successful scenario and I can view the payload in the Message Content "payload" area.
However on the web service / server side the message is completely blank. Somewhere along the line the payload has gone missing.
I can copy and paste the payload manually into the web service test area and this is fine.
Any ideas/suggestions as to what could be happening with this or how I might go about troubleshooting it?
Many thanks
Ian

Thanks Bruno,
It looks like you were right...
In the end we used Wireshark - a packet sniffing application - to check what was actually hitting the destination server. We found that the content was arriving at the server but the web service wasn't accepting the format. The creators of the web service are now investigating why and will hopefully will advide me of the format error in the message. But at least I was able to prove that the message was getting there which was the focus of this query.
Regards
Ian

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.

Error in using XI-SOAP adapter, but no error with SAP-BC

Hi,
I am working on RFC->XI->Webmethod (.asp) scenatio.
I am using SOAP adapter.
Whin I am not using "Do not use SOAP Envelop".
I am getting "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML" Error in SXMB_MONI.
But when I am using "Do not use SOAP Envelop" then I am not getting any error. in SXMB_MONI status showing Successfully Processed. But the responce i am getting is "You are not authorized to view this page // HTTP 401.1 - Unauthorized: Logon Failed"
But same web-service is working fine while connected with SAP-BC.
Please Help why scenario is working with BC, but not with XI.
Thanks & Regards

Hi Bhavesh,
Thanks for reply.
I am getting all success in message monitoring, but still web-services sying they are not getting any message.
I am attaching all 4 logs for one synchronous communication of message monitoring.
I am not able to understand where message going and why XI showing success every where.
********1st(Sent Messages)
Success SOAP: response message leaving the adapter
Success Application attempting to send an XI message asynchronously using connection AFW.
Success Trying to put the message into the send queue.
Success The response message for message cf4fd921-4a74-11db-9312-001279933263(INBOUND) was successfully transmitted to the calling application.
Success The message status set to DLVD.
Success The application sent the message asynchronously using connection AFW. Returning to application.
********2nd (Sent Messages)
Success RFC adapter received sRFC for Z_PA_SAP_TO_Webservice from D02/230. Attempting to send message synchronously
Success Application attempting to send an XI message synchronously using connection AFW.
Success Trying to put the message into the call queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the call queue.
Success The message status set to DLNG.
Success The message was successfully transmitted to endpoint http://XYZ.com:8000/sap/xi/engine?type=entry using connection AFW.
Success The application sent the message synchronously using connection AFW. Returning to application.
Success The message status set to DLVD
**********3rd (Received Messages)
Success Using connection AFW. Trying to put the message into the receive queue.
Success The XI response message for message d0372be1-4a74-11db-91d7-001279933263(INBOUND) was successfully returned to the calling application.
Success The message status set to DLVD.
**********4th (Received Messages)
Success The message was successfully received by the messaging system. Profile: XI URL: http://XYZ.com:50000/MessagingSystem/receive/AFW/XI
Success Using connection AFW. Trying to put the message into the request queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the request queue.
Success The message status set to DLNG.
Success Delivering to channel: IF_O_502_WebserviceBusService_SOAP_In_02
Success SOAP: request message entering the adapter
Success SOAP: completed the processing
Success SOAP: response message received d0372be1-4a74-11db-91d7-001279933263
Success The message status set to DLVD.
Success The message was successfully delivered to the application using connection AFW.

Soap Adapter

Hello.
I am trying to send an asynchronous message from R/3 to a web service using a soap adapter. I am using XI 2.0, with the ModuleBubbleHelperXMBWSImpl. These are the parameters I have entered:
Bubble adapter java class
classname=com.sap.aii.messaging.adapter.ModuleBubble
This adapter instantiates a bubble bag for supporting
a xmb web service gateway. A bubble bag is a collection of Bubble
instances that form some processing chain of message objects.
Below parameter Bubble.Helper specifies the helper class that implements
the ModuleBubbleHelper interface. This class is used to instantiate
a bubble bag for this adapter.
Sets the bubble module helper that can instantiate your bubble bag
Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Below this line are the parameters specific to the ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
The configuration of this helper class is divided in two parts. The first part
specifies the adapter configuration for Web-Service clients communicating with an
XMB server. The second part specifies the configuration for XMB clients
communicating with a WebService server. Either one or both parts can be configured
in a single configuration file. Or you may separate the configuration in two files:
one for Web-Service clients communicating with an XMB server (by using only
part 0 and part 1), and the other for XMB clients communicating with a Web-Service
server (by using only part 0 and part 2).
Part 0 (FromWS and ToWS) : common part ######
Keeps the XMB headers in web service messages. Unless you need XMB header
information in your web service client/server, you should set this value to false.
XMBWS.KeepHeaders=false
Keeps the attachments in web service messages.
XMBWS.KeepAttachments=false
Encodes the xmb headers into the special HTTP header string named x-xmb_ws_encoded.
Unless you need XMB header information in your web service client/server, you
should set this value to false.
XMBWS.UseEncoded=true
Encodes the value of x-xmb_ws_encoded (see UseEncoded) in the request query string
Note: To include the encoded xmb headers in the query string, both UseEncoded and
UseQueryString must be set true. When this option is set true, make sure that
the request URL is in an appropriate form so that the attached string does not
violate the syntax for URL.
XMBWS.UseQueryString=true
Uses the specified xml encoding for serializing the soap envelope. If unspecified,
the default encoding utf-8 is assumed.
XMBWS.XMLEncoding=iso-8859-1
Part 2 (ToWS): XMB clients to WS server ######
The target URL for the web service, to which the adapter sends web service messages.
XMBWS.TargetURL=http://wpg-apps-30/engsys/distapps/RMSDev/RMSPublic.asmx?wsdl
Uses a proxy server for calling XMBWS.TargetURL
#XMBWS.ProxyHost=proxy
#XMBWS.ProxyPort=8080
Uses user-authentication for calling XMBWS.TargetURL
#XMBWS.User=anonymous
#XMBWS.Password=anonymous
The port and path where the adapter waits for XMB messages from clients.
XMBWS.XMBPort=8210
XMBWS.XMBPath=/file/receiver
The default SOAPAction HTTP request header to the web Service server
XMBWS.DefaultSOAPAction="xmbws"
END
I keep getting this message:
09:46:25 (3835): Request transport message received at 8210/file/receiver
09:46:25 (3836): Request message parsed
09:46:25 (3840): Error occurred during processing: com.sap.aii.messaging.srt.BubbleException: com.sap.aii.messaging.mo.MalformedMessageException: Fatal Error: com.inqmy.lib.xml.parser.ParserException: Bad PUBLIC declaration (:main:, row:1, col:55);
I think my problem is that the XML is being created without an envelope, but I don't know how to fix this.
Can anyone help, please?
Thanks.
Nicole

The URL and the SOAP action are part of the WSDL definition.
Look at this example:
 <operation name="doGoogleSearch">
 <soap:operation soapAction="urn:GoogleSearchAction" />
 <input>
 <soap:body use="encoded" namespace="urn:GoogleSearch" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
 </input>
 <output>
 <soap:body use="encoded" namespace="urn:GoogleSearch" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
 </output>
 </operation>
 </binding>
 <service name="GoogleSearchService">
 <port name="GoogleSearchPort" binding="typens:GoogleSearchBinding">
 <soap:address location="http://api.google.com/search/beta2" />
 </port>
 </service>
</definitions>
As soap action take the value of attribut soapAction of the node soap:operation
As URL take the value of the attribut location of the tag soap:address.
Regards
Stefan

Error in Adapter engine of receiver soap adapter

Hi All,
There is one production issue i am currently facing in receiver SOAP adapter while interacting with third party web service(Asynchronous call).
Below is the description i am getting in audit logs.
Success SOAP: completed the processing
Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired.
Error The message status set to NDLV.
Moreover this is a production issue and interface was running fine till last friday.
Has someone ever faced this issue ?
Please provide your valuable inputs on this.
Thanks
Anku

Hi,
Search in sdn with your error message string,you will find ton of links.
HTTP401 error occurs for many reasons.
still no solution let us know..
Regards,
Raj

For SOAP Adapter

HI Friends,
i getting gold value from file i need to update the value in webservice for every second in website.So
how to update the value dynamicallly in websystem using soap adapter receiver is file adapter is there any options in soap adapter

You can do file --> PI --> SOAP (Receiver) asynchronous to achieve this.
Elaborate more about dynamically every second...

Receiver SOAP adapter -Async

Hi All,
My scnario is SAP -PI--webService (SOAP adapter) Asynchronous.
In case of any error while processing the data into webservice, I think webservice will pass back a relevant message to thePI through SOAP. I am able to see only the error descrtion in the CC monitoring.
How does PI interpret the XML which SOAP passes back in the event of an error during processing?Where we can find the XML message of the error?
What is the functionality is in place in SAP-PI to get the returned information from the webservice in the event of an issue?
Thanks in Advance
Kartikeya

Karthik,
Asynchronous / synchronous is decided by the sender system /adapter
> I think webservice will pass back a relevant message to thePI through SOAP
If it is Async the SOAP adapter will not get the response back from the webservice
Cheers
Agasthuri Doss

Acknowledgement for asynch scenario using SOAP adapter

Hi,
My scenario is SOAP to proxy asynchronous (using PI 7.1)
Sender is able to send the messages to XI using HTTPs protocol (SOAP adapter). since this is an asynchronous scenario XI could not send back any application acknowledge .
I understand if handshake is successful sender can see HTTP code 200 which is success.
1) Is it possible that though HTTP connection is successful and sender could not pass payload.
2) Is there any configuration needs to be done in PI 7.1 to send an acknowledge back to assure the sender that XI received payload.
3) Can we do the above using non BPM scenario.
or if BPM scenario is mandatory.
Thanks in advance.

Hi Vamsi,
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header/>
<SOAP:Body/>
</SOAP:Envelope>
above acknowledgement is seen on SOAP UI as soon as SOAP UI delivers the message to the PI (irrespective of what will happen with the message in the PI).
As you know in case of Async scenario Application Ack is not possible !
But if you want to be sure if payload is received successfully the you can use BPM wherein you can have a switch which will check the existance of payload. and as per your requirment you can take a decision.
Thanks,
Sunil Singh

Sender Axis SOAP Adapter EOIO

My PI Sender Axis SOAP Adapter is giving me the following error when I try and use an EOIO quality of service:
The XI SequenceId must be uppercase and 1-16 characters long.; nested exception is:
com.sap.engine.interfaces.messaging.api.exception.InvalidParamException: The XI SequenceId must be uppercase and 1-16 characters long.
If I use EO then the adapter works fine. Does anyone know if EOIO is supported in the Sender Axis SOAP Adapter? I did notice when I select EOIO there is no text box for the Queue Name.

Hi Krishneel,
ExactlyOnceInOrder means that the constructed XI message has its QualityOfService value ExactlyOnceInOrder and it is processed synchronously to the persistence layer of the adapter engine and asynchronously to the target service in the order of persistence.
To guarantee the exactly once delivery of a message, the client must supply a unique message ID for the message.
More on this can be found in the SAP Note 1039369 (FAQ XI Axis Adapter)
Also refer this link on basic info on Sender Axis SOAP Adapter.
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
rgds
Ven

XI acknowledgment from axis soap adapter

We have implemented an integration from SAP ERP to an external system via XI. SAP sends a message to XI via proxy which is then mapped to a web service call to the external system via the axis soap adapter. If there is a problem the axis adapater sends back an acknowlodgement message with the soap error. This message is correctly interpreted by XI as en error acknowledgement. The acknowledgement message however fails in the routing as it is not able to find a receiver agreement for routing the message back. There is of course actually no valid recepient for this acknowledgement as the original message was created using an asynchronous proxy call. The problem is however that the original message is flagged as successful even though the acknowledgement contains an error. What we want to achieve is that the error in the acknowledgment causes the original message in XI to be flagged as failed, to allow error detection. Does anyone have any idea how to achive this ?
Rgds
Evind Langsaeter

Hi
We do not require any acknowledgements. But for the cases where the soap call is delivered, but returns a http response of 500 together with a complete soap envelope containing a soap fault, the Soap Axis Receiver Adapter is issuing an u201CApplicationErroru201D Acknowledgement Message (referring to the original request message) (even though it is not requested). This Acknowledgement Message is failing on the Integration Server with a configException u201CFailed to determine a receiver agreement for the given messageu201D. We have tried to create a receiver agreement and reciever channel with the given keys from the error message, but still getting the same result.
Issue A: How to get this (non-requested) Acknowledge message to process without error.
Issue B: How to get a proper u201Cerror-messageu201D telling that the original request message was not really delivered though (as the soap call gets a http response of 500).
Rgds
Eivind

SOAP Adapter: Connection time out error

Hi Guys,
I do it one scenario for Proxy to webservice Asynchronous . I have send the input details through Proxy. In Sxmb_Moni shows success message. But Receiver side doesn't reach the payload. Because receiver side (Soap Adapter) shows connection time out error. But i have given correct URL and SOAP Action in receiver communication channel. Please give some suggestions to solve that issues. Please don't refer links.
Thanks & Regards
Vijay

hi
this is a time out error
increase the timeout value by specifying the parameter
XI.Timeout in the module parameter of soap Adapter
OR
1. This is because of TimeOut. The default timeout value for synchronous calls is 5
minutes. You can increase this value by setting parameter XI.Timeout in the module parameter table of
the SOAP adapter. The value must be given in milliseconds. For example, value 600000
represents the timeout value of 10 minutes. This parameter is not recognized in systems prior to SP13.
2.The Other Options is send the queue id with your request message.
http://host:port/XISOAPAdapter/MessageServlet?channel=p:s:c
&version=3.0&...&QueueId=xxxxxxxxxxxxxxxx
where xxxxxxxxxxxxxxxx is an ABAP queue ID.
3.Check your RWB message monitoring.
Is there any system failure message and holding message be there.
If then clear the messages.
4. Increase the time out parameter for HTTP in your altova xml spy.Defaultly it will be very low.

Lookup API - asynchonous SOAP Adapter Queue

Hi,
I have a question about the queue handling, when you use the Lookup API of the SAP PI. ([Sap Help Lookup API|http://help.sap.com/saphelp_nw04/helpdata/en/cf/406642ea59c753e10000000a1550b0/frameset.htm])
When I call a synchronous Web Service via SOAP within a message mapping via the Lookup API, the synchronous web service is called via the "SOAP_http://sap.com/xi/XI/SystemSend" adapter queue. But "SOAP_http://sap.com/xi/XI/SystemSend" is the asynchronous SOAP sender adapter queue. The threads which handle the calls are not made for handling synchronous calls. If the synchonous web service has a high response time (10 seconds for example). The thread is blocked for this time.
Synchronous threads are not blocked that long.
Is there a way to configure which adapter queue has to be used by the lookup API?
Regards,
Torsten

Hello,
Regarding the error in the trace:
nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5070] Already started operation with application sap.com/com.sap.aii.adapter.soap.app in the cluster. No other operation with this application is allowed at the moment, because it is locked in the enqueue server or the lock from there has been manually removed. at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:236) at
please see note
1339258 PI Adapter applications locked during start up
You could try restarting the SOAP Adapter applications :
com.sap.aii.adapter.soap.app
com.sap.aii.adapter.soap.lib
from the JEE NWA
-> Operation Management
-> Systems
-> Start and Stop
-> Java EE Applications
http://wiki.sdn.sap.com/wiki/display/XI/start_stop_applications
Regards,
Sarah

SOAP Adapter - HTTP 401

Hi all,
i'm pretty new to SAP-PI and need some help.
We have following asynchronous scenario : XI-Adapter >>> XI >>> SOAP-Adapter to transfer data from ERP to a 3rd Party-System.
After some changes by the Web-Service-Provider ( certificate & user creditentials) we get a HTTP 401 - Unauthorized Error.
What we did:
imported the new certificate
set the new creditentials in the communication channel for authentification

Hi,
many thank for your quick responses!
Yesterday evening i decided to do a full cache refresh. Now i am receiving following error:
Error in call over HTTP: HTTP 0 null
[EXCEPTION]
java.io.Exception: Failed to get the input stream from socket: iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier...
After that i tried to set the parameter
     Module key: soap
     paramname: trustStore
     paramvalue: TrustedCAs
for the the module XISOAPAdapterBean in the CC, but i'm still receiving the same error.
So i think something is wrong with the new certificate. Our Basis-Team is checking this atm.
Regards
Kai

Configure Soap Adapter for compress, gzip.

HI to all experts,
do anyone know how can configure a soap adapter with the parameter for compress, gzip.
i found a document which explain so:
localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
XMBWS.XMLEncoding Content-Type charset iso-8859-1
XMBWS.TransferEncoding Content-Transfer-Encoding base64
XMBWS.Encoding Content-Encoding gzip
XMBWS.AcceptEncoding Accept-Encoding compress, gzip
but i f i insert this parameter the adapter give me back a response :
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Could not access envelope: Unable to create envelope from given source: ; nested exception is com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Unable to create envelope from given source:.
seems that it have any difficult to read the payload.
let me know if anyone have an idea.
best Regards
Claudio.

Hi Stefan,
is it enough this response?
POST HTTP/1.0
Accept: /
Accept-Encoding: compress, gzip
Host: 10.180.160.29:8080
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Content-ID: <[email protected]>
Content-Disposition: attachment;filename="[email protected]"
Content-Type: text/xml; charset=iso-8859-1
Content-Description: SOAP
Content-Transfer-Encoding: base64
Content-Encoding: gzip
Content-Length: 1292
SOAPACTION:
X-XMB_WS_ENCODED: version=3.0&MessageClass=ApplicationMessage&ProcessingMode=asynchronous&MessageId=478ce922-7b48-04b0-0200-00000ab44471&TimeSent=2008-01-16T13%3A36%3A45Z&Sender.Party=%3A%3A&Sender.Service=BS_SAP_TC3_700&Receiver.Party=%3A%3A&Receiver.Service=BS_IRIS_TXI&Interface=http%3A%2F%2Fgenerali.it%2Fmerge%2FUTILITY%2F01%2Firis%5EMI_COMPAGNIE_RES&QualityOfService=ExactlyOnce
i get it by TCPGatway.
thanks a lot.
Claudio.

Asynchronous SOAP adapter

Similar Messages

Maybe you are looking for