Secondary gateway server installation is performed when a new server should be added to the existing deployment, when either a vendor or a customer primary server already exists.
This is often necessary in the following cases:
- Scalability, when some load should be distributed across multiple servers
- Access to the private network, for example for authentication or embedded terminal deployments. Because primary server doesn’t normally has access to the customer’s internal networks an additional server is required which will connect to internal authentication services (LDAP) or to printers on the Intranet.
To install secondary server the following options should be provided:
- Primary server address – this is the IP address or domain name of the primary server. It does not have to match any DNS names of the accounts.
- Account domain name – this field should be filled with the DNS name of the account to which this server will be attached to.
- API key – optional API key from the account settings, used for server registration. If left blank the default restricted API key will be used.
The installer will try to connect to the primary server and validate the entered information. If there is no connection or the specified account domain name is wrong the error message will be printed. If the entered details are valid installation will proceed.
After the secondary server starts it will attach itself to the specified account. It will be possible to see it under the tree on the left side of the web UI.
By default, secondary servers are “not trusted” by a primary server. So after adding the secondary server, go to the server's Server information and click Authorize to allow the secondary server to establish a secure connection to the primary server.