Troubleshooting outbound REST web services
Overview
Outbound REST functionality enables you to retrieve, create, update, or delete data on a web services server that supports the REST architecture. You can send a REST message by a REST workflow activity or by using the RESTMessageV2 script API.
Troubleshooting Procedure
To troubleshoot outbound REST issues, set the system property glide.rest.outbound.debug to true.
-
Go to /sys_properties_list.do.
-
If the glide.rest.outbound.debug system property is not listed in the table, click New and create the property with the following following values:
- Name: glide.rest.outbound.debug
- Type: true|false
- Value: true
Once this property is set, additional information about the outbound REST message is captured in the logs.
-
Navigate to System Logs > Node Log File Browser.
Note that you will be able to read the node log file only for the node you are currently logged in to. If you are unable to find the output for your REST call, the REST call might have been processed by another node. Try to log in through a different browser or private browsing window (incognito window) and see whether you can find the information on those node log files, or contact support for assistance with retrieving the information from the log files.
-
Select the time frame during which the outbound REST call is made and Message contains REST Msg Outbound.
Example
In the following example, an outbound REST call is made from one instance to another. This will give you additional information about the headers and the body that is sent out.
If any errors are encountered you can check them in the logs.
| Note: Test the outbound REST message first outside ServiceNow by using tools such as cURL, POSTMAN, or any other REST client. |
2017-12-28 15:12:31 (663) Default-thread-201 42EE184A4FDB0B002BEDA9D18110C707 DEBUG: REST Msg Outbound - RESTMessageClient : Executing: Outbound REST Message/Method: OutboundIncidentREST/post
HTTP Request:
POST https://<instance-name>.service-now.com/api/now/table/incident
Content-Type: application/json
Authentication type: basic
Authentication profile:
Profile name: <profile-name>
Username: admin
Password: ********
Mutual Auth: false
ECC Queue: false
Request Content:
Length: 66
Content: {"caller_id":"Abel Tuter","short_description":"from REST POST123"}
2017-12-28 15:12:32 (325) Default-thread-201 42EE184A4FDB0B002BEDA9D18110C707 DEBUG: REST Msg Outbound - RESTMessageClient : Response: Outbound REST Response
HTTP Status: 201 Created