# Profiles & Destinations

> Choose which data goes where with Tables and Messages Profiles, and add SQLite, PostgreSQL, SQL Server, and MQTT destinations.

URL: https://www.trakhound.com/docs/mtconnect-server/profiles

A **Profile** is a reusable rule for which data goes where. Each Profile has a type, a [Filter](https://www.trakhound.com/docs/mtconnect-server/filters), and one or more destinations. Profiles are listed under **Collection > Configuration > Profiles**.

| Type | Destination |
| --- | --- |
| **Tables** | Stores the Devices, Observations, and Assets in SQLite, PostgreSQL, or SQL Server (see [Database Tables](https://www.trakhound.com/docs/mtconnect-server/tables)) |
| **Messages** | Publishes the Devices and Observations to an MQTT broker (see [MQTT Messages](https://www.trakhound.com/docs/mtconnect-server/messages)) |

## Add a Profile

1. Go to **Collection > Configuration > Profiles** and click **Add Profile**.
2. Choose its **Type**, **Tables** or **Messages**. The type can't be changed after the Profile is added.
3. Set it up on its tabs (below), and click **Save Changes**.

| Tab | Settings |
| --- | --- |
| **Information** | The **Description** the Profile is listed by, and a summary of its other tabs. Tables Profiles have **Store Assets** (store the MTConnect Assets of its Devices). Messages Profiles have a **Base Topic** (`trakhound/mtconnect/collection` when blank). |
| **Destinations** | The Routers the data is sent to. Click **Add** next to each one. Routers with a Service of the Profile's type are listed first. With none selected, the data isn't sent anywhere. |
| **Filter** | The DataItems to include, and how often values are sent (see [Filters](https://www.trakhound.com/docs/mtconnect-server/filters)). |
| **Retention** (Tables) | How long Observations are kept (see [Data Retention](https://www.trakhound.com/docs/mtconnect-server/data-retention)). |
| **Devices** | Tick a Device to select this Profile for it. Changes are saved immediately. Devices that have the Profile from their Group are marked **From its Group**, and Devices with Collection off can be turned on. |

A Profile can also be selected on a Device's **Collection** tab, or given to a [Group](https://www.trakhound.com/docs/mtconnect-server/groups) so every Device in it has the Profile.

## Services and Routers

A Profile's destinations are **Routers**, and a Router sends data to one or more **Services**, the connections to a database or an MQTT broker. Saving a Service creates a Router with the same name, which is then selected in a Profile's **Destinations**. A Profile can have several destinations, for example to store the same data in two databases.

Services are configured under **Collection > Configuration**, in **Tables (SQL Server)**, **Tables (PostgreSQL)**, **Tables (SQLite)**, and **Messages (MQTT)**. Each page lists its Services with their **Status** (**Loaded** once the Service is running) and the Profiles that use them. Click **Edit** to change one, or **Add** to add another. A Service can't be removed while a Profile uses its Router.

### SQL Server

| Field | Default | Description |
| --- | --- | --- |
| Name |  | Required. Also the name of its Router |
| Description |  |  |
| Server |  | Required |
| Port | `1433` |  |
| Database |  | Required. Must already exist, and the User must be able to create tables and schemas in it |
| User / Password |  | Leave the Password blank when editing to keep the existing one |
| Trust Server Certificate | Off | Turn on when SQL Server uses a self-signed certificate |

### PostgreSQL

The same fields as SQL Server: **Name**, **Description**, **Server**, **Port** (default `5432`), **Database** (must already exist), **User**, and **Password**. The User must be able to create schemas and tables in the database.

### SQLite

A **Name**, **Description**, and **Database File** (a full path on the server). The Quick Start can leave the Database File blank to use the `data` folder in the install directory. SQLite has no schemas, so each schema is kept in its own file next to the database (ex. `data.mtconnect_observations.db`). Use SQLite for a trial or a few Devices, and PostgreSQL or SQL Server for production.

### MQTT

| Field | Default | Description |
| --- | --- | --- |
| Name |  | Required. Also the name of its Router |
| Description |  |  |
| Hostname |  | Required |
| Port | `1883` |  |
| Client ID |  |  |
| QoS | `0` | `0`, `1`, or `2` |
| Username / Password |  |  |
| Use TLS | Off |  |

> The database and MQTT Services don't require a License. Only the Devices that are collected use a seat of a [Collection License](https://www.trakhound.com/docs/mtconnect-server/licenses).
