Hi Pawan,
The JavaScript engine implements JSON.parse in GatewayScript so any DataPower object will not impose parse limits. As noted you'll need to use a parse policy in v10. If you're using v5, the only option I can think of is a custom policy that takes the payload and passes it to a HTTP Convert DataPower action with JSON encoding. This will use the JSON parse settings specified on the service's XML Manager's JSON setting object, in the case of v5 the webapi XML Manager. Depending upon your v5 version, you may need to update both the XML manager to specify your own JSON settings object as older versions of v5 used the default JSON settings and did not reference an object. Newer versions of the product would have a JSON settings object already referenced so you'd just need to update those settings. Since these are product objects, you would need to override these object's configurations by specifying an updated configuration in a gateway extension.
Regards,
Steve
------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM
------------------------------