Integration Server 10.11 | Integration Server Administrator's Guide | Using Integration Server with Docker | Running the Docker Image in an On-Premise Docker Container
 
Running the Docker Image in an On-Premise Docker Container
 
Writing the Server Log to the Console
Writing Audit Logs to the Console
Accessing an Integration Server Running in a Docker Container
Externalizing Log and Configuration Files When Running Integration Server in a Docker Container
Use the docker run command to run a Docker image, such as one created for Integration Server, in an on-premise Docker container. When the Docker image is for an Integration Server, running the Docker image starts up Integration Server.
When using the docker run command, you can explicitly map a port on the machine that hosts the Docker container to an exposed port in the Docker container. Alternatively, you can allow Docker to map the exposed port to any available port on the Docker host machine. For a Docker container for Integration Server, the exposed ports include the primary port and the diagnostic port. If you want to use Integration Server Administrator to connect to the Integration Server running in the Docker container, you must explicitly assign a host machine port to the Integration Server primary port for the container. If you allow Docker to associate the host machine port with the Integration Server port, you will not know which host machine port Docker associated with the Integration Server primary port. Similarly, if you want to be able to access Integration Server Administrator through the diagnostic port, you must explicitly map a port on the host machine to the diagnostic port exposed on the container.
Note:
Many container deployment solutions provide the ability to view the console logs STDOUT and STDERROR for a container. When running a Docker image of Integration Server in a Docker container, Integration Server writes the server log to the console as well as to the server.log file.
*To run a Docker image in an on-premise Docker container
*Run the following command:
docker run -d --name Docker_container_name
-p [host_primary_port:]primary_port
-p [host_diagnostic_port:]diagnostic_ port -p [host:]other_exposed_ port environment_variables
Docker_image
Where this placeholder
Specifies
Docker_container_name
Name of the Docker container in which you want to run the Docker image. For example, IS_Default.
host_primary_port
Optional. A port on the container host machine that you want to explicitly map to an exposed port on the Docker container, specifically the primary port of Integration Server. If you do not specify host_primary_port , the Docker container maps any available port on the container host machine to the primary_port .
primary_port
Port number for the primary port on Integration Server.
host_diagnostic_port
Optional. A port on the container host machine that you want to explicitly map to an exposed port on the Docker container, specifically the diagnostic port of Integration Server. If you do not specify host_diagnostic_port , the Docker container maps any available port on the container host machine to the diagnostic_port .
diagnostic_port
Port number for the diagnostic port on Integration Server.
host_port
Optional. A port on the container host machine that you want to explicitly map to an exposed port on the Docker container. If you do not specify host_port , the Docker container maps any available port on the container host machine to the other_exposed_port .
other_exposed_port
Port number for an exposed port on Integration Server.
environment_variables
Name=value pair for any environment variables that you want to use. For a list of Integration Server environment variables for use with Docker, see Environment Variables.
Docker_image
Name of Docker image to run in the on-premise Docker container. For example, is:microPkg
Examples
Suppose your Docker image for an Integration Server exposes port 5555 and 9999.
In the following example, the command does not include ports on the container host machine. Consequently, the Docker container automatically maps the exposed ports to available ports on the container host machine.
docker run -d --name IS_Default -p 5555 -p 9999 is:microPkg
In the following example, the command explicitly maps ports available on the container host machine to exposed ports on the Docker container.
docker run -d --name IS_Default -p 34678:5555 -p 34679:9999 is:microPkg
Note:
You can find running instances of a Docker container by running the command: docker ps -a