Solution Center Overview

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.

On this Page:

• Solution Center Module Overview
• Key Concepts
• What It Does
• Configuration Workflow
• Runtime Behavior
• Feature Highlights

Key Concepts

• Solution File (.dbsln): Encrypted SQL database containing all module configurations in a single file
• Solution List: Central display of available solutions with status indicators and preview images
• Server Connection: Access to local or remote solutions via TWebServices (port 10108)
• Multi-User Collaboration: Concurrent engineering on the same solution by multiple users
• Execution Profiles: Development, Validation, or Production modes with different security levels
• Click-Once Deployment: Browser-based Designer launch without local installation

What It Does

• Creates new solutions from scratch or industry-specific templates
• Manages solution lifecycle including backup, import, export, and version control
• Controls licensing for development, runtime, or combined capabilities
• Launches Designer for configuration and Runtime for execution
• Enables remote solution access via web UI or server connections
• Monitors solution status, resource usage, and active connections

Configuration Workflow

Solution Center Configuration Workflow

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

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

1. 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. 

2. Create or open: New (blank or template), Import/Clone, or open an existing .dbsln (local/remote). 

3. Edit or run: Edit (Designer; supports ClickOnce from web UI) or Run (choose profile). 

4. 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.