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

On Linux, install with the TWebServices bootstrap, then use Install Product in Solution Center. The Linux/Edge checklist in the Deployment Reference has the steps.

Do not copy or unzip a Windows installation onto Linux. The Linux folder layout is different.

Microsoft IIS

FrameworX 10 does not run in IIS. TServer serves the HTML5 client and its real-time connection on its own port (see HTML5 Web Client above), and TWebServices serves Solution Center and remote engineering on port 10108. No IIS role, WCF Activation or IIS application alias is needed.

The IIS steps of earlier versions do not apply to FrameworX 10, because the files they rely on are no longer installed. Those steps were the TProjectServer and fx10 aliases with their service.svc files, WCF Activation, and XBAP browser clients.

The one IIS-hosted file the product still installs is the WITSML connector's service, T.Witsml.Service.svc; see the WITSML connector documentation.

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. The API ships activation-gated off and cannot be enabled in the 10.1.5 line; it is planned to become available in a future FrameworX release, once security hardening work scheduled for a future release completes.

Full endpoint reference: SolutionCenter API Reference.

In this section...