Managing Assets and Data in My webMethods Server Containers

By default My webMethods Server containers persist data to the SAGHOME/MWS/volumes directory of the container, declared in the Dockerfile for My webMethods Server images. Unless you map a named volume, the Docker daemon mounts the MWS/volumes directory to an anonymous volume, that is, a volume with a random name, in the default location on the host file system var/lib/docker/volumes. You can use named volumes to facilitate archiving, navigation, and data sharing among different containers.

Although a My webMethods Server container can connect to a non-empty volume, unexpected results might occur if you connect a My webMethods Server container to a volume that already contains the data of another container. My webMethods Server validates the volume content at container start up, and stops the container if the validation fails. The following table lists the volumes that the Dockerfile for My webMethods Server declares, and what restrictions apply to reusing volumes between containers:

Volume	Environment Variable	Description
MWS/volumes/apps	$APPS_DIR	Stores custom applications to deploy to the My webMethods Server instance at startup. Read mode. Can be reused between different containers.
MWS/volumes/configs	$CONFIGS_DIR	Stores configuration files to supply to the My webMethods Server instance at startup. Read mode. Can be reused between different containers.
MWS/volumes/data	$DATA_DIR	Stores container runtime data, such as the My webMethods Server search index and events from the Task Engine lightweight event queue. Read and write mode. You cannot reuse this volume between different containers.
MWS/volumes/libs	$LIBS_DIR	Stores external libraries and custom jars to inject to the MWS/lib directory at startup. Read mode. Can be reused between different containers.
MWS/volumes/logs	$LOGS_DIR	Stores container runtime logs. Read and write mode. You cannot reuse this volume between different containers.
MWS/volumes/patches	$PATCHES_DIR	Stores test patches to install on the My webMethods Server instance at container startup. Read mode. Can be reused between different containers.