on 10-11-2011 11:06 AM
Hi,
We are facing a peculiar issue when using SOAP sender adapter.It is a SOAP-XI-ECC scenario.
We have created WSDL using propose URL. Edited the address location in WSDL and included QoS=ExactlyOnce.
When we are testing from SOAPUI, it is making a asynchronous call, which is the requirement. But when the actual sender is sending the data using the same WSDL, it is making synchronous call. Any idea if Synchronous/Asyncronous decision/setiing is made at XI end or the portal end? And what is the solution?
Thanks,
Vishal
By adding qualityofservice in the appended URL, if you are able to test using soapUI and make asynchornous call then the problem is with WSDL URL of sender system. Please check with them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
One more issue is that the Status of the messages sent from source system is coming as 'Log Version' in moni.
Checked smq1 and smq2, it is clear. And queues should not be a problem, since we are still getting it as Synchronous.
But any pointers regarding 'Log Version' status would be very helpful.
Thanks,
Vishal
in the end point URL being used by the source system make sure that there is appended to the URL
&QualityOfService=ExactlyOnce
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the Endpoint URL, that the Sender System Call, there's the parameter QOS=EO ??
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.