Complete configuration options for Data Server services.

Technical Reference → UNS Reference → UNS Data Servers Reference


Overview

FrameworX includes built-in services that expose your Unified Namespace (UNS) to external systems. These services run alongside your solution and provide standardized access to live data without additional infrastructure.

ServiceProtocolPurpose
OPC UA ServerOPC UAExpose UNS to enterprise systems and other SCADA platforms
MQTT BrokerMQTTPublish/subscribe access for IoT devices and cloud platforms
MCP for RuntimeMCPEnable AI/LLM models to query live solution data
DataHub ServiceTCPSynchronize data between multiple FrameworX solutions


OPC UA Server Configuration

Location: Unified Namespace → Data Servers → OPC UA Server [??]

SettingDescriptionDefault
PortTCP port for OPC UA connections4840
Security ModeNone, Sign, SignAndEncryptNone
User AuthenticationAnonymous, Username/Password, CertificateAnonymous


→ See OPC UA Server Reference for complete protocol details


MQTT Broker Configuration

Location: Unified Namespace → Data Servers → MQTT Broker [??]

SettingDescriptionDefault
TCP PortStandard MQTT port1883
WebSocket PortWebSocket transport port (0 = disabled)8083
AuthenticationAnonymous, Username/PasswordAnonymous
TLSEnable encrypted connectionsDisabled


→ See MQTT Broker Reference for complete protocol details


MCP for Runtime Configuration

Location: Scripts → Classes (custom tools)

SettingDescriptionDefault
HostListening addresslocalhost
PortMCP server port5000
TransportCommunication protocolstdio


Built-in Tools


ToolDescription
Get ValueRead current tag values from UNS
Get HistorianQuery historical data
Get AlarmsRetrieve alarm status and history

Custom Tools

Custom tools are defined in Script Classes using the [McpTool] attribute:

csharp

[McpTool("GetPanelPower", "Returns power output for specified solar panel")]
public double GetPanelPower(string panelId)
{
    return Tag.SolarPanels[panelId].Power.Value;
}

→ See AI MCP for Runtime Connector for setup details → See AI MCP for Runtime Tutorial for step-by-step guide


DataHub Service Configuration

Location: Unified Namespace → Data Servers → DataHub [??]

SettingDescriptionDefault
Listening PortTCP port for DataHub connections30001
Access KeyAuthentication key for connections(none)
Access ModeRead, Write, or ReadWriteReadWrite


→ See Data Hub Communication Service for architecture details


Startup Options

Services are enabled on the Runtime → Startup page:

ServiceStartup Checkbox
OPC UA Server?? OPCServer
MQTT Broker?? MQTTBroker
MCP for Runtime(Enabled via Scripts)
DataHub Service?? Publish to DataHub


→ See Data Servers How-to for step-by-step enable procedures


Port Summary


ServiceDefault PortProtocol
OPC UA Server4840TCP
MQTT Broker (TCP)1883TCP
MQTT Broker (WebSocket)8083TCP/HTTP
MCP for Runtime5000stdio
DataHub Service30001TCP

Partner APIs

For development partners requiring direct programmatic access:

APIDescription
.NET APINative .NET library for direct solution integration
REST APIHTTP-based access for web and cloud applications


Contact Tatsoft for partner API access and documentation.


See Also

  • Data Servers — Concept overview
  • Data Servers How-to — Enable and configure services
  • TagProvider Services — Connect to external systems (FrameworX as client)