Software AG Products 10.11 | Running Business Processes and Composite Applications | Administering My webMethods Server | Startup and Configuration | Using My webMethods Server with Docker | Running and Customizing My webMethods Server Containers | Redirecting Container Logs to a Non-Perishable Storage
 
Redirecting Container Logs to a Non-Perishable Storage
When you create a new container from a My webMethods Server image, the startup script for My webMethods Server maps the wrapper.log to the standard output stream (STDOUT) for the container. At runtime, the My webMethods Server instance stores all logs in the default container log directory MWS/volumes/logs directory on the container file system. This directory is mapped by default to an anonymous volume, created with a random name by the Docker daemon. When the container stops or gets restarted, the log files from previous runs are sourced back to the MWS/volumes/logs directory from the anonymous volume. You can map a directory from the host file system, or create a named volume persist the files to a non-perishable location and keep the log data for auditing purposes.
Additionally, you can change the log location on the container file system using the LOGS_DIR environment variable. For more information, see Environment Variables that My webMethods Server Containers Support.