on 10-13-2011 11:11 PM
Hi,
For clarification, used to be (and still appears to be) that for transaction input properties, data type needed to be 'simple' (ie: string etc), and although we can have transaction input properties of type XML, they still appear in the WSDL as string. Although I can see that this works fine even if the string content is actually XML, and the inbound data (which in fact is XML as a string) still looks like XML in the transaction, is this still the recommended approach? Or is there another recommended way to get an XML payload passed in to a transaction using Runner / SOAPRunner from an external application.
Additionally, when calling the Runner (or SOAPRunner) from an external application, is there then any limit to the length of the URI call? I know that browsers have limits on the path, but here we're playing with a path + query string outside of browsers?
Are there any limitations on the Netweaver side?
By the way, currently using MII V12.2.2
Regards
Kevin.
Hi Kevin,
You can pass XML as string to a transaction and make input parameter as XML in transaction.
That is perfectly fine.
As far as I know about the limit of URL, It depends on the server.
However there are two methods to call a http webservice. GET and POST.
Use the POST method which is having more limit than GET method. I have faced issue with GET on high volume of data so replaced it with POST method. I have used the url with query parameters of a few MB's (approx 4-5) and never faced the limit issue with POST. You can check exact limit with some load testing on the server.
Thanks
Anshul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anshul,
Thanks for the quick reply. Yes, seems like we are on the same page. What version MII have you successfully ran your large query string via http post?
BTW, have you also used https for same, or know of any differences using https?
Kevin.
Edited by: Kevin Hibbins on Oct 14, 2011 12:51 AM
User | Count |
---|---|
11 | |
6 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.