| HTML |
|---|
<style>
.text-span-6 {
background-image: linear-gradient(99deg, rgba(170, 163, 239, .5), rgba(125, 203, 207, .5));
border-radius: 50px;
padding-left: 15px;
padding-right: 15px;
}
#title-text {
display: none;
}
.panelgradient {
background-image: linear-gradient(180deg, #d5def0, whitesmoke);
border-radius: 8px;
flex-direction: column;
justify-content: center;
align-items: center;
padding: 4rem;
display: flex;
position: relative;
}
</style>
<div class ="panelgradient">
<h1 style="text-align: center;">Solutions Manager</h1>
</div> |
Introduction to the Solutions Manager
The platform is designed for creating real-time data applications, structured into solutions. A solution includes configurations for various functional Modulesmodules, such as tag definitions, alarms, communication, and displays.
The Solutions Manager is the central hub for organizing and managing your solutions. It enables you to create, open, and edit solutions from your computer or remote devices, facilitating efficient workflow and productivity.
On this page:
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
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.
| bgColor | #ffffff |
|---|
Project File
In order to facilitate distinction
from legacy product versions, the Project File
refers to files with the extension .tProj, a legacy configuration.
| Anchor | ||||
|---|---|---|---|---|
|
The Solutions Manager interface is the main hub for managing and organizing your Solutionssolutions.
Some very unique and powerful features include:
The platform creates a file for each Solutionsolution. All configurationconfigurations, including tag definitiondefinitions, displays drawingdisplay drawings, images, and report templates is , are stored in a single file — an file—an encrypted SQL database with the extension
.dbsln— for easy management.You can open multiple Solutions at the same time solutions simultaneously or allow multiple engineers to work on each Solutionsolution.
You can access
Solutionsolution files located
inon your computer
,or on remote devices with the Platform Services enabled.
When accessing remote devices, you can
fromuse a pure HTML5 interface
,without
theneeding
ofany
locationlocal installation.
To enable multiple users to work concurrently on the same solution, follow the procedure described in the section Multi-User Collaboration.
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:
- 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
onin 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 is , called the Solution List and , shows a list of solutions solutions on your computer or on a previously set remote computer set previously. Click "Refresh" to update the solutions list is in case external applications or uses users modify the contents of the folders.
Each item in the solution list is represents a complete configuration for an application, each image is with each image corresponding to an independent solutionsolution. The image used for the solution preview is the contents content of the display named "MainPage" in that solution.
On In the top right corner, you can select List, Cards, or Table view.
List View
Card View
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 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, backup and restore the Solution solution files, working directly on in the computer folders, just as you 'd do would with any other file. When moving files directly on 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.
| Warning | ||
|---|---|---|
| ||
Be extreme extremely careful when renaming solution files (or solution Namesnames). There are macros and properties with the solution Nema name that may have been used to create Database database files, configuration files, or any other application-specific implementationimplementations. When renaming a Solution solution that is already in production, it is necessary to address any specific configuration, configurations or external connections , that might have been created using that specific name. If you want to Delete a Solution, you just need to Delete the <solutionName>.dbsln file that count as the solution. The folder named <solutionName>-Designer contains users settings and temporary files and it can be deleted anytime. When the solution runs, it may create databases files, text files, that are application-specific implementation, and those files should be traced and deleted, similarly when you are renaming solutions. |
Upgrade from Legacy Projects
When a file with the extension .tProj is found, it shows on 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 the "Upgrade Version" command button is enabled.
| Info | ||
|---|---|---|
| ||
In order to Edit a legacy Projectproject, you need to use the tools for the specific version of that Project. The Solutions Manager will only handle upgrades for that project to the current Solution solution features. |
For further details on the Upgrade process to to the page Migrating Legacy Projects.
Access Solutions on Remote Computers
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 Remote Computer.
For Remote Computers: If the remote computer has the Web Server enabled and you are using a Windows computer, you can view the solutions on the remote computer via the URL.
Select the Desired Solution: You can use the search box or modify the visualization options to find and select the solution you need.
Requirements
The Solutions Manager can access configuration files from other Computer and Devices. There are two ways to accomplish that, computers and devices through two methods: connecting to a Remote Server via Server at Server Information , or using a url URL to open an open UIinterface.
Both methods require that that the connected server has the TWebServices running on the remote computer, and that the necessary firewall ports are open. In On Windows computercomputers, you can setup the TWebServices to run, set up TWebServices by opening a local instance of the Solutions Manager at on the target server , and setup the configuring TWebServices in on the ServerInformation Server Information page. For Linux and other operating systemsystems, you need to setup the configure TWebServices to run on power-up startup using the OS's tools of the OS. The TWebServices by default. 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 Remote Solution Server
At On the page Server Information page, just put simply enter the IP , address or computer 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 the Solutions solutions on a remote server , without even installing the product in on your local computer.
Just open browser and use the url: httphttp://<Server IP or Name>:10108/solutions. Example: http://192.169.1.1:10108/solutions
The requirements are that the remote device has the TWebServices running, . If the device has an 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 you open a Solution solution for editing, its it is not necessary to have the Designer pre-installed in on your computer, the . The system will use the click-once ClickOnce technology (if supported by the browser supports it) and to open a Designer window, getting retrieving the necessary files from the remote computer. Most common browser allow click-once, browsers allow ClickOnce; check the compliance on the browser's technical information , querying for Click-Once compatibility.
Reference Information
Executables Installation Folder
Using the Microsoft App standard, the MSIX installer creates a folder under \Program Files\WindowsApps\ for the product. That folder shouldn't not be accessed directly by the users, and the installation should be added or removed, using the Windows Add/Remove apps utility.
In order to comply with same FactoryFloor or DataCenter requirements, it's also to install the product using the traditional setup.exe, which give further control on the installation folder. Read about custom installation at Deployment ? Managing Installations.
Documents Product Folders
The first time the product is executed in the computer, it automatically various Folders under MyDocuments special folder, using the product name and the initial node for the folders.
to confirm ClickOnce compatibility.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|
...