Deploying Web Author in a Docker Container
It is a common practice to use Docker containers to deploy Oxygen XML Web Author. This topic contains some advice on how to create a custom Docker image.
For some sample Docker configurations, see the following public GitHub repository: https://github.com/oxygenxml/web-author-docker.
HTTP Configuration
The HTTP/HTTPS ports of the container must be exposed.
One of the benefits of using Docker containers is that you can deploy multiple instances of Oxygen XML Web Author to provide high availability. In this case, you may want to consult the documentation about running Oxygen XML Web Author behind a load balancer.
Configuration
The server configuration that can be changed using the administration page is stored in the Data Directory. If you want to persist some of this configuration when containers are removed, you can map parts of this directory it to a volume.
Alternatively, you can add the initial configuration of the server as part of the file system of the Docker image.
Licensing
The license server has some protections built in to prevent users from duplicating a deployment with the same license. As a result, deploying the license server in a Docker container is not supported.
Logging
Oxygen XML Web Author is configured to log to both standard output and to a file so that you are able to use the standard Docker commands to obtain the logs.