Secure Global Desktop 4.31 Administration Guide > Clients and webtops > Relocating the browser-based webtop to your own JSP container

Relocating the browser-based webtop to your own JSP container

The browser-based webtop is a JavaServer Pages (JSP) application which you can relocate to your own JSP container. The JSP container can be on the same host as Secure Global Desktop or on a different host.

Note You can't relocate the classic webtop.

To use your own JSP container, the container must support:

• Version 2.2 of the Java Servlet specification.
• Version 1.2 of the JavaServer Pages specification.

Note Once you relocate the webtop to your JSP container, you have to manually upgrade the webtop by following the above steps for each new release.

To relocate the browser-based webtop:

1. Re-configure the ports used by the Secure Global Desktop Web Server.
   • If your web server/JSP container is on the same host as Secure Global Desktop, you may have to re-configure the ports used by the Secure Global Desktop Web Server.
   • The Secure Global Desktop Web Server may be listening on the standard HTTP or HTTPS ports (80/tcp or 443/tcp), depending on the ports selected when you installed Secure Global Desktop. You need to configure your web server to listen on ports 80/tcp or 443/tcp and configure the Secure Global Desktop Web Server to use different ports (by editing the /opt/tarantella/webserver/apache/version/conf/httpd.conf file).
   • The Tomcat component of the Secure Global Desktop Web Server uses port 8005/tcp and 8009/tcp. If these ports are used elsewhere, for example by your JSP container, you must change the Tomcat configuration. Edit the /opt/tarantella/webserver/tomcat/version/conf/server.xml file and change the server shutdown port (port 8005/tcp) and the Coyote/JK2 AJP 1.3 Connector port (8009/tcp).
2. Copy the webtop web application to your JSP container.
   • Copy all the files in the following directories into the web applications directory on the new host:
     • /opt/tarantella/webserver/tomcat/<version>/webapps/sgd
     • /opt/tarantella/webserver/tomcat/<version>/webapps/axis

     Note These directories contain symbolic links, make sure you preserve the links when you copy the directories.

3. Copy the required library and class files.
   • The browser-based webtop requires some additional library and class files, which must be copied to your container.
   • Copy the following Jar files from the /opt/tarantella/webserver/tomcat/<version>/common/lib directory to the global library directory on your container:
     • axis.jar
     • commons-discovery.jar
     • commons-logging.jar
     • jaxrpc.jar
     • saaj.jar
     • xerces.jar
   • Copy the following class files from the /opt/tarantella/webserver/tomcat/<version>/common/classes directory to the global class directory on your container:
     • com/tarantella/tta/webservices/client/listener/SSListener.class
4. Configure the web services endpoints.
   • The browser-based webtop uses the SOAP protocol (over HTTP) to access the services provided by a Secure Global Desktop server. The browser-based webtop uses a Resources.properties file to determine which server and port to send the web services requests to. This is currently set to http://localhost.
   • Edit the Resources.properties file in the sgd/WEB-INF/classes/com/tarantella/tta/webservices/client/apis directory on the new host. Replace http://localhost:port with http://server:port where server is the DNS name of a Secure Global Desktop server and port is the port that the Secure Global Desktop Web Server listens on. Do this for each of the web services listed in the properties file.
   • If the webtop has been relocated to a different host or you are using Secure Global Desktop security services, we recommend you secure the SOAP connections to a Secure Global Desktop server.
5. Restart your JSP container and the Secure Global Desktop Web Server.
   • You must restart your JSP container to apply the global library and class file changes.
   • If you made any configuration changes to the Secure Global Desktop Web Server, you must restart it (tarantella webserver restart) to apply the changes.
6. Log in to the relocated webtop.

Note If you are using third party authentication, you may also want to configure a new trusted user for the relocated webtop.

Copyright © 1997-2007 Sun Microsystems, Inc. All rights reserved.