Installation Guidelines
From Ogce
Contents |
OGCE Installation Guidelines
Overview
The OGCE portal combines portlets developed by the GridPort team at TACC and SDSU, the Extreme Lab, the Community Grids Lab at Indiana University, and tools and portlets from the Sakai Project. Grid access and high level programming APIs are provided by a portal-compatible version of the Java COG Kit.
Each of the various OGCE applications and services may be installed in your home directory. If you are system administrator, be sure not to run the applications as root. Create a user specifically for these applications, and be sure this user has ownership of all of them.
Each of the various OGCE applications and services (OGCE, Axis 2, GTLAB, Shindig Gadget Container) comes bundled with an Apache Tomcat Server. When you run startup.sh for any of the OGCE applications and services, the Tomcat Server is launched along with all of the necessary portlets. The OGCE uses port 8080 by default. Other services such as Shindig or Axis 2 use ports 7070 and 9090 by default respectively, so you may run all of these simultaneously. However, the GTLAB server also uses 8080, so you must change this to something like 8888 to run this also. These changes may be made in the ???? file.
Java issues
Be sure you have the $JAVA_HOME, $JRE_HOME, and $CLASSPATH environment variables specified for the user who runs the startup.sh scripts. They are typically something like /opt/SDK/jdk or /opt/SDK/jdk/jre/.
If you are using one of the applications requiring MySQL, be sure the jdbc drivers are installed with your Java installation so the OGCE services can communicate with and upate the database.
If you are getting unexpected errors when you try to start your server(s), it may be due to orphaned java processes. Check your processes with a command such as 'ps -elf | grep java' for example to see if you observe any orphaned java processes, and kill any you see. Then try starting your server again.
Throughout the online documentation you will see references to testing your installations using http://localhost/. If you are not running your web browser on the server, then you will need to substitute 'localhost' with your own server's domain name such as 'gw12.quarry.iu.teragrid.org'.
MySQL issues
Be sure you get the correct version of MySQL for your version of unix/linux. When you create your users, the generic SQL command to grant privileges to the various users such as xreg_ogce for the XRegistry database access or rps_dev for the Resource Prediction Service:
grant all on xregistry_ogce.* to 'xreg_ogce'@'%' identified by 'xreg_pass';
may need to be modified to be specific to the actual server being used in the pom.xml script, i.e.:
grant all on xregistry_ogce.* to 'xreg_ogce'@'gw12.quarry.iu.teragrid.org' identified by 'xreg_pass';
Thoroughly testing your various MySQL user's access to their respective databases at the command line is easy and essential to proper function of your portal services.
If possible, have PHPMyAdmin installed so you may have easy browser access to your database(s). This will allow you to easily check to see if your SQL scripts have run properly. If you are not the system administrator, submit a request to have access to it. Many administrators will be less reluctant than others, and it can't hurt to ask.
See this page to make sure that the database accepts external connections.
The first command is for localhost, obviously, and the second is for all external connections. You'll probably need to do this for other accounts that you create.
shell> mysql -u root mysql> SET PASSWORD FOR @'localhost' = PASSWORD('newpwd'); mysql> SET PASSWORD FOR @'host_name' = PASSWORD('newpwd');
Maven
What is Maven? Maven is a compiling utility that is used by the OGCE development team to compile the various grid portals and services that are part of the OGCE. Maven comes bundled with several of the OGCE tarballs, but you really only need one copy installed and the path added to your $PATH environment variable.
Parameter files: pom.xml
What is a pom.xml file?
(from the Maven web site)
"POM stands for 'Project Object Model'. It is an XML representation of a Maven project held in a file named pom.xml. When in the presence of Maven folks, speaking of a project is speaking in the philosophical sense, beyond a mere collection of files containing code. A project contains configuration files, as well as the developers involved and the roles they play, the defect tracking system, the organization and licenses, the URL of where the project lives, the project's dependencies, and all of the other little pieces that come into play to give code life. It is a one-stop-shop for all things concerning the project. In fact, in the Maven world, a project need not contain any code at all, merely a pom.xml."
The pom.xml file is a properties or parameters file where you modify certain values to conform to your local system configuration.
You will need to modify at least the following pom.xml files for the various portals and services used in the OGCE:
$HOME/ogce-portal-only/pom.xml (change one line containing the domain name of the web server)
$HOME/ogce-axis-services/pom.xml (change four lines containing domain name, database, database user, database user's password)
$HOME/GTLAB/pom.xml (change the portal server ip address
$HOME/ShindigOGCE/ishindig-trunk/pom.xml
