---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# JDBC type data source

# JDBC type data source {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 minutes to read  
A JDBC data source retrieves its data via a JDBC driver, usually type 4
network.
The JDBC connection is available either directly from the ServiceNow instance (a VPN setup
required), or via a dedicated MID Server installed inside your firewall that can access the
database port.  
Note:  
JDBC calls from the MID Server are never encrypted. Limit the rights available to the MID Server user whenever making JDBC calls from a MID server.

## JDBC data source supported database formats {#r_JDBCTypeDataSource__section_fsh_4rc_m1b}

JDBC data sources support several database formats and ports.
{#r_JDBCTypeDataSource__table_jnc_grj_dq__entry__2}

| SQL Server Type | Port |
|-|-|
| MySQL | 3306 |
| Microsoft SQL Server | 1433 |
| Oracle | 1521 |
[Table 1. Supported database formats]

{#r_JDBCTypeDataSource__table_jnc_grj_dq}  
Note:  
Oracle DATE fields are loaded as ServiceNow Date/Time fields.

## JDBC data source SQL statement requirements {#r_JDBCTypeDataSource__section_bmj_wrc_m1b}

JDBC queries that run SQL statements must specify a column name.
For example, this query specifies the column name ServerID.

    SELECT DISTINCT 'server_name:' + CONVERT ( VARCHAR , lg .ResourceID ) AS 'ServerID' 
    ,LastHWScan
    ,Account0
    ,Category0
    Fromv_GS_WORKSTATION_STATUSsInner  JOIN
    v_GS_LocalGroupMembers0lg
    ON s .ResourceID  = lg .ResourceID
    WhereType0  = 'Local' AND Category0  = 'SystemAccount'

## SQL server integrated authentication for Windows {#r_JDBCTypeDataSource__section_awk_psc_m1b}

A JDBC data source can use the ID of for the Windows MID Server service user to
authenticate with SQL Server.

The Use integrated authentication check box on the Data Source form
determines if the JDBC data source uses the MID Server service user credentials. For this
field to appear on the Data Source form, the integration must meet these criteria:

* The MID Server must be running on a Windows computer with SQL Server.
* The MID Server service must use the same credentials that SQL Server requires.
* The data source Type is JDBC.
* The data source Use MID Server check box is selected.
* The data source Format is SQLServer.

{#r_JDBCTypeDataSource__ul_dbx_ymj_dq}  
Important:  
If integrated authentication is chosen, and you are integrating with Microsoft System Center Configuration Manager, the account running the MID Server service must have read rights on the SCCM database.  
Figure 1. Data Source form  
Note:  
The Last run database field on the JDBC data source is case-sensitive for the SQL server.

## Adding JDBC drivers for unsupported database formats {#r_JDBCTypeDataSource__section_znh_ztc_m1b}

Use the following procedure to extend the data source to use a driver for a database that
is not provided in the base system. JDBC connections are supported for the following default
databases:

## Add a new JDBC format choice {#ariaid-title2}

Extend the available JDBC driver options by creating a new choice list entry to
specify the JDBC driver Java package name.

### Before you begin

Role required: import_admin

### About this task

Add a new choice list entry for the new database to the Format
field in the sys_data_source table.

### Procedure

1. Navigate to System Import Sets \> Administration \> Data Sources.
2. Click New.
3. In the Data Sources form, right-click the Format field label, and select Show Choice List from the pop-up menu.  
4. Click New in the list of choices.
5. Provide the following values to create the new database choice.  
   Look at the existing drivers for examples.
   * Table: sys_data_source
   * Label: Database name that appears as an option in the Format choice list, for example: Teradata.
   * Value: Package name and class of the driver. For example, the value for TeraData is com.ncr.teradata.TeraDriver.  
     Note:  
     The driver package and class must be provided by the driver vendor. This information is often available in the vendor's documentation, such as for [MariaDB](https://mariadb.com/kb/en/mariadb/about-mariadb-connector-j/) or [Teradata](https://developer.teradata.com/doc/connectivity/jdbc/reference/current/faq.html).
   * Dependent value: JDBC

6. Click Submit.  
   The new data source now appears in the list of available JDBC formats.

## Add Sybase or DB2 JDBC format choices {#ariaid-title3}

Extend the available JDBC driver options by activating the Sybase or DB2
choices.

### Before you begin

Roles required: admin  
Important:  
To use Sybase or DB2 JDBC drivers, you must manually install the driver JAR file on a MID server. Refer to [KB0551236](https://support.servicenow.com/kb_view.do?sysparm_article=KB0551236) for more information.

### About this task

Activate the Sybase or DB2 JDBC drivers to connect with those database formats through a MID server. This procedure assumes you are using the following Sybase or DB2 drivers:{#t_AddSybaseAndDB2Drivers__table_ttl_h4c_2t__entry__3}

| Format | Driver | Driver class |
|-|-|-|
| Sybase | jconnect-jdbc | com.sybase.jdbc3.jdbc.SybDriver |
| DB2 | db2jcc | com.ibm.db2.jcc.DB2Driver |
[Table 2. Drivers]

{#t_AddSybaseAndDB2Drivers__table_ttl_h4c_2t}

If you are using a different implementation of the Sybase or DB2 driver, you
must modify the choice Value to use the driver class from
your driver implementation.

### Procedure

1. Navigate to System Import Sets \> Administration \> Data Sources.
2. Click New.
3. In the Type field, select JDBC.
4. Right-click the Format field label, and select Configure Choices from the pop-up menu.
5. Move the Sybase or DB2 Universal choices from the Available column to the Selected column.
6. Click Save.  
   The new data source now appears in the list of available JDBC formats.

## Install a driver on a MID Server {#ariaid-title4}

You can install a new JDBC driver JAR file to a MID server to access database formats
that are not supported by default.

### Before you begin

Role required: agent_admin

### Procedure

1. Navigate to MID Server \> JAR Files.
2. Click New.
3. Complete the following fields:  
   * Name: A unique and descriptive name for identifying the file in the instance.
   * Version: A version number for the file, if one is available.
   * Source: Location of the JAR file for reference purposes. Source information is not used by the system.
   * Description: Short description of the JAR file and its purpose in the instance.
4. Click the paper clip icon in the banner and attach the JAR file to the record.  
5. Click Submit.
6. Restart the MID Server service.  
   The platform makes the JAR file available to any MID Server configured to communicate with the instance.

## Create a JDBC data source for an unsupported database format {#ariaid-title5}

Add a JDBC data source by defining a data source record.

### Before you begin

* Role required: import_admin
* This procedure covers how to create a JDBC data source for an unsupported database format. For general information on creating a JDBC data source, including a detailed description of form fields, see [Create a JDBC type data source](https://www.servicenow.com/docs/_atpKCANn2CkjsCVQqze6w "Create a JDBC type data source record to define what data an import set should import.").
{#t_CreateANewDataSource__ul_yfg_1p2_mjc}

### Procedure

1. Navigate to AllSystem Import SetsAdministrationData Sources and click New.
2. In the Data Source form, select JDBC from the list in the Type field.
3. Select the new data source from the choice list in the Format field.  
4. [Configuring the form layout](https://www.servicenow.com/docs/access?context=configure-form-layout&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) and add the Connection URL field.
5. Provide the connection URL to the JDBC data source, and then click Submit.  
   No other connection information is required.  

## Create an import connection alias {#ariaid-title6}

Create an import connection alias for the JDBC type data source records.

### Before you begin

Role required: import_admin

### Procedure

1. Navigate to AllSystem Import SetsAdministrationImport Connection Alias..
2. Select New.
3. Provide a name for the alias.
4. Select the name of the alias to open the JDBC connections page.
5. On the JDBC connections page, select New
6. Fill the form.  
   {#create-import-connection-alias__table_tpf_3x3_z3b__entry__2}

   | Field | Description |
   |-|-|
   | Name | A unique name for this JDBC connection. |
   | Use MID Server | MID Server to use to connect to this data source. |
   | Format | Select one of the following formats: MySQL, Oracle, or SQL Server. |
   | Instance name | Used to support dynamic port connectivity with SQL Server. To ensure connectivity, provide the instance name for a SQL Server that receives a new port number dynamically after each reboot. This field only appears when SQLServer is selected as a data source format. |
   | Server | Name of the server from which the tables will be imported. |
   | Database name | Name of the database instance. |
   | Database port | Port number for the database. Leave this field empty when using dynamic port connectivity with SQL Server. |
   | Use integrated authentication | Selected to enable the JDBC connection to use the ID of the user configured for the Windows MID Server service for SQL Server authentication. For additional details, see [JDBC type data source](https://www.servicenow.com/docs/LX0YsmaCANyqiyiccb2YYQ#r_JDBCTypeDataSource "A JDBC data source retrieves its data via a JDBC driver, usually type 4 network."). |
   | Connection URL parameters | Optional parameters to add to the end of the URL generated for this data source. Semicolon-separated list of parameters. |
   | Connection URL parameters | Optional parameters to add to the end of the URL generated for this data source. Semicolon-separated list of parameters. |
   | Connection URL | Read-only field auto-generated by the system. To set connection URL manually, select the Manually set connection URL option. |
   | Manually set connection URL | Option to manually set the connection URL. |
   | Import connection alias | The import connection alias associated with the JDBC connection. |
   | Use username password to authenticate | Option to provide the username and password for authentication. When this option is switched off, the connection properties are used for authentication. |
   | Username | User name for authentication on the JDBC server. |
   | Password | Password for authentication on the JDBC server. |
   | Connection timeout | Number of seconds before MID Server connection cache pool closes and removes it from the pool. Zero (0) means no timeout. |
   | Query timeout | Number of seconds the JDBC driver waits for a query (SELECT) to complete. Zero (0) means no timeout. If timeout is exceeded, the integration considers the JDBC result inaccessible and places it in an error state |
   [ ]

   {#create-import-connection-alias__table_tpf_3x3_z3b}
7. Select Submit.

*[\>]: and then