Related Topics:
- Solution Center (Reference) - Entry point for Solution Center User Interface
- Managing Solutions (Reference) - Start, Stop, and open diagnostics tools on running solutions.
Solutions Location
Access Modes
The key option is this table is the Access Mode, it will define if the platform will work with files local, or remote.
| Mode | Description | Use Case | License |
|---|---|---|---|
| Local Computer Files | Direct file system access | Single user development | Standard |
| Solution Server | Network access via TWebServices | Multi-user collaboration | Engineering users |
Local Computer Files
Local Search Folders
Directories scanned for solution files (.dbsln and .tproj):
| Operation | Function | Shortcut |
|---|---|---|
| Add Search Path | Include new folder | + button |
| Remove Search Path | Exclude folder | - button |
| Refresh | Rescan folders | F5 |
Folder Properties
Each folder has individual settings:
| Property | Description | Default | Impact |
|---|---|---|---|
| Visible | Show in solution list | Checked | Local display |
| Allow Remote Access | Enable network access | Unchecked | Remote users can view |
If Allow Remote checkbox is unchecked, the solutions in that folder will be accessible my remote Solution Centers tools, neither by the local MCP for Designer tool.
Only a local instance of the Designer.exe will be able to access those solutions
Default Locations
| Folder | Path | Purpose |
|---|---|---|
| User Solutions | Documents\FrameworX\Solutions | Personal projects |
| Shared Solutions | Public\Documents\FrameworX | Team projects |
| Templates | Documents\FrameworX\Templates | Solution templates |
Solution Server Connection
Connection Parameters
| Field | Description | Required | Default |
|---|---|---|---|
| Server | IP address or hostname | Yes | localhost |
| Port | TWebServices port | Yes | 10108 |
| Access Key | Security password | If configured | (none) |
| Timeout | Connection timeout | No | 30 seconds |
Common Addresses
| Address | Description | Use Case |
|---|---|---|
| 127.0.0.1 | Local loopback | Testing |
| localhost | Local machine | Development |
| 192.168.x.x | Local network | Team access |
| hostname.domain | Domain name | Enterprise |
Connection Actions
| Button | Function | Status Indicator |
|---|---|---|
| Connect | Establish connection | Green = Connected |
| Update | Refresh server info | Yellow = Updating |
| Disconnect | Close connection | Gray = Disconnected |
Connected Server Information
Server Details Display
| Information | Description | Example |
|---|---|---|
| Operating System | Server OS version | Windows Server 2022 |
| Server URL | Full connection string | http://192.168.1.100:10108/ |
| Server IP | Network address | 192.168.1.100 |
| Version | FrameworX version | 10.2.0.1234 |
| Platform | .NET version | .NET 8.0 |
Running Services
| Service | Purpose | Default Port | Status |
|---|---|---|---|
| TWebServices | Solution access | 10108 | Required |
| MQTT Broker | MQTT communications | 1883 | Optional |
| HardKey | License service | 10109 | As needed |
| OPC UA Server | OPC UA endpoint | 48030 | Optional |
Service Management
| Action | Function | Requires |
|---|---|---|
| Start Service | Launch service | Admin rights |
| Stop Service | Halt service | Admin rights |
| Install as Windows Service | Auto-start on boot | Admin rights |
| View Logs | Check service logs | Read access |
Local Computer Management
Access Key Configuration
Security for remote connections:
| Field | Description | Requirements |
|---|---|---|
| Set AccessKey | Define password | 8+ characters recommended |
| Verify | Confirm password | Must match |
| Apply | Save settings | Restarts service |
Warning: Pressing Apply with empty fields removes the AccessKey
Security Settings
| Setting | Description | Default |
|---|---|---|
| Require AccessKey | Password for remote access | Disabled |
| Allow Guest Access | Permit anonymous viewing | Disabled |
| SSL/TLS | Encrypted connections | Disabled |
| IP Restrictions | Limit by IP range | None |
SSL/TLS Certificate Configuration
To configure a TLS/SSL certificate for TWebServices, click the SSL button in the Solution Center panel. Settings are saved to TWebServices.json in the machine settings folder on the server.
| Source | Description | Availability |
|---|---|---|
| Certificate File | Load a .pfx or .crt file from the file system | Local and remote |
| Certificate Store | Select a certificate by thumbprint from the Windows local machine store | Local only |
Certificate File mode: Browse for a .pfx or .crt file. For .pfx files, enter the certificate password. When connected to a remote server, the file is uploaded automatically to the Certificates\ subfolder in the server's machine settings directory.
Certificate Store mode: Enter the SHA-1 thumbprint of a certificate already installed in the Windows local machine store. Not available when connected to a remote server.
Validate Certificate: Checks the certificate and displays its subject, expiration date, and issuer. Only available in local mode. Validation is required before saving (unless using Delete).
Delete Certificate: Clears the certificate configuration and disables HTTPS for TWebServices.
Once a certificate is configured, the Solution Center will connect to this server using HTTPS only.
TWebServices Configuration
Service Requirements
| Component | Requirement | Check Method |
|---|---|---|
| Port Available | 10108 not in use | netstat -an |
| Firewall | Port open | Windows Defender |
| Permissions | Read/write access | Folder properties |
| License | Valid runtime | License panel |
Starting TWebServices
Method 1: From Solution Center
- Go to Server Information
- In Connected Server section
- Select WebService in Add Services
- Click Start
Method 2: Manual Start
- Navigate to installation folder
- Run TWebService.exe
- Check system tray icon
- Verify port in tooltip
Method 3: Windows Service
- Open Services (services.msc)
- Find "TWebService-FrameworX"
- Start service
- Set to Automatic
Service Status Indicators
| Indicator | Location | Meaning |
|---|---|---|
| Tray Icon | System tray | Green = Running |
| Services Panel | Windows Services | Status column |
| Task Manager | Processes tab | CPU/Memory usage |
| Server Info | Solution Center | Running Services list |
Multi-User Configuration
Requirements for Collaboration
| Component | Server | Client |
|---|---|---|
| Software | FrameworX installed | FrameworX installed |
| License | Engineering users > 1 | Valid license |
| Service | TWebServices running | Network access |
| Connection | Solution Server mode | Server connection |
Setup Steps
On Server:
- Set Solution Server to http://localhost/
- Configure folders with Allow Remote
- Start TWebServices
- Optional: Set AccessKey
On Client:
- Select Solution Server mode
- Enter server IP:Port
- Enter AccessKey if required
- Connect
Important Notes
- Cannot mix local and remote editing of same solution
- Server must also connect to itself for multi-user
- Each folder has independent remote permissions
Script Compilation in Multi-Engineering Mode
Script compilation runs on the client (Designer) machine when editing a solution remotely via Solution Server. The server receives and executes the compiled output only. If your scripts reference external DLLs, those DLLs must be available on the client machine at build time and on the server machine at runtime. Use path macros and consistent folder placement across both machines to avoid reference errors. See Scripts References Reference for recommended folder structure and available macros.
Web Interface Access
Browser URL Format
http://<server>:10108/solutions
http://<server>:10108/solutions?accesskey=<key>
https://<server>:10108/solutions (if SSL enabled)ClickOnce Support
For Designer launch from browser:
| Browser | Support | Notes |
|---|---|---|
| Edge | Full | Recommended |
| Chrome | With extension | ClickOnce addon |
| Firefox | Limited | Manual launch |
| Safari | No | Use desktop client |
Troubleshooting
Connection Issues
| Problem | Cause | Solution |
|---|---|---|
| Can't connect | Service not running | Start TWebServices |
| Access denied | Wrong AccessKey | Verify password |
| No solutions | Wrong path | Check folder settings |
| Timeout | Network issue | Check firewall/ports |
Service Issues
| Problem | Cause | Solution |
|---|---|---|
| Won't start | Port in use | Change port or stop conflict |
| Crashes | Permission issue | Run as administrator |
| Not in services | Not installed | Install as Windows Service |
File Access Issues
| Problem | Cause | Solution |
|---|---|---|
| Solutions not visible | Not in search path | Add folder |
| Can't save | Read-only | Check permissions |
| Locked files | Open elsewhere | Close other instances |
Log Locations
| Log Type | Path | Content |
|---|---|---|
| TWebServices | Logs\WebService\ | Connection logs |
| Access | Logs\Access\ | Login attempts |
| Errors | TraceLogs\ | Error details |
Best Practices Checklist
Folder Organization
- Separate folders for Dev/Test/Production
- Use descriptive folder names
- Set appropriate visibility per folder
- Regular backup of solution folders
Security
- Always use AccessKey for production
- Limit remote access to specific folders
- Use SSL for sensitive environments
- Regular license audits
Performance
- Limit search paths to active folders
- Regular cleanup of old solutions
- Monitor service resource usage
- Optimize network connectivity
In this section...