Differences

This shows you the differences between two versions of the page.

--- runtimesetup [2022/03/24 15:40]
wikiadmin [Final Configuration of the Runtime Installation]
+++ runtimesetup [2023/02/01 10:43] (current)
wikiadmin [Windows]
@@ Line 1: / Line 1: @@
-=====Setting up Runtime Deployments=====
+=====Setting Up and Configuring Runtime Deployments=====
 This article covers the basics of setting up and running MIX on a deployment system. It also covers using MIX in the TransSECS or MIStudio installation for testing purposes.
@@ Line 6: / Line 6: @@
 These instructions are specific to Windows systems but can be used to understand how to set up a MIX runtime on Linux systems.
+=== Copy Files for the Runtime ===
 There is a MIX directory in your development installation. This is normally used for testing your MIStudio or TransSECS/MIStudio MIX target deployments. When it is time to move your deployed code to a final deployment system, follow these steps:
@@ Line 17: / Line 19: @@
 . Transfer the mixruntime to your deployment system. We recommend a simple directory structure, either in Users/Public or to the main harddrive. Never use directory names which contain spaces or non-alphanumeric characters.
-====Final Configuration of the Runtime Installation====
+===Final Configuration of the Runtime Installation===
 MIX is started using the MIX.exe executable in the MIX directory. This executable uses the jre location set up in the MIX.conf configuration file. Following the steps above will set up the deployment so that this configuration is used as-is.
@@ Line 84: / Line 86: @@
 </code>
+See also:
+[[rundevicesdeploymentsasaservice|How to run a TransSECS Devices deployment as a service]]
 ====OPCUA Server Deployments====