Overview
Solutions refer to the applications developed on the software platform. Their purpose is to store all configuration information for your application. The solution saves its configuration in a file with the ".dbsln" extension. It is a database file that stores all configuration items of an application, such as Tags, Alarms, Device configurationsA Solution represents a complete application built using the platform. It stores all configuration data in a .dbsln file, including tags, alarms, device settings, graphical displays, scripts, etcand more.
When you create creating a new Solution, you create solution, the system generates a new .dbsln file , with some basic settings, with initial metadata like name and description. The remaining of the solution configuration is executed performed using the Designer software tool.
On this page:
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Creating a New
SolutionsSolution
To create a new solution, in the Solutions Manager, click the New... button at the top of the solution list to start the New Solution Wizard.
Wizard Step 1 - Product Features
Define the Product Series for your solution by selecting the product family and the product model.
The software platform technology powers four product options:
- Unlimited: Unlimited tags, unlimited users, unlimited communication points, and all platform features.
- FactoryStudio: Scalable models based on the number of communication points, enabling SCADA, MES, Advanced HMI, and a wide range of industrial applications.
- EdgeHMIEdgeMachine: Scalable models based on the number of communication points, with a subset of features typically required for HMI on machines and embedded devices.EdgeGateway
- EdgeConnect: Scalable models based on the number of communication points, with features for data collection in the field, including various protocols, data logging, and scripting.data connections
For details about product families and licensing models, see the Product Series pageYou can select the FrameworX product when creating solutions for unlimited communication points and unlimited users.
| Info | ||
|---|---|---|
| ||
Solution Configuration tools are available free of charge, but a license is required to deploy your solution in a production environment. The Product Family and Model (number of points) selected when creating a new solution should reflect the intended license you plan to acquire for production installation. You still can change those settings after creating the solution, in the Designer tool under Solution Settings. |
Wizard Step 2 - Platform
Define the target platform for your solution by selecting Windows or Multi-platform.
A Target Platform is where you intend to deploy your solution for execution in production. Here are the options, with guidance for selection:
Platform | Description |
|---|---|
Windows | Select if your application requires Windows-only components such as Windows Authentication or third-party libraries like Canary Historian. |
Multi-Platform | Select for Linux or cross-platform environments. This option requires .NET 8 installed on the computer that will execute the solution and on the computer developing the application |
Windows: Use this option if Windows Authentication is required or if Canary Historian or any other product or library that requires Windows will be used on the same computer.
. |
Wizard Step 3 - Solution Name and template
Define the name and review the location for saving your solution file. Then, you can select a solution template and press the Create New Solution button.
If no template was selectedyou don’t select a template, the default HeaderLayout template will be used by default. applied automatically.
| Anchor | ||||
|---|---|---|---|---|
|
Solution templates can greatly accelerate the development process by providing pre-configured settings and modules. They offer a useful starting point for building your application and help you start faster by providing preconfigured components, settings, and modules. These templates can be customized to fit suit your specific application needs. When selecting a template, consider the functionality required and the type of application you are building.
Examples of available templates include web applications, mobile apps, and desktop applications.Pre-built solution templates help you get started quickly by providing the foundational structure for your starter layouts for web-based, desktop, or mobile solutions. Some templates are included with the software installation.You can add, modify, or create additional templates by editing the solution files in the Templates folder, and you can also create or import your own.
Adding New Templates
The templates available when creating a new solution are standard solution files located in the user's Documents folder under Templates.
If you receive To use a new template received from your a vendor or integrator, copy it to that foldersimply copy the .dbsln file into the Templates folder located in your Documents directory. You can also modify customize existing templates in that directory by editing by opening and modifying the solution files in that folder.To create a new template, simply create a solution and save it in the Templates folder within the Documents directory. For example, you might use a path like: Documents\<productName>\Templates
Solution Creator Tool
When you need to create multiple solutions—such as deploying hundreds of edge devices based on configuration files—the platform provides a utility to automate and streamline this process.
For details, see the Solution Creator page.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|
...