Debugging web services in ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2015 03:11 PM
During development of integrations, it is frustrating to see your web service request is failing for reasons unknown. You would like to see what is going under wraps to get better idea of whats going on. ServiceNow provides different flavors of web services (inbound, outbound)(REST,SOAP).
How do we know what is going on with my request. how are headers coming through. what is the request body like and what are responses generated.
Are there any limitations
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-20-2015 09:44 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-20-2015 11:38 PM
Hi Venkata Koya,
This did NOT work for me. There are still no logs recorded for my REST Outbound service.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-21-2015 12:23 PM
what version of servicenow your instance is ?
Are you using RestMessageV2 API ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-24-2016 03:46 PM
what about SOAP response object . How and where to check if an incident id or change request in the response object is sent back to the inbound soap request from an external system say servicemanager trying to create an incident using inbound soap ws-security?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-24-2016 05:32 PM
For inbound SOAP requests, there is a different property which logs request body "glide.processor.debug.SOAPProcessor". This logs entire request body in localhost logs and as well as in DB Logs table