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:
- Create and manage solutions (.dbsln files)
- Launch Designer for configuration
- Start Runtime for execution
- Manage licensing and server connections
- Enable multi-user collaboration
Key Concepts
| Term | Description | Details |
|---|---|---|
| Solution File (.dbsln) | Encrypted SQL database containing all configurations | Single file contains tags, displays, scripts, all modules |
| Solution List | Central display of available solutions | Shows status, preview images, organization folders |
| Server Connection | Access to local or remote solutions | Via TWebServices (port 10108) |
| Execution Profiles | Runtime modes with different security levels | Development, Validation, or Production |
| Multi-User Access | Concurrent engineering capability | Multiple users can work on same solution |
| Click-Once Deployment | Browser-based Designer launch | No local installation required |
What Solution Center Does
| Solution Management | Solution Execution | System Administration |
|---|---|---|
Create new solutions Open existing solutions Upgrade legacy projects | List running solution Run solutions Run diagnostics tools | License management Service configuration Remote access setup |
Typical Workflow
| Step | Action | Description | Options |
|---|---|---|---|
| 1. Connect | Select server | Choose local or remote server | Local, IP address, domain name |
| 2. Create/Open | Solution selection | New solution or open existing | Blank, template, import, .dbsln file |
| 3. Verify License | Check status | Ensure appropriate license | Development, Runtime, Combined |
| 4. Configure | Launch Designer | Edit solution configuration | Exclusive or multi-user mode |
| 5. Select Profile | Set execution mode | Choose runtime behavior | Development, Validation, Production |
| 6. Execute | Start Runtime | Run the solution | With selected profile and clients |
Feature Highlights
Solution Organization
- Single-file architecture - All configurations in one .dbsln file
- Preview images - MainPage display shown as thumbnail
- Multiple views - List, Card, or Table display options
- Search and filter - Quick solution location
- Folder organization - Logical grouping of solutions
Collaboration Features
- Multi-user support - Concurrent engineering on same solution
- Server-based access - Centralized solution repository
- Access control - Security keys for remote connections
- Version management - Built-in backup and restore
- Legacy migration - Upgrade path from .tProj files (v9.1+)
License Management
- Unified licensing - Single point for all operations
- License types - Development, Runtime, Combined, Trial
- Feature visibility - Tag count, user limits, I/O points
- Remote activation - Online and offline activation
- Expiration monitoring - Proactive renewal alerts
Deployment Flexibility
- Click-Once technology - Zero-installation Designer access
- Cross-platform - Windows desktop and web browser
- Remote management - Full functionality over network
- Template library - Industry-specific starting points
- Automated startup - Solution auto-launch configuration
How It Fits in the Solution Lifecycle
Solution Center is the first touchpoint in the Solution Lifecycle:
It serves as both the starting point for new solutions and the ongoing management hub throughout the solution's lifecycle. |
Next Steps
Continue Learning
- [Designer (Concept) →] - Understand the configuration workspace
- [Runtime (Concept) →] - Learn about solution execution
- [The Four Pillars →] - Begin building your solution
Practical Guides
- [Solution Center How-to Guide] - Step-by-step instructions
- [Creating Your First Solution] - Quick start tutorial
- [Remote Access Setup] - Configure server connections
In this section...
Feature Highlights
Solution Organization
- Single-file architecture: All configurations in one .dbsln file
- Preview images: MainPage display shown as solution thumbnail
- Multiple views: List, Card, or Table display options
- Search and filter: Quick solution location by name or description
- Folder organization: Logical grouping of related solutions
Collaboration Features
- Multi-user support: Concurrent engineering on same solution
- Server-based access: Centralized solution repository
- Access control: Security keys for remote connections
- Version management: Built-in backup and restore capabilities
- Legacy migration: Upgrade path from .tProj files (v9.1+)
License Management
- Unified licensing: Single point for all license operations
- License types: Development, Runtime, Combined, Trial
- Feature visibility: Tag count, user limits, I/O points
- Remote activation: Online and offline license activation
- Expiration monitoring: Proactive license renewal alerts
Deployment Flexibility
- Click-Once technology: Zero-installation Designer access
- Cross-platform: Windows desktop and web browser support
- Remote management: Full functionality over network
- Backup/restore: Solution portability between systems
- Template library: Industry-specific starting points
Operational Control
- Execution profiles: Separate development and production modes
- Resource monitoring: CPU, memory, and connection tracking
- Service management: Individual module enable/disable
- Diagnostic access: Integrated log viewing and troubleshooting
- Automated startup: Solution auto-launch configuration
Solution Center Overview (Editor note: text for Consolidation)
Overview
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.