Differences

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

--- runtimesetup [2020/10/12 13:05]
wikiadmin [TransSECS Build without Opening the Application]
+++ 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.  You must have a complete, licensed, TransSECS installation and a valid project folder in order to run the headless build.  The project folder must contain the .tsx file and the .xpj.  If other files have been added to the project, to support special functions such as Web Services the may also need to be in folder, but in general, just the .tsx and .xpj are required.
-If you are running TransSECS from the executable, either the Windows TransSECS.exe (TransSECSDevices.exe for the Devices version) or on Linux from the Linux executable, you can edit the TransSECS.conf (or TransSECSDevices.conf) file to enable the headless build.
-First, close all TransSECS applications.
-Copy the TransSECS.exe to TransSECSHeadless.exe and TransSECS.conf to TransSECSHeadless.exe (for Devices, copy the TransSECSDevices.exe and TransSECSDevices.conf - whichever file you have been using to start TransSECS)
-In TransSECSHeadless.conf, look for a line similar to this:
-<file>
-wrapper.java.additional.7=-Dtranssecs.headless=false
-</file>
-and change to:
-<file>
-wrapper.java.additional.7=-Dtranssecs.headless=true
-</file>
-When you double-click the executable, the application will start, compile the last project you had open, and then exit.  You can test this by deleting the deployment folder in the project (everything except the .tsx and .xpj) and use the headless feature to rebuild it.  You should see all the same files, including deployment, documentation, etc. as you would if you had build from within the TransSECS editor.
-If you are running TransSECS from a script or a batch file, you will need to add the system property //"-Dtranssecs.headless=true"// to the start of the java command line:
-<file>
-java -Dtranssecs.headless=true ....
-</file>
-The property name //"transsecs.headless"// is case sensitive, it must be all lower case.
-===Choosing which Project to build===
-When running TransSECS normally, the project loaded is described in the //"application.properties"// file in the TransSECS folder.  This may look something like this:
-<file>
-#Default TransSECS Application Properties 2007-09-14 10:05:27.593
-#Fri Sep 14 10:05:27 MDT 2007
-lastBrowsedDirectory=C:\\Users\\Public\\ErgoTech\\TransSECSDevicesTrial\\Projects
-project.dir=C:\\Users\\Public\\ErgoTech\\TransSECSDevicesTrial\\Projects\\GEMTool
-way_criteria=1
-sort_criteria=3
-</file>
-The same file applies when running a headless TransSECS build, the project listed in the //"project.dir"// line will be the project built.
-When running TransSECS, the configuration property file to read is provided as an argument to the application.  You will see this in the .conf file as the line //wrapper.app.parameter.2=application.properties//
-<file>
-# Application parameters.  Add parameters as needed starting from 1
-wrapper.app.parameter.1=com.ergotech.transsecs.secs.TransSecs
-wrapper.app.parameter.2=application.properties
-</file>
-For this argument, you can provide the full path the a customized application.properties file.  TransSECS will read that file at startup and compile the project described in the file.  For example, if you create a file in the folder //C:\\Users\\MyProjects\\// called //headlessbuild.properties// with this content:
-<file>
-#Default TransSECS Application Properties 2007-09-14 10:05:27.593
-#Fri Sep 14 10:05:27 MDT 2007
-lastBrowsedDirectory=C:\\Users\\Public\\ErgoTech\\TransSECSDevicesTrial\\Projects
-project.dir=C:\\Users\\MyProjects\\GEMTool
-way_criteria=1
-sort_criteria=3
-</file>
-and you change the appropriate line in the.conf file to read:
-<file>
-wrapper.app.parameter.2=C:\\Users\\MyProjects\\headlessbuild.properties
-</file>
-When you start the headless build, the project in C:\\Users\\MyProjects\\GEMTool will be built.
-This property can, again, be added as an argument in a script of batch file.  This time at the end of the command line:
-<file>
-java -Dtranssecs.headless=true .... C:/Users/MyProjects/headlessbuild.properties
-</file>
-===Building only a Selected Tools===
-Some TransSECS projects contain multiple tools.  In this case, it is usual to build all the tools and the headless build will do this.  There may be occasions where only a sub-set of the tools should be built.  This is supported by adding additional tools to the command line.  The name of the configuration properties file must be first - the //wrapper.app.parameter.2// as described above.  The tools must then be added as //wrapper.app.parameter.3//, //wrapper.app.parameter.4// and so on.  The property is just the name of the tool as defined in the TransSECS project.  The tool must already exist in the project.
-<file>
-wrapper.app.parameter.2=C:\\Users\\MyProjects\\headlessbuild.properties
-wrapper.app.parameter.3=GEMTool
-wrapper.app.parameter.4=RFIDReaderTool1
-</file>
 ====OPCUA Server Deployments====
@@ Line 173: / 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