Managing Solutions (Reference): Centralized control for solution execution and diagnostics. Access by selecting a solution in Solution Center and clicking Manage.
Related Topics:
This page provides controls for managing a selected solution, enabling actions such as starting, stopping, editing, or launching diagnostic tools when the solution is active. It comprises four main sections: Solution Information, Actions, Credentials, and Start Tools.
On this page:
Table of Contents maxLevel 2 minLevel 2 indent 10px exclude Steps style none
Children Display | ||||||
---|---|---|---|---|---|---|
|
The Edit button opens the Designer to edit the solution. If security constraints are enabled, you may need to type in the Credentials that will allow you to edit the solution. Or, if the solution allows guest access, you can Start the Designer without credentials, and use the Logon button in the Designer toolbar before editing.
When the Read-Only check-box is set, the Designer will start in View-Only mode, not allowing modifications, independently of the security authorizations. You still may need the security credential to view the contents, if the solution was protected.
The platform supports multi-user and multi-project organization, allowing for the simultaneous editing and running of multiple projects. All modules are integrated into a unified user interface: The Designer, is the comprehensive and user-friendly environment that handles all setup for software modules, execution settings, and testing tools, from tag definition and communications to drawing user interface displays.
→ See Designer (IDE Overview) for the user documentation on solution configuration.
Many solutions can be opened simultaneously by any user, there is no restriction on that.
The same solution can also be opened by many users, allows concurrent distributed engineering. The Evaluation mode license allows for one local and one remote engineering user.
→ See Licensing and Activation (Reference) for more information.
Opening in View mode
If the solution file is locked or another local instance of the solution is open, it will open in Read-Only View mode. In this mode, you can still run or export the configuration but cannot make edits.
You can run a Solution by:
Using the Run button
Starting the execution manually after you open the solution for editing at the Designer tool (Runtime → Startup → Start).
→ For more information, see Runtime (Solution Execution).
When starting the Solution, you can select the Execution Profile that will be used. Execution Profiles allows you to have one solution configuration, that will use distinct connections with Databases, or Network IP to remote devices, according the the environment where that solutions is executed.
The typical environments to run a solution are in Development network, in the Validation system, and of the Production system.
→ See Startup Execution Profiles for more information.
Information | |
---|---|
Info | Description |
Name | Indicates the name assigned to the solution. |
Description | Provides a brief description field for additional details about the solution's purpose or configuration |
Status | Shows the current running profile and port number. |
Path | Displays the file path location of the solution configuration file (.dbsln). |
Note that the platform supports simultaneous multi-user access, enabling concurrent editing and execution across projects within a unified interface.
Users can open multiple solutions concurrently. This capability supports distributed engineering by allowing multiple users to simultaneously work on the same solution. Evaluation licenses permit one local and one remote user for engineering purposes.
Actions | |
---|---|
Action | Description |
Edit (Open Designer) | Opens the Designer tool for editing the solution. If security restrictions are active, credentials may be required to access the editing functions. |
Read-Only | Enables view-only mode in Designer, preventing modifications. |
Open Web Displays | Launches the solution’s displays within a web browser. The SSL checkbox enables secure access |
Open RichClient Displays | Opens displays through the RichClient application, |
Run in Profile | Shows the selected profile under which the solution runs. |
Stop | Stops or shuts down the solution’s execution. |
Credentials are applied solely within this page, with commands on the home page defaulting to guest credentials and a production profile. The username and password entered on this page are reset upon navigation away from it
Credentials | |
---|---|
Field | Description |
Username | Enter the username required to perform actions on this page, if necessary. |
Password | Enter the password associated with the username. |
Field | Description | Example |
---|---|---|
Name | Solution identifier | TankFarmMonitor |
Description | Purpose/notes about solution | Production monitoring system |
Status | Current execution state | Running (Production, Port:3101) |
Path | Full file location | C:\Solutions\TankFarm\TankFarm.dbsln |
Version | Solution version number | 1.2.0 |
Modified | Last save timestamp | 2024-12-15 14:30:00 |
Size | Database file size | 45.2 MB |
Status | Description | Color |
---|---|---|
Stopped | Solution not running | Gray |
Starting | Initialization in progress | Yellow |
Running | Active execution | Green |
Stopping | Shutdown in progress | Orange |
Error | Execution failed | Red |
Action | Function | Requirements | Notes |
---|---|---|---|
Edit (Open Designer) | Launch Designer for configuration | Dev license, credentials | Opens in edit mode |
Read-Only | View configuration without editing | View permissions | Checkbox option |
Run in Profile | Start with selected profile | Runtime license | Dropdown selection |
Stop | Halt running solution | Running state | Graceful shutdown |
Action | Description | Requirements |
---|---|---|
Open Web Displays | Launch browser interface | Runtime active, port 80/443 |
Open RichClient Displays | Launch desktop client | .NET client installed |
SSL | Enable secure connection | SSL certificate configured |
Profile | Purpose | Database | Diagnostics | Security |
---|---|---|---|---|
Development | Testing/debugging | SQLite local | Full trace | Minimal |
Validation | Pre-production test | Test server | Warnings | Standard |
Production | Live operation | Production SQL | Errors only | Full |
Field | Description | Scope | Persistence |
---|---|---|---|
Username | Login identifier | This page only | Session only |
Password | Authentication credential | This page only | Session only |
Important Notes:
Tool | Purpose | Access Requirement |
---|---|---|
Property Watch | Monitor/modify tag values | Runtime active |
Trace Window | View system messages | Always available |
Module Information | Check module status | Runtime active |
Runtime System Monitor | Performance metrics | Runtime active |
Alarms Monitor | Active alarm display | Alarms configured |
Historian Monitor | Trend chart interface | Historian configured |
Real-time monitoring and modification of tags and system properties.
Feature | Description | Use Case |
---|---|---|
Browse Tree | Navigate tag hierarchy | Find specific tags |
Live Values | Real-time updates | Monitor changes |
Write Values | Modify if permitted | Testing/debugging |
IntelliSense | Auto-completion | Quick navigation |
Search | Find tags by name | Large systems |
Type | Read | Write | Examples |
---|---|---|---|
Tags | YES | YES | Process values |
System Properties | YES | NO | Runtime stats |
Device Status | YES | NO | Communication state |
Module Info | YES | NO | Module health |
System message viewer for debugging and monitoring.
Level | Messages Shown | Use Case |
---|---|---|
Error | Errors only | Production |
Warning | Errors + Warnings | Validation |
Info | All except debug | Development |
Debug | Everything | Deep debugging |
Category | Description | Color |
---|---|---|
System | Core runtime messages | Black |
Device | Communication messages | Blue |
Script | Script execution | Green |
Database | SQL operations | Purple |
Error | Error messages | Red |
Detailed status for each runtime module.
Metric | Description | Normal Range |
---|---|---|
State | Running/Stopped/Error | Running |
CPU Usage | Processor utilization | < 50% |
Memory | RAM consumption | < 500 MB |
Thread Count | Active threads | 1-10 |
Start Time | Module launch time | - |
Errors | Error count | 0 |
Module | Function | Critical |
---|---|---|
TServer | Main runtime process | Yes |
Devices | Communication manager | Yes |
Alarms | Alarm processing | No |
Historian | Data logging | No |
Scripts | Script execution | No |
Metric | Description | Alert Threshold |
---|---|---|
CPU | Total processor usage | > 80% |
Memory | RAM utilization | > 90% |
Disk I/O | Read/write operations | > 100 MB/s |
Network | Bandwidth usage | > 80% capacity |
Handles | System handles | > 10,000 |
Counter | Description | Update Rate |
---|---|---|
Tags/Second | Tag update rate | 1 second |
Alarms/Minute | Alarm generation | 1 minute |
DB Writes/Second | Database operations | 1 second |
Client Count | Connected clients | Real-time |
Problem | Cause | Solution |
---|---|---|
Can't edit | File locked | Check who has it open |
Tools disabled | Not running | Start solution first |
No credentials | Guest access | Enter valid username |
Profile missing | Not configured | Setup in Designer |
Stop fails | Hung process | Force stop via Task Manager |
Log Type | Path | Content |
---|---|---|
Runtime | Logs\Runtime\ | Execution errors |
Diagnostics | Logs\Diagnostic\ | Tool outputs |
Security | Logs\Security\ | Access attempts |
Page Tree | ||
---|---|---|
|
The Start Tools feature provides diagnostic tools to access, monitor, and optimize solution performance. These tools are accessible when the selected solution is active, and the Designer is connected to the runtime system.
It allows users to access, read, and write tags and internal system properties. Enables real-time adjustments and optimization of system configurations, helping identify issues through error codes and property values.
→ Read more at Property Watch.
This tool provides insights into module operations and communication channels, displaying information about virtual reading groups, error codes, and events.
→ Read more at Trace Window.
It displays detailed data on module operations and communication status to monitor communication pathways and troubleshoot errors
→ Read more at Module Information.
Shows the status of the server or device running the solution, whether local or remote, providing information about runtime performance and operational health.
→ Read more at Runtime System Monitor.
This tool provides an Alarm Viewer interface, allowing users to track and respond to active alarms and review past alarm records for comprehensive monitoring.
→ Read more at Alarms Monitor.
Enables the tracking of historical data through a Trend Chart interface
→ Read more at Historian Monitor.
In this section: