Techex TxCore Integration Configuration

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Configuration Overview

hi connects to one TxCore instance through a TxCore Core Integration Node. hi reads the MWEdges of that instance, with their Sources and outputs, and uses them for compressed routing. Create one Node for each TxCore instance.

Configuration	What hi Sees	Use When
TxCore Compressed Routing	The MWEdges of the TxCore instance, with their configured Sources and outputs.	hi must route compressed streams through TxCore.

Caution

Each TxCore instance serves the TxCore REST API documentation under /doc/ below its base URL. Confirm API access and account permissions with Techex before commissioning.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and minimum hi version in Required Configuration.
Obtain the TxCore URLs and a TxCore account for hi from the TxCore administrator.
Confirm the network access in Network Requirements.

Configure TxCore Compressed Routing

Device Configuration

Confirm that the TxCore REST API is reachable from the hi server. The REST API exposes all functions of the TxCore administration interface.
Create a TxCore service account with permission to read MWEdges and update their Sources. Confirm the account setup with Techex.
Record the base URL of the TxCore instance, and the URL of each redundant TxCore instance. Confirm that the hi server reaches the primary URL and each redundant URL.
When a URL uses HTTPS, confirm that the hi server trusts its certificate.

hi Configuration

Add the TX Core Core Integration integration (manufacturer TechEx) in Inventory.
Enter the base URL. The field starts with https://; replace it with http:// only when the TxCore instance uses HTTP.
To add failover, select Add Redundant Host and enter the URL of each redundant TxCore instance.
In the Tx Core Login group, enter Login name and Password.
Create the Node and wait for hi to read the MWEdges.
When the Node must reconnect, use Reinitialize or Reset in the Operations group. These operations are available only after the Node is created.

Settings Summary

Setting	Device Side	hi Side
Base URL	URL of the TxCore instance	Base URL
Failover	URL of each redundant TxCore instance	Redundant Host entries
Account	TxCore account with MWEdge permissions	Login name and Password

Common Checks

Symptom	Check
The Node does not connect.	Confirm the base URL, the account, and the network route. For HTTPS, confirm that the hi server trusts the certificate.
An MWEdge, Source, or output is missing.	Confirm that the account can read it in TxCore.

Verify the Configuration

Compare the MWEdges, Sources, and outputs in hi with TxCore. Make a controlled change in TxCore and confirm that polling shows it in hi. Route a test stream from hi and confirm the change in TxCore. When redundant hosts are configured, test failover in a maintenance window.