App Node Requests
Introduction
There are a number of changes to licensed app nodes which you need to request outside the Mendix Portal.
These changes, listed below, are described in this document.
Requesting a New Licensed App Node
If you want to deploy your app to a new licensed node in Mendix Cloud, Mendix Cloud Dedicated, or on-premises/virtual Mendix on Kubernetes, you can request one from Mendix Support.
Fill in the required details for the new licensed app node on the Request New App Node page. If your request matches your entitlements, your Mendix Cloud node is created automatically. Mendix Support will contact you via a ticket in the Mendix Support Portal if more information is needed or to send you keys for apps deployed on-premises or to a virtual Mendix on Kubernetes.
By default, all developers in your organization can create node requests. You can limit this to Mendix Admins only by contacting your Customer Success Manager or requesting it via a support ticket.
These are the hosting types that you can make requests for:
- 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.
Resizing an Existing Environment
If your environment is not the right size, for example it has too little database storage, you can request a resize from Mendix Support.
Fill in the required details on the Resize Environment page.
Mendix Support will contact the Technical Contact for the app via a ticket in the Mendix Support Portal to discuss 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.