Alexander Lukichev, Intel Corporation
Version 1.0 November 16, 2007
Version history
Version and date |
By whom |
Changes |
1.0 November 16, 2007 |
Alexander Lukichev |
updates for 1.5.2 |
Before installing GPE Portal Client you have to obtain its package. One possible option is to build it from the sources.
$ svn co https://gpe4gtk.svn.sf.net/svnroot/gpe4gtk/gpe4gtk/branches/1.5.0
$ cd 1.5.0/shared/build; mvn install
$ cd 1.5.0/shared; mvn install
$ cd 1.5.0/gtk4; mvn install
The portal client WAR can now be found in 1.5.0/gtk4/clients/portlet/target
.
Obtain a portlet container. One possible option is to download Apache Pluto bundled with Tomcat. After the
portlet container is downloaded, unpack it. Don't forget to set the appropriate CATALINA_HOME
environment variable.
Unpack the portlet bundle to the corresponding webapp location. For example for Pluto container this may look like:
$ cd $CATALINA_HOME/webapps
$ mkdir gpeportalclient && cd gpeportalclient
$ jar xvf gpe4gtk-portlet-client-1.5.2.war
The portlet container must be configured to include the installed portlet. Refer the portlet container manual for the deployment procedure.
Deploying to a Pluto container includes:
$CATALINA_HOME/webapps/pluto/WEB-INF/pluto-portal-driver-config.xml
Additional configuration steps must be performed before running the client:
The VO Credential Service (VOCS) is used for issuing proxy certificates to the registered users. The users provide
their Grid login and password during GPE Portal Client login stage (don't miss with the container login stage that may be
performed before!). The VOCS URL is defined at gpeportalclient/WEB-INF/potrlet.xml
with the parameter
VOCS_URL
.
The list of trusted CA certificates is used for establishing secure connections to the grid services. You should
place the trusted CA certificates in POM format to the gpeportalclient/WEB-INF/trusted
directory.
Run the portlet container. E.g. for Pluto container:
$ $CATALINA_HOME/bin/startup.sh