Skip to main content

Major changes coming to MAE 17.0

POSTED: | UPDATED: | by Stefan Schüttenkopf

IMAGERY

With the upcoming major version of M.App Enterprise (release mid of May) IMAGERY will be deprecated. This will bring some changes on how to handle images in M.App Enterprise.
💡
All of your apps are still running, despite the changes with IMAGERY
What are the consequences and what is the way forward?

UI

  • For the initial 17.0 release IMAGERY still can be found in CONTENT
  • As soon as you click on IMAGERY a message welcomes you with the deprecation notification
  • The list is read-only and only the 🗑 icon is available
  • In the CONTENTLEGENDS list all legends containing IMAGERY get a ⚠ icon
  • All IMAGERY layer in the tree of the legend also get a ⚠ icon

Way forward?

Handling of images in M.App Enterprise will be done in Luciad Fusion in the future.
💡
Installation of Luciad Fusion is always possible. Even though you just have a "Essentials" license of MAE.

Necessary steps

💡
File location of your images doesn't need to be changed.
  • Install Luciad Fusion
Lesson 1 (optional): Installing Luciad Fusion for MAE
This article gives you some information about the installation of Luciad Fusion, which is integrated since the release of M.App Enterprise 2019. 💡We strongly recommend to install Luciad Fusion on a seperate server.💡For the storage of the metadata you will need to create an empty database before installing
  • Crawl data
  • Create a supported service from the list below
    • WMS
    • WMTS
    • WFS
    • ECWP

If you want to use ECWP in your browser, you will need to fulfill some requirements:

  • You need to enable CORS in the web.config (see Release Guide for MAE 16.8.1)
  • You need to ensure that Fusion is supporting ECWP (see this blog post)

Mobile

There is a new client app available for this release of mobile called MAE Mobile. Which means if you plan to stay on the 16.x line – please continue to use the “old” M.App Enterprise app. If you prefer to upgrade to the latest major only the new app is usable.

Other main features are:

  • Change the framework to MAUI
  • Luciad as the new map engine (default on Windows)
  • Many new fields, actions and script functions
  • Developer mode

If you plan to upgrade to the new mobile app there is a migration post available here:

Mobile Migration
Starting with M.App Enterprise 17.0, a new mobile client will be delivered. It is based on Microsoft MAUI and attempts to stay backward compatible with your existing shells, but requires M.App Enterprise 17.0 as server version. To avoid breaking existing apps, it will be published as

FAQ

After the update I just get a 500 error page, when opening Management / Studio / Apps page

You have to manually delete the ISAPI Filter in your IIS.

In there you have to delete M.App Core Filter