|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (3)
View Page Historyh1. Moving a container
{gliffy:name=Moving a container standalone}
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|version=2}
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.
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