Not sure on how to get started or looking for a workflow to get M.App Enterprise up and running. Tutorials provide step by instruction on some of the most common configurations and workflows to get M.App Enterprise configured up and running quickly.
This article gives you an overview of the first steps to do in M.App Enterprise to get the application up and running. You may also find some hints throughout the entire article.
Installation of M.App Enterprise
Before installing M.App Enterprise you need to create an empty database. This applies to the Master database (metadata schema for the installation) as well to the Tenant database (metadata schema for the studio). More details later.
The installation progress is pretty straight forward. There are some things to consider of:
A warehouse user must be created beforehand installing M.App Enterprise
Most of the time it is sufficient to create a local user account on the server, where the application should be installed
Or you can also use an user from the active directory
WebDAV mustn't be used if you want to install M.App Enterprise on the same server
Master DB --> the metadata schema for Management user, Tenants and Charges
Create an empty one before installing M.App Enterprise
If you want to use Oracle for the master database please ensure that the correct Oracle client is installed on the server (Oracle 12c or higher - 64bit)
For more information have a look at the detailed community article here.
Responsibilities of the Management user?
He is the "super" admin if this a fitting name. He controls all tenants with the corresponding initial studio administrator account and is responsible for the charges of all M.App Enterprise environments.
Tenants can be different customers for example. They are all managed with the same M.App Enterprise application, but the metadata schemas can be located on different server even in different database provider.
For example: M.App Enterprise is installed on Server 1 with one management user and he creates for different purposes or customers or whatever Tenant1 in Oracle on Server2, Tenant2 in SQLServer on Server3 and Tenant3 in PostGIS also on Server3. Please ensure that everytime a new tenant is created an empty database has to be created beforehand. The Studio Administrator of Tenant1 is accessing his studio with the URL: https://SERVER2/Studio/?tenant=Tenant1 and so on.
All metadata schemas are seperated from each other and only the management user is seeing and can edit the different connections. By creating a tenant the management user has also to create the first studio administrator account and this studio administrator has full access to the user and role management for all the apps he ever has created.
Depending on the database provider, there are some requirements, which must be fulfilled by the user, who created the database.
PostgreSQL: Case - sensitive database. So all tables AND columns must be lowercase.
SQL Server: Case - insensitive database. Can be checked by the following SQL statement:
select table_name, column_name, collation_name from INFORMATION_SCHEMA.COLUMNS where table_name = @table_name
Defines the name of the environment for which the charge should be used. So if you are using different systems, you can charge different environments with a different amount of hours. For example you have a Development and a Production environment, than you can use for example 2000h (one charge file) for the Dev environment and for example 6000h (another charge file) for the Production environment.
Upload of the charge file. Charge files are provided by the product team and are basically the license files, where for example the amount of hours you have bought are stored.
We recommend to install the application of M.App Enterprise and the Tile Service on two seperate server. The installation progress is also straight forward.
There are two things to consider of:
You have to use the same warehouse user you have created in the application itself
If the application and the tile service is running on the same server you can leave the textfield Domain empty or type in .
You have to use the same master database for the Tile Service and the application.
Again please ensure that the Oracle client is installed, if Tile Service and application are seperated and the master database is located in Oracle.
Starting from M.App Enterprise 2018 the Geoprocessing Server is delivered as additional standalone component. It is mandatory to install it on a separate server (it could be the same server you install TileService on, but you have to consider carefully the loading of this server in production environments).
You can download the dedicated installer from the main download page, you will see a dedicated link for the specifc release.
The last step of the M.App Enterprise wizard now includes the configuration of the Geoprocessing Server endpoint. Please put this url in the form (with no slash at the end):
The main thing to consider is the access to the Warehouse folder from this additional server. The warehouse should be configured as UNC path and should be accessible from both servers using the warehouse user.
More details can be found in the following tutorial: