Clustering My webMethods Server Containers
Although you can create a cluster from My webMethods Server containers manually by running the containers against the same database and using the same JMS provider, the recommended approaches to create a clustered environment are using Docker Compose or Kubernetes.
Certain limitations apply when creating and using clusters from My webMethods Server containers:
Regardless of the selected approach, you cannot create a hybrid cluster, which is a cluster that includes both
My webMethods Server instances, installed on premise regular servers/VMs and instances that run in Docker containers. When adding a new cluster node that runs either in a container or from an on-premise installation,
My webMethods Server checks whether the node type matches the cluster type, and shuts down the node if the validation fails.
You cannot run containers with different
My webMethods Server versions in the same cluster.
You cannot restart or shut down the cluster, or individual cluster members from the Cluster Administration page. Placing a node in maintenance mode from the
Cluster Administration page overrides the maintenance configuration from the image or the
/MWS/volumes/configs/instance_cfg directory (if available) on container restart.
When using Kubernetes for clustering, you should define the
My webMethods Server using
StatefulSet and
Ingress objects.