Docker-compose files

With Docker, you can:
tdm49
With Docker, you can:
  • Create Docker containers from Docker images.
  • Build Docker images from Dockerfiles and source files.
In both cases, we recommend that you synchronize these commands with a
docker-compose.yml
file. You can use the
docker-compose up
command to start one or more docker-compose.yml files; all the services (i.e. containers) you start with the
docker-compose up
command exist on the same Docker network, which means that they can communicate with each other. Docker services identify themselves by their
hostname
parameter.
3
How to use docker-compose files
To execute a docker-compose.yml file, use a
docker-compose up
command similar to this one:
docker-compose -f
docker-compose.yml
-f
docker-compose-messaging.yml
-f
docker-compose-masking.yml
up -d [--scale
masking=3
]
Where:
  • -f
    Each
    -f
    flag
    defines another docker-compose.yml file to add to the network. The
    docker-compose
    command adds services from each docker-compose.yml file to your Docker network.
    The command adds or reconfigures services in the order in which you supply docker-compose.yml files to the command.
    For example, If you define a service (e.g. TDMWeb) in
    docker-compose.yml
    , and then define it again in
    docker-compose-ora.yml
    , the second set of parameters overwrites the first set.
  • (Optional)
    --scale
    masking=n
    This creates
    n
    number of instances of the service
    masking
    (i.e. the Scalable masking with Docker.
The example above starts a Docker network with the following services:
  • OrientDB (from
    docker-compose.yml
    )
  • TDMWeb (from
    docker-compose.yml
    )
  • Message Bus Server (from
    docker-compose-messaging.yml
    )
  • 3 Masking Engines (from
    docker-compose-masking.yml
    ,
    --scale masking=3
    )
Customize the docker-compose.yml files you need, to reflect your configuration (for example, parameters of your 
gtrep
 repository).
Tip: See the 
README-RUN.md
 and 
README-BUILD.md
 files for details on how to combine these docker-compose.yml files for different use cases.
Name of the Docker network
To start other Docker containers on your Docker network, either TDM Portal REST ActionService container) or with re-execution of the
docker compose up
command, the 
--network
parameter must match the name of your Docker network's name.
In all the docker-compose*.yml files we provide, the network name is
tdm_default
.
To change the name of the Docker network you create with your docker-compose.yml file, amend the
name
parameter in the 
networks
section of each docker-compose.yml file you call in your
docker-compose
command:
networks:
  default:
    name:
tdm_default
Available docker-compose files
TDM Portal's functionality in Docker is available in the following docker-compose*.yml files, available from http://casupport.broadcom.com:
  • Files available to
    start services from images:
    • docker-compose.yml
      The base for a TDM Portal environment. This starts the OrientDB services.
    • docker-compose-messaging.yml
      This starts the Message Bus Server service, necessary for scalable masking.
    • docker-compose-masking.yml
      This starts the Masking Engine service, for scalable masking.
    • docker-compose-ora.yml
      This starts the Oracle database service.
      It is necessary to build this container yourself before you can use
      the docker-compose-ora.yml
      file. It is intended for Advanced users and should not be used in a production environment.
  • Files available to
    build images:
    For more information, see Docker-compose Files to Build Images.