Previously you have used a Tomcat and deployed
midpoint.war inside it. Now it's possible to use embedded Tomcat within midPoint.
Migration with example
The original state is a clustered midpoint, node 1. The setup is as follows:
|Start script JVM settings|
|Shutdown script JVM settings|
We start the migration with a new installation and leave the original midpoint.home directory untouched:
- shutdown your existing midPoint (Tomcat) node 1
- install midPoint to a new directory, e.g. "
/opt" by uncompressing "
midpoint-3.7-dist.tar.gz" there (the version must be the same as your previously used version!). The resulting directory will be
- run the newly installed midPoint by executing "
This ends with a new midPoint installation using embedded H2 repository, i.e. not using your repository. But now we have the "
/opt/midpoint-3.7" directory populated with required subdirectories.
Now shutdown the new midPoint with embedded H2 repository by executing "
Now copy the configuration from the original midPoint to the new standalone deployment:
|Main midPoint configuration file|
|Exported files (if any)|
|JMX configuration for authentication (only when using cluster)|
/opt/midpoint-3.7/bin/midpoint.sh" script and update
JAVA_OPTS to contain the settings used previously:
Now start your new midPoint again by executing "
/opt/midpoint-3.7/bin/start.sh". It should connect to your original repository.
If everything works, use the same steps for migrating your node 2.
midpoint.sh file may be updated with the newer midPoint release. As it also contains your own customizations (e.g. JAVA_OPTS), be sure to backup the
midpoint.sh before uncompressing midPoint upgrade to the same directory, and then merge your changes back. In the future there should be another script for such customizations that would not be overwritten by midPoint upgrade, but rather included when starting and stopping midPoint.
Since midPoint 3.9 it is possible to place your customizations to "bin/setenv.sh" (or "bin/setenv.bat") script to avoid modification of
midpoint.sh. For example:
Don't forget that the URL for midPoint is now http://localhost:8080 (without "
And also that the log is now created in