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 you to manage multiple solutions from a single interface while supporting both local and remote access through desktop and web interfaces.
Key Functions:
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.
What you can do
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).
Key concepts & terms
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.
How it fits in the platform
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.
Interface at a glance
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.
Configuration at a glance
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.
See also
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.
Notes on structure (so we’re consistent across modules)
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.
Link down to Reference and sideways to Designer and Runtime Concept pages to preserve the mental model.