E-mail
IntroductionWhen a topology is declared as dynamic, several operating tasks can be done to modify the topology:
|
Operating a dynamic topology Contributors
No contributors found for: authors on selected page(s)
|
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.
|
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.
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.
|
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.