Run MTA on premises
This document describes the MTA implementation steps for customers that bring their own Mendix license and environment, either local or cloud hosted.
This could be any custom cloud environment like a Cloud Foundry or Kubernetes Pod or an on-premise installation. The main difference with Menditect hosting MTA on the Mendix cloud is that the client is responsible for managing the cloud platform.
When installing MTA for the first time, always clean up your existing environment first (both the database and the Mendix model).
Configuring a new MTA implementation
Your cloud needs to meet at least the specifications of the Mendix S21-STANDARD container, see Mendix Cloud Container resources.
- You will receive information from Menditect on how to download the MDA file that you need to set up MTA.
- Deploy and transport it to the environment in your cloud.
When deploying MTA on the Mendix Cloud, you need to use at least an S21 Resource Pack.
When deploying MTA on another Cloud provider, you need to have at least 2 GB of RAM for the App and 1/2 CPU core available.
- Check the content of the following environment variables for the MTA application:
You may notice that MTA also contains environment variables from the MTA Plugin Module. This is because Menditect regression-tests MTA with MTA. Menditect on-premise customers and partners do not have to set these values.
- If MTA will be configured to use SAML SSO, additionally set these values (otherwise, use the default value):
- Toggle these scheduled events to Currently Enabled:
Below steps are important and MTA will not work if these steps are skipped.
- Make sure that any firewalls applicable have whitelisted these URLs, on ports 80 and 443:
Make sure the /rest path allows all access (in Mendix: Environment details -> Network -> Path Based Access Restrictions and set the path /rest/ on allow access).
Make sure the /rest-doc path denies all access (in Mendix: Environment details -> Network -> Path Based Access Restrictions and set the path /rest-doc/ on deny all access).
Start the MTA application.
Change the MxAdmin password of the environment to your own MxAdmin password.
Create a database backup.
Upgrading an existing MTA implementation
- Always create a backup of your database before bringing MTA down and upgrading.
- During deployment, make sure that you check all the values of the Constants for the Mendix model.
- After upgrading with the provided MDA file in this directory, make sure to login using the admin account (usually MxAdmin).
- Run all the migrations from the top menu in MTA, from old to new.
- Wait for all of the migrations to be done.
- When running into errors, contact Menditect support (firstname.lastname@example.org), and do not proceed with test scripting.
- Login with a Tester account and check if the test configurations can be executed.
Test application actions
After updating MTA, make sure that all the test applications have the newest version of the MTA Plugin module installed.
Missing anything? Let us know!
Last updated 22 November 2023