{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
Both a container of an autonomous topology and a container member of a more complex topology can be attached to another existing topology.
{gliffy:name=Moving a container standalone|align=center|border=false|version=5}
The attachment is realized through the JMX API of the container to move using the method '{{attachContainerTo}}' of the MBean '{{Topology}}' with the following parameters:
* a container member of the target sub-domain,
* the topology pass-phrase of this remote container.
During the attachment process, the container attached is reconfigured to use the registry of the target sub-domain. After the attachment, the endpoints of the container moved are available in the target topology, and no more available in the initial topology.
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|align=center|border=false|version=5}
The detachment is realized through the JMX API of the container to detach using the method '{{detachContainer}}' of the MBean '{{Topology}}'.
After the detachment, the endpoints of the container are no more available in the initial topology. They are moved in the new one.
{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
Both a container of an autonomous topology and a container member of a more complex topology can be attached to another existing topology.
{gliffy:name=Moving a container standalone|align=center|border=false|version=5}
The attachment is realized through the JMX API of the container to move using the method '{{attachContainerTo}}' of the MBean '{{Topology}}' with the following parameters:
* a container member of the target sub-domain,
* the topology pass-phrase of this remote container.
During the attachment process, the container attached is reconfigured to use the registry of the target sub-domain. After the attachment, the endpoints of the container moved are available in the target topology, and no more available in the initial topology.
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|align=center|border=false|version=5}
The detachment is realized through the JMX API of the container to detach using the method '{{detachContainer}}' of the MBean '{{Topology}}'.
After the detachment, the endpoints of the container are no more available in the initial topology. They are moved in the new one.