# Resource Databases Connector

{% hint style="info" %}
Alemba is currently reviewing and updating the whole of the connector section, including all subsections.  Expect this section to be updated by end of June, 2025.
{% endhint %}

The connector requires configuration of the associated ICNF file within the ASM Core folder structure so that it can cater for any schema in third-party databases. This connector can import external resource data into ASM Core such as:

* Configuration Items
* Services
* Service Actions
* Person records
* Subscriber Groups
* Knowledge articles
* Organization
* Location
* Cost Center
* Contract records.

The connector can retrieve data from many tables in a database and define links and views for the elements imported.

{% hint style="info" %}
Resources cannot be imported until the associated ICNF file has been configured for the target database. Learn more about [Configuring the Database Resource Connector](#installi).
{% endhint %}

This section of the documentation describes the details of the connector, including:

* The name of the files used
* Connector class
* Connection methodology
* Use case scenario

{% hint style="info" %}
You should familiarize yourself with the information in [Installing Connectors](/asm-hermes/integrate/managing-integration/connectors-to-asm-core/installing-connectors.md) before installing any connectors, and read the [Integration](https://github.com/andriabradac/ASM-Sync/blob/10.6.8/integrate/managing-integration/connectors-to-asm-core/generic-connectors-to-asm-core/resource-databases-connector/broken-reference/README.md) topics for more information on how to configure them.
{% endhint %}

### Use Case Scenario

<table data-header-hidden><thead><tr><th width="185"></th><th></th></tr></thead><tbody><tr><td>Purpose</td><td>An organization records employee data in a third-party database and wants to import and merge that data with ASM Core.</td></tr><tr><td>Role</td><td>The role of this connector is to expose the data in order to allow for population and ongoing consistency checks of the ASM Core CMDB.</td></tr></tbody></table>

### Connector Description

The table below provides a description of the CMDB databases Connector.

<table data-header-hidden><thead><tr><th width="280"></th><th></th></tr></thead><tbody><tr><td>Information fields</td><td>Name</td></tr><tr><td>Connector</td><td>3rd-party database &#x3C;-> ASM Core</td></tr><tr><td>Assembly</td><td>Alemba®.Connector.SQL.FedCMDB.dll</td></tr><tr><td>Connector class (Source class)</td><td>Alemba®.Connector.SQL.FedCMDB.Connector</td></tr><tr><td>Configuration file</td><td>Alemba®.Connector.SQL.FedCMDB.icnf</td></tr><tr><td>Connection methodology</td><td>Database</td></tr></tbody></table>

### Connection Parameters

{% hint style="warning" %}
The login account used to access the database must have permissions to read and write to the specified table(s).
{% endhint %}

If using Windows Authentication to log into the database

* the Windows User configured for the ASM Connector Service, and the IIS User account for the Web UI, must both have read and write permissions to the database
* append **;Integrated Security=SSPI** to the connection string
* leave blank the Login ID and Password fields in the connection parameters

<table data-header-hidden><thead><tr><th width="215"></th><th></th></tr></thead><tbody><tr><td>Parameters</td><td>Description</td></tr><tr><td>Connection String</td><td><p>Database server connection string. Formats:</p><p>Server=&#x3C;DatabaseServer>;Database=&#x3C;DatabaseName></p><p>Server=&#x3C;DatabaseServer>;Database=&#x3C;DatabaseName>;Integrated Security=SSPI</p><p>Server=localhost;Database=Core</p><p>Server=localhost;Database=Core;Integrated Security=SSPI</p></td></tr><tr><td>Login ID</td><td>Login ID for the third-party database</td></tr><tr><td>Password</td><td>Password for the third-party database</td></tr></tbody></table>

{% hint style="warning" %}
Connecting to an Oracle database may require a different connection string format, for example, Datasource=\<DatabaseName>.
{% endhint %}

### Diagnostics

The connector has the facility to trace information. The data can be obtained through Polling tracing or Application tracing.

### Configuring the Database Resource Connector <a href="#installi" id="installi"></a>

This connector requires configuration of the connector configuration file (.ICNF) to expose the tables and attributes in the third-party database that contain resources to be imported into ASM Core.

Unlike other connectors, the ICNF file for the Database Resources Connector does not come pre-configured. Configuration of **Alemba®.Connector.SQL.FedCMDB.icnf** is required.

A Tutorial for [Configuring the Database Resources Connector](/asm-hermes/integrate/managing-integration/connectors-to-asm-core/generic-connectors-to-asm-core/resource-databases-connector/tutorial-for-configuring-the-database-resources-connector.md) has been provided as a guide on how to configure the ICNF file for this connector. For further assistance with configuring your ICNF file, contact your Account Manager to engage an Alemba® Professional Services Consultant.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.alemba.com/asm-hermes/integrate/managing-integration/connectors-to-asm-core/generic-connectors-to-asm-core/resource-databases-connector.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.