- General Best Practices for Managing Configuration File Precedence
Describes the best practices for managing the configuration order for Mendix Portable Runtime.
Mendix Portable Runtime (previously called Portable App Distribution) provides a flexible and straightforward method for isolated server-based deployments. By enabling customers to generate a bundled artifact packaged as a .zip file and run it directly, Mendix Portable Runtime simplifies the deployment process.
Mendix Portable Runtime offers the following benefits:
You can test Mendix Portable Runtime on a Free App. For more information about Free Apps and their limitations, as well as licensing apps outside of the Mendix Cloud, see Licensing Apps.
To license a Mendix app on the Mendix Portable Runtime, add it to your configuration. For more information, see Obtaining a Mendix License.
The Mendix Portable Runtime functionality is available in Mendix Studio Pro versions 10.24.19 LTS, 11.9, 11.6.5 MTS, and above. The functionality will be enabled for more Studio Pro versions in future releases.
You must also ensure that you have the supported version of Java Runtime Environment.
In most production environments, deployment packages are created by using the Mx-Build command-line tool. However, you can also manually create a deployment package if required, for example, for a local test deployment.
After you create the Mendix Portable Runtime file, deploy it to your environment.
To run your app locally, perform the following steps:
Extract ..\releases\YourApp_portable_YYYYMMDD_hhmm.zip to a local folder.
Set the M2EE_ADMIN_PASS admin port password by performing one of the following actions:
set M2EE_ADMIN_PASS=<your password>export M2EE_ADMIN_PASS=<your password>Run the app by using one of the following commands:
<your folder location>\bin\start.bat<your folder location>\bin\start.ps1<your folder location>\bin\startchmod +x ./bin/start first.
For more information about deploying to a self-hosted environment, refer to the following topics:
The Windows Service Console will stay as it is. Mendix Portable Runtime does not replace the Windows Service Console scope. The goal of Windows Service Console is to provide customers a Windows UI experience that our other products cannot offer.
Mendix Portable Runtime is included in the Server-Based subscription portfolio and uses the same license model. If you are entitled to the subscription, you can request a license to use with Mendix Portable Runtime. For more information, see Licensing Apps.
Unlike the traditional M2EE-based or Cloud Foundry buildpack deployment, where Mendix fully supports the tooling, handling, and execution of the Mendix application package end-to-end, the Mendix Portable Runtime approach shifts the responsibility model. With Mendix Portable Runtime, the package requires only Java to run, and while Mendix officially supports the Mendix Portable Runtime package itself, all implementation, configuration, and deployment activities are the sole responsibility of the customer, meaning that Mendix does not officially support Linux or Cloud Foundry deployment as a platform, but exclusively supports the Mendix Portable Runtime package and what Mx runtime supports. For more information, see Support for Different Deployment Strategies.
Describes the best practices for managing the configuration order for Mendix Portable Runtime.
Describes the folder structure and commmand line parameters for the Mendix Portable Runtime deployment method for Mendix apps.
Describes how to deploy using a Docker image by using Mendix Portable Runtime.
Describes the available monitoring tools for Docker deployments of Mendix.
Describes how to use Mendix Portable Runtime to deploy on Kubernetes without installing the Mendix Operator.
Describes how to deploy to a Cloud Foundry environment by using Mendix Portable Runtime.
How to install and configure Mendix on a Linux system using Mendix Portable Runtime.
Describes how to solve potential issues with Mendix Portable Runtime.