...
The platform independent build "portable" requires the previous prior installation of .NET 6 incl. ASP.NET Core. The current version is provided by Microsoft at the following link:
...
We recommend using the "Hosting Bundle" provided by Microsoft, as this contains all the required components.
The advantage of When using the platform-independent version is that you can install , updates for the .NET Framework can be installed independently of the Connect software. In the event of security-critical errors in the Microsoft .NET Framework, they you can thus react immediately and do not have without having to wait for the delivery of an update of the Connect Server. In addition, the identical installation files can be used for all supported operating systems.
...
The Connect Server is delivered with a ready-to-run configuration. The integrated web server is available listens on port 80 after startup and responds to HTTP requests. For more information about customizing the configuration, please refer to chapter Konfiguration Configuration (Connect 2022).
Starting the Connect Server (as a console application)
The Connect Server can be operated directly started as a console application. This scenario is recommended for test scenarios and possibly for smaller small proof of concept projects. Note that in this scenario, the Connect Server is terminated by closing the console as well as by the user logging off terminates the Connect Server. Disconnecting a remote desktop connection (without logging off) does not affect the running Connect Server.
To start the Connect Server as a console application, change set the current directory to the folder with directory containing the Connect Server and start the executable file named "GalileoGroup.Connect.Server.exe". Alternatively, you can start the Connect Server via Windows Explorer by double-clicking on the file "GalileoGroup.Connect.Server.exe".
...
Activate the console window with the Connect Server and terminate the Connect Server by pressing the key combination Ctrl + C. Closing the console window directly is not recommended, as this cannot ensure that all running may result in communication processes are not being terminated properly.
Operation as Windows service
In Windows-based production environments, it is recommended to operate the Connect Server as a Windows service. In this scenario, log output is written to the Windows event log. The one-time setup is described below:
...
After The user has been successfully created, it must be assigned the authorization to log in as a Windows service. Press Win + R keys and , type "secpol.msc" in the following input windowinto the dialog windows and press enter. Now a window will be displayed with a tree structure on the left side. There, open Open the "Local Policies" node and then click on the "Assign User Rights Assignment" node. In the right half of the screen, select the "Log on as a service" entry via double-click.
In the following dialog window, click the "Add user or group" button and select the newly created local user. If the user is not found, restrict the search path to the local computer name.
Now the new user must be allowed access to needs the authorization to access the folder where the application was installed. In this example, the folder "C:\Program Files\Galileo Group\Connect\server" is used. To do this, enter the following commands in a PowerShell with administrator privileges:
...
The registration can also be accomplished with the help of PowerShellusing a PowerShell with administrator privileges. Here is an example which can be used as a template:
...
Deregistering the Windows service
If To remove the Windows service is to be removed again, this can be done with the , enter following command in a PowerShell with administrator privileges:
| Code Block | ||
|---|---|---|
| ||
$ServiceName = "Connect Server" cmd /c csc delete $ServiceName |
If you are using PowerShell 7 is already in use on the corresponding system, deregistration , this task can also be performed accomplished using the Remove-Service cmdlet.