The Runtime Startup section of Designer Interface allows you to Start and Stop the execution of the Solution, specific the Execution Profile you want to use, and to customize all settings connections with that execution.
The setting you defined here are also applied when the Startup is executed by the StartSolution command line, or starting the Solution as a Windows Server. This section focus on the various settings you have available and starting and stopping manually, to learn about other methods to start the execution refer to the chapter Deploying the Application.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Runtime Startup Settings
The are various ways to start the execution of a Solution. You can start it manually by going to the Runtime→Startup page. The various other ways to setup its execution are detailed in the chapter Deploying the Application.
When you click on the Start button on the Designer interface, the follow steps are executed:
| Note | ||
|---|---|---|
| ||
Some specific configurations, including Windows Authentication and Windows Service are exclusively available when Windows is selected as the Target Platform for the solution. This Selection of Windows as Target Platform, at Solution Settings, unlocks the specific functionalities and security feature that are inherent and exclusive to Windows operational systems. |
Startup Parameters
Those parameters define which Profile the solution will use, Communication Ports and other settings. It allows to control the starting and stopping of the execution, as well the Online Configuration.
Startup Commands and Options
Startup Commands and Options | |
Run Startup | This command button starts the application. |
Stop | This command button stops the application. |
Online configuration | You can use Enable Online Configuration to apply changes in real-time. All changes must be saved before they can appear on a screen. This is a setting you check to make changes apply immediately. You need to be connected to the running app for it to work. |
Execution Profiles
Execution profiles allow dynamic replacement of database connections or device nodes during solution runtime, enabling smooth transitions between development, validation, and production environments.
Execution Profiles | |
|---|---|
Development | The Development profile provides an environment with debugging and development tools enabled. Developers use this profile during the development and testing phases to test and troubleshoot the solution. |
Production | The production profile optimizes performance and stability for running in the production environment. Based on the selected profile, it automatically applies different database connections or device configurations. |
Startup Port Settings
The startup port settings allow you to define the network ports used by the application, both for internal communication and external access via the web. It is possible to activate automatic port allocation and configure authentication via Windows.
Startup Port Settings | The ports must be enabled and available on the server. |
Main Port | Sets the port that each execution profile uses to access. By default, the Development profile uses the 3301 port, the Validation execution profile uses the 3201 port and the Production execution profile uses the 3101 port. These ports must be enabled and available on the server. |
Auto Ports | The "Auto Ports" option ensures that the software runs even when the specified main ports are unavailable. When this option is enabled, and if the port defined in "Main Port" is unavailable for some reason, the software will automatically search for and select an available port for use. |
WA Port | Defines the port used by software platform for access with Windows Authentication. |
Windows Authentication | Checks if the system can only accept Windows Authentication. |
Web Port | Enables the web port in the solution. By default, the port is set to 80. |
Windows Service | Setup Solution to start as a Windows Service. Current Status: Remove Service and Apply Service. |
Execution Environment
The execution environment allows you to choose between running the application locally or on a solution server. This section also includes settings for the MQTT broker, facilitating communication between IoT devices.
| Execution Environment | |
Local Computer | The Solution is launched locally on the local computer. |
Solution Server | Read-only. Displays the IP address or the name of the computer where the solution is, which is based on the configuration in the Server tab. |
Path/Use Solution Path | Overrides the default execution path, which is the solution file location. Used by the system to allow one station to automatically update the solution in the redundant pair when doing online solution changes and HotStart commands. |
Startup Modules
Startup Modules allow you to define which application components will be active when starting, ensuring that only the necessary modules are loaded, optimizing resources and performance.
Startup Modules | Select which modules will be started up when running the solution. |
Devices | Enables Devices module. |
Alarms | Enables Alarms module. |
Historian | Enables Historian module. |
Datasets | Enables Datasets module. |
Reports | Enables Reports module. |
Scripts | Enables Scripts module. |
Displays | Enables Displays module. |
OPC Server | Enables the OPC Server. |
Redundancy Enabled
Redundancy configurations allow you to define a high availability environment, where a secondary server can take over operations in the event of a primary server failure.
Redundancy Enabled | |
Primary Server IP/Port | Enter the IP address and port of the primary server. |
Secondary Server IP/Port | Enter the IP address and port of the secondary server. |
Timeout | Connection timeout time, in seconds. If reached, this will cause the system to switch to the secondary server. |
On Primary Startup |
|
Replication |
|
Command Lines and URLs
The command lines and launch URLs provide commands and shortcuts necessary to launch the application and access different clients, such as RichClient, SmartClient and HTML5 Client, ensuring flexibility in accessing the application.
Command Lines and URLs | |
Startup Command line |
|
Rich Client command |
|
Smart Client URL | This URL is used to access the Smart Client interface via a web browser, allowing for interaction with the industrial solution using advanced, intelligent features. The IP address and port number define the network location of the service. |
HTML5 Client URL | This URL provides access to the HTML5 Client interface. This allows users to interact with the solution using web technologies and ensures compatibility with modern web browsers. |
NoSplash | When checked, this option suppresses the display of the splash screen during the startup of the application, potentially reducing the startup time. |
WA | When checked, this option enables the Windows Authenticator for added security during the startup and operation of the solution on Windows operating systems. |
SSL | When checked, this option enables Secure Sockets Layer (SSL) for encrypted and secure communication between the client and the server, protecting data integrity and confidentiality. |
ViewOnly | When checked, this option sets the client to a read-only mode, where the user can view but cannot modify the configurations and data. |
| Tip | ||||
|---|---|---|---|---|
| ||||
Click on the |
Accessing HTML5 Clients on Devices Connected to the Same Network
To access HTML5 clients from other devices on the same network, follow these instruction:
Understanding the Localhost Address
The address 127.0.0.1 is the loopback address or "localhost". It refers to the device where the application runs, such as the engineering workstation or the controller computer.
Network Configuration
Assume you have an engineering workstation where your solution runs. This workstation has a specific IP address on the local network, different from 127.0.0.1.
Accessing from Other Devices
Open any browser on the target device (notebook, smartphone).
Enter the IP address of the engineering workstation followed by the port used by the application. The URL format will be http://
<Workstation-IP>:<Port>.
Practical Example
Identifying the Workstation's IP Address:
Assume the engineering workstation's IP address is 192.168.0.8 and the application uses port 3201.
Accessing the Application:
In the browser on the target device (notebook, smartphone), type the following URL: http://192.168.0.8:3201/HTML5.
If SSL is enabled, use https://192.168.0.8:3201/HTML5.
This process will allow you to access the HTML5 application running on the engineering workstation from any device connected to the same local network.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|