docker-compose.yml

# Simple composed Docker Essbase server from image that has been pushed to a registry. Assumes that there is a .env
# file in the same folder that defines SQL_PW (the password for the SQL database), EPM_PW (the password to use
# for the Essbase server and WebLogic contianer (can't be 'password' but can be 'password1', for example), and
# that REGISTRY is set, e.g. your organization name in Docker Hub.
# 
# Once this file and the .env file are in place, you can start Essbase by running docker-compose up --detached
# You can then follow the logs by running docker-compose logs --follow essbase
# 
# If you follow the output and everything goes right, then you should see various MaxL commands running that
# load up the sample cubes. You can go to launch EAS via its Java web launch link by navigating to 
# http://localhost:9000/easconsole 
#
# You can access a shell on the Essbase server by running docker-compose exec essbase /bin/sh
# Once in the Essbase server's shell you can run the MaxL interpreter (if you want) by executing
# startMaxl.sh -u admin -p $EPM_PASSWORD -a
# 

version: '3'
services:
  db: 
    image: "microsoft/mssql-server-linux:2017-latest"
    expose:
      - "1433"
    environment:
      ACCEPT_EULA: Y
      SA_PASSWORD: ${SQL_PW}
      MSSQL_PID: Express

  essbase:
    depends_on: 
      - db
    image: ${REGISTRY}/essbase:latest
    container_name: essbase
    ports:
      - "9000:9000"
    ulimits:
      nofile:
        hard: 32000
        soft: 10000

    environment:
      # There are some password requirements for various components; don't attempt to just set "password" here -- 
      # it'll cause configuration to fail because WebLogic requires a stronger password. password1 will work
      # EPM_ADMIN: admin
      EPM_PASSWORD: ${EPM_PW} 
      SQL_HOST: db
      SQL_USER: sa
      SQL_PASSWORD: ${SQL_PW}
      RESTART_EPM_AFTER_LCM_IMPORT: "false"
      AUTO_START_ADMIN_CONSOLE: "false"