---
title: External Device Database Integration for Devices
slug: reference-guide-3-0-0/external-device-database-integration-for-devices
description: Learn how to import devices from an external database into Single Connect with our comprehensive guide. Discover the configuration settings, step-by-step instructions, and essential parameters for seamless integration. Easily add or edit element type prop
docTags: 
createdAt: 2022-07-26T14:31:32.000Z
---

The external device database import configurations allow Single Connect to automatically detect and discover instances for the relevant Device Groups, based on their custom tags.

The following configuration is required in order to add/discover devices from external device databases.

### Configurations on the System Config Manager

Navigate to Administration > System Config Man. and set the following parameters:

| **Parameter Name**              | **Parameter Value**                                                                                                                                                                                                                                                                                                       | **Encryption**       |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
| **device.database.driver\_n**   | Database driver for external database connection. <br />Ex.: device.database.driver\_0 = org.postgresql.Driverdev                                                                                                                                                                                                         |                      |
| **device.database.password\_n** | External database password.                                                                                                                                                                                                                                                                                               | must be set as “yes” |
| **device.database.source**      | Database IP addresses. Multiple values must be separated by “**;**”.  Ex.: 10.10.10.10;20.20.20.20                                                                                                                                                                                                                        |                      |
| **device.database.sql\_n**      | SQL Query to import devices. IP address, hostname, element type specifier and one of the tag values is mandatory.&#xD; Ex.: device.database.sql\_0 =&#xD;<br />SELECT **dynName** AS IP\_ADDRESS, server AS HOSTNAME , os AS ELEMENT\_TYPE\_SPECIFIER , id AS PORT, os as TAG\_OS, site as TAG\_SITE FROM devicedatabase. |                      |
| **device.database.url\_n**      | JDBC URL address for database connection. &#xD;<br />E.g: device.database.url\_0 = jdbc\:postgresql://10.10.10.10:5432/databasename&#xD;                                                                                                                                                                                  |                      |
| **device.database.user\_n**     | External database username.                                                                                                                                                                                                                                                                                               |                      |

### Add/Edit Element Type Properties for External Database Integration

Importing instances from an external database requires an Single Connect job for synchronization. The job will update the information on Single Connect periodically, depending on the cron expression:

1. Navigate to **Administration&#x20;**> **Jobs Scheduler**.
2. Open the **Trigger List** tab.
3. Select **DeviceDatabaseImportJob&#x20;**&#x61;s the Job.
4. Fill in the **Trigger Name** and **Cron Expression** fields.
5. To enable the job, select **Enabled** for the **Active&#x20;**&#x66;ield and click **Save**.

### Device Inventory Export

Devices with SSH/Telnet or MSSQL access protocols, can be exported to be used in other clients. SSH/Telnet devices are exported in the SecureCRT client format. MSSQL devices are exported in the SQL Server Management client format.
To export devices in the supported format:

1. Navigate t&#x6F;**&#x20;Device Management** > **Device Inventory**.
2. Click th&#x65;**&#x20;Export** button at the bottom of the device group list.
   Two options are displayed after clicking the **Export** button:**&#x20;MSSQL EXPORT** and **SECURECRT EXPORT**.

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/bKPkEy2N_EbLiyUczBwZ0_image.png "Export Devices")

- To export MSSQL devices, select **MSSQL EXPORT** and clic&#x6B;**&#x20;OK**.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/2SHlFdpSV_l1xuxhNqg54_image.png" size="38" width="475" height="163" caption="MSSQL Device Import" position="center" showCaption="true"}

An xml file is exported in the “regsrvr” format. The exported file is imported to the “Registered Servers Field” of the SQL Management Studio client for easy usage. When the Single Connect IP address and the bind port related to the target MSSQL device are exported into the file, only the username and password are required to log in.

- To export devices with SSH/Telnet access protocol, select **SECURECRT EXPOR**T.
- Select **Operating System** and fill in the **Username** field, then click **OK**.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/6YTfHGqJZBiX1mDIuiIk1_image.png" size="38" width="433" height="325" caption="SSH/Telnet Device Import" position="center" showCaption="true"}

A zip file is exported in the SecureCRT format to be imported to the SercureCRT client. The Single Connect IP, SSH proxy port, device IP and the port are exported into the file. During the connection from SecureCRT, only the username and password will be required.