Solution Center (Reference)

Key Concepts and Terms

Solution File / Solution Name

The configuration of an application (solution) is saved is a file with extension .dbSln. All modules settings are stored in that file. The solution name matches the name of the configuration file.

Project File

In order to facilitate distinction from legacy product versions, the Project File refers to files with the extension .tProj, a legacy configuration.

Understanding the Solutions Manager

The Solutions Manager interface is the main hub for managing and organizing your solutions.

Some very unique and powerful features include:

• The platform creates a file for each solution. All configurations, including tag definitions, display drawings, images, and report templates, are stored in a single file—an encrypted SQL database with the extension .dbsln — for easy management.

• You can open multiple solutions simultaneously or allow multiple engineers to work on each solution.

• You can access solution files located on your computer or on remote devices with the Platform Services enabled. When accessing remote devices, you can use a pure HTML5 interface without needing any local installation.

• To enable multiple users to work concurrently on the same solution, follow the procedure described in the section Multi-User Collaboration (Reference).

Navigating the User Interface

The User Interface is composed by the following sections:

• The right side contains help-only information; you can close that section if you wish.
• The middle box, called the Solution List, displays a list of solutions on your computer or on a previously set remote computer.
• The left side provides summary information and navigation for additional content. It includes:
  • Server Information (Reference): Select folders, view, and manage connected servers (or local computers).
  • Licensing And Activation: See and modify the license on the connected server (or local computer).
  • Product Information: Displays the current version and list of installed drivers.

Selecting a Solution

The main area in the Solution Manager is where you can select a solution and execute commands on the selected solution or create a new solution.

The middle box, called the Solution List, shows a list of solutions on your computer or on a previously set remote computer. Click "Refresh" to update the solutions list in case external applications or users modify the contents of the folders.

Each item in the solution list represents a complete configuration for an application, with each image corresponding to an independent solution. The image used for the solution preview is the content of the display named "MainPage" in that solution.

In the top right corner, you can select List, Cards, or Table view.

Working with Solutions 

The buttons on the top of Solutions List allow to manage the select solution or create a new one.

New:  go to Creating a New Solution

Edit: Open the Designer software, to configure the selected solution

View: Open the Designer software, in Read-Only mode, which is useful if you simply want to check its configuration.

Run: Starts the execution of the selected solution. It will start in Production mode using guest credentials. For more options on starting, you can use the Manage Button. 

Manage: navigates to the Managing Solutions (Reference) page, allowing to perform various actions with the selected solution. 

Solution Configuration File

The configuration for the entire solution, is stored in single file with the extension .dbsln. That file is an encrypted embedded SQL database, with the configuration tables of the various modules, like Tags, Alarms, Scripts and Displays. 

You can move, rename, duplicate, back up, and restore the solution files, working directly in the computer folders, just as you would with any other file. When moving files directly in the computer folders, you need to press the "Refresh" button to update the list content.

Other files extension for Solutions are created, when using the Publish feature, as described in the chapter Runtime Build and Publish.

Upgrade from Legacy Projects 

When a file with the extension .tProj is found, it appears in the Solution List with the prefix "Project." Only projects from versions 9.1 and 9.2 can be upgraded directly. For older project files, you must first use the 9.1 or 9.2 product to upgrade them to those versions.

When a legacy project is selected, the "Upgrade Version" command button is enabled.

For further details on the Upgrade process to the page Migrating Legacy Projects.

Accessing Solutions Files

By default, the system will display solutions from your local computer first. You can modify the list of visible solutions by going to the Solution Server page. At that page, you can select to show the solution files from the Local Computer for from a Computer running the TWebServices communication service.

When using Collaborative Engineering, allowing other uses to access the same solution, use the Solution Server connection. The Direct Access to the Solution locks the file to a single user.

For Solution Server access: The target server must have the TWebServices running. You can connect using the desktop version of the Solutions Manager, or the Web UI using a URL. 

Requirements

The Solutions Manager can access configuration files from other computers and devices through two methods: connecting to a Remote Server via Server Information or using a URL to open an interface.

Both methods require that the connected server has TWebServices running and that the necessary firewall ports are open. On Windows computers, you can set up TWebServices by opening a local instance of the Solutions Manager on the target server and configuring TWebServices on the Server Information page. For Linux and other operating systems, you need to configure TWebServices to run on startup using the OS's tools. By default, TWebServices uses port 10108.

When multiple users open the same solution from the Server, it allows Multi-User Collaboration on the solution development.

Connecting to a Solution Server 

On the Server Information page, simply enter the IP address or domain name of the server you want to connect to and press the Connect button.

→ Read more about the Server Information page.

Using the Solution Manager Web UI 

It is possible to access solutions on a remote server without installing the product on your local computer.

Just open browser and use the url: http://<Server IP or Name>:10108/solutions. Example: http://192.169.1.1:10108/solutions

The requirements are that the remote device has TWebServices running. If the device has a security AccessKey defined, the URL shall be:

http://<ServerIPorName>:10108/solutions?accesskey=<key>

Using the Designer in Click-Once Mode

When you are using the Solutions Manager WebUI and open a solution for editing, it is not necessary to have the Designer pre-installed on your computer. The system will use ClickOnce technology (if supported by the browser) to open a Designer window, retrieving the necessary files from the remote computer. Most common browsers allow ClickOnce; check the browser's technical information to confirm ClickOnce compatibility.

Solution Center Quick Reference 

Overview

SolutionCenter is your primary entry point for managing FrameworX solutions. It provides centralized control over solution creation, configuration, licensing, and execution. From SolutionCenter, you can create new solutions, open existing ones, manage licenses, and launch both the Designer for configuration and Runtime for execution.

Where It Fits in the Platform

SolutionCenter serves as the hub that connects all FrameworX components:

• Create and Manage - Solutions, templates, and backups
• Configure - Launch Designer to build your solution
• Execute - Start Runtime to run your solution
• Monitor - View solution status and diagnostics
• License - Manage product licensing and features

Main Interface Components

Solution List Panel

The left panel displays all available solutions on your system:

• Recent Solutions - Quick access to recently opened solutions
• Solution Folders - Organized by location or category
• Solution Status - Icons showing if solution is running, stopped, or in design mode
• Search Function - Find solutions by name or description

Solution Actions Toolbar

Primary actions available for solution management:

• New - Create a new solution from scratch or template
• Open - Open existing solution for editing or execution
• Edit - Launch Designer to configure the solution
• Run - Start Runtime with the selected solution
• Stop - Stop running solution
• Backup - Create solution backup
• Import/Export - Transfer solutions between systems

Information Panel

Displays details about the selected solution:

• Solution Properties - Name, version, creation date, last modified
• Product Family - FrameworX edition (Unlimited, Edge, Gateway)
• License Status - Current license type and expiration
• Runtime Status - Running, stopped, or configuration mode
• Resource Usage - Tags used, concurrent users, I/O points

Creating a New Solution

Step 1: Click New Solution

Opens the New Solution wizard with the following options:

• Solution Name - Unique identifier for your solution
• Product Family - Select FrameworX edition
• Template - Start from blank or industry template
• Location - Where to store solution files

Step 2: Configure Initial Settings

• Default User - Administrator account setup
• Database - Embedded or external SQL database
• Execution Profile - Development or Production mode
• Client Settings - Default client type and startup options

Step 3: Confirm and Create

• Review solution settings
• Click Create to generate solution structure
• Solution opens automatically in Designer

Opening Existing Solutions

Local Solutions

• Browse to solution file (.dbsln)
• Double-click or select and click Open
• Solution loads with last saved configuration

Remote Solutions

• Connect to remote server
• Enter server credentials
• Browse available solutions
• Open with appropriate permissions

From Backup

• Click Import Solution
• Select backup file (.dbback)
• Choose restore location
• Verify solution integrity

License Management

Viewing License Status

• Product Edition - Unlimited, Edge, Gateway, or Trial
• License Type - Development, Runtime, or Combined
• Expiration Date - For time-limited licenses
• Feature Limits - Tag count, user count, I/O points

Activating License

1. Click License Management
2. Select Activate License
3. Enter license key or upload license file
4. Verify activation status
5. Restart if required for changes

License Types

• Development - Full Designer access, limited runtime (2 hours)
• Runtime - Production execution, no Designer access
• Combined - Both development and runtime capabilities
• Trial - Full features for evaluation period

Launching Designer

Standard Launch

• Select solution from list
• Click Edit button
• Designer opens with solution loaded
• Automatic backup created (if enabled)

Designer Options

• Read-Only Mode - View configuration without editing
• Exclusive Mode - Lock solution for single user
• Multi-User Mode - Enable collaborative development
• Debug Mode - Additional diagnostic information

Starting Runtime

Runtime Startup Options

• Startup Mode - Normal, Test, or Maintenance
• Execution Profile - Development, Validation, or Production
• Client Launch - Auto-start displays or manual
• Services - Enable/disable specific modules

Runtime Monitoring

• Status Indicators - Green (running), Yellow (starting), Red (error)
• Performance Metrics - CPU, memory, communication status
• Active Users - Current client connections
• Module Status - Individual module health

Solution Properties

General Properties

• Name - Solution identifier
• Description - Purpose and scope
• Version - Current solution version
• Author - Creator information
• Company - Organization details

Execution Settings

• Startup Triggers - Automatic or manual start
• Redundancy - Standalone or hot-standby
• Security - Windows or custom authentication
• Communications - Port assignments

Advanced Settings

• Database Connection - SQL server settings
• Backup Schedule - Automatic backup configuration
• Log Settings - Diagnostic and audit logging
• Performance - Memory and thread pool settings

Best Practices

Solution Organization

• Use descriptive solution names with version numbers
• Maintain separate solutions for development and production
• Regular backup schedule for critical solutions
• Document solution purpose in description field

Development Workflow

• Always backup before major changes
• Use development license for configuration
• Test in validation profile before production
• Keep production runtime separate from development

Performance Optimization

• Close unused solutions to free resources
• Monitor resource usage regularly
• Archive old solutions not in active use
• Optimize database connections

Troubleshooting

Common Tasks

Daily Operations

• Start Runtime for production solutions
• Monitor solution status
• Check license expiration
• Review error logs

Development Tasks

• Create development copy of production solution
• Test changes in validation profile
• Export solution for deployment
• Manage version control

Maintenance Tasks

• Backup critical solutions
• Update license before expiration
• Clear old log files
• Optimize database

Related Topics

• Designer Environment - Configuration interface
• Runtime Execution - Production operation
• Quick Start - First solution tutorial
• Installation Guide - Initial setup

AI Assistant Data

<details> <summary>Structured Information for AI Tools</summary>

json

{
  "module": "SolutionCenter",
  "category": "Platform Architecture",
  "purpose": "Central management hub for FrameworX solutions",
  "keyFeatures": {
    "solutionManagement": ["Create", "Open", "Backup", "Import/Export"],
    "execution": ["Designer Launch", "Runtime Start", "Monitor Status"],
    "licensing": ["View Status", "Activate", "Manage Features"],
    "profiles": ["Development", "Validation", "Production"]
  },
  "commonTasks": [
    "Create new solution",
    "Open existing solution",
    "Launch Designer",
    "Start Runtime",
    "Manage licenses",
    "Backup solutions"
  ],
  "userRoles": ["Administrator", "Developer", "Operator"],
  "relatedModules": ["Designer", "Runtime", "License Manager"],
  "fileTypes": {
    "solution": ".dbsln",
    "backup": ".dbback",
    "license": ".lic"
  }
}

</details>

In this section: