Manage, open, and organize your solutions in a central hub.
How-to → Solution Center | Tutorial | How-to Guide | Reference
This guide walks you through using Solution Center to create, organize, and manage your solutions. Learn to work with local and remote solutions, configure licensing, and launch both Designer and Runtime environments.
Prerequisites:
Table of Contents maxLevel 2 minLevel 2 indent 10px exclude Overview style none
Windows Desktop:
Web Interface:
http://<server>:10108/solutions
http://<server>:10108/solutions?accesskey=<key>
First time running:
Built-in Templates:
Adding Custom Templates:
Toggle between display modes:
View | Description | Best For |
---|---|---|
List | Compact text list | Many solutions |
Cards | Preview thumbnails | Visual selection |
Table | Detailed information | Comparing properties |
Search and Filter:
Folder Organization:
For Editing (Designer):
Read-Only Mode:
Quick Start:
Advanced Start:
From the Manage page:
Action | Description | Use Case |
---|---|---|
Edit | Open in Designer | Configure solution |
Read-Only | View without changes | Review configuration |
Open Web Displays | Browser interface | Test web clients |
Open RichClient | Desktop interface | Test Windows clients |
Stop | Halt execution | Stop running solution |
Server: 192.168.1.100
Port: 10108
AccessKey: (if required)
On Server:
On Client:
Enable concurrent development:
Check current license:
Online Activation:
Offline Activation:
Hardware Key:
Selected solution shows:
Available when solution is running:
Monitor and modify tags:
View system messages:
Check module status:
Cannot see solutions
Cannot connect to server
Solution won't open
Designer won't launch
License not recognized
This guide covered managing solutions through Solution Center, from creation and organization to remote access and diagnostics, providing the central hub for all solution management tasks.
Page Tree | ||
---|---|---|
|
The Solution Center serves as the primary entry point and management hub for all FrameworX solutions. It provides centralized control over solution creation, configuration, licensing, and execution, enabling users to manage multiple solutions from a single interface while supporting both local and remote access through desktop and web interfaces.
Step | Action | Description |
---|---|---|
Connect to Server | Select local or remote | Choose local computer or connect via IP/domain |
Create/Open Solution | New or existing | Start from template or open .dbsln file |
Verify License | Check status | Ensure appropriate development/runtime license |
Launch Designer | Edit or View mode | Configure solution with exclusive or multi-user access |
Configure Profile | Set execution mode | Choose Development, Validation, or Production |
Start Runtime | Execute solution | Run with selected profile and client settings |
Solution Center is the platform’s home screen and launch point. It lets you create, open, license, and launch solutions, and jump into Designer (configure) or Runtime (execute). It can manage local or remote solutions and supports multi-user collaboration.
Create/Open solutions (local or remote) and organize them in the Solution List.
Launch Designer to edit (or read-only) and start Runtime with the chosen profile (Dev/Validation/Production).
Manage licenses (view status, activate) for the connected machine.
Backup / Import / Export / Clone solutions for deployment or recovery.
Access remote servers via TWebServices (web UI at /solutions, supports ClickOnce Designer launch when available).
Upgrade legacy projects (.tProj) to current solutions (.dbsln).
Solution file (.dbsln) — encrypted SQL file that stores the whole configuration (tags, alarms, scripts, displays). Backups use .dbback.
Solution Center / Solutions Manager — UI names you’ll see for the same entry point.
TWebServices — required service for remote access; default port 10108; optional AccessKey in the URL.
Profiles — Development, Validation, Production (affect Runtime behavior).
License types — Development, Runtime, Combined, Trial.
Solution Center is the UI environment for solution management & launch: from here you open solutions, configure (Designer), and execute (Runtime). The Platform UI environment table in the overview places SolutionCenter alongside Designer and Runtime.
Solution List — recent/organized solutions; search, status, views.
Actions Toolbar — New, Open, Edit, Run, Stop, Backup, Import/Export.
Information/Properties — solution details, license status, runtime state.
Connect to a server (optional): enter IP/DNS in Server Information; ensure TWebServices is running. Or open the Web UI at http://<server>:10108/solutions.
Create or open: New (blank or template), Import/Clone, or open an existing .dbsln (local/remote).
Edit or run: Edit (Designer; supports ClickOnce from web UI) or Run (choose profile).
License & properties: check/activate license; review execution and advanced settings.
Designer Workspace (Concept) — where you configure modules and UI.
Runtime & Clients (Concept) — how execution and clients work.
Solution Center (Reference) — screens, buttons, and task details.
Keep Overview to 2–4 sentences.
Use “What you can do” for outcome-oriented bullets (value before UI details).
Keep UI specifics brief in Interface at a glance; deep details live in Reference.