Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

TL;DR: Yes, for the time being. But it will be deprecated soon.

Midpoint 3.7 introduced stand-alone deployment model for midPoint. There were many good reasons for that change. But perhaps the strongest motivation was to lower entry barrier by making midPoint installation simpler. But there are other advantages too: midPoint is now bundled with a matching version of Tomcat. This combination gets better testing, as it is unrealistic to test midPoint with all existing versions of Tomcat. The bundling may make some upgrade easier (especially upgrades where Tomcat needs to be upgraded as well). With stand-alone deployment we are bundling startup scripts that are customized for midPoint and ready to use. And so on and so on. There is a lot of small advantages that make it easier to use midPoint in standalone mode - especially for users that are not entirely at home in Java EE world.

Stand-alone deployment is now the primary deployment method. But it is not the only one. Now there are two deployment methods:

Stand-alone deployment is recommended option. Explicit deployment to Tomcat will be deprecated soon.

titleExplicit deployment to web container will be deprecated

Explicit deployment to an external web container was supported since the beginning of midPoint. That was the usual practice at the time when midPoint started. But that was some time ago and the world is a different place now. MidPoint supports stand-alone deployment model for several years. It is now the default and recommended deployment model. It works very well and it simplifies a lot of things. Therefore in order to simplify midPoint maintenance and support we will be deprecating the explicit deployment model. Stand-alone deployment will be the only supported option in the future.

This document was moved to