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


This page describes the steps required to install midPoint Identity and Access Management from a binary distribution. MidPoint is a Java web application. MidPoint primary deployment model is a stand-alone deployment based on Spring Boot. However there is an alternative form of WAR archive. All that is essentially needed is to deploy it in a suitable container. This guide provides instructions to install midPoint in Apache Tomcat.

Starting from midPoint 3.7 the WAR deployment model is just an alternative way to deploy and run midPoint. However, the stand-alone deployment model is now the primary and recommended one.

The deployment to web container is still supported. However the only supported web container is Apache Tomcat. Other web containers (application servers) may be supported if the support is explicitly negotiated in midPoint subscription. Except for those cases midPoint development team will not provide any support for other web containers.

Currently there are no plans to remove support for deployed midPoint installation using a WAR file. However, it is possible that this deployment form will get phased out eventually unless there are active subscribers preferring this deployment method. MidPoint subscription is strongly recommended.

Before You Start

Release Notes

Please make sure to see Release Notes for list of environments that are known to work and for the list of known issues in current release.


Java SE Development Kit 8

The development environment requires at least JDK 8. You can use OpenJDK wich might be already installed on your system of you can download JDK from Oracle.

JAVA_HOME environment variable should point to the JDK installation path.

Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8

Optional AES-128 is used by default for encrypt/decrypt operations, so JCE is not needed. If you want to use bigger key size, e.g. AES-256, then JCE is required for cryptographic operations. You can download it at After downloading zip file follow installation instructions written in README.txt

Java 8 only

MidPoint 3.6 is supported only on Java 8 platforms. MidPoint supported both Java 7 and Java 8 for several years. The support for Java 7 was deprecated in midPoint 3.4.1 and it was removed in midPoint 3.5. It is finally the time to abandon obsolete technology and to move on.

Apache Tomcat

midPoint needs an application server. We recommend Apache Tomcat 8.x.

Apache Tomcat can be downloaded from The Apache Tomcat installation directory is further referenced as <tomcat>. In windows platform prefer downloading of zip file to downloading of windows installer as later do not populate bin directory with all batch files. You will start tomcat server via running the startup.bat file from <tomcat>\bin directory.


Get midPoint

Download the midPoint binary release from Evolveum download site.

Unpack the archive file to a convenient location. Following instructions will refer to the relative paths inside this archive.

Please do NOT set the unzipped directory as your MidPoint Home Directory. Doing so, "schema" directory would conflict with midPoint embedded schemas. Instead, create a new directory as described below.

MidPoint Home Directory (midpoint.home)

If you intend to use custom connectors or schemas you need to create a directory anywhere on your system. This directory will be used to store your custom connector code, schemas, initial configuration and may also contains other files. MidPoint will populate that directory on first start. The directory will not be overwritten when midPoint is restarted or redeployed.

As an intended side-effect, this directory will also be used to store your embedded database repository data (H2).

If you don't want to use custom connectors or you want just to try midPoint, you can skip this chapter and continue to the #Initialize Database.

Create the Directory

You can create your custom directory anywhere in your system. We often use locations such as /opt/midpoint or /var/opt/midpoint on linux platforms and c:\midpoint directory on windows platforms. The directory has to be writable by the application server.

See MidPoint Home Directory page for a description of the directory structure.

Tomcat "" Customization

To actually use the Custom Directory, modify the script (UNIX) or setenv.bat batch file (Windows) located in <tomcat>/bin. If this file does not exist then create a new file. Set the "JAVA_OPTS" variable in this file. On UNIX machines add the line:

JAVA_OPTS="$JAVA_OPTS -Dmidpoint.home=$MIDPOINT_HOME$MIDPOINT_HOME/keystore.jceks -server -Xms512m -Xmx2048m"

On windows platforms, add line:

set JAVA_OPTS=%JAVA_OPTS% -Dmidpoint.home=c:/midpoint -server -Xms512m -Xmx2048m

This line sets up MidPoint Home Directory location, memory options and truststore location. It also overrides default JVM keystore. This is needed for proper SSL support in connectors, notifications and other libraries that are not under direct midPoint control. See Keystore Configuration page for more details.

Configure Tomcat

Tomcat has a limitation of maximum size of POST data it accepts. This can cause problems when editing or importing large objects. So it is advisable to raise (or eliminate) the limit by editing the server.xml file, e.g.:

<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxPostSize="100000000"/>


<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxPostSize="-1"/>

Initialize Database

MidPoint comes with an embedded database engine (H2) that is perfectly suitable for testing and demo installations. This database will be used by midPoint after the installation. Therefore there is no need to set up a separate database if installing midPoint for the first time. The database files will be stored in midpoint.home directory.

The database can later be changed to a full-scale database engine. The Repository Configuration page provides the instructions.

Deploy midPoint

MidPoint appliation is deployed by using the midpoint.war file located in the war subdirectory of the distribution archive. To deploy midPoint WAR file, use the following steps:

  1. Stop Tomcat if it's already running.
  2. Copy midpoint.war to <tomcat>/webapps directory.
  3. Start Tomcat. It should pick up and deploy the "midpoint" application.

Post-Installation Steps

Test midPoint administration GUI

Log in to the midPoint administration console using the following URL:






A home page of the midPoint console should be displayed. This is a pretty dynamic web application using AJAX for better user interaction. The look&feel is quite minimalistic now, we are working on an improvement just now.

If there is a problem, please check Tomcat logs in <tomcat>/log/catalina.out and <tomcat>/log/idm.log.

Optional Post-Installation Steps

MidPoint encrypts some data to protect sensitive parts of the database such as passwords. First start of midPoint generates and encryption key for you. But it generates a short encryption key that is suitable both for use by export-limited and full-strength cryptography modules. Therefore is full-strength JCE extension was installed it is recommended to change the encryption key to a full-strength key. It can be achieved by keytool utility. The Encryption and Keys page describes the procedure.

What Now?

For an quick introduction to use of midPoint please follow the instructions on First Steps page. Full Administration Interface is also available.

See Also


  • No labels