Table of Contents |
---|
...
Replacing TightVNC applet with noVNC in the client-premium webapp
Download the noVNC distribution package from: http://kanaka.github.com/noVNC
Note that this is the same package we used for the websockify
...
To replace the tightvnc applet without changing any code in Abiquo, we will need to rename tightvnc to back up this file and replace the tightvnc file with the noVNC one.
Code Block |
---|
ABIQUO 2.6 or below: # cp -r kanaka-noVNC-c2b1409 /opt/abiquo/tomcat/webapps/client-premium/ # cd /var/www/opthtml/abiquoui/tomcatlib/webapps/client-premium/remoteaccess/ ABIQUO 3.0: # cp -r kanaka-noVNC-c2b1409 /var/www/html/ui/lib/remoteaccess/ # cd /var/www/html/ui/lib/remoteaccess/ BOTH VERSIONS: # mv tightvnc tightvnc.old # mv kanaka-noVNC-c2b1409 tightvnc |
...
Note that the name of the extracted directory might change as new versions are released, as can the noVNC files. We will use the vnc_auto.html file from noVNC but with some changes. Place the tightvnc.html file under:
/opt/abiquo/tomcat/webapps/client-premium/tightvnc/ in Abiquo 2.6 and below
or
/var/www/html/ui/lib/remoteaccess/tightvnc/ in Abiquo 3.0
Now you will need to edit this file to suit your environment. Edit the file and change the following values to contain the websockify public IP and port the proxy will be listening on:
host = "8.8.8.100";
port = 41337;
...
Tip |
---|
Note that if you use a balancer for your websockify proxies, you need to edit the tightvnc.html file in client-premium webappto point to the IP and port of the balancer. |
...