Web Server Configuration Reference

Set up and customize the integrated web server.

Reference → Installation → Folders | Licensing | Updates | SecureGateway | Web Server 

HTML5 Web Client — Built-in HTTP Server

The HTML5 Web client does not require IIS, TWebServices, or any external web server. TServer includes a built-in HTTP server that serves displays to browsers automatically.

When TServer starts, it opens an HTTP port based on the active Execution Profile:

The Web client is accessed from a browser at:

http://<server-address>:<port>/html5/

Both the client application files and the real-time communication (tag values, alarms, events) are served through this same port.

Requirements for Production

• TServer running with the correct Execution Profile
• The corresponding port open in the firewall for client access
• A modern browser with WebAssembly support (Chrome, Edge, Firefox)

TWebServices (Built-in)

TWebServices is a separate service used for Solution Center access and remote engineering. It is not responsible for serving HTML5 Web clients at runtime.

Default port: 10108   |   Access URL: http://<ServerIP>:10108/solutions

When Required

TWebServices enables:

• Solution Center WebUI access
• Remote access to solution configurations
• Remote engineering

Setup Process

1. Open FrameworX -> Server Information.
2. Click Add Services.
3. Select WebServices and click OK.
4. Accept the Windows security elevation prompt, if displayed.
5. The service will be installed and run as a Windows Service.

Port Configuration

By default, TWebServices uses port 10108. If port 10108 is already in use, the port can be changed in the machine settings file below.

C:\Users\Public\Documents\FrameworX\MachineSettings\TWebServices.json

Important: add or update the portnumber parameter inside the appSettings section of TWebServices.json.

Example TWebServices.json

{
  "appSettings": {
    "portNumber": "10109"
  }
}

After changing the port, restart the TWebServices Windows Service for the new configuration to take effect.

Check Whether a Port Is in Use

netstat -aon

tasklist

Access After Restart

After the service is restarted, access Solution Center using the configured port.

http://<ServerIP>:<portnumber>/solutions
Example: http://192.168.0.10:10109/solutions

Auto-Start Solutions

Auto-start is configured per solution through the Solution Center UI. Select the solution and enable the AutoStart option. The setting is stored internally and applied when TWebServices starts.

Linux Deployment

1. Copy from Windows: FrameworX/net8.0/
2. To Linux: /home/FrameworX/
3. Run TWebServices executable
4. Configure auto-start in systemd or Docker

Microsoft IIS Configuration

Alternative deployment option for enterprise environments that already use IIS infrastructure.

When to Use IIS

• Running the runtime behind an existing IIS infrastructure
• Enterprise security requirements (SSL termination, Windows Auth)
• Integration with other IIS-hosted services
• Advanced authentication scenarios

Prerequisites

IIS 7.x — Run as Administrator from C:\Windows\Microsoft.NET\Framework64\v4.0.30319:

aspnet_regiis -i -enable
ServiceModelReg.exe -r

IIS 8.0+ — Enable in Windows Features:

• ASP.NET 4.5+: IIS → World Wide Web Services → Application Development
• HTTP Activation: .NET Framework Advanced Services → WCF Activation
• Dynamic Compression: Web Server → Performance Features

Service Installation

TProjectServer (Remote Configuration)

• Alias: TProjectServer
• Physical Path: C:\Program Files\Tatsoft\FrameworX
• Application Pool: ASP.NET v4.0
• Permissions: Everyone (Read), IIS_IUSRS (Read/Write)
• Test: http://localhost/tprojectserver/service.svc

TWebClient / TSmartClient

• Alias: fx10
• Physical Path: Installation folder
• Application Pool: ASP.NET v4.0
• Anonymous Authentication: Enabled
• MIME Type: .xbap → application/x-ms-xbap
• Test: http://localhost/fx10/service.svc

Dynamic Compression

Server → Configuration Editor → system.webServer/httpCompression → add application/json to Dynamic Types → restart IIS.

SSL/HTTPS Configuration

1. Server Certificates → Create Self-Signed Certificate → enter name → mark for Server Authentication
2. Site → Bindings → Add → https / port 443 → select certificate
3. Update Web.config:

<security mode="Transport">
<transport clientCredentialType="None"/>
</security>

1. For HTML5 clients with HTTPS: TStartup.exe /project:MyProject /html5port:443

Troubleshooting IIS

SolutionCenter API

TWebServices on port 10108 also hosts the SolutionCenter API, a JWT-authenticated REST surface for managing the FrameworX installation remotely — list, run, and stop solutions; transfer files; activate licenses; read and write machine settings; inspect runtime connections. Activation-gated, default-OFF in 10.1.5 GA.

Full endpoint reference: SolutionCenter API Reference.

In this section...