It is not always necessary to manually install the UM with the described installation method. In some cases it makes sense to run the UM in a docker container:

If you have a dockerized application infrastructure
To develop CSE based applications in a local UM instance

This section describes how you can create a customized UM Docker image.

We do not provide pre-built docker images because

years of practice have shown that setting up a UM instance usually involves customizing it in many ways and touching and adding a lot of files. That means, you would have to ADD or COPY a lot of files anyway.
While configuration variables (“cmsbs.properties”) can be passed via environment variables, there are a number of situations where whole files need to be added to the image: i.e. the licence file, sender and reply-to addresses, additions or modifications to the data model, optional UM Apps or custom CSE code.
Often times there will be more than just one single UM instance, so there is the need to end up with three or sometimes even more slightly different setups and thus different images.
The more customizing needs to be done, the more it makes sense to be able to first implement and test these customizations on your local machine and let the docker image create when you are done.
There is a tool that is desiged to do exactly that: The UM Kickstarter.

Creating a customized docker image

To create your own custom UM docker image, install UM Kickstarter following Install Kickstarter, first.

Next, create a new project:

umkickstarter my-um-project
cd my-um-project

Next, copy your personal license file to env/devel/cmsbs-conf/cmsbs.license.

You are now ready to create your custom UM docker image:

gradle dockerimage -Penv=devel

Running a UM from a custom docker image

Start your dockerized UM:

docker run --rm --network host \
    -e UM_ADMIN_USERNAME=admin -e UM_ADMIN_PASSWORD=admin \
    myproject:devel

Go to http://localhost:8080/cmsbs and login as admin / admin.

The default for Kickstarter based UM installations is to use an embedded H2 database that stores its data in /UM/cmsbs-work/db.h2.* inside the docker container’s volume. As this is fine for local development you probably want to use a ‘real’ database engine at some point in time.

Running a local ‘real’ database

There is quite a number of supported database engines to choose from (see Installation Requirements for a list of officially supported databases).

Select one of the database engines listed below and start an instance with the given docker run command.

Configure UM to use new database

Create a file env/devel/cmsbs-conf/conf.d/database.properties below your Kickstarter directory and paste the given UM configuration snippet according to the database chosen.

Create the directory cmsbs/WEB-INF/lib/ below your Kickstarter directory and add the following line to your build.gradle file:

Download the appropriate JDBC driver and copy the JAR file to the directory cmsbs/WEB-INF/lib/ your just created.

Recreate and run docker image using the freshly created database:

The UM instance running on http://localhost:8080/cmsbs should now populate and use the new database.

Docker images for popular database engines

The following represents a subset of the supported databases for which there are easy to use docker images available on docker hub.

Each subsection contains a docker run command to start the according database listening on its respective standard TCP port and a docker run command to start a UM instance using that very database.