Windows Installation


This document describes how to configure and start up a running version of MMS 4 using the MMS Reference Implementation (MMSRI).

Versions Used to Test these instructions

  • MMSRI v4.0.0-b2

  • Windows 10 (64-bit) 10 Enterprise (v 10.0.19041 Build 19041)

  • Docker Desktop (Community Edition) v2.5.0.0

    • Docker Engine v19.03.13

    • Docker-Compose v1.27.4

1. Download and install Docker Desktop

If you already have a fairly modern version of Docker Desktop installed you can skip this step.

Download the Docker Desktop Community installer and follow the installation instructions.

2. Download and install Git for Windows

If you already have Git you can skip this step.

Go to the Git for Windows site and download the latest version.

This will not only install Git, but will also provide Git BASH, a shell command for working with Git in Windows.

3. Clone the MMS 4 Repository

If you already cloned the repository, make sure you are on the correct branch/tag by following the checkout step (4).

Clone the repository and checkout the latest tagged version, as of the writing of these instructions.

  1. Open GitBash

  2. Navigate to the folder you want to clone the repo on, e.g., C:\repos\mmsri, but you may need to clone in your user folder if you do not have permission to create a new folder at the root drive level, for example :

    cd /c/repos/mmsri

    If you have to use a deeply nested folder, make sure you check out the “Windows Maximum Path Length Issue” entry in the Troubleshooting section below, this will explain how to extend Windows’ maximum path length.

  3. Clone the MMS Reference Implementation repository

    git clone
  4. Checkout the right branch/tag:

    git checkout 4.0.0-b2

4. Get setup

IMPORTANT: Windows PowerShell is the recommended shell for the remaining steps.

  1. Open “Windows PowerShell”.

  2. Navigate to the folder where you cloned the mmsri repository (e.g., C:\repos\mmsri)

  3. Make sure that docker-compose is available by running:

       docker-compose --version
    You should see something like this:
    docker-compose version 1.27.4, build 40524192

5. Start and Monitor MMS

  1. Start up the containers

       docker-compose up -d
    You should see something like this:
    Creating network "mmsri_default" with the default driver
    Creating mmsri_minio_1         ... done
    Creating mmsri_postgres_1      ... done
    Creating mmsri_elasticsearch_1 ... done
    Creating mms                   ... done

    If you are running this for the first time, you will see a much longer output.

    If you modify the configuration file you will have to rebuild the MMS image by running: docker-compose up build

  2. Make sure the containers are running:

       docker-compose ps
    You should see something like this:
            Name                       Command               State                       Ports
    mms                     java -Djdk.tls.client.prot ...   Up>8080/tcp
    mmsri_elasticsearch_1   /tini -- /usr/local/bin/do ...   Up>9200/tcp,>9300/tcp
    mmsri_minio_1           /usr/bin/docker-entrypoint ...   Up>9000/tcp
    mmsri_postgres_1 postgres    Up>5432/tcp
  3. Or you can monitor what the server is doing by tailion and following the log for the mms container by:

       docker-compose logs -t -f mms
    which should show something like this:
    Attaching to mms
    mms              | 2020-11-19T03:08:38.615040700Z
    mms              | 2020-11-19T03:08:38.628149200Z   .   ____          _            __ _ _
    mms              | 2020-11-19T03:08:38.628227300Z  /\\ / ___'_ __ _ _(_)_ __  __ _ \ \
    mms              | 2020-11-19T03:08:38.628232500Z ( ( )\___ | '_ | '_| | '_ \/ _` | \ \
    mms              | 2020-11-19T03:08:38.628239900Z  \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
    mms              | 2020-11-19T03:08:38.628243000Z   '  |____| .__|_| |_|_| |_\__, | / / / /
    mms              | 2020-11-19T03:08:38.628245800Z  =========|_|==============|___/=/_/_/_/
    mms              | 2020-11-19T03:08:38.649950000Z  :: Spring Boot ::        (v2.3.2.RELEASE)
    mms              | 2020-11-19T03:08:38.650075200Z
    mms              | 2020-11-19T03:08:39.160885900Z 2020-11-19 03:08:39.151  INFO 1 --- [           main] org.openmbee.mms.mmsri.MMSRIApplication  : Starting MMSRIApplication on mms with PID 1 (/app.jar started by root in /mms)
    mms              | 2020-11-19T03:08:39.161316700Z 2020-11-19 03:08:39.161  INFO 1 --- [           main] org.openmbee.mms.mmsri.MMSRIApplication  : The following profiles are active: test
    mms              | 2020-11-19T03:08:42.769460100Z 2020-11-19 03:08:42.767  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
    mms              | 2020-11-19T03:08:43.167079600Z 2020-11-19 03:08:43.166  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 374ms. Found 15 JPA repository interfaces.
    mms              | 2020-11-19T03:08:45.885452700Z 2020-11-19 03:08:45.881  INFO 1 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'persistenceJPAConfig' of type [org.openmbee.mms.rdb.config.PersistenceJPAConfig$$EnhancerBySpringCGLIB$$ca626494] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    mms              | 2020-11-19T03:08:46.187477700Z 2020-11-19 03:08:46.187  INFO 1 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean '' of type [] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    mms              | 2020-11-19T03:08:46.216919800Z 2020-11-19 03:08:46.216  INFO 1 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'methodSecurityMetadataSource' of type [] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

6. Use MMS

Refer to the MMS documentation, but to test if the service is running, you can go to: ``http://localhost:8080/actuator/health` <http://localhost:8080/actuator/health>`_, which should show healthy.

Check out the REST API

  1. Go to ``http://localhost:8080/v3/swagger-ui.html` <http://localhost:8080/v3/swagger-ui.html>`_ to see more info on the API.

  2. At the top of the page click on the green outline Authorize button to see the “Available Authorizations” modal window.

  3. Use the basicAuth (http, Basic) option to authenticate the session by using test for both the Username and Password.

    After you click the “Authorize” button, you should see its label change to Logout.

  4. Click the Close button, and you are now logged in the API.

    All the endpoints should now show a closed black lock.

Configuring MMS

IMPORTANT: This reference configuration is not intended to be used for production environments.

With that said, it is possible to configure MMS with this pre-built docker image by defining appropriately named environment variables in the docker compose file.

To do so, study the ``` <>`_ configuration file, and determine how to define associated ENVIRONMENT VARIABLES in the mms service in the docker-compose.yml file.

For example, you could specify a different username/password for MMS by modifying the ``docker-compose.yml` <>`_ file as follows:

  build: .
  container_name: mms
  hostname: mms
    - "SDVC_ADMIN_USERNAME=type_your_username_here"
    - "SDVC_ADMIN_PASSWORD=type_your_password_here"


This section covers some of the most critical issues you may face when setting up MMS in a Windows Environment.

Windows Maximum Path Length Issue

By default Windows, does not allow paths to be longer than 260 characters.

If you see a copy error when building the custom CET JupyterLab or the installers in Windows, it may be because one of the paths is over 260 characters long.

How to Fix This

  1. Open the Registry Editor (regedit.exe) in Admin mode ..

    If you do not have admin mode, you may be able to ask your support IT department to provide you with a local admin, or do this fix for you.

  2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

  3. Change the value of the LongPathsEnabled variable from 0 to 1

  4. Restart your computer and try again…