Soap adapter for asynch ?

Hi Guys,
I need to configure receiver soap receiver for asynchronus process. where i need to mention in the soap adapter the qos is exactly once.
Thanks,
srini

Hi Sudheer,
I am getting the following error in the sxmb_moni on the R/3 side.
race level="1" type="T">Get definition of external pipeline = SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="1" type="T">Queue name : XBTS0007</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTS0007</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ClearingHousePaymentOrderRequest_Out*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/APPL/SE/Global</Trace>
<Trace level="1" type="T">no interface found</Trace>
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
any help would be really appreciated
Thanks,
srini

Similar Messages

Error in Receiver Soap Adapter for Google API

Hi,
I am working on HTTP-XI-Soap scenario which on the receiver side calls google API for spell check.
I get the following error : No Deserializer found to deserialize a ':key' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
However if I try calling the webservice individually using SOAP Client it works fine and do get desired response.The soap message that is sent by the client to the target URL is :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:GoogleSearch" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
 <urn:doSpellingSuggestion soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
 <key xsi:type="xsd:string">qXWD4x1QFHIo/dePqlYOLwT7kMmkv80E</key>
 <phrase xsi:type="xsd:string">Bratney</phrase>
 </urn:doSpellingSuggestion>
 </soapenv:Body>
</soapenv:Envelope>
However if i remove the "xsi:type="xsd:string" part from the element 'phrase' and 'key' it returns the same error as it does while using with XI.
Hence I am assuming that that the outgoing soap message elements need to have the above highlighed attribute.
Now I want to have this attribute(xsi:type="xsd:string) in the soap message that is sent from XI.
My question is , Is there any setting using which I can add the attributes in the above form to the outgoing message from XI.I do not want to use a adapter Module.
Thanks & Regards,
Sidharth

Hi Sidharth,
You post here the soap message that is sent by the client to the target URL, but did you look to the soap message that is sent by XI?
Try the AF monitor http://<host>:<j2ee-port>//MessagingSystem/monitor/monitor.jsp?
Because XI soap adapter doesn't support all tags of wsdl rpc-based, we need to adjust them...
Look to the SOAP FAQ (SAP note number 856597) under question "Can I convert an RPC styled WSDL to a document styled WSDL?"... Look at last but one paragraph ;o)
So, you need to change this attribute to one that it is compatible...
Go to http://service.sap.com/xi > Media Library > Documentation and there you will find this xls document -> SAP XI 3.0 (SP11) - Supported XML Schema and WSDL (EN) in this document you have all the compatible elements of wsdl for XI.
One more thing, you can adjust your soap request and change or add the required tags You can do it with xslt-mapping or create your won data types in XI without import the WSDL generated by google.
Hope it helps,
Ricardo.
Message was edited by: Ricardo Quintino

Issue with Receiver SOAP adapter for synchronous scenario

Hello All,
We are facing a strange issue with the SOAP adapter in the interface we have setup. This is the 1st time we are using SOAP adapter in our system (PI 7.11 SP7). We are making a synchronous HTTP call to the web service exposed by another system in our landscape. The payload is send with SOAP envelope and there are no credentials to be maintained in PI settings.
The issue is that we are always getting timeout exception in PI audit logs after sending the request (3 minutes - standard timeout value, no additional config for this). But target system has confirmed that they are sending the response back. We tested from our server OS level and have received the response back in the same screen (to verify there is no firewall/port issue in between the systems). But when tried from RWB, it is always giving the timeout exception and we are not able to see any other log.
We have tried checking in the NWA logs as well after increasing the logging level to ALL for com.sap.aii.adapter.soap. But surprisingly, we didn't get any logs at all for the outgoing SOAP call or incoming response and hence we are unable to trace the issue.
We have setup another synchronous inbound SOAP interface (PI exposing the webservice) and it is working fine. We are also able to trace the logs in both audit log and NWA logs.
Is there anywhere else we can check for the logs? Audit logs is showing timeout error and we are not able to see anything in NWA logs.
Does the target system need to maintain PI credentials in the header when they send the synchronous response back?
Are there any specific settings which should be checked to enable the sync communication? (this should not be the case since the inbound interface is working fine)
Please help.
Thanks
Justin

Hi Amit,
Thanks for the reply.
Yes we had tested successfully via SOAP UI as well (forgot to mention that). We are getting back the expected response in SOAP UI without using any credentials. We got the same response when we tested it through OS commands from PI server.
The WS is hosted by the target system and they haven't maintained any credentials at their end. So when PI is trying to access, we don't need to provide any credentials. My question is, whether the target system should keep any credentials to send the synchronous response back to PI (java stack). We have tried that as well but since there aren't any logs, we are unable to verify whether the credentials are coming correctly.
The service interfaces are correct and PI configuration are OK. I will try the XPI inspector for logs as you have suggested.
Thanks
Justin

Prefer HTTP or SOAP Adapter for file upload

Hi,
I have the following scenario:
Data (about 50 MB) is sent to PI and should get uploaded as file to a third party system.
I don't want to the use the File Adapter as I would have to use the FTP protocol and then have to install a FTP server.
On the third party system exists already a Web service for uploading files (in this case I would take the SOAP Adapter).
Another possibility would be to transfer the data with the HTTP Adapter.
My question is what are advantages and disadvantages of transferring the data to the third party system with the HTTP Adapter and respectively with the SOAP Adapter.
Thanks and regards
Patrick

Hi,
thanks for your answer, but most of threads say only that SOAP Adapter is for communication with Web services and HTTP not.
I know this already and in my case I can use both Adapters for the same task and want to know which I should choose in this case.
Like which one is maybe faster, more reliable, practicable , better for large files...
Regards
Patrick

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.

SEND SYNC IN BPM SOAP ADAPTER FOR WS

Hi all,
I´m having problems with an BPM that send a sync message to a ws using a Soap adapter. I have the following error
Work item 000000087293: not possible execute CL_SWF_XI_MSG_BROKER, method SEND_SYNCHRON.
I´m on SP15.
Any Idea?
Many thanks
Noelia

Hi,
Go thru this thread:
Interface Mappings in BPM Collect Pattern
Then try this
1)do a CACHE REFRESH. Is it working?
2) Check transaction SWDD
3) If no other go then try this:= Copy your old BPM to a new name and delete the old one. The again eport it in the Configuration with the old name.
Regards
Suraj
Message was edited by: S.R.Suraj

Failed in Message Mapping for Sender SOAP Adapter

I am using a synchronous Sender SOAP adapter for sending SOAP messages using HTTP security protocol. I am trying to send SOAP messages to XI and then to RFC-R/3. And Responses back from RFC to XI and then to SOAP. I am getting an error for failed in message mapping in SXMB_MONI for converting SOAP messages to RFC. When I debug it in Message Mapping in Integration Repository, it works fine.
Any help is appreciated.
Thanks in advance!
Mrudula

Hi,
try to do a full cache refresh
regards,
Jakub

ABAP Proxy without SOAP adapter in PI7.3

Hi All,
We have dual stack implementation of PI7.3 but we do not wish to use the SOAP adapter for configuring an ABAP proxy scenario.
Is this possible? Is the Javastack only configuration in NW Admin available for use in dual stack implementation also?
Thanks and Regards,
Diptee

Hi All,
So it essetially means that only the below 2 options are available for ABAP proxy scenarios in PI7.3 for a ABAP+Javastack installation
- use of SOAP adapter over XI protocol
- use of conventional proxy configuration of the ABAP Integration Server
And the only Javastack config cannot be used for a dual stack implementation.
Please confirm if above is correct.
Regards,
Diptee
Edited by: diptee s on Sep 21, 2011 4:48 PM

PI 7.3 AEX - XI 3.0 message protocol in the SOAP adapter.

Hello,
My client's landscape is on SAP PI 7.3 AEX(Java only installation) and SAP ECC 6.0 EhP4.
I have configured a HTTP-Proxy scenario. For the proxy messages to go into the SAP ECC system, I have configured a SOAP Receiver adapter in PI 7.3 AEX.
I have created a service interface in ESR in PI 7.3 and generated the proxy in the SAP ECC system.
I have configured the SOAP receiver to use the XI 3.0 protocol and by using the Addressing Type as 'URL Address'. The URL that I am using is " http://<SAP_ECC_server>:PORT/sap/xi/engine?type=entry ".
When I try to test the scenario, the messages are not reaching the target ECC destination and in the SOAP Receiver communication channel, I am getting the following error:
Information: Delivering to channel: SOAP_RECEIVER
Information: MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Information: SOAP: request message entering the adapter with user Guest
Error: SOAP: call failed: java.io.IOException: unable to create a socket Information SOAP: sending a delivery error ack ...
Now, in my client estate there is also a SAP PI 7.11 system, I have replicated the service interface in the ESR on 7.11 and regenerated the proxy in SAP ECC. When I now run the scenario, it works.
Just stressing here on the point that, the abap proxy generated from SAP PI 7.3 ESR did not work(but worked when I generated the abap proxy from SAP PI 7.11 ESR) when configured using the XI protocol on the SOAP adapter.
ALso, I have gone through the 'Note 1247043 - Release Restrictions for EHP 1 for SAP NetWeaver PI 7.1'.
Is the behaviour I am facing a release restriction on SAP PI 7.3
Need suggestions from anyone who has tried configuring this scenario, is there anything that I have missed?
I am happy to share more info if required...
Thanks in advance,
Best Regards,
Karthik

HI Karthik,
Did you able to resolve this in PI 7.3??
Even i am also facing the same issue in receiver soap adapter for abap server proxy:
SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
Please let me know how did u resolve this?
Thanks,
Prasanthi

Sender SOAP Adapter problem in PI 7.1

Hello Everyone,
I have a problem with Sender SOAP Adapter
In PI 7.0 i am able to receive the messages through sender SOAP Adapter for both HTTP and HTTPS. But when i am testing in PI 7.1 i am unable to receive any messages at Adapter level for both HTTP and HTTPS
All sender leagcy system are getting different error messages like
1. 400 HTTP Bad request.
2. Invalid request.
3. BAPI error message
Could any one please assist me in this problem.
Thanks
Vick

Hi Vick,
Try like this......in ID from your sender agreement in which you have your sender SOAP comm channel, from menu select Display WSDL and then copy the WSDL URL and give it to source applications to use it.............create a service user for them to access PI 7.1 server while sending the SOAP req msg.............
your source applications may have to generate proxy from this WSDL URL in their application and then they can send a SOAP req msg to your PI 7.1 server............
Regards,
Rajeev Gupta

Connecting XI with other XI using SOAP adapter, is it possible?

Hi all,
I know that for connection between XIs is recommended using XI connectivity adapter. But I want to send/receive messages trough other XI outside of my network and Im thinking using SOAP adapter for effect. Is it possible?
Thanks in advance.
Cheers,
Ricardo.

Yes, it is. But why? Both are SOAP messages based on HTTP.
Regards
Stefan

SOAP Adapter = Webservice???

Hi,
I have created a service using the SOAP Adapter. My question is now: Is this service a webservice. If yes, how would I be able to obtain the related WSDL?
The outbound interface is accessed by the following URL:
http://myserver/XISOAPAdapter/MessageServlet?channel=:MY_BUSINESSSYSTEM:MY_COMCHANNEL
simply adding the argument &wsdl to the url doesn't pass back any WSDL.
Kind regards,
Heiko

hi,
>>I have created a service using the SOAP Adapter. My >>question is now: Is this service a webservice
yes having a soap adapter for a particular scenario makes that scenaro accessable by SOAP, ie webservice.
>>http://myserver/XISOAPAdapter/MessageServlet?>>channel=:MY_BUSINESSSYSTEM:MY_COMCHANNEL
>>simply adding the argument &wsdl to the url doesn't >>pass back any WSDL.
i see where u r coming from , unlike ohter development platforms, where if you know the endpoint , adding &wsdl gives you the wsdl. But in XI we are merely exposing the interface to be accessable by a soap sender. Hence you have to generate the wsdl manually from Configuration Drectory. Tools->webservce
cheers,
Naveen

SOAP Adapter Content-Type

Hi,
we move a Interface from BC to XI and now the problem come up that the content type isn't correct anymore.
With BC we Post a request with Content Type application/x-sap.idoc to a specific url.
With XI i use the SOAP Adapter for sending the Idoc structure but now in the header the Content-Type is application/xml is there any possibility to change this in the SOAP Adapter.
Or do i have to use another adapter? Somebody has experience with that?
Regards,
Robin

I don't know a standard way to modify the Content-Type.
You can write a custom adapter module that make this:
From http://help.sap.com/saphelp_nw04/helpdata/en/cd/5af7c0c994e24fb0d0088443513de2/content.htm
"In the receiver adapter, if you want to add your own modules to process the request message, you add them before the module specified below; if you want to add your own modules to process the response message, you add them after the following module:
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean"
Or you may try to use the HTTP adapter, there you have the control on content-type
Regards,
Sandro

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

What would be the web servendpoint for a scenario using sender SOAP adapter

Hi,
I have setup a scenario to consume a Service interface in SAP namespace. This is a asynch inbound SI which is not point to point enabled which means the WSDL we get are only the definitions with no endpoints. So I exported it as an external definition which I will then use as sender interface so the scenario looks like this:
Third Party -> SOAP Sender Adapter -> Outbound SI(Imported WSDL) -> XI Box (Mapping etc) -> Inbound SI -> XI Receiver Adapter -> ABAP box
Once all has been setup, for SOAP sender adapter for third party to send data the URL looks like this.
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
But I dont think so this is the endpoint beacuse if I give this in browser I only get an OK status from XI box, what should I give to third party they can use as WSDL endpoint to generate the proxy/stub on their side to send data to SAP.
Regards, Shadab

This is a asynch inbound SI which is not point to point enabled which means the WSDL we get are only the definitions with
no endpoints. So I exported it as an external definition which I will then use as sender interface so the scenario looks like this:
Third Party -> SOAP Sender Adapter -> Outbound SI(Imported WSDL) -> XI Box (Mapping etc) -> Inbound SI -> XI Receiver
Adapter -> ABAP box
Inbound (receiver-end) Service Interface is to be developed from an imported WSDL......not the Outbound (Sender-end) Service Interface.....you actually did the procedure which needs to be done when SOAP is at receiver-end.
If you are clicking the WSDL tab in Service Interface and then taking it as the required WSDL then note that this is not the one.....it is to be generated from ID --> Tools --> Display WSDL (it will be based on the outbound SI)......this will have the end-point which you you mentioned
Now you give this WSDL to the sender application (it will have the end-point) and ask them to develop their coding accordingly.
If you need to view that WSDL in explorer, then you have to publish it somewhere....like in Service Registry (or WSnavigator)
Regards,
Abhishek.

Soap adapter for asynch ?

Similar Messages

Maybe you are looking for