Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Configuration with multiple remote administration servers

&pagelevel(5)&pagelevel

Complex configurations can also be defined in which remote administrators access multiple remote administration servers.

The figure below shows an example of this.

Separate configuration with two remote administration servers

Areas A and B are theoretically strictly separated, but Jack is permitted to administer instances from areas A and B, whereas Curt can only administer instances from area B.

The same method can also be used to define a redundant configuration with a second remote administration server. This allows implementation of a simple backup solution.

Redundant configuration with a second administration server as a backup.

If Computer 1 fails, the remote administrator can use Computer 2 as the remote administration server. In order to do this,

  • the ADM administrator must always ensure that the configuration data on the two computers is consistent,

  • the admission profiles for accessing the remote administration server and the partner list entries (if they are used) are identical on Computer 1 and Computer 2,

  • the admission profiles on the administered instances are defined in such a way that they accept both remote administration servers as partners.

If authentication is used, you must also note that

  • the keys for the computers from which administration is performed must be present on both remote administration servers,

  • the administered instances require the keys of both remote administration servers.

For this reason, with complex configurations in particular, you should implement failsafe protection of the remote administration server using a cluster. You can find examples of how to set up a cluster in the manual "openFT (Unix and Windows systems) - Installation and Operation".