Java SE Development Kit 6
The development environment requires JDK 6. Recommended is JDK 6 update 11 or above. Update 4 contains the JAX-WS 2.1 but there are some issues, so we suggest something after update 11 or the latest which you can download at http://java.sun.com/javase/downloads/widget/jdk6.jsp
JAVA_HOME environment variable should point to the JDK 6 installation path.
Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 6
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
midPoint needs an application server. Currently, Apache Tomcat 6.0.x is supported. More application servers will be supported in later releases.
Apache Tomcat can be downloaded from http://tomcat.apache.org/download-60.cgi. The Apache Tomcat installation directory is further referenced as <tomcat>.
Prepare midPoint software
Download the midPoint binary release according to the following table:
Directory for Custom Components (midpoint.home)
If you intend to use custom connectors, you need to create a custom directory somewhere on your system. This directory will be used to store your custom code and will not be overwritten when you redeploy midPoint application.
As an intended side-effect, this directory will also be used to store your embedded BaseX repository data.
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.
You can create your custom directory anywhere in your system. We often use locations such as "
The directory has to be writable by the application server user.
The directory structure is described here.
To actually use the Custom Directory, modify the "
catalina.sh" script located in
<tomcat>/bin/catalina.sh and set the "JAVA_OPTS" variable.
Repository initialization is not required, an embedded BaseX repository will be used by default.
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 "idm" 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
For an quick introduction to use of midPoint please follow the instructions on First Steps page.