Adding the Tomcat Virtual Platform to a gHN

From Gcube Wiki
Jump to: navigation, search


The Tomcat Virtual Platform can be deployed on a gHN by uncompressing the related archive inside the $GLOBUS_LOCATION//virtual-platforms folder:

tar -zxvf org.gcube.vre-management.virtualplatform-tomcat-X.tar.gz

This will create a $GLOBUS_LOCATION//virtual-platforms/Tomcat6 folder with the resources needed to enable the Tomcat 6 platform. Afterwards, the tar.gz archive and the doc folder (also created by the command above) should be removed.

gHN Configuration

Download, install and configure a Tomcat 6.0.X instance (tests have been made with version 6.0.32).

Then next step is to add a user with the privileges needed to perform deployments on the instance. This is done by adding the following lines to the $CATALINA_HOME/conf/tomcat-users.xml file:

 <!-- other config settings -->
 <role rolename="manager-gui"/>
 <role rolename="manager"/>
 <role rolename="manager-script"/>
 <user username="USERNAME" password="PASSWORD" roles="manager-gui,manager,manager-script"/>

where USERNAME and PASSWORD are chosen by the Site Manager.

After the configuration, the instance must be started with the following command:


Do note that the Tomcat 6 instance can be hosted on any machine, not only on the one hosting the Tomcat Virtual Platform. This is because the interaction between the two are performed with a network protocol (HTTP).

Platform Configuration

The final step is to configure the Tomcat Virtual Platform for interacting with the Tomcat 6 instance.

In the $GLOBUS_LOCATION//virtual-platforms/Tomcat6 folder, the file has to be edited for a proper configuration. Some of the settings reported in the file do not be touched and left with their default values, other must be filled.

The parameters to set are:

  • BaseURL: the host and port on which the Tomcat instance to bridge has configured to run
  • User: a valid username holding the roles of manager-gui, manager and manager-script
  • Password: the password for that username

The following example shows an example of configured file:


Verifying the Installation

If everything was properly configured, following a gHN restart, the gHN profile reports the availability of the Tomcat Platform as follows:

     <!-- ... -->


  • If the platform does not appear in the gHN profile, possible causes are:
    • the Tomcat instance is down
    • the Tomcat instance is running on a different port than the one indicated in the
    • the hostname is wrongly reported in the

  • If the deployment of web applications with gCube does not work, double check the hostname and password of the privileged user. They can be verified by logging in the Manager Service of the Tomcat instance available at http://BaseURL/manager/html

  • Troubles with deployments and undeployments with gCube can be verified in the Manager Service of the Tomcat instance available at http://BaseURL/manager/html. Here available web apps are listed and can be managed. However, it is strongly not recommended to manage applications from the Manager Service as this may cause misalignment with the gHN local state.