Click the navigation item Nodes Instances in the Domain section of the navigation. An overview of all node instances that are assigned to the current domain is displayed.

Figure: Overview of Node Instances

On this Page:

In the screenshot above, e2ebridge.e2e.ch is the only node instance in domain Education. If only one node instance exists in a domain, the Bridge installation can be converted back to a stand-alone installation by clicking the button Convert to Standalone. Domain Education and all user and group information of the domain will be deleted.

Deployed services will not be removed in this case.

Importing a Bridge Node Instance

The domain can be expanded by importing other node instances. You can only import node instances that are not already included in another domain. Click Import Node Instance to import a node instance into your domain.

The form for importing a node instance will be displayed.

Here, you should enter the following:

  • Enter the node instance name or the IP address of the host you want to import.
    When entering the node instance name, use the fully qualified domain name (FQDN). For example, given a node instance with name myhost and domain name example.com , the fully qualified domain name is myhost.example.com .
  • Enter a port number, the Bridge will listen to.
    The default E2E services port number 8080 is suggested. You need to enter the port number that was defined during the Server installation on the node instance you want to import.
  • Enter the Console service password of the node instance you want to import.
    You defined this password when you installed the Bridge on the node instance you now want to import. Do not enter the Console service password of the Bridge installation you are currently working with, or the password of the user admin.

  • Click Import Node Instance to import the node instance into the domain. You may also Cancel the operation.

Users and groups are shared between node instances of a domain. If you import a node instance into a domain, the user admin of the domain is also shared with the imported node instance.

Example: Suppose, node instance A, which is member of a domain, is importing node instance B into the domain. B is having a pre-defined user admin, whose password was initialized during the installation. After successfully importing B into the domain, you cannot login to B with its former user admin password anymore. You need to use the admin password of the domain B was imported to.

When importing a node instance into a domain, make sure not to use the administrator password of the imported node instance for future logins.

The Console service password will never be changed.

After importing the node instance successfully, the updated list of all node instances belonging to the domain is displayed. You can import further node instances, or you can remove other members of the domain, except the node instance of the Bridge you are currently working with (which is the one on e2ebridge.e2e.ch in the example below).

Whenever you are importing or removing a node instance, or managing a user or a group, all mutations are distributed to all node instances of the domain. Hence, each node instance knows the same as another member of the domain. If a node instance within a domain cannot be connected for some reason, all mutations are blocked, until all node instances are accessible again in this domain. Mutations of composite services are not blocked. You can still work with services of all accessible node instances.

Figure: Overview of Node Instances after Import of an Instance

Removing a Bridge Node Instance from a Domain

Each node instance that is being removed will be converted to a stand-alone installation. You cannot remove the node instance you are currently working on, so you need to use the Bridge of another node instance to remove your current node instance. If the node instance you want to remove is not available anymore you can force the removal of it. In this case, the removed node instance will not be converted to a stand-alone node.

In order to remove a node instance from a domain, click the corresponding Remove  button.
You need to confirm the removal of the node instance by clicking the button Remove Node Instance on the following page. You may also Cancel the transaction.

Deployed services will not be removed on removal of a node instance from an Bridge domain.

After a node instance has been removed from a domain, every remaining node instance gets informed that the removed node instance is not a member of the domain any longer.
There might be situations that a connection to a node instance cannot be restored anymore, because the machine has been disposed for instance. The disconnected node instance would be displayed as stopped node instance in the node instances list. If you want to remove such a disconnected node instance, you need to select the option Force Removal. The forced mutation is also distributed to the other members of the domain.

  • No labels