Complete configuration options for Data Server services.
Technical Reference → UNS Reference → UNS Data Servers
Expose the Unified Namespace to external clients, AI systems, and other FrameworX solutions.
Modules → Data Foundation → Data Services | Reference
OPC UA Server
Expose your UNS to external OPC UA clients using industry-standard protocols.
Capabilities
- Browse and subscribe to any tag in the UNS
- Read/write access with configurable security
- Historical data access (if Historian configured)
- Alarm and event subscriptions
Configuration
Configuration
Location: Unified Namespace → Data Servers → OPC UA Server [??]Navigate to Unified Namespace → TagProvider Services and click the OPC UA Server icon.
| Setting | Description | Default |
|---|---|---|
| Port |
| TCP port for OPC UA connections | 4840 | |
| Security Mode | None, Sign, SignAndEncrypt | None |
| User Authentication | Anonymous, Username/Password, Certificate | Anonymous |
→ See OPC UA Server Reference for complete configurationprotocol details
MQTT Broker
Built-in MQTT broker for publish/subscribe messaging without external infrastructure.
Capabilities
- Full MQTT 3.1.1 and MQTT 5.0 support
- Sparkplug B compatibility
- Topic-to-tag mapping
- QoS 0, 1, and 2 support
- WebSocket transport option
Configuration
Configuration
Location: Unified Namespace → Data Servers → MQTT Broker [??]Navigate to Unified Namespace → TagProvider Services and click the MQTT Broker icon.
| Setting | Description | Default |
|---|---|---|
| TCP Port |
| Standard MQTT port | 1883 |
| WebSocket Port |
| WebSocket transport port (0 = disabled) | 8083 | |
| Authentication | Anonymous, Username/Password | Anonymous |
| TLS |
| Enable encrypted connections | Disabled |
→ See MQTT Broker Reference for complete configurationprotocol details
MCP for Runtime
Enable AI language models to query live solution data through Model Context Protocol.
Capabilities
- Query tag values from the UNS
- Retrieve alarm status and history
- Access historian data for trend analysis
- Extend with custom tools via Script Classes
How It Works
AI Model (Claude) ←→ MCP Protocol ←→ TMCPServerStdio.exe ←→ TServer.exe
↓
[Live UNS Data Access]Configuration
Location: Scripts → Classes (custom tools)
| Setting | Description | Default |
|---|---|---|
| Host | Listening address | localhost |
| Port | MCP server port | 5000 |
| Transport | Communication protocol | stdio |
Built-in Tools
| Tool | Description |
|---|---|
| Get Value | Read current tag values from UNS |
| Get Historian | Query historical data |
| Get Alarms | Retrieve alarm status and history |
Custom Tools
Create solution-specific tools using Script Classes. AI models can invoke any method you expose.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
Distributed data aggregation for multi-solution architectures. Enables multiple FrameworX solutions to share and access tag, device, server, and alarm namespaces.
Capabilities
- Multi-solution data synchronization
- Centralized UI solution consuming data from multiple edge solutions
- Shared alarm management across solutions
- Scalable distributed architecture
Architecture
| No Format |
|---|
+-------------+ +-------------+ +-------------+
| EDGE 1 | | EDGE 2 | | EDGE 3 |
| (Publish) | | (Publish) | | (Publish) |
+-------------+ +-------------+ +-------------+
| |
+--------------------------------------+
|
|
+------------------+
| UI Solution |
| (DataHub Service |
| Port 30001) |
+------------------+ |
Configuration
Location: Unified Namespace → Data Servers → DataHub [??]
Configuration
| Setting | Description | Default |
|---|---|---|
| Listening Port | TCP port for DataHub connections |
| 30001 | ||
| Access Key | Authentication key for connections | (none) |
| Access Mode | Read, Write, or ReadWrite | ReadWrite |
→ See Data Hub Communication Service for complete configuration
Enabling Services at Runtime
architecture details
Startup Options
Services Built-in services are enabled on the Runtime → Startup page:
| Service | Startup |
|---|
| 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
| Service | Default Port | Protocol |
|---|---|---|
| OPC UA Server | 4840 | TCP |
| MQTT Broker (TCP) | 1883 | TCP |
| MQTT Broker (WebSocket) | 8083 | TCP/HTTP |
| MCP for Runtime | 5000 | stdio |
| DataHub Service | 30001 |
| TCP |
Partner APIs
For development partners requiring direct programmatic access, additional APIs are available:
| API | Description |
|---|---|
| .NET API | Native .NET library for direct solution integration |
| REST API | HTTP-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)
- TagProvider Services — Configure built-in services
- AI MCP for Runtime Connector — AI integration details
- Data Hub Communication Service — Multi-solution architecture Data Foundation — UNS overview