The following screenshot shows the recommended server architecture for using M.App Enterprise as a platform.
M.App Enterprise Application Server
TileServer - if you don't use Caching very extensively you could also put the Warehouse on the M.App Enterprise Application server
LuciadFusion - full potential when running M.App Enterprise PRO
Geoprocessing - only makes sense when executing Spatial Models on M.App Server
Independently of the application servers you would need a database server as well, which handles not only the Metadata tables (Management and / or Tenant) but could also function as your spatial data source.
💡
If you are extensively using LuciadFusion for M.App Enterprise (like having a big amount of (True) Orthophotos and 3D Mesh and so on, we recommend a seperate Warehouse folder for M.App Enterprise and LuciadFusion in order to not limit I/O performance.
💡
System Requirements for the application server can be found here.
Definition
Geoprocessing - within setup of M.App Enterprise
LuciadFusion - within setup of M.App Enterprise
(Spatial) Database
Master DB - within setup of M.App Enterprise
Tenant DB - within Management of M.App Enterprise
Spatial DB - within Studio of M.App Enterprise
Communication
Communication between Application Servers (M.App Enterprise, LuciadFusion & Geoprocessing) to the clients (Desktop, Mobile & Browser) is done via https://, which means you need a valid certificate for every single one of your servers.
💡
If you are using one or more Load Balancer the SSL certificates must be used on that level.
Testing and Deployment
If it comes to Testing & Deployment we recommend the process seen in the next screenshot:
💡
The export of your Tenant database is now possible via the Management of M.App Enterprise
The export of your