XML Payload to Transaction Input

Question

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.

Answer 1

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