Introduction
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 | |
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 enable users to configure and run solutions with different settings tailored to specific environments or stages of development. The latest release introduces three primary execution profiles: |
Development | This profile is designed for use in live environments, where the solution is fully functional and serves end-users. It optimizes performance and stability while minimizing the system's resource usage. Debugging and development tools are generally disabled or limited in this profile to ensure seamless operation. |
Validation | The development profile is tailored for solution creation, testing, and iteration. It enables a wide range of debugging and diagnostic tools to assist developers in identifying and resolving issues during the development process. While performance might not be fully optimized in this profile, the focus is on providing a robust environment for developers to build and refine their solutions. |
Production | The validation profile is intended for use during the final stages of solution development, such as quality assurance and user acceptance testing. It provides a balance between the development and production profiles, enabling necessary debugging tools while maintaining a level of performance and stability suitable for testing. This profile helps ensure that the solution meets its requirements and performs as expected before being deployed to a production environment. |
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 | |
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 | 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 | |
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 | |
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. |
Configuration and Runtime Process Isolation
In a software development solution, it is essential to maintain stability and prevent interference between various stages and components of the solution. Configuration and runtime process isolation is a technique used to achieve this goal, ensuring that the configuration and development aspects of the solution do not negatively impact the solution's runtime environment.
The configuration process involves setting up parameters, profiles, and other solution settings, which define how the solution should operate. On the other hand, the runtime process focuses on executing the solution and maintaining optimal performance. By isolating these processes, developers can modify configurations and test new features without disrupting the running solution.
This isolation is achieved through several means:
Separate Environments: By using separate environments for development, testing, and production, it is possible to work on solution configurations and features without affecting the runtime environment. Any changes made during development are not reflected in the runtime environment until they are thoroughly tested and deployed.
Containerization: Containerization technologies, such as Docker, allow developers to create isolated containers for different parts of the solution. This approach ensures that modifications made in one container do not impact the runtime environment or other containers.
Version Control: Implementing version control helps manage solution configurations and code changes. This method allows developers to experiment with configurations, roll back to previous versions, and track changes without affecting the runtime environment.
Access Control: By implementing access control mechanisms, it is possible to restrict modifications to the runtime environment and configuration settings. This approach ensures that only authorized personnel can make changes, reducing the risk of accidental disruptions or unauthorized access.
By employing configuration and runtime process isolation, solutions can maintain stability, enhance security, and minimize disruptions during the development and execution phases. This practice allows for continuous improvements, troubleshooting, and adjustments without compromising the solution's overall performance.
Working with the Runtime
Working with the runtime is a key aspect of software development, as it involves managing the execution of a program while it's running. This includes starting and stopping the execution, switching execution profiles, and applying configuration changes. This comprehensive guide provides an overview of best practices and techniques for efficiently working with the runtime.
Starting and Stopping the Solution Execution
To start the solution execution, you need to launch the application or server, depending on the solution type. It's essential to monitor the system for any errors or issues during startup, as they may prevent the application from running correctly.
To stop the solution execution, you can use the appropriate command or interface provided by the runtime environment or the application itself. Make sure to gracefully shut down the application to avoid data loss or corruption.
To start the solution is production mode,
Go to Runtime → Startup
Click the Run Startup button
Applying Configuration Changes
Configuration changes can be applied to the runtime environment to modify the behavior of the application. These changes can include modifying settings, adding or removing modules, or adjusting resource allocation. To apply configuration changes, follow these steps:
Identify the configuration file or settings for your application.
Modify the configuration settings as needed.
Restart the application or reload the configuration to apply the changes, depending on the capabilities of the runtime environment.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|