App Node Requests
Introduction
This document describes some changes to licensed app nodes that you can request outside the Mendix Portal. These changes are listed below.
Requesting a New Licensed App Node
To deploy your app to a new licensed node, you will need to request a node from Mendix Support. When submitting your request, you must specify the hosting type for your application. The available options are:
- Mendix Cloud – Select this option for apps deployed to public Mendix Cloud.
- Mendix Cloud Dedicated – Select this option for apps deployed to Mendix Cloud Dedicated.
- Mendix for Private Cloud – Select this option for apps deployed to Kubernetes using the Mendix Operator. Refer to Mendix on Kubernetes for more information.
- Server-based (Windows Server) – Select this option for apps deployed to Windows. You are required to enter the Server ID, which you can retrieve by following the steps in the Windows Server section of Licensing Apps.
- Container-based (Docker, Cloud Foundry, Kubernetes) – Select this option for apps deployed to Docker, Cloud Foundry, or Kubernetes, without Mendix Operator.
- SAP – Select this option for apps deployed to SAP.
To request your node from Mendix Support, complete the following steps:
- Submit the request – On the Request New App Node page, fill in the required details, including your desired hosting type.
- Automatic node creation – If your request matches your entitlements, your Mendix Cloud node will be created automatically.
- Follow-up – Mendix Support will contact you via a ticket in the Mendix Support Portal if additional information is needed or to provide keys for apps deployed on-premises or using a virtual Mendix on Kubernetes.
Resizing an Existing Environment
If your environment needs resizing, for example, due to insufficient database storage, you can do so using one of the following methods:
-
Self-service – If your application's tenant is self-service enabled and you are the Technical Contact, you can resize the environment by changing its plan. For details, refer to Changing Your Plan in Mendix Cloud.
-
Request from Mendix Support – Fill in the required details on the Resize Environment page. Afterwards, Mendix Support will contact the application's Technical Contact through a ticket in the Mendix Support Portal to discuss the request's priority and timing.
Offboarding an Environment
If you no longer need an environment, you can offboard it. Alternatively, you can reuse it for another app. See Linking Your App to a Licensed Node in Licensing Mendix Cloud Apps for more information.
You can offboard a single environment or an entire node (all three of the test, acceptance, and production environments for example) by filling in the required details on the Offboard Environment page. Only the Technical Contact of the application can request (and confirm) the offboarding. Once the offboarding is confirmed, the process will take place automatically. If you cannot use the Offboard Environment page for any reason, please raise a ticket with Mendix Support.
Offboarding will remove access to everything related to the node. If you want to access any data or other information, you will need to ensure this is backed up outside the Mendix Portal.
The following will be removed:
- Environments
- Cloud Containers
- Database
- FileDocument Storage
- Backups
- Alerts
- Logs
When your app is offboarded, only the deployed app and its data is removed. You still retain all access to the data associated with the development of the app, such as Epics, App Insights, and the repository on the Team Server.