Page tree
Skip to end of metadata
Go to start of metadata

TL;DR: Yes. It is supported. And it will be supported.

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:

Both methods are equally supported. And while we prefer and recommend stand-alone deployment, explicit deployment to Tomcat is still there. It is supported. And as far as we can tell it is here to stay. We will support Tomcat deployment as long as there is at least one midPoint subscriber that prefers this method. Therefore if you prefer explicit Tomcat deployment and you have active midPoint subscription you are perfectly safe. There is no need to migrate to stand-alone deployment just for the fear of losing the support. There may be other reasons for you to consider migrating to stand-alone deployment, though. And stand-alone deployment is something that is definitely worth having a look at. But if you still prefer explicit Tomcat deployment you can have it. And we will support it.

  • No labels