Installation from binaries
- Before You Start
- Post-Installation Steps
- See Also
This page describes the steps required to install midPoint Identity and Access Management from a binary distribution. MidPoint is a Java web application distributed in a 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.
This document is somehow generic. This is done by purpose so it can be applied to a variety of operating systems and environments. Yet there are some more detailed guides for some environments that may be useful as companion to this document:
Ubuntu Linux, Tomcat and PostgreSQL database
Before You Start
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
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 http://www.oracle.com/technetwork/java/javase/downloads/index.html. 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.
midPoint needs an application server. We recommend Apache Tomcat 8.x.
Apache Tomcat can be downloaded from http://tomcat.apache.org/download-80.cgi. 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.
Download the midPoint binary release according to the following table:
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
/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.
To actually use the Custom Directory, modify the
setenv.sh 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:
On windows platforms, add line:
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.
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.:
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
The database can later be changed to a full-scale database engine. The Repository Configuration page provides the instructions.
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:
- Stop Tomcat if it's already running.
- Start Tomcat. It should pick up and deploy the "midpoint" application.
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
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.
Other or source versions installation
For other release please see version dependent install guide
- Release 3.6 (Comenius)
- Release 3.5.1 (Einstein Update 1)
- Release 3.5 (Einstein)
- Release 3.4.1 (Heisenberg Update 1)
- Release 3.4 (Heisenberg)
- Release 3.3.1 (Lincoln Update 1)
- Release 3.3 (Lincoln)
- Release 3.2 (Tycho)
- Release 3.1.1 (Sinan Update 1)
- Release 3.1 (Sinan)
- Release 3.0 (Newton)
- Release 2.2 (Crius)
- Release 2.1.1 (Coeus maintenance release)
- Release 2.1 (Coeus)
- Release 2.0 (Rhea)
- Release 1.10 (Phoebe)
- Release 1.9 (Cronus)
- Release 1.8 (Hyperion)
- Release 1.7 (Prometheus)