---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Direct JDBC Probe

# Direct JDBC Probe {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

A direct JDBC probe specifies all the parameters necessary in the outbound
ECC Queue XML payload.  
It is a standalone probe that is decoupled from a JDBC Data Source and does not insert into an import set. The required field in the ECC Queue record for a direct JDBC probe is Topic and it must equal JDBCProbe. The Source field is reserved for the `sys_id` of the data source record in the case of a JDBC data source.  
Note:  
If you have ServiceNow Discovery enabled on your platform, add the skip_sensor parameter to the probe to avoid the discovery sensors from processing the probe and resulting in a "No sensors defined" error.

## XML Structure

A direct JDBC probe has the following XML payload structure

    <parameters><parameter name = "skip_sensor" value = "true" /><parameter name = "parameter_name" value = "parameter_value" />
      ...
      <parameter name = "work" ><select  ... >
          ...
        </select></parameter></parameters>

**Related tasks**   

* [JDBCProbe](https://servicenow-prod.fluidtopics.net/4E7tkaBMmwGF4VBg9ZKK9A "A JDBC probe runs on the MID Server to query an external database via [JDBC] and returns results to ServiceNow.")