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:
- Platform installed and licensed
- Understanding of solution concepts
- Network access for remote connections
Accessing Solution Center
Starting Solution Center
Windows Desktop:
- Start Menu → Program Group → Solution Center
- Or double-click desktop shortcut
- Or run from installation folder
Web Interface:
http://<server>:10108/solutions
http://<server>:10108/solutions?accesskey=<key>
Initial Setup
First time running:
- Solution Center opens with local computer selected
- Default folders scanned for solutions
- License status displayed
- Recent solutions list empty
Creating Solutions
New Solution Wizard
- Click New button in toolbar
- Step 1 - Product Features:
- Select Product Family (FrameworX, FactoryStudio, Edge)
- Choose Model (tag/point limits)
- These match your intended license
- Step 2 - Platform:
- Windows: For Windows-only features
- Multi-Platform: For Linux/.NET 8
- Step 3 - Name and Template:
- Enter solution name
- Select template (optional)
- Review save location
- Click Create New Solution
Using Templates
Built-in Templates:
- HeaderLayout (default)
- Industry-specific templates
- Starter projects
Adding Custom Templates:
- Copy .dbsln file to Documents\Templates
- Template appears in wizard
- Modify existing templates as needed
Managing Solution List
Solution Views
Toggle between display modes:
View | Description | Best For |
---|---|---|
List | Compact text list | Many solutions |
Cards | Preview thumbnails | Visual selection |
Table | Detailed information | Comparing properties |
Organizing Solutions
Search and Filter:
- Type in search box to filter
- Search by name or description
- Clear to show all
Folder Organization:
- Go to Server Information
- Click Add Search Path
- Select folders to scan
- Set visibility options
Working with Solutions
Opening Solutions
For Editing (Designer):
- Select solution from list
- Click Edit button
- Or double-click solution
- Designer launches
Read-Only Mode:
- Select solution
- Click View button
- Designer opens without edit rights
Running Solutions
Quick Start:
- Select solution
- Click Run button
- Runs in Production mode
- Uses guest credentials
Advanced Start:
- Click Manage button
- Select execution profile
- Enter credentials if needed
- Click Run in Profile
Solution Actions
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 |
Connecting to Remote Servers
Server Configuration
- Go to Server Information
- Select Solution Server
- Enter connection details:
Server: 192.168.1.100 Port: 10108 AccessKey: (if required)
- Click Connect
Requirements for Remote Access
On Server:
- TWebServices running
- Port 10108 open in firewall
- AccessKey configured (optional)
On Client:
- Network connectivity
- Valid credentials
- Appropriate license
Multi-User Collaboration
Enable concurrent development:
- On server, go to Server Information
- Select folders for sharing
- Check Allow Remote
- Check Visible
- Multiple users can now edit
License Management
Viewing License Status
Check current license:
- Product Family and Model
- License Type (Dev/Runtime)
- Expiration date
- Feature limits
Activating Licenses
Online Activation:
- Click Online Activation
- Enter Serial Number
- Enter Activation Code
- Click Activate
Offline Activation:
- Click Get Site Code
- Save file
- Send to vendor
- Receive license file
- Click Load License Key
Hardware Key:
- Insert USB dongle
- License auto-detected
- No activation needed
Solution Properties
Viewing Solution Info
Selected solution shows:
- Name: Solution identifier
- Description: Purpose/notes
- Status: Running/Stopped
- Path: File location
- Version: Solution version
- Modified: Last change date
Diagnostic Tools
Available when solution is running:
Property Watch
Monitor and modify tags:
- Click Property Watch
- Browse tag tree
- View real-time values
- Modify if permitted
Trace Window
View system messages:
- Click Trace Window
- Select modules to monitor
- Set filter levels
- Watch events in real-time
Module Information
Check module status:
- Click Module Information
- View module states
- Check communication
- Monitor performance
Best Practices
Solution Organization
? Use descriptive names with version numbers ? Separate folders for Dev/Test/Production ? Regular backups before major changes ? Document in description field
Remote Access
? Set AccessKey for security ? Use specific folders for remote access ? Monitor connections in Server Information ? Close unused remote sessions
License Management
? Monitor expiration dates ? Keep backup of license files ? Document activation codes ? Plan renewals in advance
Troubleshooting
Cannot see solutions
- Check folder paths in Server Information
- Click Refresh to rescan
- Verify .dbsln files exist
- Check folder permissions
Cannot connect to server
- Verify TWebServices running
- Check firewall port 10108
- Test network connectivity
- Verify AccessKey if set
Solution won't open
- Check file not corrupted
- Verify appropriate license
- Close if open elsewhere
- Check user permissions
Designer won't launch
- Verify development license
- Check .NET installation
- Clear temp files
- Restart Solution Center
License not recognized
- Verify USB dongle connected
- Check license expiration
- Confirm correct product family
- Restart Solution Center
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
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
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 |
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
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.
.