|
| 1 | +--- |
| 2 | +title: "Mendix Portable Runtime" |
| 3 | +url: /developerportal/deploy/portable-app-distribution-deploy/ |
| 4 | +weight: 15 |
| 5 | +description: "Describes the Mendix Portable Runtime deployment method for Mendix apps." |
| 6 | +no_list: false |
| 7 | +description_list: true |
| 8 | +--- |
| 9 | + |
| 10 | +## Introduction |
| 11 | + |
| 12 | +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. |
| 13 | + |
| 14 | +## Benefits |
| 15 | + |
| 16 | +Mendix Portable Runtime offers the following benefits: |
| 17 | + |
| 18 | +* Simplified deployment - Portable apps eliminate complex installation procedures, making it easier and faster to get software up and running across different machines. This reduces setup time and potential configuration errors. |
| 19 | +* Enhanced consistency - By bundling all dependencies, portable apps ensure a consistent operating environment for the application, regardless of the underlying system configuration. |
| 20 | +* Improved mobility and flexibility - Teams can easily move applications between workstations, virtual machines, or even cloud instances without the need for reinstallation, fostering greater agility in project work. |
| 21 | +* Reduced system impact - Portable apps often run in isolated environments, which can help prevent conflicts with other installed software and maintain system stability. |
| 22 | +* Streamlined updates - Managing updates can be more straightforward, as new versions of a portable application can often be deployed by simply replacing the package. |
| 23 | +* Layered configuration - Mendix Portable Runtime supports defining base configurations that can be extended with environment-specific or deployment-type-specific entries (for example, distinct configurations for development, testing, or production environments). |
| 24 | + |
| 25 | +## Licensing |
| 26 | + |
| 27 | +You can test Mendix Portable Runtime on a [Free App](/developerportal/deploy/mendix-cloud-deploy/#free-app). For more information about Free Apps and their limitations, as well as licensing apps outside of the Mendix Cloud, see [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/). |
| 28 | + |
| 29 | +To license a Mendix app on the Mendix Portable Runtime, add it to your configuration. For more information, see [Obtaining a Mendix License](/developerportal/deploy/licensing-apps-outside-mxcloud/#get-license). |
| 30 | + |
| 31 | +## Prerequisites |
| 32 | + |
| 33 | +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. |
| 34 | + |
| 35 | +You must also ensure that you have the supported version of [Java Runtime Environment](/refguide/system-requirements/#java). |
| 36 | + |
| 37 | +## Creating a Mendix Portable Runtime File {#creating-a-portable-app-distribution-file} |
| 38 | + |
| 39 | +In most production environments, deployment packages are created by using the [Mx-Build](/refguide/mxbuild/) command-line tool. However, you can also [manually create a deployment package](/refguide/create-deployment-package-dialog/) if required, for example, for a local test deployment. |
| 40 | + |
| 41 | +## Deploying Your App |
| 42 | + |
| 43 | +After you create the Mendix Portable Runtime file, deploy it to your environment. |
| 44 | + |
| 45 | +### Deploying Locally {#deploy-local} |
| 46 | + |
| 47 | +To run your app locally, perform the following steps: |
| 48 | + |
| 49 | +1. Extract `..\releases\YourApp_portable_YYYYMMDD_hhmm.zip` to a local folder. |
| 50 | +2. Set the **M2EE_ADMIN_PASS** admin port password by performing one of the following actions: |
| 51 | + |
| 52 | + * For Windows, run the command `set M2EE_ADMIN_PASS=<your password>` |
| 53 | + * For Linux, run the command `export M2EE_ADMIN_PASS=<your password>` |
| 54 | + |
| 55 | + {{% alert color="info" %}}The Mendix admin port can be used to fetch metrics and other runtime data from an app. It requires a password for security reasons. |
| 56 | + {{% /alert %}} |
| 57 | + |
| 58 | +3. Run the app by using one of the following commands: |
| 59 | + |
| 60 | + * For Windows, run the command `<your folder location>\bin\start.bat` |
| 61 | + * For Windows Powershell, run the command `<your folder location>\bin\start.ps1` |
| 62 | + * For Linux, run the command `<your folder location>\bin\start` |
| 63 | + |
| 64 | +{{% alert color="info" %}} |
| 65 | +On Linux, if the ZIP was extracted on Windows, the +x flag is not preserved. Windows does not have the executability bit. You need to run the command `chmod +x ./bin/start` first. |
| 66 | +{{% /alert %}} |
| 67 | + |
| 68 | +### Deploying to a Self-Hosted Environment |
| 69 | + |
| 70 | +For more information about deploying to a self-hosted environment, refer to the following topics: |
| 71 | + |
| 72 | +* [Mendix Portable Runtime for Docker](/developerportal/deploy/docker-deploy-pad/) |
| 73 | +* [Mendix Portable Runtime for Linux](/developerportal/deploy/linux-pad/) |
| 74 | +* [Mendix Portable Runtime for Cloud Foundry](/developerportal/deploy/cloud-foundry-pad/) |
| 75 | + |
| 76 | +## Frequently Asked Questions |
| 77 | + |
| 78 | +### What Will Happen with my Windows Deployment using Windows Service Console? |
| 79 | + |
| 80 | +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. |
| 81 | + |
| 82 | +### Do I Need to Buy a New Subscription to Implement Mendix Portable Runtime? |
| 83 | + |
| 84 | +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](/developerportal/deploy/licensing-apps-outside-mxcloud/). |
| 85 | + |
| 86 | +### Does Mendix Fully Support Deployments using Mendix Portable Runtime on Linux or Cloud Foundry Environments? |
| 87 | + |
| 88 | +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](/support/deployment-strategy-support/). |
| 89 | + |
| 90 | +## Read More |
0 commit comments