Step 7: Test TIBCO MFT Command Center   Docker Image

Now that the Docker image is created, you must test the Docker image using the dockerrun command. This step shows how to test the Docker image. Note that by default, the   TIBCO MFT Command Center server connects to the database used in the initial TIBCO MFT Command Center   installation. The database connectivity can be changed at a later time to point to a different database.

The Docker run command allows you to redirect the container ports to the ports on the Docker host.

Note: Make sure that the ports defined by the -p parameter are unique and available on the Docker host when running multiple   containers on the same Docker host.

    Procedure
  1. To test the HTTPS and HTTP ports, run the following command. In the Internet Server, if you want to test other protocols like SFTP, you must add the port mapping to the command below.

    docker run -it --rm -p 8443 : 8443 -p 8080 : 8080 -e \ COM_TIBCO_MFT_TRACEDIR='/tmp' library/mftcc:v.v.v (where v.v.v is the product version)

    Note: The above command is for Internet Server only.
    The following table describes the parameters in the run command:
    Parameter Description

    -p 8443:8443 -p 8080:8080

    		 Maps the ports used by the container to the ports accessible by the network.
    -e \ COM_TIBCO_MFT_TRACEDIR='/tmp -library/mftcc:v.v.vDefines the location where TIBCO MFT Command Center   log files are created. TIBCO MFT Command Center   creates a directory for the machine name. Under this directory,   TIBCO MFT Command Center writes MFT log and Server log files.

    Note: If you have made any changes to the Docker image that you want to make permanent, you can use the Docker commit command to commit the changes to an image. However, make sure to do this before the Docker image is removed.