Grid Grouper Installation Guide
Grid Grouper: Administrators Guide | Developers Guide | caGrid: Documentation Guides
Overview
This guide provides step by step details on how to install and configure Grid Grouper version 1.4.
Prerequisites
In order to install and run Grid Grouper, the following prerequisite software must be installed:
Step 1: Install caGrid/Grid Grouper
In this step you download and install Grid Grouper using the caGrid Installer. If you already have caGrid 1.4 installed on your machine, proceed to the next step. To install caGrid/Grid Grouper, do the following:
Installer Prerequisites
The caGrid Installer installs all prerequisites except for Java and MySQL.
- Java 6 JDK
- Make sure the JAVA_HOME environment variable is set and points to the location where the JDK has been installed.
- (Optional) If you are deploying caGrid core services locally, you may also need a MySQL database
.

Note
MySQL is only required for the security services and GME. You can use 4.x (with transaction enabled; i.e., use InnoDB engine) or 5.x.
Installing caGrid 1.4 Using the Installer
| Internet Resources Required by the Installer Unless you are using a customized installer, the installer will need to be able to access these internet resources:
|
- Download the caGrid 1.4 Installer, unless you have a customized installer that you have been instructed to use for your grid. The downloaded installer should be contained in the file caGrid-installer-1.4.zip. If you are using a customized installer the name may vary.
- Unzip the file caGrid-installer-1.4.zip. This creates the directory caGrid-installer-1.4. This documentation refers to this directory as CAGRID_INSTALLER_LOCATION.
- From a command prompt, launch the installer using the following command:

Do not launch the installer by double-clicking the jar file 
> cd *CAGRID_INSTALLER_LOCATION*
> java -jar caGrid-installer-1.4.jar - Select the I agree to this license checkbox and then click Next.
- Select the Install/Configure caGrid Software checkbox and then click Next.
- The installer detects whether or not you have already installed Ant
. It installs or reinstalls it, depending on your installation status. In either case, you must specify the location where you want to install Ant.
- The installer detects whether or not you have already installed Globus
. It installs or reinstalls it, depending on your installation status. In either case, you must specify the location where you want to install Globus.
- The installer asks you for a location on your local file system to install caGrid. Specify a location to install caGrid and click Next.

To select a file location that is not in the User's Home directory, Click the Look In: drop down list and select a new starting location. - The installer displays a list of tasks that the installer will perform. Click Next to begin the installation process. At this time the installer downloads, builds, and installs several components. This process takes several minutes.
- Once the installer has completed installing all the components, click Next.
- The installer prompts you to specify which Grid you want to configure your installation to use. The installer supports configuring caGrid to work out of the box with many community Grid environments. For testing and development purposes, we recommend selecting the Training Grid. If you do not want to configure caGrid to work with an existing Grid you may select that as well. The installer can also be modified to support additional Grids.
- The installer shows a summary of the tasks to be completed. Click Next to configure caGrid to use the selected target Grids. This process takes several minutes.
- Once the installer has finished configuring caGrid to use the target Grid, click Next. The final screen reminds you to set your ANT_HOME and GLOBUS_LOCATION environment variables. Set these variables immediately and click Finish.
Congratulations! You have successfully installed caGrid.
| Add ANT_HOME/bin to PATH You will be running the ant program from the command line so add ANT_HOME/bin to PATH. |
Step 2: Obtain Host Credentials
Grid Grouper requires that it runs as a secure service. In order to run a secure service, the container hosting the service must run with a host credential. A host credential consists of an X.509 certificate and private key. In a production environment it is very important that this credential be issued by a certificate authority trusted by your environment. For the purposes of this guide we will provide instructions on how to obtain a host credential from Dorian. Dorian is an open source service framework for issuing PKI credentials and is a trusted certificate authority in many Grid environments. Most target grids (selected in the last step) are configured with one or more Dorian instances. This guide will provide documentation on requesting a host credential from the Training Dorian. Similar steps can be used for requesting a host credential from other Dorian instances.
|
Requesting a host credential from the Training Dorian requires an account. Any user may request an account from the Training Dorian. If you have an account with the Training Dorian, please complete the steps below to get a host credential. If not, click here for directions on requesting an account, and then return to this page to proceed with the steps below:
|
Immediately after clicking the Request Certificate button, the UI will submit the host certificate request to Dorian. Upon receiving the request, Dorian will either immediately approve the request or submit the request to an administrator for approval. In the case where the request is immediately approved, the host credentials (certificate and private key) will be written to the directory specified. The file containing the certificate will be named THE_HOSTNAME_YOU_ENTERED-cert.pem,. The file containing the private key will be named THE_HOSTNAME_YOU_ENTERED-key.pem.
In the case of a host certificate request requiring approval from an administrator, the file containing the private key will be named THE_HOSTNAME_YOU_ENTERED-key.pem. The host certificate WILL NOT be written since it is not issued until the request is approved. You will need to wait for an administrator to approve your request before proceeding forward. The GAARDS UI provide a means of checking the status of your request. For directions on how to do this click here.
| Please take note of the locations where the host certificate and private key were written. These will be needed later to configure the container. |
Step 3: Configure a Secure Container
In this step we will configure a web service container that will host Grid Grouper. Grid Grouper can be deployed to the Tomcat, JBoss, and Globus containers. This guide will provide detailed instructions for how to use the caGrid Installer to install and configure a secure Tomcat container. You will need to supply the installer with the host credentials created in the last step.
- From a command prompt, launch the caGrid Installer:

> cd \ CAGRID_INSTALLER_LOCATION
> java -jar caGrid-installer-1.4.jar - Select the I agree to this license box and then click Next.
- Select the Install/Configure Grid Service Container box and then click Next.
- Select the Container to which you want to deploy your service. Because this guide will use a secure Tomcat, select the Should this container be secure? box and then click Next.
- In the hostname box, enter the hostname of your server. This should match the hostname you used when you created your host credentials. Click Next.

If you plan on using this container to deploy a service that registers to an existing grid, it is important that you use a publicly resolvable DNS name (or static IP). Otherwise, you will need to manually edit configuration files later to correct this. - From the Obtain host credentials method list, select the option that applies to your situation and click Next.

Options: - If you do not yet have credentials for your service, select Use GAARDS to obtain host credentials.
- If you have host credentials that are not in the default location, then select Browse to host credentials on the file system.
- If you have host credentials that are in the default location, then select Host credentials are already installed.
Default credential location:
- On Windows, this will be a path like "C:\Documents and Settings\<USERNAME>\.cagrid\certificates".
- On Linux/MAC this will be a path like "/Users/YOUR_USERNAME/.cagrid/certificates".
- If you selected Browse to host credentials on the file system, the next screen will prompt you for the location of your credentials. Enter the location of your host certificate in the Certificate text box. Enter the location of your private key in the Key text box. Click Next.
- The next screen asks where you want to install Tomcat. Enter that location in the Directory text box and click Next.
- A list of tasks appears that the installer will perform in order to install and configure Tomcat. Click Next.
- Once the installer has completed installing all of the components, click Next.
- Click Next. The final screen reminds you to set your ANT_HOME, GLOBUS_LOCATION and CATALINA_HOME environment variables. Set these variables immediately and click Finish.
Congratulations! You have successfully installed and configured your Tomcat container.
Step 4: Configure Grid Grouper
To configure Grid Gouper, specify the database information for your MySQL database. This is specified in the configuration file, GRID_GROUPER_HOME/resources/conf/grouper.hibernate.properties. To configure the database information for grid grouper, open the file GRID_GROUPER_HOME/resources/conf/grouper.hibernate.properties and edit the following properties:
| Property |
Description |
|---|---|
| hibernate.connection.url | The connection URL for the Mysql database (this includes the name of the database) |
| hibernate.connection.username | The username of the database user |
| hibernate.connection.password | The password of the database user |
Step 5: Initialize Grouper Database
In this step, create and initialize the Grid Grouper database. To create the database, please type the following from the command line:

> mysql -u YOUR_DATABASE_USER -p
Enter password: YOUR_DATABASE_PASSWORD
create database grouper;

> cd GRID_GROUPER_HOME
> ant grouperInit
Step 6: Configure Default Storage Engine for MySQL
The default storage engine for MySQL, MyIASM, cannot handle a large number of concurrent write operations in a short amount of time, thus creating the need to change the storage engine of the Grouper tables to InnoDB. InnoDB was developed to handle a larger number of transactions.

> cd GRID_GROUPER_HOME/resources/sql
> mysql -u YOUR_DATABASE_USER -p
Enter password: YOUR_DATABASE_PASSWORD
mysql> use YOUR_DATABASE;
mysql> source set_innodb_engine.mysql.sql;
mysql> quit
Step 7: Configure Collation setting for MySQL
The default collation setting for MySQL is latin1_swedish_ci. This collation is case insensitive. This command will change the setting on a single column in the member table. This is to prevent mistyped grid identities from appearing in GridGrouper.

> cd GRID_GROUPER_HOME/resources/sql
> mysql -u YOUR_DATABASE_USER -p
Enter password: YOUR_DATABASE_PASSWORD
mysql> use YOUR_DATABASE;
mysql> source set_collation.mysql.sql;
mysql> quit
Step 8: Add Initial Administrator
Grid Grouper must be initially provided with at least one administrator. Grid Grouper provides a command line tool for bootstrapping GridGrouper and initially adding administrator(s). To leverage this command line utility, type the following from a command prompt:

> cd GRID_GROUPER_HOME
> ant addAdmin
Step 9: Edit Service Metadata
Grid Grouper provides service metadata to clients and other services that describe information about the service, operations supported by the service, and information on the organization hosting the service.
Edit the service metadata to reflect your organization as follows:
- Open the Grid Grouper service metadata file GRID_GROUPER_HOME/etc/serviceMetadata.xml.
- In the hostingResearchCenter element near the bottom of the file, do the following:
- Supply ResearchCenter infomation.
- Supply Address. This is the address that is used when mapping your service on the caGrid Portal.
- Supply the PointOfContact. This is the person responsible for maintaining the service.
A completed example:
<ns1:hostingResearchCenter> <ns53:ResearchCenter displayName="Ohio State University" shortName="OSU" xmlns:ns53="gme://caGrid.caBIG/1.0/gov.nih.nci.cagrid.metadata.common"> <ns53:Address country="US" locality="Columbus" postalCode="43210" stateProvince="OH" street1="3190 Graves Hall" street2="333 W. 10th Ave."/> <ns53:pointOfContactCollection> <ns53:PointOfContact affiliation="OSU" email="John.Doe@osumc.edu" firstName="John" lastName="Doe" phoneNumber="(555) 555-5555" role="Maintainer"/> </ns53:pointOfContactCollection> </ns53:ResearchCenter> </ns1:hostingResearchCenter>
| Note By default, Grid Grouper registers with and publishes its service metadata to the Index Service. The default Index Service is configured as the Index Service of the target grid you selected when you installed Grid Grouper. You can find configuration details about registering and publishing to the Index Service, including disabling registration and changing which Index Service with which to register, on the Registration and Discovery page. |
Step 10: Deploy Grid Grouper
At this point we have completed configuring Grid Grouper and the Tomcat container Grid Grouper will run in. We are now ready to deploy Grid Grouper to the Secure Tomcat Container. This can be done from a command prompt:

>cd GRID_GROUPER_HOME
> ant deployTomcat

> cd GRID_GROUPER_HOME
> ant deployJBoss

> cd GRID_GROUPER_HOME
> ant deployGlobus
Step 11: Verifying the Installation
Once you have deployed Grid Grouper, you have completed the installation and configuration of Grid Grouper. Next we will verify that the installation was successful. Before doing so, however, we must first start the Grid Grouper service. This is done by starting the container where the Grid Grouper was deployed. To start a secure Tomcat container, run the start-up script (startup.sh or startup.bat) located in CATALINA_HOME/bin. Please check the Tomcat log files (CATALINA_HOME/log/catalina.out) to ensure that there are no errors or stacktraces and that the container successfully started and bound to the port you specified during the installation. Once the container has started, verify that the Grid Grouper installation was successful. To accomplish this use the GAARDS UI, which is a graphical user interface for administering security services such as Grid Grouper. Specifically, verify that the administrators group was successfully created and that the initial administrators of the group were added. In order to accomplish this, first configure the GAARDS UI to be able to communicate with the Grid Grouper just instantiated. To accomplish this, please complete the following steps:
|
Type the following from a command prompt: $ cd GAARDS_UI_HOME $ ant ui
Next we must login as one of the initial administrators created earlier. To accomplish this, complete the following steps:
Next, verify that you can view the administrators group for Grid Grouper. To accomplish this, complete the following steps:
This lists all the members of the grid grouper administrators group in the table below the Search button. You should see the grid identity of the initial administrator you added earlier through the command line.
|





