NGASI AppServer Manager has the optional feature of managing
remote servers directly from one installation of
NGASI AppServer Manager. The benefits here is obviously the time and
effort saved from central management within a multi-server Cloud
environment. The first step would be to add Remote Server(s)
as described below.
In order to interact with the remote server, NGASI AppServer Manager
requires the password or Public/Private Key for the root system of the
remote user. The SSH protocol is used for communication.
NGASI AppServer Manager uploads and install a lightweight program
used for interacting back and forth.
The default location of the package is /usr/saase/.
If the package or NGASI AppServer Manger is installed other than the
default location, please add the following entry to
wsportal.properties file:
saase=<PATH>/saase/
To add Remote Servers to the Remote Server List,
Login to NGASI AppServer Manager as admin user.
Click the Remote Servers Tab 
.
Enter the appropriate information in the Form.
Click Save to add Remote Server 
with the appropriate information.
Key Based Authentication How-To:
Generated Public Key
If selected Generated Public Key based authentication method,
copy and paste the Public key info into the following file of the
Remote server:
/root/.ssh/authorized_keys2 (or /root/.ssh/authorized_keys)
NOTE create directory /root/.ssh if not exists and set directory
privilege to 700.
Also set authorized_keys2 privilege to 600.
User Provided Private Key
The opposite to Public Key, submitted Private Key will be used for
authentication to the remote server.
This assumes a matching public key was already placed in the
/root/.ssh/authorized_keys2 (or /root/.ssh/authorized_keys)
file at the remote server.