This demo shows how to run midPoint container with alternative repository implementation.
docker-compose up command successfully finishes you should see something like this on the console:
Now you can log into midPoint using https://localhost:8443/midpoint URL, with an user of
administrator and a password of
You can safely ignore console messages like this:
This is a part of standard midPoint conflict resolution process. The mentioned transactions are really retried and they succeed eventually.
demo/postgresql composition contains the following containers:
|This is the standard container providing midPoint functionality. It contains standalone Tomcat running midPoint application, reverse Apache proxy, and TIER Beacon.|
|This container hosts midPoint repository; this time it is implemented on PostgreSQL 9.5 database.|
The containers publish the following TCP ports. (Port mapped to localhost denotes the mapping of container port to the host port where it can be reached from the outside.)
|Container||Port number||Port mapped to localhost||Description|
|443||8443||HTTPS port to be used to connect to midPoint application|
|80||-||HTTP port to be used to connect to midPoint application|
|9090||-||Tomcat AJP port used for Apache httpd ↔ Tomcat communication|
|5432||5432||Port used to connect to the PostgreSQL database|
The following volumes are created to persist data and other relevant files.
|Volume name||Description||Used by container|
|The midPoint home directory. Contains schema extensions, logs, custom libraries, custom ConnId connectors, and so on.|
|Volume hosting PostgreSQL database used by midPoint.|
Configuring the composition
The following configuration properties are supported. Please refer to the main documentation page for their explanation.
You can tailor these to your needs.
The following Docker secrets are used:
The following configuration files are used:
|Target file||Source location|
You can modify or replace these files as needed.