It will help me to debug but as permanent solution I am trying log every request which I will be receiving in to a table. I am trying to get correct location to call activity to save incoming request into table. Exception scenarios, We will not get control in service activity to log request.
You can enable debug on the pyInvokeRestConnector activity.
I have not yet checked this activity but definitely we will have a javastep which will form the request. If you dont want to put debug on full activity, then you need to manually add oLog.infoForced("Request", request) <<soemthing like this to log the message>>.
I will check once and will give you the complete step.
We had a similar requirement and the approach we followed was to override the pyInvokeRestConnector to capture the raw response in a new parameter .In the 5th step of the activity you can include the below code.Once you do this you will have all the details on the parameter page and you can use an activity to get details from the parameter page and write it into a table.
if (! (ignoreData || responseMap == null))
responseBody = responseMap.get("body");
// CUSTOM CODE TO SET THE WEBSERVICE RESPONSE TO A PARAMETER ON PARAMETER PAGE
how about mapping the JSON request and response to a string properties and you do the mapping in your service activity using ClipboardPage.adoptJSONObject(strJSON) and ClipboardPage.getJSON() Engine API methods.
so the control will come to your Service activity and you can handle parsing errors.