Running the Docker Containers

After building the Docker images, you can run the images as containers to start containerized TIBCO Fulfillment Order Management.

Based on the environment and setup you need, you can at-max start the following images as a Docker containers:

  • AOPD image used to start as a Docker container: $AF_HOME/docker/fom-aopd/4.0.0
  • TIBCO Fulfillment Order Management Configurator image used to start as a Docker container: $AF_HOME/docker/fom-configurator/4.0.0
  • TIBCO Fulfillment Order Management Configurator image used to start as a Docker container: $AF_HOME/docker/fom-ocs/4.0.0
  • OMS-server image used to start as a Docker container: $AF_HOME/docker/fom-oms/4.0.0
  • OMS-UI image used to start as a Docker container: $AF_HOME/docker/fom-omsui/4.0.0
  • OPE image used to start as a Docker container: $AF_HOME/docker/fom-ope/4.0.0

Running Different Containers for TIBCO Fulfillment Order Management Components

Prerequisites

Before you start the OMS server as a Docker container, you must complete all the steps in Configuring for OMS Docker Containers.

Procedure

  1. Note: Ignore this step if you are going to use AOPD in co-located mode.
    Start tibco/fom-aopd:4.0.0 as a container using the following command: 
     $] docker-compose --file docker-compose-run-aopd.yml up -d
    1. Check that the container has started using the following command: 
     $] docker ps -a

    This command gives all the information about the started container. You can also see the port on which AOPD has started as a container. Use this port to configure AOPD configurations for Plan-Preview through Configurator UI.

  2. Start tibco/fom-oms:4.0.0 as a container using the following command: 
     $] docker-compose --file docker-compose-run-oms.yml up -d
    1. Check the details for the OMS server container by executing the following command: 
       $] docker ps -a
      The output also gives you the port number which you must use for accessing the OMS server.
    2. Configure the server information (address and port) using the Configurator UI. These properties are used by OMS UI at the startup time, so after making these changes, start the OMS UI container.
  3. Start the tibco/fom-omsui:4.0.0 as a container using the following command: 
    $] docker-compose --file docker-compose-run-omsui.yml up -d
    1. Check the details for the OMS UI container by executing the following command: 
     $] docker ps -a

    You are able to access the OMS UI on the port which you had set for the HOST_OMS_UI_PORT variable in the .env file.

  4. Note: Ignore this step in case you do not plan to use OPE in co-located mode.
    Start tibco/fom-ope:4.0.0 as a container using the following command: 
     $] docker-compose --file docker-compose-run-ope.yml up -d
    1. Check the details for the OPE container by executing the following command: 
     $] docker ps -a
    The output gives you the port which you must use for accessing OPE.