on 01-16-2015 8:48 PM
Hi All,
We are still not able to make SOAP to IDOC scenario working. I have set Asynchronous in Sender "Service Interface" and set "Exactly Once" in sender soap communication channel. I got WSDL from sender agreement and sent to my java team. And I asked them to use URL http://<hostname>:<port>/ XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>. But PI always get error saying "Only asynchronous processing supported for IDoc adapter outbound processg". I see in the error log, "QualityOfService has been set back to BestEffort and ProcessingMode has been set to synchronous. When I test using SoapUI and using URL "
&Sender.Service=BS_XXX&Interface=http%3A%2F%2Fsoapadapter_SOAPtoIDoc%5EMI_XXX." . It seems to be working. But our Java team could not generate a web service client based on my wsdl and even changed end point url to "
&Sender.Service=BS_XXX&Interface=http%3A%2F%2Fsoapadapter_SOAPtoIDoc%5EMI_XXX.". Anyone has any idea? If anyone could provide this kind of sample asynchronous web service client, would be great appreciate.
Thanks a lot!
Charles
Hi Charles,
Try to Re- generate WSDL file with Asynchronous in Sender "Service Interface" and set QualityOfService as "Exactly Once" . then re-publish the new generated WSDL to the web-service team. Also to try to refresh the cache once.
WSDL URL format:
http://<PI HOST name>:<PORT as what comes in IFR page>/XISOAPAdapter/MessageServlet?channel=<Party>:<Service Name>:<Channel Name>
..............
Mutti
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mutti,
How do you "Re- generate WSDL file with Asynchronous in Sender "Service Interface" and set QualityOfService as "Exactly Once" " ? I see there is wsdl tab in sender service interface. I can display and save the wsdl to my local PC. But I can't publish it from there, since the button is grayed out for outbound service interface. Also, where you can set QualityOfService as "Exactly Once"?
Thanks,
Clarles
Hello,
There is a possibility that your sender partner is sending the messages with QoS best effort.
Also, you can try generating the WSDL using following option in ID:
Tools>Define web service> Next> Click on propose URL and continue mentioning the required information. At the end, it will generate the WSDL.
Thanks,
Kedar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Charles
Do you know why the Java team couldn't generate a client for your WSDL? SOAPUi must have generated a client.
regards
Steve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.