Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
runtimesetup [2020/05/12 19:41] wikiadmin created |
runtimesetup [2023/02/01 10:43] (current) wikiadmin [Windows] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | Setting | + | =====Setting |
- | ---- | + | 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. |
- | **Configuring MIX Installations** | + | ====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/ | ||
+ | |||
+ | 1. Create a mixruntime directory in a convenient location or on a removable usb flash drive on your development system. | ||
+ | |||
+ | 2. Copy the whole MIX directory as a subdirectory under this mixruntime. | ||
+ | |||
+ | 3. 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. | ||
+ | |||
+ | 4. Transfer the mixruntime to your deployment system. We recommend a simple directory structure, either in Users/ | ||
+ | |||
+ | ===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==== | ||
When MIX is running, go to your MIX IP Address (e.g. 192.168.1.xx) and run setup.html, http:// | When MIX is running, go to your MIX IP Address (e.g. 192.168.1.xx) and run setup.html, http:// | ||
Line 16: | Line 39: | ||
Check License Status -- check the MIX Project Deployment License status and the MIX Runtime License status | Check License Status -- check the MIX Project Deployment License status and the MIX Runtime License status | ||
+ | |||
+ | {{: | ||
**Licensing the Project** | **Licensing the Project** | ||
Line 25: | Line 50: | ||
MIX is the 24/7 deployment platform for MIStudio projects and needs to be licensed for each system it runs on. This license is the MIX Runtime license (ErgoIOTLicense.lic). | MIX is the 24/7 deployment platform for MIStudio projects and needs to be licensed for each system it runs on. This license is the MIX Runtime license (ErgoIOTLicense.lic). | ||
- | To prepare to license MIX for your runtime platform, use the "Get Pre-License Key" option on the ErgoTechIOT Management Utilities page. You need to have MIX running, even if not licensed to access this configuration utility. When you click on "Get Pre-License Key" a key will be generated which needs to be sent (emailed) to your distributor who will return a license file for this system. | + | To prepare to license MIX for your runtime platform, use the "Get Pre-License Key" option on the ErgoTechIOT Management Utilities page (setup.html). You need to have MIX running, even if not licensed, to access this configuration utility. When you click on "Get Pre-License Key" a key will be generated which needs to be sent (emailed) to your distributor who will return a license file for this system. |
- | After you save the key (ErgoIOTLicence_xxxxxxx.lic) file (where xxxxxxx is the pre-license key value), Use " | + | After you receive |
- | **TransSECS Deployments** | + | ====TransSECS Deployments==== |
TransSECS will generate self-contained deployment code in your project directory. For each deployment distributed to a runtime system, a TransSECS runtime license must be installed to validate the installation. | TransSECS will generate self-contained deployment code in your project directory. For each deployment distributed to a runtime system, a TransSECS runtime license must be installed to validate the installation. | ||
+ | ===Windows=== | ||
- | **OPCUA Server Deployments** | + | TransSECS deployments can be set up on Windows systems with these steps: |
+ | 1. Make a simple directory on the Windows system for the deployment. For example, C:/ | ||
+ | 2. Copy the contents of the deployment to this new directory. You can include the ToolName directory with all the generated files, or you can take the contents of the ToolName directory and copy the complete contents to a new simple directory created in 1. above | ||
- | **OPCDA Gateway** | + | 3. A JRE must be available to run the software. This can be either installed on the Windows system or copied from the TransSECS installation (MIStudioSuite/ |
+ | {{: | ||
- | **Other Deployments** | + | 4. Edit run.bat to point to this local JRE, or use the system' |
- | **Modbus Slave** | + | Open run.bat in a text editor. Edit the line that says: |
+ | set path=C: | ||
+ | to use a local JRE: | ||
+ | < | ||
+ | set path=.\jre\bin\; | ||
+ | </ | ||
+ | |||
+ | to use the system' | ||
+ | < | ||
+ | set path=%path% | ||
+ | </ | ||
+ | |||
+ | See also: | ||
+ | [[rundevicesdeploymentsasaservice|How to run a TransSECS Devices deployment as a service]] | ||
+ | ====OPCUA Server Deployments==== | ||
+ | |||
+ | MIX and ErgoTech' | ||
+ | |||
+ | |||
+ | ====Other Deployments==== | ||
**//How To//** | **//How To//** | ||
Line 55: | Line 103: | ||
[[Products/ | [[Products/ | ||
How To start a runtime when Windows starts up | 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 | ||