Differences

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

--- runtimesetup [2020/10/12 12:18]
wikiadmin
+++ 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.
+====Making a MIX Runtime Installation=====
+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:
+. Create a mixruntime directory in a convenient location or on a removable usb flash drive on your development system.
+. Copy the whole MIX directory as a subdirectory under this mixruntime.
+. Find the jre in the Windows MIStudioSuite installation directory and copy this as a subdirectory under mixruntime. After this step you will have two subdirectories in mixruntime: MIX and jre.
+. 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===
+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.
+Run the MIX.exe to start MIX. If you have problems starting MIX look in the mix_wrapper.log for information on start-up errors.
-----
 ====Configuring MIX Installations====
@@ Line 63: / Line 86: @@
 </code>
-====TransSECS Build without Opening the Application====
+See also:
+[[rundevicesdeploymentsasaservice|How to run a TransSECS Devices deployment as a service]]
-TransSECS tool files (.tsx and .xpj) are ASCII text XML file.  These can be stored in a source control system such as GIT, Source Safe or similar for tracking and change management.
-The TransSECS "headless" build allows the complete project to be built from the command line without the application opening and without user intervention.  This command line can be used in a script to automatically build the deployment.
-The headless build behaves exactly as if the application had been opened and the "build" button pressed.
 ====OPCUA Server Deployments====
+MIX and ErgoTech's Cloud deployment can include an OPCUA server as part of the deployment.  This allows selected tags within the deployed project to be exported as OPCUA tags.  This happens automatically with the OPCUA version of TransSECS, but requires configuration for both MIX and Cloud deployments.  If you purchased a MIX or Cloud OPCUA solution these details should have been provided as part of that purchase.
-====OPCDA Gateway====
 ====Other Deployments====
-**Modbus Slave**
 **//How To//**
@@ Line 91: / Line 103: @@
 [[Products/WindowsStartup|Start Runtime Automatically]]
 How To start a runtime when Windows starts up
+[[StartWindowsMIXasService|Start MIX as a Service on Windows]]
+[[StartMIXonLinuxAsAService|Start MIX Runtime on Linux as a Service]]
+How to start a runtime (MIX or TransSECS Deployment) on Linux as a Service