Overview

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:

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:


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

  • Switch back to primary

  • Keep secondary active

Replication

  • AlarmHistorian

  • TagHistorian

  • Retentive



Command Lines and URLs

Startup Command line

  • TStartup.exe: It's the executable file responsible for initiating the startup process.

  • /solution: Specifies the path to the solution file that will be run.

  • /profile:2: Defines the profile configuration to be used.

  • /OnlineConfig:true: Indicates whether the online configuration is enabled or not.

  • /wa: Enables the Windows Authenticator.

  • / port1:3301: Specifies the port number used during the startup.

Rich Client command

  • TRichClient.exe: It's the executable file used to start the Rich Client.

  • /port1:3301: Specifies the port number to be used by the Rich Client.

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.




In this section: