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

Similar Messages

How to Send Multiple Attachment by SOAP Adapter

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

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

Send a file usring SOAP adapter

Can I send a file using SOAP adapter on the sender side.
reg,

Henrique Pinto,
I am trying something out. The scenario I am trying would be a very small but imp part of a bigger business requirement.
I am trying out different options to show the clinet.
1.Started XMLSPY and selected, SOAP>Create new SOAP request>
Now u r asked to browse for the wsdl....DONE. Clicked on OK
Now the request created as an xml file.
2.Go to SOAP> Send SOAP request > there is a new xml file which is the response.
I did not get any errors. I see a file in the target directory.
My problem is where it would really be picking up the data.
WSDL has only referrence to the definition of the message type
(in the definition of O/B interface )
As you have already mentioned that in XI, message type should be refering to file message. If this is the case, how would I incorporate the data in that message.
I hope I am clear.
reg,
Message was edited by:
Naveen Chitluri

IDOC to BPM-SOAP adapter is sending Empty envelop

Hello,
I have a scenario where im using BPM Async/sync bridge to realize the IDOC to SOAP adapter scenario.
The web services will take the request and send the response in string (CDATA). Everything is working fine upto the synchronous interface mapping. After the data gets converted, It calls the SOAP adapter.It is here that im facing the issue. The soap adapter is sending an empty envelop without any data. But in monitoring i can see the data that it is supposed to send.
Please, can anybody help me????
Thanks,
Lakshmi

If I understand correctlty, you are doing a asynt to sync to asyn scenario. In this case you dont need an async-sync bridge.
Your BPM should have only a receive step, sync send and then an asyn send step. You might have one transformation wherever applicable. If you have opened any bridges in BPM, please remove them and try.
VJ

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

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.

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

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

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

File adapter sends return message to SOAP adapter

Hi,
I have managed to send a message using a SOAP sender adapter to a file using the file adapter. The respective message is written to a file. Though both adapters are configured to work in an asynchronous way, the file adapter seems to try to return as message. This results in an error message: "Das Interface-Mapping ... ist nicht im Laufzeit-Cache vorhanden". I have updated and checked the runtime cache. The respective mapping program is available and working, since the file adapter writes the send date to the file. So why this message?
Kind regards,
Heiko

The file adapter replies the sent message, when it is addressed in sync mode.
Set in the SOAP sender channel the Quality-of-Service to Exactly-Once to avoid this behavior.
Regards
Stefan

Send attachment with receiver SOAP adapter

Dear Guru's,
We have created a scenario SAP ERP (ABAP Proxy) -> PI 7.0 -> (Webservice) OSB.
In the ABAP Proxy have we attached a file (jpg). In the SXMB_MONI we see first the file (named attach), and second the MainDocument. It seem's this is the wrong sequence.
We tried to correct this with AF_Modules/PayloadSwapBean in the receiver SOAP adapeter, but it does not work.
There are blogs who tells about how to configure the parameters. We did it as follows:
AF_Modules/PayloadSwapBean swap1
AF_Modules/PayloadSwapBean swap2
swap1: swap.keyName = payload-name
swap1: swap.keyValue = attach
swap2: swap.keyName = payload-name
swap2: swap.keyValue = MainDocument
In the communication channel audit log the swap is processed succesfully, but we don't see nothing changing in the message sequence.
Can somebody please help me with this issue?
Kind regard,
Jeroen Jung

Hi Stefan,
The main thing at this moment is to change the sequence of the payload and attachement. PI puts the attachement first and than the payload and in that sequence the receiver application can't deal with it.
This is a multipart related message and in the header it refers to the image (image/jpeg) first instead of the payload (application/xml).
As you can see in the first message we have used PayloadSwap Adapter module in the receiver SOAP Communication Channel to change this sequence and in the Audit Log of the SOAP CC we can see that it does SWAP functionality succesfully but the result is the same and nothing happens.
Here below you can see the result of a http snapper grabber:
POST /EnterpriseContentManagement/ProxyServices/PS_EnterpriseContentManagement_v1 HTTP/1.0
Accept: */*
Host: localhost:8090
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
CallingType: SA
Content-Type: multipart/related; boundary=SAP_00e371ef-3ca3-11df-9503-001f2966194a_END; type="image/jpeg"; start="payload-9A6BAB4B2FE1273DE10000000A503151 @ sap.com"
Content-Length: 939196
SOAPACTION:
--SAP_00e371ef-3ca3-11df-9503-001f2966194a_END
content-id: payload-9A6BAB4B2FE1273DE10000000A503151 @ sap.com
Content-Type: image/jpeg
*********binary attachment data************
--SAP_00e371ef-3ca3-11df-9503-001f2966194a_END
content-id: payload-9B6BAB4B2FE1273DE10000000A503151 @ sap.com
Content-Type: application/xml
<?xml version="1.0" encoding="utf-8"?>
*********XML Message************
--SAP_00e371ef-3ca3-11df-9503-001f2966194a_END--
Do you have an idea how we can switch the sequence of payload and the attachment? Or why the SWAP functionality doesn't have any result?
Kind regards,
Danke
Jeroen Jung

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

PI 7.1 problems publishing a WSDL of a sender soap adapter

We have upgraded our dev system from XI 3.0 to PI 7.1 and now I'm facing a problem with SOAP adapter. I have searched for answers here for a while but couldnu2019t find them. That why I start an own thread.
I thought with PI 7.1 it is very easy to publish the WSDL of SOAP adapter respectively a sender agreement. All you have to do is to choose your sender agreement and select the menu item "display WSDL" There you can get the WSDL and a WSDL URL. So it would be possible to deliver this URL to my partners. But while checking this URL respectively the delivered WSDL I've found a problem.
First of all the the WSDL URL doesn't look really good:
http://<server>:<port>/dir/wsdl?p=1_1ce2e954fe9632818bfff6c32f370748_portTypeBindingService
But it works. If I call this URL with a browser or with XML Spy I get the correct WSDL. Any chance to get a better readable URL?
The next thing is the proposed soap:address location in the WSDL. It has the following form:
http://<server>:<port>/XISOAPAdapter/MessageServlet?senderParty=&senderService=MYSERVICE&receiverParty=&receiverService=&interface=MYINTERFACE&interfaceNamespace=MYNAMESPACE"
If I compare it with the documentation i can see that the URL is completely different.
http://help.sap.com/saphelp_nwpi71/helpdata/en/43/951aceb1146353e10000000a11466f/frameset.htm
But again if it works all is fine but it doesn't work at least it doesnt work with XML Spy. The reason is the use of "& a m p ;" instead of only "&".
If I create a SOAP request with XML Spy an sent it to the XI I get the following error message: " Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=null;AN=null;ANS=null;"
But if I change the SOAP request parameters replacing all the "& a m p ;" with "&" then it works.
Any chance to manage this? If I provide a WSDL on this way I want that my partners can use this "out of the box"

Kulwant
Yes of course I can change that manually but therefore I have to save the WSDL to my local hard disc, change the WSDL and send it to my partner via mail. This is exactly the way I've done this till now. But with PI 7.1 I like to use the new opportunities.
Bhavesh
I have also no Service Repository till now. That's the reason why I want to use the way described in my initial post.
In PI 7.1 you can open the corresponding sender agreement of you SOAP adapter. There you find a menu item "display WSDL". If you choose this you get a window which displays the correct WSDL and an URL where you can find the WSDL too. If you copy this URL to a browser you get the same WSDL too.
http://help.sap.com/saphelp_nwpi71/helpdata/en/31/daa0404dd52b54e10000000a1550b0/content.htm
First part of my question is regarding to this URL. The URL has a strange format.
The second part is regarding to the form of soap:address in this generated WSDL. Here I have problems with the use of this "& a m p ;" string. But I have no influence on it. If I deliver my partners the obove mentioned URL to the WSDL and the WSDL contains this soap:address URL my partner will probably have the same problem like I with my XML Spy.
Gaurav
I don't understand you answer. I know the correct soap address but the IB tool generates it with this "& a m p ;" string instead of only "&". Thatu2019s the point. No idea if and how I can handle this.
But thank you for the note number. Was helpful. The number is in the online documentation too but I've read over it.
To bad that the online documentation isn't correct regarding to the soap address. But believe me the German version is even worse. There you can find the two soap adapter settings (XI parameter: interface namespace, interface) that are no longer existed in PI 7.1
Now I will test if a .NET application can handle this soap address correctly.
Edited by: Gil Ritter on Nov 14, 2008 11:25 AM

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

Enable a user for SOAP adapter

Dear all,
I'm using XML Spy to send message to XI SOAP adapter (sender adapter). It always requires me to input the user name and password. I have a user with limited authority in the XI server. How cound I enable this user so that I can use it to communicate with the SOAP adapter?
Thanks, Jerome

Jerome,
ask your basis to create a sercivce userid and password . for testing you can use ur userid even though if dont many authorization.if ur user basic authorization this should work.
Regards
Sreeram.G.Reddy

SEND SYNC IN BPM SOAP ADAPTER FOR WS

Similar Messages

Maybe you are looking for