{section}
{column}
h1. Introduction
When a topology is declared as [dynamic|Topology Configuration], several operating tasks can be done to modify the topology:
* move a running container from a sub-domain to another sub-domain,
* detach a running container from its current sub-domain.
{column}
{column:width=350px}
{panel:title=Operating a dynamic topology}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}
h1. Moving a container
{gliffy:name=Moving a container standalone}
h1. Detaching a container
Any container member of a dynamic sub-domain can be hot-detached at any moment. After detachment, the container is running in a dedicated standalone topology, ie. in a dedicated sub-domain of a dedicated domain.
{gliffy:name=Detaching a container|version=5}
The detachment is realized through the JMX API of the container to detach using the method '{{detachContainer}}' of the MBean '{{Topology}}'.
{column}
h1. Introduction
When a topology is declared as [dynamic|Topology Configuration], several operating tasks can be done to modify the topology:
* move a running container from a sub-domain to another sub-domain,
* detach a running container from its current sub-domain.
{column}
{column:width=350px}
{panel:title=Operating a dynamic topology}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}
h1. Moving a container
{gliffy:name=Moving a container standalone}
h1. Detaching a container
Any container member of a dynamic sub-domain can be hot-detached at any moment. After detachment, the container is running in a dedicated standalone topology, ie. in a dedicated sub-domain of a dedicated domain.
{gliffy:name=Detaching a container|version=5}
The detachment is realized through the JMX API of the container to detach using the method '{{detachContainer}}' of the MBean '{{Topology}}'.