Java SE Development Kit 6
The development environment requires at least JDK 6 update 26. As far as after February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites (see http://www.oracle.com/technetwork/java/eol-135779.html), recommended is JDK 7 which you can download at http://www.oracle.com/technetwork/java/javase/downloads/index.html.
JAVA_HOME environment variable should point to the JDK 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.x or 7.x is supported. More application servers will be supported in later releases.
Apache Tomcat can be downloaded from http://tomcat.apache.org/download-70.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.
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 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 or BaseX).
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 (you will use midpoint.war file for this purpose as it is ordinary zip packed file). We often use locations such as
/opt/midpoint or /var/opt/midpoint on linux platforms or c:\midpoint directory on windows platforms. 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.
On windows platforms, add line
at the beginning of "catalina.bat" batch file located in
Repository initialization is not required, an embedded database repository (H2) will be used by default. The database files will be stored in
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