This user guide provides a brief introduction about the Secure Global Desktop (SGD) portlet and explains how you can install and configure SGD portlet in Portal Server 7.2.
The SGD portlet adheres to the JSR 168 standard for writing portlets and aims to securely access and transfer information between SGD and Portal Server using SRA. The SGD portlet uses Single Sign-On mechanism and enables to launch Webtop sessions from within a portlet.
The SGD portlet can be configured by setting the following preferences.
Install Sun Java System Portal Server version 7.1 or above.
Install SGD Server version 4.2.x or 4.3.x.
Deploy SGD portlet.
Login to Portal Server console and create a channel for SGD portlet.
Edit the portlet properties and set the preferences as mentioned below.
The Portals page appears.
The Desktop Tasks and Attributes page appears.
The Deploy Portlet wizard appears.
The Enter the Portlet WAR and Portlet Deployment Information page appears.
The Verify Information page appears.
The Results page appears.
The Manage Containers and Channels for the Portal that you have selected (portal 1) appears.
The WorkContainer specific tasks and properties appear in the right pane.
The New Channel or Container wizard appears.
The Specify Channel Type page appears.
The Specify Provider/Portlet/Producer Name page appears.
The Specify Channel Name page appears.
The Review page appears.
The Results page appears. A message appears that a new channel has been created.
The new channel is created and listed under the WorkContainer in the left pane of the Manage Containers and Channels for portal 1 page. The right pane displays the Tasks, Portlet Preferences, and Properties for the new channel.
For example, if you want to configure for access.indigo-insurance.com, using HTTPS on port 8080, the format is https://access.indigo-insurance.com:8080/axis/services/rpc/.
Note - This URL is used by the web services client of the portlet. So, you can use the DNS name and port that are appropriate for resolution and connection from the host running the portal application.
Set the sgdaccess value provided in the tomcat-base/webapps/sgd/WEB-INF/classes/com/tarantella/tta/webservices/client/views/Resources.properties file on your SGD server. The sgdaccess value format looks something similar to this c2dkX3RydXN0ZWRfdXNlcjpJcSxnVDBHI2I0LVlxYUZAeFRkSA==.
Note - The sgdaccess preference is optional. If you do not set this preference, set incorrectly, or if the third party authentication is disabled in Secure Global Desktop server, you will be provided with the standard SGD login, form where you can choose to save the SGD credentials for automatic login later.
Note - This preference is for advanced use. Usually, the Tarantella Client is downloaded directly from the SGD Web Server by the web browser.
For example, if the Netlet was listening on port 5555, the tcc-sra-proxy-route attribute will be CTSOCKS:localhost:5555 or if SOCKS proxy is not used, then it is CTTTAP:localhost:5555.
Follow the steps to create and configure a static Netlet rule.