Next Topic

Previous Topic

Book Contents

Secure Remote Access Gateway

Configuration Files

etc/emerald.xml on Web Application
etc/emerald.properties on DGE

Description

The following section in etc/emerald.xml on the Web Application allows setting up a secure tunnel from the Web Application to a remote DGE or DGE extension and connect to a remote router or server using telnet, ssh, VNC or rdesktop.

<remote-access>
<enabled>true</enabled>
<port>7654</port>
<connection-pool>
<size>20</size> <!-- # of concurrent sessions -->
<start>11701</start> <!-- ports 11701 - 11711 -->
</connection-pool>
<idle-timeout>900</idle-timeout> <!-- 30 minutes -->
<session-timeout>21600</session-timeout> <!-- 6 hours -->
<jms-broadcast-topic>traverse_sshbroadcast</jms-broadcast-topic>
</remote-access>

On the DGE, the remote access section is in the etc/emerald.properties file.

## remote access
traverse.tools.sshClient=/path/to/ssh/client
traverse.tools.sshClient.extraParams=

If you have multiple IP addresses on the Web Application, external and internal, or inside a NAT network, then you need to let the DGE or DGE extension know the external (public) IP address or domain name of the server where Web Application is running. For this create/edit the plugin/site.properties file and add the following line:

traverse.tools.sshClient.webapp.host=webapp_server_ip

where webapp_server_ip is the IP address in dotted-quad or a domain name. If there is a firewall in front of this Web Application server, it will need to allow incoming traffic on TCP/7654.