> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery/txone.md).

# TXOne

Connect your TXOne StellarOne console to pull protected OT endpoints into Dispel as devices, mapped to a Wicket and refreshed on a recurring sync.

## Overview

The TXOne integration lets Dispel pull the OT endpoints managed by your TXOne **StellarOne** console and bring them in as Dispel devices. You connect to StellarOne once, map it to a Dispel facility and Wicket, and Dispel imports the matching devices and keeps them current on a recurring sync.

TXOne is an **asset-discovery** integration. Dispel connects to your StellarOne management console and only ever reads from it.

In StellarOne, **agents** are the StellarProtect endpoints under management. Dispel imports each agent as a device, reporting its IP, MAC, hostname, operating system, and installed ICS applications. Because a StellarOne console represents a single environment, Dispel treats the console as one **site** that you map to a single Wicket.

#### What Dispel imports

* Managed agents (hostname, IP address, MAC address, operating system) as Dispel devices.
* Observed network protocols and ports for each agent.
* A link back to the agent in StellarOne, stored on the device.

{% hint style="info" %}
**Where to find it.** Sign in as an organization administrator and open **Settings → Integrations**. TXOne appears in the **Asset Discovery / Network Visibility** section. Click **Connect** on the TXOne card to begin.
{% endhint %}

## Before you begin

You'll need the following from your TXOne StellarOne console:

* An **API key**, generated from the StellarOne Management Console (see the StellarOne Administrator's Guide for the exact steps).
* The **StellarOne URL** of your console — for example `https://stellar1.example.com`.
* If your console uses a **self-signed TLS certificate**, be ready to enable the self-signed option during setup.

{% hint style="warning" %}
**Allowlist Dispel's IP.** When you open the connection form, Dispel shows a **Whitelist IP** value. Add this address to your network firewall allowlist so Dispel can reach the StellarOne console.
{% endhint %}

## Connecting TXOne

1. Go to **Settings → Integrations** and click **Connect** on the TXOne card.
2. Optionally set a **Display Name** to tell this integration apart from others (you can connect more than one console).
3. Fill in the connection fields:

| Field                              | Type       | Notes                                                                        |
| ---------------------------------- | ---------- | ---------------------------------------------------------------------------- |
| **StellarOne URL**                 | Config     | The URL of your TXOne StellarOne management console.                         |
| **Allow Self-Signed Certificates** | Config     | Toggle on if your console uses a self-signed TLS certificate.                |
| **API Key**                        | Credential | The API key generated in StellarOne. Stored encrypted and never shown again. |

4. Click **Test Connection** to confirm Dispel can authenticate against StellarOne. Fix any reported error before saving.
5. Click **Save**. Dispel saves the integration and immediately runs the initial sync.

{% hint style="info" %}
**Your credentials are encrypted.** The API key is encrypted at rest and is never displayed again after you save. When editing later, leave the credential field blank to keep the stored value.
{% endhint %}

## Mapping the console to a Wicket

Once the initial sync finishes, open the integration to find the **Site Mapping** section. TXOne appears as a single site representing your StellarOne console.

> Map each vendor site to a Dispel facility and wicket. Devices from mapped sites will be synced into Dispel.

1. Pick a **Facility**.
2. Pick a **Wicket**. If the facility has only one Wicket, Dispel selects it for you.
3. Click **Save Mappings & Import**.

Dispel imports the console's agents into the mapped Wicket — you'll see progress move from waiting, to fetching, to syncing, to complete — and then reports how many devices were imported (for example, **"12 devices imported"** or a breakdown of new versus already-imported devices). Imported devices appear in the mapped Wicket alongside any devices you've added manually.

## Keeping your inventory current

* Dispel **re-syncs automatically** on a recurring schedule, so newly enrolled agents and changed details are picked up without any action from you.
* To pull the latest inventory immediately, open the integration and choose **Refresh**.
* To change connection details or rotate the key, edit the integration and use **Save & Sync**. Leave the credential field blank to keep the current key.

## Connection status

Each integration shows a status so you always know where it stands:

| Status              | Meaning                                                 |
| ------------------- | ------------------------------------------------------- |
| **Not Initialized** | Saved, but the first sync hasn't run yet.               |
| **Initializing**    | Running the first sync.                                 |
| **Ready**           | Connected and synced; the mapping is applied.           |
| **Needs Refresh**   | New vendor data is available; run a refresh to pull it. |
| **Refreshing**      | A sync is in progress.                                  |
| **Pending Changes** | Mapping changes are saved but not yet applied.          |
| **Applying**        | Importing devices for your saved mapping.               |
| **Failed**          | The last operation failed — see the error guidance.     |

A separate **health badge** (Connected, Degraded, Unreachable) reflects whether Dispel can currently reach the StellarOne console.

## Troubleshooting

If a sync or test connection fails, Dispel classifies the error and suggests a fix:

| Error                     | What it usually means and how to fix it                                                                                                                         |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Authentication Failed** | The API key was rejected. Generate a new key in StellarOne and update the integration.                                                                          |
| **Endpoint Unreachable**  | Dispel couldn't reach the console. Verify the StellarOne URL and that Dispel's IP is allowlisted in your firewall.                                              |
| **Certificate Error**     | The console presented an untrusted TLS certificate. If it uses a self-signed certificate, enable **Allow Self-Signed Certificates** in the connection settings. |
| **Connection Timed Out**  | The console took too long to respond — often network latency or a firewall rule between Dispel and your network.                                                |
| **Configuration Error**   | The URL looks wrong. Re-check the connection settings.                                                                                                          |

## Frequently asked questions

<details>

<summary>Can I connect more than one StellarOne console?</summary>

Yes. TXOne supports multiple integrations, so you can connect several consoles side by side. Give each a distinct **Display Name** to tell them apart.

</details>

<details>

<summary>Why does TXOne show only one site?</summary>

A StellarOne console represents a single environment, so Dispel models it as one site mapped to one Wicket — rather than a list of sites to map individually.

</details>

<details>

<summary>My console uses a self-signed certificate. Will the connection fail?</summary>

Not if you enable **Allow Self-Signed Certificates** in the connection settings. Leave it off when your console presents a certificate from a trusted authority.

</details>

<details>

<summary>Does connecting TXOne change anything in StellarOne?</summary>

No. Dispel only reads from StellarOne. It never creates, modifies, or deletes data on the TXOne side.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery/txone.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.