Published Network Ports

The sedex Client offers services on network ports which can be reached via HTTP or HTTPS. These container ports have to be published to the outside. On this page you find information about the available network ports, as well as how these network ports can be published with Docker.

Docker Network Port Mapping

By default, when you create or run a Docker container, it does not publish any of its internal network ports to the outside world. To make a port available to consumers outside of Docker, use the --publish option. This maps a container port via a free port on the Docker host to the outside world.

Network ports of the sedex Client

The following diagram shows the components of the sedex Client Docker container and which network ports they are offering internally.

The sedex Client Docker container offers the following services on (internal) network ports:

• Network port 8000: Monitoring (HTTP)
  On port 8000, the sedex Client provides a simple text page that lists the current status of various operational parameters. See Monitoring Status for details on monitoring.
• Network port 8080: sedex Webservice Proxy (HTTP)
  On port 8080, the sedex Client provides an HTTP proxy through which applications can access defined third-party Web services. This port is deprecated and serves for backwards compatibility only. For new applications, you should use port 8443 and the secured HTTPS protocol from the beginning. See sedex Webservice Proxy for details about the sedex Webservice Proxy.
• Network port 8443: sedex Webservice Proxy (HTTPS)
  On port 8443, the sedex Client provides an HTTPS proxy through which applications can have a secured access to defined third-party Web services. See sedex Webservice Proxy for details about the sedex Webservice Proxy.

Publish network ports with Docker

By default Docker does not publish any ports of a container to the outside world. To make a port available to users outside of Docker, use the --publish option of the Docker command. See the Docker documentation for details.

The following excerpt from a Docker command shows the relevant options to publish the network ports of the sedex Client container. The three parameters <YOUR_MONITORING_HTTP_PORT>, <YOUR_WS_PROXY_HTTP_PORT> and <YOUR_WS_PROXY_HTTPS_PORT> must be replaced by free network port numbers on your container platform:

TemplateConcrete Example

  [...]
  --publish <YOUR_MONITORING_HTTP_PORT>:8000 \
  --publish <YOUR_WS_PROXY_HTTP_PORT>:8080 \
  --publish <YOUR_WS_PROXY_HTTPS_PORT>:8443 \
  [...]

  [...]
  --publish 12010:8000 \
  --publish 12020:8080 \
  --publish 12021:8443 \
  [...]

The internal container port number is given

Use the --publish option to map an external network port to the internal network port offered by the container. You can select any free external network port number. However, the internal network port number for the sedex Client Docker container is given and must always be 8000, 8080 or 8443.

General Information about published network ports

• In our examples, we usually publish a network port on the same network port number that the port has internally. Of course, you can set the external port to any number that is still free, but then you have to adapt the commands accordingly.
• If you are running multiple sedex Client Docker containers in parallel on the same Docker host, you will need to find and specify three different free external ports numbers for each container.
• Other container platforms (Kubernetes, OpenShift, etc.) use similar and more specific concepts for published network ports. Please refer to the corresponding documentation for your platform.