Open Grid Computing Environments

GCE11 Workshop Paper Submission Deadline Extension

2011-09-26T12:37:00.001-07:00

Papers for the GCE11 workshop at Supercomputing 2011 can be submitted through October 3rd, 2011. See http://www.collab-ogce.org/gce11 for more details.

OGCE Workflow Tools Now in Apache Airavata

2011-09-08T13:57:00.000-07:00

The OGCE's tools for managing scientific applications and workflows on grids and clouds are now the Apache Airavata incubator project. Community contributions are welcome, and you can become part of the project. We are now following the Apache Software Foundation model for building open source communities.

GCE11 Workshop

2011-07-27T17:28:00.000-07:00

The Gateway Computing Environments 2011 workshop will be at Supercomputing 2011. Submissions are open and welcome. See http://www.collab-ogce.org/gce11/index.php/Main_Page for more information.

Positions available

2011-07-27T12:04:00.000-07:00

The OGCE team at Indiana University has positions available. See https://jobs.iu.edu/joblisting/index.cfm?jlnum=4193&search=2 for more information. If you are interested, please apply through Jobs@IU. If you would like more information, contact Marlon: marpierc [at] indiana edu.

OGCE Gadget Container GridShib Support

2011-04-04T13:14:00.000-07:00

The OGCE gadget container now includes GridShib support as part of the default build. We use GridShib to decorate TeraGrid community security credentials with logging attributes: the authentication instant, the user's email address, the user's browser's IP address, and the user's gadget container user name. All installation and configuration steps are handled by the OGCE build process: "mvn clean install" handles the jar deployments and resource configuration files. Decorated credentials can be used or exported to other services.

GridShib is optional, and gadget container deployments not using it will work as normal.

OGCE Gadget Container Part of Apache Rave Incubator

2011-04-04T13:04:00.000-07:00

The OGCE Gadget Container is being contributed to the Apache Rave incubator project. The ultimate goal is to produce high quality software for running production Open Social containers. See http://wiki.apache.org/incubator/RaveProposal for more information. We will continue to develop the OGCE gadget container in the interim until Rave is ready to release. We will also extend the Rave core to accommodate the requirements of Science Gateways.

TG10 OGCE Paper

2011-01-19T12:13:00.000-08:00

The official version of our TeraGrid 10 paper, "Open grid computing environments: advanced gateway support activities", is now available through the ACM:

http://portal.acm.org/citation.cfm?id=1838590&CFID=6079067&CFTOKEN=84307850

OGCE SciDAC2010 Tutorial

2010-12-07T12:03:00.001-08:00

SciDAC 2010 tutorial slides.

OGCE SciDAC2010 Tutorial

View more presentations from marpierc.

OGCE TeraGrid 2010 ASTA Support

2010-12-07T12:02:00.001-08:00

Presentation on advanced support activities by the IU Science Gateway Group at TeraGrid 10 (accepted presentation).

OGCE TeraGrid 2010 ASTA Support

View more presentations from marpierc.

OGCE TeraGrid 2010 Science Gateway Tutorial Intro

2010-12-07T12:00:00.001-08:00

Tutorial intro slides at TG10 in Pittsburgh, August 2-5, 2010

OGCE TeraGrid 2010 Science Gateway Tutorial Intro

View more presentations from marpierc.

Building Science Gateways with Gadgets and OpenSocial

2010-12-07T11:36:00.001-08:00

Check out this SlideShare Presentation:

Building Science Gateways with Gadgets and OpenSocial

View more presentations from marpierc.

Twitter, SlideShare

2010-12-06T09:00:00.000-08:00

OGCE's Twitter feed is http://twitter.com/ogceproject. We have many slide presentations at SlideShare: http://www.slideshare.net/marpierc/presentations.

OGCE's XBaya Running a GridChem Workflow

2010-11-17T14:00:00.000-08:00

The movie shows the XBaya workflow composer creating and executing a computational chemistry workflow in the GridChem Science Gateway.

OGCE Demos and Presentations at SC10 in New Orleans

2010-11-10T07:03:00.001-08:00

Please stop by and see us at SC10 November 15-18 in New Orleans at the following times and locations:

We have a mini-workshop Tuesday from 10:00 am - 12:00 noon at the IU booth.
Monday-Thursday at the IU Booth, we have walk-up demos on demand at the interactive touch screen kiosk.
Monday-Thursday at the Purdue Booth, we also have on demand demos.
Wednesday from 1:00-2:00 pm, we have on demand presentations and demos at the NCSA booth.

GCE10 Program Now Available

2010-11-09T09:49:00.000-08:00

The GCE10 workshop program is now available from http://www.collab-ogce.org/gce10/index.php/Program. GCE10 is being held Sunday, November 14th at SC10 in New Orleans. Pre-prints and slides will be made available from the GCE10 web site.

GCE10 Deadline Extension

2010-08-30T12:45:00.001-07:00

The new submission deadline for GCE10 papers is September 13th. The call for papers is available from www.collab-ogce.org.

TG10 Tutorial Agenda

2010-08-01T08:09:00.000-07:00

Here is the agenda for the OGCE tutorial at TG10 on Monday, August 2nd. Tutorial material will be available for download.

1:00-2:15

Introduction
computational chemistry workflow demo
build demo

2:15-2:30: Break
2:30-5:00

Hands on demo of OREChem workflow (using XBaya composer)
Hands data mining tutorial (using XRegistry and Experiment Builder gadgets)
Gadget container overview

Agenda is subject to improvisation based on audience interest and participation.

Sample Build Instructions Movie for OGCE Portal and Services

2010-07-15T13:51:00.001-07:00

This link shows how to get the OGCE code base and build the portal and services: http://ogceportal.iu.teragrid.org/tutorials/CodeBuild.htm

GCE10 Workshop Accepted for Supercomputing 2010

2010-06-30T16:47:00.000-07:00

The Gateway Computing Environments workshop (GCE10) has been accepted at SC10. The workshop will be held in room 387 in the New Orleans Convention center on Sunday, Nov 14^th from 9-5:30. More details coming soon. For previous proceedings of this series, please see http://www.collab-ogce.org/gce10/index.php/Main_Page.

Condor jDRMAA Example

2010-06-03T21:28:00.000-07:00

Notes on using the DRMAA java implementation to submit Condor Jobs.

The Condor jDRMAA implementation can be downloaded from their sourceforge page using svn

svn co https://condor-jdrmaa.svn.sourceforge.net/svnroot/condor-jdrmaa

and use ant to build the jar or alternatively download the jar from

http://sourceforge.net/projects/condor-jdrmaa/files/condor-jdrmaa/0.2/condor-drmaa-0.2.jar/download

Version 0.2 uses the condor command line clients to submit and manage jobs.

Hence you must make sure that the condor binaries are on path and CONDOR_CONFIG is set if your Condor config file is not in /etc/condor.

The notes here pertain to Condor 7.4.2 on Mac OS X but should work on any platform that supports Condor and Java.

140-182-140-134:0.3 archit$ condor_version

$CondorVersion: 7.4.2 Mar 29 2010 BuildID: 227044 $

$CondorPlatform: I386-OSX_10_4 $

Here is the Java Class I used to perform the Job Submission.

Note that it is in the package org.ogce.jobsub.api

To replicate my setup do

mkdir -p org/ogce/jobsub/api

Create org/ogce/jobsub/api/DRMAAJobSubmission.java with the following using your favorite editor.

package org.ogce.jobsub.api;

import java.util.ArrayList;

import java.util.LinkedList;

import java.util.List;

import java.util.Set;

import org.ggf.drmaa.*;

import net.sf.igs.*;

public class DRMAAJobSubmission {

public static void main(String[] args) {

Session session = null;

String jobPath = "/bin/echo";

session = SessionFactory.getFactory().getSession();

String jobId = null;

JobTemplate jt = null;

JobInfo status = null;

ArrayList argslist = new ArrayList();

argslist.add("Hello");

try {

System.out.println(session.getDrmSystem());

System.out.println(session.getContact());

System.out.println(session.getDrmaaImplementation());

session.init("localhost");

jt = session.createJobTemplate();

jt.setRemoteCommand(jobPath);

jt.setWorkingDirectory("/tmp");

jt.setJoinFiles(true);

jt.setOutputPath("/tmp/hello.out" );

jt.setArgs(argslist);

jt.setTransferFiles(new FileTransferMode(false, false, false));

} catch (DrmaaException e) {

e.printStackTrace();

}

try {

jobId = session.runJob(jt);

status = session.wait(jobId, Session.DONE);

if (status.wasAborted()) {

System.out.println("job " + jobId + " never ran");

} else if (status.hasExited ())

{

System.out.println("job " + jobId +

"finished successfully with Exit Status "

+ status.getExitStatus());

} else if (status.hasSignaled ())

{

System.out.println("job " + jobId + " finished due to signal" +

status.getTerminatingSignal ());

} else

{

System.out.println("job " + jobId +

" finished with unclear conditions");

}

} catch (DrmaaException e) {

System.out.println("Internal Exception: " + e.getMessage());

e.printStackTrace();

}

catch (org.ggf.drmaa.InternalException ie)

{

System.out.println("Internal Exception: " + ie.getMessage());

ie.printStackTrace();

}

To Compile the file use

javac -cp ./condor-drmaa-0.2.jar org/ogce/jobsub/api/DRMAAJobSubmission.java

and to submit the echo job do

java -cp ./condor-drmaa-0.2.jar:. org.ogce.jobsub.api.DRMAAJobSubmission

This assumes you have the condor-drmaa jar in the current folder.

You should see something like

Condor

job 25.0 finished successfully with Exit Status 0

Session.init("localhost") call is used to initiate the Condor DRM adaptor and tell it to connect to the scheduler running locally.

The JobTemplate class is used to create the job description which gets translated into a condor submit file which is used as an argument to condor_submit.

The Session class has a number of static members that are used to indicate Job Status. The JobInfo class returned by Session.wait is used to retrieve the current status of the job after it has been submitted using the session.runJob method. Session.wait takes as its second argument the time until which the call must block. In this case the call blacks until the job Completes as indicated by Session.DONE.

In Order to specify job attributes not supported by the Getters and Setters we can use the setNativeSpecification method of the JobTemplate class.

So In order to submit a Condor-G job all we need to do is add the line

jt.setNativeSpecification("Universe=Grid \n globusscheduler=qb1.loni.org/jobmanager");

before submitting the job.

Please note that the attributes must be separated by a new line (\n) character so that the submit file is generated correctly. Also it must be noted that jDRMAA sets the Universe to Vanilla by default, but since the Native Specification is written in the submit file after the Universe=Vanilla line, it can be used to override the Universe setting.

Gadget Container, Registry, and Experiment Builder Movie Links

2010-05-18T08:41:00.000-07:00

The links below show movie tutorials for the OGCE Gadget Container and two major new gadgets in the "ogce-all" release described in the previous post.

OGCE Gadget Container: portal software for running secure Open Social gadgets: http://ogceportal.iu.teragrid.org/tutorials/Gadget_Container.htm
XRegistry Gadget: a gadget for registering host computers and scientific application services into the OGCE XRegistry service: http://ogceportal.iu.teragrid.org/tutorials/XregistryInterface.htm
Experiment Builder Gadget and XBaya Workflow Composer: the experiment builder gadget allows you to build, execute, and monitor experiments from services and workflow stored in XRegistry: http://ogceportal.iu.teragrid.org/tutorials/ExperimentBuilder.htm

OGCE "All" Release Candidate

2010-05-12T07:40:00.000-07:00

An initial release candidate of the next generation of the OGCE software stack is now available. The download is available by anonymous SVN checkout using the command.

svn co https://ogce.svn.sourceforge.net/svnroot/ogce/ogce-all-rc1

This is a preview release that will need to undergo additional acceptance testing, but it is stable for early users. Future updates can be obtained using the usual "svn update" command, and the release can be modularly rebuilt.

This download integrates several software components:

The OGCE Gadget Container: an iGoogle-style portal container for science gateways.
Experiment Builder and XRegistry gadgets for interfacing with the OGCE GFAC and XRegistry services and the XBaya workflow composer
XRegistery and GFAC services for registering, launching, monitoring, and sharing application services and workflows.
A collection of third party gadgets.

Everything can be built with a single command: mvn clean install. Maven profiles also allow you to build subcomponents:

mvn clean install -Dservices-only builds only GFAC and XBaya. These services can run on separate servers from the gadget container, and you can run more than one instance of these services.
mvn clean install -Dgadget-container builds just the gadget container.
mvn clean install -Dgadgets-and-clients builds the gadget container, registry gadget, and experiment builder gadget.

Updated TeraGrid CA Files

2010-04-28T13:32:00.001-07:00

(Reposting from general TeraGrid mailing lists)

Changes have been made to the list of Teragrid recognized Certificate Authorities.

The new CA tarball, v1.10, can be found on repo. This tarball adds the new PSC MyProxy CA, with hash value 4b2783ac. You can obtain a copy of the tarball and signatures file from the software WG site at:
http://software.teragrid.org/security/teragrid-certs.tar.gz
http://software.teragrid.org/security/teragrid-certs.tar.gz.asc

Please incorporate the new list as specified (RPs, Science Gateways and users within 24 hours)

New OGCE Discussion List, Google Group

2010-04-26T12:40:00.000-07:00

We have created a new, open group for OGCE discussion questions and announcements. The group URL is http://groups.google.com/group/ogce-discuss, and the group email address is ogce-discuss@googlegroups.com. This email address replaces the older discuss@ogce.org mailing list.

You are welcome to join, and we also allow anonymous viewing and moderated posts by group non-members. Only project managers can see the member list.

The project RSS feed is http://groups.google.com/group/ogce-discuss/feed/rss_v2_0_msgs.xml.

Build and Deploy to Maven2 Repo

2010-03-27T11:55:00.000-07:00

OGCE components use Maven2 for build and Archiva for repository management. For legacy reasons some dependencies are exist in extreme lab maven repository. To upgrade these components and release a version and deploy a jar file to extreme lab maven 2 repository, add the following distributionManagement tag to the pom.xml.

<distributionmanagement>
<repository>
<uniqueversion>false</uniqueversion>
<id>xRepo</id>
<name>Extreme Lab Repository</name>
<url>scp://mneme.extreme.indiana.edu/l/extreme/java/repository</url>
<layout>default</layout>
</repository>
</distributionmanagement>

mvn deploy will deploy the generated jar files to the repository but will prompt to enter the password and will also assume local account name. To avoid password prompt and to specify a different user name the following settings.xml can be placed in the $HOME/.m2 directory. For security reasons, never include the settings.xml in any of the packages, this file should be protected by file system security and is strongly advised to set the file permissions to 600.

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xsi="http://www.w3.org/2001/XMLSchema-instance" schemalocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<servers>
<server>
<id>xRepo</id>
<username>smarru</username>
<privatekey>${user.home}/.ssh/id_dsa</privatekey> 
<passphrase>some_passphrase</passphrase>
<filepermissions>664</filepermissions>
<directorypermissions>775</directorypermissions>
<configuration></configuration>
</server>
</servers>
</settings>

Gadget Container Theme Customization

2010-03-26T09:35:00.001-07:00

The OGCE gadget container has been updated to simplify theme customization. See http://www.collab-ogce.org/ogce/index.php/OGCE_Gadget_Container_Theme_Customization for more information.

OGCE Messaging Service Released

2010-03-17T06:06:00.000-07:00

We are pleased to announce the release of our Axis 2 based Messaging Service. This is a standalone publish/subscribe service that is also being integrated into the OGCE workflow suite.

For more information and download instructions, see http://www.collab-ogce.org/ogce/index.php/Messaging.

OGCE Simple Monitoring Script

2010-03-11T20:34:00.000-08:00

A simple perl based service monitoring script is available to check out from sourceforge svn at Service Monitoring Dashboard. This is a cleaned up version of the LEAD SOA Status Page authored by Suresh Marru and Marcus Christie.

The perl script periodically pings the registered services and if a service is done, sends an emails to the registered contacts. The scripts also writes our a html page with the following color convention:

Green - Service is up
Red - Service is down
Yellow - Request timed out (i.e., took longer than the default 20 seconds)

The OGCE Team has deployed and will maintain the script. The status of the services can be viewed at Monitoring Dash Board. All services are pinged every 10 mins and the page is refreshed. Additionally, XSUL based services are instrumented with finer details like uptime and total requests served. In the future Axis2 based services will also be explored for more instrumented data. OGCE hosted gateway (demo/tutorial) services as well as gateway services will be monitored. To add a service to the monitoring list, send an email to {smarru or mpierce} at cs.indiana.edu (Note that only project supported gateways will be monitored).

Gateways can checkout the script and deploy and maintain on their own servers. To add a service to the script, use the following template:

push (@services, {
$NAME => "OGCE Gateway Portal",
$ID => "OGCEPortal",
$URL => "https://ogceportal.iu.teragrid.org:8443/gridsphere/gridsphere",
$CONTACTS => [admin@gateway.org],
$GATEWAYS_R_US => $OGCE
});

The GATEWAYS_R_US is a variable to categorize the services. For instance, to generate a separate listing of OGCE Hosted Services and a list of Gateway Services. The perl script is commented to explain these terminologies. The documentation is very naive but will be enhanced more.

Questions or comments, email smarru at cs.indiana.edu

Overview of OGCE Science Gateway Support

2010-03-11T12:20:00.001-08:00

The slideshow below was presented at the Indiana University Pervasive Technology Institute and focuses on IU OGCE activities. For fuller overviews, see for example http://www.collab-ogce.org/ogce/index.php/Tutorials
OGCE's Advanced Science Gateway Support

View more presentations from marpierc.

Analytics Reports for OGCE Web Site

2010-03-10T07:46:00.000-08:00

Images below are from our Google Analytics traffic tracking from March 1, 2009-March 1, 2010. The first shows overall site traffic. The second shows global traffic sources. Click the image to see a larger version.

Download Java Server Faces Components for Amazon Cloud Services

2010-03-10T07:28:00.000-08:00

We have Amazon EC2 user interface components built with Java Server Faces available for download or SVN checkout.

The tar.gz version is available from http://ogce.svn.sourceforge.net/viewvc/ogce/ogce-amazon-gadgets/awsGadget.tar.gz?view=tar.

To check the code out from SVN, use the command

svn checkout https://ogce.svn.sourceforge.net/svnroot/ogce/ogce-amazon-gadgets/awsGadget

This will create a directory $HOME/awsGadget. To build the gadgets, use the command

mvn clean install -Dcatalina.home=/path/to/your/tomcat

For example, if you download (separately) Apache Tomcat 6.0.18 and put it in your awsGadget directory, you would run the command

mvn clean install -Dcatalina.home=./apache-tomcat-6.0.18/

Start your tomcat server and point your browser to http://localhost:8080/AWSGadget/index.jsp.

Note the login page requires your Amazon secret key, so you will need to run this over HTTPS. This code is provided as is under our usual SourceForge license.

OGCE Jira URL

2010-03-01T10:44:00.001-08:00

We are opening up our Jira project and bug tracking system for anonymous viewing. The URL is http://grids.ucs.indiana.edu:8080/jira.

Using GFac to wrap an application as a service

2010-03-01T07:03:00.000-08:00

Launching applications on Super Computers and managing the application during its lifetime and its output after it ends are challenging tasks. GFac aims at being able to provide simple GUI tools that can help launch and manage the application on remote supercomputers.

This post aims at serving as a quickstart to configuring a XSul based GFac persistent service.

The first step is to install GFac and XRegistry components. Good documentation to do this can be found on the OGCE web pages.

After the installation is complete set the GFAC_HOME environment variable to point to the GFac's target/dist-bin folder:

export GFAC_HOME=/Users/archit/ogce/ogce-xsul-services-1.0-RC1/sgfac/target/dist-bin

Now create a folder to house the configuration files that will be used by our service.

cd ogce-xsul-services-1.0-RC1/sgfac
mkdir helloworld
cd helloworld

Now use your favorite editor to create the three XML configuration files needed by GFac to start the persistent service namely the App description document, the host description document and service description document.

Application Description File helloworldapp.xml:

<ApplicationDescription xmlns="http://www.extreme.indiana.edu/namespaces/2004/01/gFac" xmlns:lead="http://www.extreme.indiana.edu/lead">
<applicationName
targetNamespace="http://www.extreme.indiana.edu/lead">HelloWorldApp</applicationName>
<jobType>single</jobType>
<project> <projectName>TG-XXXXXXXXXX</projectName>
<projectDescription>
TG staff
</projectDescription>
</project>
<queue>
<queueName>SERIAL</queueName>
<queueDescription>
BigRed queue
</queueDescription>
</queue>
<maxWallTime>30</maxWallTime>
<count>1</count>
<rslparm name="project">TG-XXXXXXXXXX</rslparm>
<rslparm name="queue">SERIAL</rslparm>
<deploymentDescription>
<hostName>
bigred.iu.teragrid.org
</hostName>
<executable>/N/u/tg-archi/BigRed/helloworld</executable>
<workdir>
/N/u/tg-archi/BigRed/gfactmp
</workdir>

<tmpDir>
/N/u/tg-archi/BigRed/gfactmp
</tmpDir>
<applicationEnv>
<name>FIRST_NAME</name>
<value>Archit
</value>
</applicationEnv>
</deploymentDescription>
</ApplicationDescription>

ServiceDescription file: helloworldsvc.xml

<ServiceMap xmlns="http://www.extreme.indiana.edu/namespaces/2004/01/gFac"
xmlns:lead="http://www.extreme.indiana.edu/lead">
<service>
<serviceName targetNamespace="http://www.extreme.indiana.edu/lead">HelloWorldService</serviceName>
</service>
<lifeTime>
<notAfterInactiveMinutes>-1</notAfterInactiveMinutes>
</lifeTime>
<portType>
<method stageOutputDataFiles="true" forceFileStagingToWorkDir="true">
<methodName>Run</methodName>
<application paramValuesOnly="true" useLEADNameListFile="true">
<applicationName targetNamespace="http://www.extreme.indiana.edu/lead">HelloWorldApp</applicationName>
</application>
<inputParameter>
<parameterName>lastname</parameterName>
<parameterType>String</parameterType>
</inputParameter>
<inputParameter>
<parameterName>inputfile</parameterName>
<parameterType>URI</parameterType>
</inputParameter>
<outputParameter>
<parameterName>friendCount</parameterName>
<parameterType>String</parameterType>
</outputParameter>
<outputParameter>
<parameterName>friendListFile</parameterName>
<parameterType>URI</parameterType>
</outputParameter>
</method>
</portType>
</ServiceMap>

Host Description File: bigred.xml

<HostDescription xmlns="http://www.extreme.indiana.edu/namespaces/2004/01/gFac" xmlns:lead="http://www.extreme.indiana.edu/lead">
<documentInfo>
<documentName targetNamespace="http://www.extreme.indiana.edu/lead">BigRed</documentName>
</documentInfo>
<hostName>bigred.iu.teragrid.org</hostName>
<hostConfiguration>
<tmpDir>/N/u/tg-archi/BigRed/gfactmp</tmpDir>
<globusGatekeeper wsGram="true">
<endPointReference>
https://gatekeeper.bigred.iu.teragrid.org:8443/wsrf/services/ManagedJobFactoryService
</endPointReference>
<jobmanagertype>Loadleveler</jobmanagertype>
</globusGatekeeper>

<gridFTP>
<endPointReference>gridftp.bigred.iu.teragrid.org:2811</endPointReference>
</gridFTP>
</hostConfiguration>
</HostDescription>

Create the service properties file:
Finally, create the GFac service property file: helloworld.properties. This will tell GFac where to get the service, application, and host description files you just made.
serviceMapFile = helloworld/helloworldsvc.xml
appDescFile = helloworld/helloworldapp.xml
hostDescFile = helloworld/bigred.xml
port = 12346
#Comment this to make Factory and Services starts up without https
#transportSecurity=true
#private key used by the GFac to connect to other services, and start https socket, if it is enabled
ssl.hostcertsKeyFile=/home/ogce/ogce-xsul-services-1.0-RC1/sgfac/target/dist-bin/conf/ogce_services_key.pem
ssl.trustedCertsFile=/home/ogce/ogce-xsul-services-1.0-RC1/sgfac/target/dist-bin/conf/trusted_cas.pem
registryURL=https://<yourip>:6666/xregistry?wsdl
#Ask Gfac to go to local mode, so it can work without credentails. Comment if you need a remote installation
installation=local
myproxyServer=myproxy.teragrid.org
myproxyUserName=XXXXX
myproxyLifetime=86400
myproxyPasswd=XXXXXX
#gfac.prefferedProvider=Local|Gram|WSGram|SSH|ResourceBroker
wsgramPrefered=true

Now with your JAVA_HOME and GFAC_HOME set start the persisitent HelloWorldService using the run.sh provided with GFac as foolows:

./run.sh helloworld/helloworld.properties

This will start the service on port 12345 and you are ready to submit HelloWorld jobs.

Web Server DNS Updates Complete

2009-12-17T08:26:00.000-08:00

The DNS entry for the host server of the OGCE and GCE Workshop websites has been updated. The usual URLs (http://www.collab-ogce.org, etc) should work correctly.

OGCE Web Site Problems

2009-12-16T14:40:00.000-08:00

We are changing the IP address of the Web server that virtually hosts the www.collab-ogce.org web site. You can access the OGCE site with this URL:

http://gf18.ucs.indiana.edu/ogce/index.php/Main_Page

The GCE08 and 09 workshops can be reached at

http://gf18.ucs.indiana.edu/gce08/index.php/Main_Page

and

http://gf18.ucs.indiana.edu/gce09/index.php/Main_Page

OGCE Cyberaide JavaScript Release

2009-12-16T07:17:00.000-08:00

The SC09 stable release of Cyberaide JavaScript is available from http://www.collab-ogce.org/ogce/index.php/JavaScript_COG. You can either check the code out from SVN or download the tar:

SVN Checkout Command: svn checkout https://cyberaide.googlecode.com/svn/tags/cyberaide-javascript-SC09

Tar download link: http://www.collab-ogce.org/ogce/downloads/cyberaide-javascript-SC09.tar.gz

OGCE Gadget Container Added to Nightly Build and Test

2009-12-08T06:12:00.000-08:00

The OGCE Gadget Container has been added to the NMI nightly build and test system. To see a dashboard of all tests, go to http://nmi-s003.cs.wisc.edu/nmi/index.php?page=results%2Foverview&opt_project=OGCE.

OGCE Gadget Container REST API

2009-12-07T11:23:00.000-08:00

Notes by Gerald Guo, the developer of the gadget container. We are developing a REST API for the gadget container that allows you to work with it programmatically. The following example shows how to add a gadget to a layout using curl. If you prefer, a tool like the Firefox plugin Poster can be used.

Curl example:
1) Authentication
    curl -H Connection:keep-alive -d "screenname=testuser&password=testuser"
-v -k -o output.txt -c cookies
https://gf13.ucs.indiana.edu:7443/ishindig-webapp/signin

2) Add a new gadget (Calender gadget)

First, create a file named "gadget.json" with following content:
{ "gadgetname":"Embedded Calendar",
"gadgetspecsrc":"https://gf13.ucs.indiana.edu:7443/gadgets-repo/EmbeddedCale
ndar.xml"}

Then execute this command:
curl -d @gadget.json -H Content-Type:application/json -H
Connection:keep-alive -v -k -c cookies -b cookies
'https://gf13.ucs.indiana.edu:7443/ishindig-webapp/rest/users/@self/layouts/
index/0/tabs/index/0/columns/index/2/gadgets/index/-1'

In the long POST URL, position (consisting of tuple
gadget index>) of the new gadget is specified.
    layouts/index/0 : this specifies the layout the gadget will be added to
    tabs/index/0     : this specifies the tab the gadget will be added to
    columns/index/2 : this specifies the column the gadget will be added to
    gadgets/index/-1 : this specifies position of the gadget within
containing column. -1 means appending.

Then you can log in OGCE gadget container via web interface
(https://gf13.ucs.indiana.edu:7443/ishindig-webapp/www/sign.jsp) to check
whether it has been added.

This feature is currently only available in the SVN trunk. It is not part of the SC09 tagged release.

XBaya Workflow Composer as Mashup Builder

2009-12-07T06:27:00.001-08:00

WS02 is using and extending XBaya to work as a mashup composer: http://kkpradeeban.blogspot.com/2009/11/this-screen-cast-shows-development-of.htm.

OGCE Gadget Container Release

2009-11-24T08:54:00.000-08:00

The SC09 tagged release of the OGCE Gadget Container is now available. See http://www.collab-ogce.org/ogce/index.php/OGCE_Gadget_Container for download links and more information. Features include

Several gadgets pre-configured in the build, including RSS readers, GMail, Google Talk, TeraGrid status monitoring gadgets, and more.
Support for Social Networking using Google Friend Connect.
Embedded Apache Shindig container.
Support for OAuth-secured gadgets.
Support for OpenID login.
Administration interfaces.
Alternate layouts and skins.
Drag-and-drop gadget layouts.

Using Friend Connect Gadgets in OGCE Gadget Container

2009-11-13T06:50:00.000-08:00

Google Friend Connect allows you to easily develop social applications using Open Social, OAuth, and OpenID without requiring detailed knowledge of specifications or software tools. FriendConnect applications are just HTML and JavaScript and can be easily converted into Google Gadgets.

The OGCE Gadget Container comes configured to run FriendConnect applications. However, you must do a few additional steps outside of our build process. These instructions refer to actions you should take at the Friend Connect website.

Register with FriendConnect. Click "Get Started" and check the agreement.
Register your URL. If you are just testing things on localhost, there is no need to do this. The OGCE gadget container comes with a site ID for localhost. This gives you a social network of 1.
After registering, you will be redirected to your FriendConnect management dashboard. It will have a URL similar to
http://www.google.com/friendconnect/admin/site/overview?id=02963187904381158078
The number 02963187904381158078 in this example is your site ID.
Go to the OGCE Gadget Container's config/ishindig.properties file and change the value of site.friendconnectID to your new site ID.
If you have already built the OGCE Gadget Container before, you will need to redeploy the gadgets. Use the command mvn clean install -f third_party_gadgets/pom.xml.
You will also need to reload your browser to see the changes if you were logged into the portal.

If you have registered and configured everything correctly, the Friend Connect tab should look like the page below.

OGCE Gadget Container and OpenID

2009-11-11T19:09:00.000-08:00

The OGCE Gadget Container lets you associate an OpenID with your login account. You can do this in one of two ways. We will assume you have an OpenID already. Chances are you do, even if you don't realize it. For more information, see http://openid.net/get-an-openid/. For a concrete example, you can use Blogger blogs as OpenID URLs. If you were an owner of this blog, you would type http://collab-ogce.blogspot.com in the OpenID URL fields of the images below.

Your first option is to associate your openID with your gadget portal account when you create first it. Before creating the account, log into your OpenID account by typing its URL in the lower left text field of the login page.

You will be redirected to your OpenID login page. Login and you will be redirected back to the gadget login page (above). Now fill out the form on the right to create a new account.

From now on, you can just type your OpenID URL in the gadget login page and use your OpenID account to login. It will be associated with your user account.

Your second option is to add or update your OpenID URL after you have created an account. To do this, first create an account and login with your portal user name. Then click the the "User Info" button on the upper right tool bar area. You'll get a popup like the one below.

Type your OpenID URL in the field provided (next to last in the image). You can then use your OpenID for future logins instead of your portal password.

OGCE Gadget Container Supports HTTPS

2009-11-09T15:12:00.000-08:00

Previous posts on the OGCE Gadget Container have used HTTP in the examples, but the latest version in SVN now supports HTTPS/SSL. This applies to all three parts of the system: the layout manager (the visible part), a slightly-patched Shindig gadget container, and locally served gadgets. Remote gadgets using HTTPS can also be embedded. HTTPS support builds out of the box in the usual way ("mvn clean install"). No additional configuration is required.

The big news here is that with our Gadget Container will support "HTML" style gadgets over HTTPS, not just "URL" style gadgets (that is, IFrames). This means you can build SSL-secured gadgets that can take full advantage of the Gadget and Open Social JavaScript APIs.

Using the OGCE Gadget Container

2009-11-03T11:28:00.000-08:00

The OGCE Gadget Container allows you to deploy and display Google and Open Social gadgets. To get the gadget container, check it out from SourceForge with SVN:

svn co https://ogce.svn.sourceforge.net/svnroot/ogce/ShindigOGCE/ishindig-trunk/ ogce-gadget-container

You can also download the tar through SF's source code browser: http://ogce.svn.sourceforge.net/viewvc/ogce/ShindigOGCE/ishindig-trunk.tar.gz?view=tar

Next, cd into the source directory and do the following:

* Unpack Apache Maven (included in the download):
tar -zxf apache-maven-2.2.1.tar.gz; export PATH=/path/to/ogce-gadget-container/apache-maven-2.2.1/bin:$PATH

This will make sure you have the correct version of Maven.

* Edit config/ishindig.properties. Edit site.host to be your server's IP address. You can use localhost if you want. For your first build, don't change the H2 database settings, but you can use MySQL in the future.

* Build and deploy everything by running mvn clean install from the top level directory (ogce-gadget container if you used the svn checkout command above).

* Start Tomcat with startup-tomcat.sh.

You should now point your browser to ~~http://your.server.name:7070/ishindig-webapp~~https://your.server.name:7443/ishindig-webap. You should see the screen below. Create an account and log in.

After logging in, you should see a tabbed layout like the one below:

You can move gadgets around by drag and drop. Click the skins layout (drop down on the upper right) to change colors. Click the layout drop down (also upper right) to switch between table and tree layouts. Add tabs by clicking the "add a tab" button. You can create a layout like so:

To add a gadget, click the "Add a gadget" link in the upper left tool bar area. Fill out the form by providing a nickname for the Gadget and the URL to its XML definition.

Gadgets can be loaded from anywhere, but we provide a selection that can run locally in the gadgets-repo directory. We render gadgets using Apache Shindig, which is included in the download and deployed by Maven. You can use Shindig to render most gadgets available from iGoogle.

To administer users, click the Admin interface link on the login page and log in as administrator (admin/admin are the defaults).

Finally, you can clean up your installation with the command mvn clean. This will return you to the original SVN check out state, EXCEPT it will not delete the database. If using the default H2 database, the directory for the database files is set in conf/ishindig.properties. By default the directory is located in $HOME/ogce-h2-data/. You must delete this manually.

Job Submission and JavaScript Gadgets

2009-11-03T08:33:00.000-08:00

This post continues our series on using the Cyberaide JavaScript API for common Grid operations. For more information on downloading and installing the current code, see
http://collab-ogce.blogspot.com/2009/10/using-ogces-javascript-api-to-myproxy.html. If you already have to code, just use svn update from your working directory to get the latest updates.

In previous posts, we took a tour of the APIs for getting a proxy and submitting simple jobs. These have been assembled into a single gadget, cyberaideJobman.xml, located in the client sub-directory. To build , run mvn clean install from the top level cyberaide directory and then start Tomcat with the startup-tomcat.sh script. The gadget will be available from http://your.server.name:8080/grid/cyberaideJobman.xml. This is suitable for testing purposes, but you should modify Tomcat to run SSL. Near-future versions of the build system will do this by default.

You can now point your favorite gadget container (such as iGoogle) to the above URL. Steps for adding a gadget depend on the container. For iGoogle (assuming you have an account), click "Add stuff" in the upper right corner and then "Add feed or gadget" in the lower left corner. Cut and paste your gadget's URL.

OGCE Web Site Up Again

2009-10-30T12:05:00.000-07:00

The server upgrade is complete and the OGCE web site is available again.

OGCE Website Down for Upgrade

2009-10-30T09:56:00.001-07:00

We are upgrading the OGCE website (www.collab-ogce.org). The site should be up again soon.

Making a MyProxy Gadget

2009-10-22T13:01:00.001-07:00

In an earlier post we looked at a simple example that described how to build a Web interface to MyProxy with the Cyberaide JavaScript API. Now we will turn it into a gadget. This is straightforward, and you can easily test it out with iGoogle, Apache Shindig, or Google Code's wiki. We can reuse most of the previous example, so we will only discuss changes below.

Step 0: Wrap the HTML and JavaScript in the CDATA section of a new file, MyProxyGadget.xml:

<?xml version="1.0" encoding="UTF-8"?>
<Module>
<ModulePrefs title="MyProxy Gadget"
height="500">
</ModulePrefs>

<Content type="html">
<![CDATA[

Actual code goes here

]]>
</Content>
</Module>

It is also possible to use an iFrame for simplicity. The iframe can be embedded in the CDATA section and point to the HTML file's URL, or you can use a "url" gadget. In this case, change Content's type attribute value from "html" to "url" and provide the URL for the HTML code you want to embed.

Step 1: You will need to use full paths to all imported JavaScript libraries, images, and so on. Relative paths will not work. So for example, you import the CogKit2.js library like so:

<script type="text/javascript" src="https://my.host.com/grid/CogKit2.js"></script>

where my.host.com should be replaced with your Cyberaide deployment server. Note this also applies to the Cyberaide agent server URL. This must be changed from

var url="../agent/services/agent";

to

var url="https://my.host.com/agent/services/agent";

Step 2: You will need to use a modified SOAP JavaScript library, soapclientGadget.js. This replaces soapclient24NSMod.js. This is our modification. The library is available from our SVN repository.

Step 3: Load your gadget in your favorite gadget container. To use iGoogle, create an account and log in if necessary and then click the "Add Stuff" link in the upper right. Assuming you haven't published your gadget yet, click the "Add feed or gadget" link in the lower left side of the page. Type in the full URL to your gadget and submit. That's it.

More on JavaScript and Globus GRAM

2009-10-20T12:56:00.000-07:00

In the previous post, we looked at how to submit a job using the JavaScript CoG API (a.k.a Cyberaide JavaScript). We'll now look at the remaining parts of the job management API: listing all jobs, checking status of a particular job, listing outputs of a job, and viewing output. We'll just show the JavaScript codes and not the full HTML. The complete example is JobSubGadget.html.

As we saw last time, after a job is submitted, we are returned a job id. We actually treat all jobs as workflows, so this will be colloquially referred to as a wfid in the text. Also as we saw in the last post, all our function calls are accompanied by a callback function. JavaScript is a functional language, so you can pass functions as arguments to other functions. The recipient function then invokes your function.

Listing All Your Jobs

All of your jobs are stored persistently (using a lightweight database and the file system), so you can list all of your jobs' IDs with the function below. The callback function receives a JSON-formatted WFID list, which you can cast directly into a JavaScript variable if you choose.

/*--------------------------------------------------*/
// List jobs
/*--------------------------------------------------*/
function showJobs() {
jscog.listMyWf(listMyWfResponse);
}
//The call back.
function listMyWfResponse(jsonRet){
alert(jsonRet);
}

Checking the Status of a Particular Job

This method returns the status of a particular job as a JSON object. It takes a WFID as input. In the example, we obtain the WFID from the value of an HTML element called "wfid-status". This line of the example is not required.

/*--------------------------------------------------*/
// Check job status
/*--------------------------------------------------*/
function showStatus() {
var wfid=document.getElementById("wfid-status").value;
jscog.statusQuery(wfid,statusQueryResponse,"");
}
//The callback function.
function statusQueryResponse(jsonRet,loc) {
alert(jsonRet);
}

Listing Job Output Files

This function lists the output files associated with a particular WFID. In the previous example, this is the standard output file. Once again the output is JSON-encoded, and the input is obtained from a document element's value (wfid-list in this case). Again, this method for determining the input WFID value is only illustrative.

/*--------------------------------------------------*/
// List job output files
/*--------------------------------------------------*/
function listOutputFiles() {
var wfid=document.getElementById("wfid-list").value;
jscog.listOutput(wfid,listOutputResponse,"");
}
function listOutputResponse(jsonRet) {
alert(jsonRet);
}

Show the Output of a Job

Finally, we can view one of the output files as shown below. The return value is JSON-encoded as before.

/*--------------------------------------------------*/
// Show job output
/*--------------------------------------------------*/
function displayResult() {
var wfid=document.getElementById("wfid-display").value;
var outputfile=document.getElementById("wfid-outputfile").value;
jscog.displayResult(wfid,outputfile,fetchOutputResponse,"");
}
function fetchOutputResponse(jsonRet) {
alert(jsonRet);
}
function fetchOutputResponse(jsonRet,loc) {
alert(jsonRet);
}

Submitting a Grid Job with OGCE JavaScript API

2009-10-19T14:33:00.000-07:00

In the previous post, we showed how to get a MyProxy credential with the OGCE's Cyberaide JavaScript API. We'll now look at how to submit a simple job. We'll build up a very simple HTML page to do this, but you should note that we have much more appealing clients than this if you want to use something out of the box.

Let's start by building upon our earlier MyProxyGaget.html example. This file is called JobSubGadget.html and is in the client subdirectory of the source code. We will combine the MyProxy form with a Job Submission form to simplify security issues; that is, the user will be presented with a form to get a proxy credential (shown last time) and a form to launch a job. The job launching form only appears after the user successfully authenticates.

To do this, we will start with a little jQuery trick. We'll wrap the two tables in <div> classes called proxyFormClass and jobSubClass and define the following CSS entries:

.proxyFormClass {
}

.jobSubClass{
display: none;
}

Then in the authentication callback function (see previous post), we put the code snippet below:

$('div.jobSubClass').show();
$('div.proxyFormClass').hide();

This will turn off the proxy form fields and turn on the job submission fields.

Now we're ready for the job submission form itself. Here's a very bare bones one:
<div class="jobSubClass" id="jobSub">
Fill in the form below to launch a job.
<table>
<tr>
<td>Command</td>
<td><input name="cmd" type="text" id="cmd" size="50" value="/bin/ls"/></td>
</tr>

<tr>
<td>Arguments</td>
<td><input name="arg" type="text" id="arg" size="50" value="-l"/></td>
</tr>
<tr>
<td>GRAM Host</td>
<td><input name="rHost" type="text" id="rHost" size="50" value="grid-co.ncsa.teragrid.org"/>
</td>
</tr>

<tr>
<td>GridFTP Host</td>
<td><input name="ftpHost" type="text" id="ftpHost" size="50" value="gridftp-co.ncsa.teragrid.org"/>
</td>
</tr>

<tr>
<td>Standard Output</td>
<td><input name="stdout" type="text" id="stdout" size="50" value="junk-ls.out"/>
</td>
</tr>

<tr>
<td>Provider</td>
<td><input name="provider" type="radio" id="gt2" checked>GT2
<input name="provider" type="radio" id="gt4">GT4</td>
</tr>
<tr>
<div name="submitStatus" id="submitStatus"/>
</tr>

</table>
<input name="button1" type="button" class="runButton" id="button1" onclick="submitJob();return false" value="Submit job"/>
</div>

This should look familiar. One important thing to note (besides the little div wrapper) is that we need to provide the hostname for both the GRAM and GridFTP hosts. We need this to both run the job and pull back the output. Not all grid installations (notably the TeraGrid) run both the GRAM and GridFTP server on the same machine (network file systems), so we have to allow for this.

Now let's look at some minimal JavaScript code to invoke the service. The main thing we need to do is collect the submission form's parameters and invoke the service.

function submitJob() {
/* extract job specification */
var cmd = document.getElementById("cmd").value;
var arg = document.getElementById("arg").value;
var rHost = document.getElementById("rHost").value;
var ftpHost=document.getElementById("ftpHost").value;
var stdout = document.getElementById("stdout").value;
var provider = document.getElementsByName("provider");
var prov = null;
if(provider[0].checked){
prov = "GT2";
}
else {
prov = "GT4";
}

/* construct karajan workflow */
var strProj = jscog.constructRemoteJob(cmd, arg, rHost, stdout, ftpHost, stdout, prov);
document.getElementById("submitStatus").innerHTML = "Job Submitting";
loc="";
jscog.submitWf(strProj,submitResponse,loc);

}

Job submission is actually a two step process in the API: first we construct the job's workflow (we use the CoG's Karajan on the backend), and then we submit the constructed workflow script (jscog.submitWf()). We also need to write a callback handler (submitResponse in the submitWf() command) to see if the job was submitted successfully. Here is a really simple one:

/*
* Callback to handle the submission response.
*/
function submitResponse(ret) {
document.getElementById("submitStatus").innerHTML="Your job has been submitted with workflow ticket "+ret;

}

The callback function gets an integer ret back from the server. If submission was successful, then this integer will be the job ticket, which you can use to query status and get back results or error messages.

Using OGCE's JavaScript API to MyProxy

2009-10-19T10:01:00.000-07:00

We are in the process of releasing a JavaScript COG API, Cyberaide, that works with common Grid services like MyProxy, GRAM, and GridFTP. Our goal is to provide a method for embedding these calls into many different frameworks, including non-Java languages and tools such as PHP and Ruby on Rails. We are want to provide tools that can be used to build Open Social gadgets that perform Grid operations.

For a fuller description of the project, see http://cyberaide.org/projects/cyberaide/cyberaide-javascript. To browse or download the working version of the code, see http://code.google.com/p/cyberaide/. The examples (very actively developed) can be built using one command,

mvn clean install

from the cyberaide source's top level directory. Edit the top level pom.xml file's properties first. Use the version of Maven provided in the download. You can also rebuild portions of the system with the command

mvn clean install -f client/pom.xml

where client is one of the project modules. After you build everything, start up Tomcat (use the startup-tomcat.sh convenience script). Point your browser to http://localhost:8080/jsportal.html to see some examples.

To shut down everything, you can use the shutdown scripts (shutdown-tomcat.sh and shutdown-mediator.sh). To see debugging information, check out the log files: agent.log and mediator/mediator.log.

MyProxy API Example
The full example is called "MyProxyGadget.html" and is located in the subdirectory client of the source code. To start, you need a set of HTML input fields as usual:

<table>
<tr>
<div id="authStatus" name="authStatus"/>
</tr>
<tr>
<td>Myproxy Server Host:</td>
<td><input name="host" type="text" id="myproxy.host" size="50" value="myproxy.teragrid.org"/></td>

</tr>
<tr>
<td>Myproxy Server Port:</td>
<td><input name="port" type="text" id="myproxy.port" size="50" value="7512"/></td>
</tr>
<tr>
<td>Myproxy Username:</td>
<td><input name="user" type="text" id="myproxy.user" size="50"/></td>
</tr>
<tr>
<td>Myproxy Passphrase:</td>
<td><input name="password" type="password" id="myproxy.password" size="50"/></td>
</tr>
</table>
<input name="button0" type="button" class="runButton" id="button0" onclick="auth();return false" value="Authenticate"/>

Next, you need to import the COG JavaScript library:

<script type="text/javascript" src="CogKit2.js"/>

Now implement the auth() method from your button's onclick attribute. This should of course be located in a section <script language="javascript" > section.

/* Initialize the JavaScript COG */
var url = "../agent/services/agent";
var jscog = new CogKit2(url);
var authStatus = false;

//Define your auth function here.
function auth(){

//These point to the elements in the table above.
var host = document.getElementById("myproxy.host").value;
var port = document.getElementById("myproxy.port").value;
var user = document.getElementById("myproxy.user").value;
var password = document.getElementById("myproxy.password").value;

//A little window dressing
document.getElementById("authStatus").innerHTML=" Authenticating";

//Now invoke the JS CoG auth method from the imported library.
jscog.auth(host, port, user, password, authResponse);
}

The last argument, authResponse, is a callback function that you can use to determine if authentication was successful or not. A sample implementation is shown below.

/*
* the authenticate callback function
*/
function authResponse(ret) {
if(ret){
authStatus = true;
document.getElementById("authStatus").innerHTML="Authenticated successfully!";
document.getElementsByName("password")[0].value="";
} else{
authStatus = false;
document.getElementById("authStatus").innerHTML="Failed to Authenticate!";
document.getElementsByName("password")[0].value="";
}
}

We'll look at more functions in upcoming posts.

Maven Out of Memory Errors

2009-09-09T13:13:00.000-07:00

We have seen some Maven errors compiling the OGCE portal on Mac OS X 10.5 with Java 1.6. To remedy this, set the MAVEN_OPTS environment variable:

(bash) export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=128m"
(csh) setenv MAVEN_OPTS "-Xmx1024m -XX:MaxPermSize=128m"

The actual values (1024m and 128m) can be varied if necessary.

The error message output from running "mvn clean install" is shown below.

...
/target/classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
Failure executing javac, but could not parse the error:

The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError: Java heap space
at com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385)
...

Velocity Portlet Bridge Updates

2009-07-06T14:29:00.000-07:00

Thanks go to Michel David da Costa for updates to the Velocity Portlet Bridge code. This is used to build various older portlets in OGCE (see for example JobSubmission) and will work in various versions of GridSphere and uPortal.

The code is here:

http://ogce.svn.sourceforge.net/viewvc/ogce/OGCE-Util/VelocityPortlet/trunk/.

You can check this out anonymously using SVN:

svn co https://ogce.svn.sourceforge.net/svnroot/ogce/OGCE-Util/VelocityPortlet/trunk VelocityPortlet

If you prefer, you can also get the tar from http://ogce.svn.sourceforge.net/viewvc/ogce/OGCE-Util/VelocityPortlet/trunk.tar.gz.

To build, use Apache Maven 2.0.x and the command

mvn clean install

OGCE TG09 Tech Track Presentation

2009-06-24T09:17:00.001-07:00

SlideShare Presentation:

OGCE TG09 Tech Track Presentation

View more OpenOffice presentations from marpierc.

Cloud and Gateway Developer Positions at the Pervasive Technology Institute

2009-06-24T08:14:00.001-07:00

We are looking to fill two positions. Please see the full ad below.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The following positions based at IUB and reporting to Marlon Pierce, Assistant Director, Community Grid Labs, is being posted externally. If interested, you must apply online at http://www.jobs.indiana.edu/. Refer to positions number #00034420 and #00034425.

Principal Software Research Engineers - PAE4IT (Two positions available)

Description and Responsibilities:

Indiana University is looking for experienced individuals to fill multiple positions in Cloud computing , Grid computing, and message-oriented middleware development. The positions call for expertise in Web service software development, experience developing Java Messaging Service (JMS) applications and related Enterprise event bus technologies, experience with distributed systems, sensor webs, and/or audio-video systems research and advanced development.
Working independently, the incumbent provides expertise in the evaluation, development, implementation and deployment of specific Cloud Computing, Message-Oriented Middleware, and Grid-related technologies in conjunction with Pervasive Technology Institute and Research Technology staff and collaborators. Investigate research problems in distributed computing systems, develop software using best software engineering practices, publish peer-reviewed research articles in workshops and journals, evaluate existing technologies, supervise staff and graduate students, and oversee all development aspects of Cloud and Grid scientific data and application management. Work with scientific users to develop Cloud and Grid systems. Collaborate with key academic researchers and open source user community including faculty, scientific researchers, and grant stakeholders.
Indiana University's Pervasive Technology was recently awarded a 5 year extension to its core funding from the Lilly Endowment, following its highly successful initial 7 years (as the Pervasive Technologies Laboratories). PTI will be located in Indiana University's new state of the art Research Incubator facility. See http://www.pervasive.iu.edu/ for more information. To date, the PTI laboratories have published more than 880 peer-reviewed papers, have won over $180,000,000 in grants over and above their core funding, and have released and maintain numerous open source software packages. PTI researchers work closely with Indiana University's Research Technology group, who maintain IU's world class cyberinfrastructure, http://racinfo.indiana.edu/cyberinfrastructure/.
Qualifications:

Master's degree in Computer Science or relate technical discipline (such as physics, informatics, engineering) is required. PhD preferred. Ph. D. incumbents must have demonstrated (through peer-reviewed publications and software products) a primary research focus on one or more of the following: a) distributed, parallel, Grid and/or Cloud computing; b) high performance, distributed messaging systems; c) audio/video collaboration systems; and d) security in distributed systems. Incumbents with Master's degree must have five to seven years experience in software development and deployment in the appropriate field or fields.

Requirements include a proven ability to undertake and succeed in innovative research projects, and excellent communication skill (covering scientific article writing, presentation skills, and the ability to work with and lead teams). Experience developing software systems using standard software engineering practices (such as source code management software, build and test systems, etc). For Cloud and Grid incumbents, experience developing Web Services, REST services, scientific workflows, and distributed Web applications on Unix/Linux/Mac OSX and/or Windows. Experience developing applications on Grids using software such as Globus or Condor. Experience developing scientific and research Cloud applications using Amazon Web Services, Microsoft Azure, Google AppEngine, and related systems. Experience developing data-parallel scientific, machine learning, and/or information retrieval algorithms using systems such as Apache Hadoop and Microsoft Dryad. For audio/video stream incumbents, demonstrated knowledge and implementation of standards as well as innovative systems. For message-oriented middleware incumbents, demonstrated sophisticated experience with standard MOM software. MOM incumbents should have experience both with core MOM development (efficient routing, security, reliable delivery) as well as applications.
Ability to foster and maintain collaborations with internal and external academic researchers through a balanced, service-based approach required. Demonstrated ability to learn new technologies and tools. Demonstrated initiative in evaluating and adopting new technologies. Organizational and leadership skills required. Able to operate effectively in a complex and dynamic environment with the capability of functioning as a project leader. Excellent oral and written communication skills. Demonstrated conceptual, analytical, and logical abilities. Ability to interact successfully with staff and faculty in extended consultations; demonstrate enthusiasm for new technologies; and deliver excellent outcomes under high pressure and short deadlines. Excellent communication skills required to interact with people of varying levels of knowledge.

Indiana University is an Affirmative Action/Equal Employment institution.

OGCE Portal 2.5

2009-06-22T09:15:00.000-07:00

OGCE Portal 2.5 is available for download. The release includes updates to the XBaya portlet, the addition of the GFAC portlet into the main build, and bug fixes to the GPIR portlet.

You can get the code by either SVN anonymous checkout or by downloading the tar.gz.

SVN Anonymous Checkout: svn co https://ogce.svn.sourceforge.net/svnroot/ogce/tags/ogce-portal-only-2.5-release

Download the Tar: http://ogce.svn.sourceforge.net/viewvc/ogce/tags/ogce-portal-only-2.5-release.tar.gz?view=tar

OGCE Workflow Suite: XBaya, XRegistry, and GFAC

2009-06-21T15:24:00.000-07:00

Ogce Workflow Suite Tg09

View more OpenOffice presentations from smarru.

Open Life Science Gateway: Gadgets, Open Social, and JSON-RPC

2009-06-20T06:17:00.001-07:00

The Open Life Science Gateway code (developed by Wenjun Wu) demonstrates how to develop science gateways with Google Gadgets, Open Social, JSON-RPC, and other Web 2.0 techniques. Browse code here: http://ogce.svn.sourceforge.net/viewvc/ogce/ogce-olsg/.

You can get the code by anonymous SVN checkout or download the tar.gz.

SciDAC Tutorial: GTLAB Tag Libraries Overview

2009-06-19T08:14:00.002-07:00

GTLAB Installation Tutorial for SciDAC 2009

View more OpenOffice presentations from marpierc.

SciDAC Tutorial: OGCE Overview

2009-06-19T08:14:00.001-07:00

OGCE Overview for SciDAC 2009

View more OpenOffice presentations from marpierc.

OGCE Axis Services 1.0 Tagged

2009-06-17T18:54:00.000-07:00

Version 1.0 of the OGCE Axis Services have been tagged. See http://ogce.svn.sourceforge.net/viewvc/ogce/tags/ogce-axis-services-1.0/ This includes the Resource Discovery Service and the Resource Prediction Service. See http://www.collab-ogce.org/ogce/index.php/Main_Page#Key_to_Release_Status for an explanation of our release tagging conventions.

Get the tar: http://ogce.svn.sourceforge.net/viewvc/ogce/tags/ogce-axis-services-1.0.tar.gz?view=tar

Check out from SVN: svn checkout https://ogce.svn.sourceforge.net/svnroot/ogce/tags/ogce-axis-services-1.0

GTLAB TG09 Release Tagged

2009-06-17T17:32:00.000-07:00

GTLAB has been tagged. This release includes integration with Tomcat's login, new tags and examples for displaying INCA status information on the TeraGrid, simple support for GridShib invocations, and various bug fixes. See http://ogce.svn.sourceforge.net/viewvc/ogce/tags/GTLAB-tg09/.

Get the tar: http://ogce.svn.sourceforge.net/viewvc/ogce/tags/GTLAB-tg09.tar.gz?view=tar

Check out from SVN: svn co https://ogce.svn.sourceforge.net/svnroot/ogce/tags/GTLAB-tg09

Tagged Releases for GFAC and XRegistry Services

2009-06-16T10:17:00.000-07:00

Latest stable release versions of the GFAC and XRegistry services are available for download from our SourceForge repository. This is part of the "TeraGrid 09" release of OGCE software, one of our two major updates this year. OGCE portal software tag releases are in preparation.

Tar Bundles:

XRegistry: http://ogce.svn.sourceforge.net/viewvc/ogce/tags/xregistry-tg09.tar.gz?view=tar

GFAC: http://ogce.svn.sourceforge.net/viewvc/ogce/tags/sgfac-tg09.tar.gz?view=tar

SVN Anonymous Checkout
XRegistry: svn co https://ogce.svn.sourceforge.net/svnroot/ogce/tags/xregistry-tg09

GFAC: svn co https://ogce.svn.sourceforge.net/svnroot/ogce/tags/sgfac-tg09

OGCE Overview Presentation from E-Science 2008

2009-06-04T08:29:00.001-07:00

OGCE Project Overview

View more OpenOffice presentations from marpierc.

GTLAB Slides

2009-06-04T08:11:00.001-07:00

Gtlab Install

View more OpenOffice presentations from marpierc.

OGCE-Utils and Small SVN Reorganization

2009-06-03T11:21:00.000-07:00

The Proxy Manager API and Velocity Portlet Bridge code have been moved to the new OGCE-Util directory in SVN (see http://ogce.svn.sourceforge.net/viewvc/ogce/OGCE-Util). The util directory in general is for standalone applications with jar (rather than war) targets that may get used by other projects.

XRegistry Added to NMI Build and Test

2009-06-03T10:26:00.000-07:00

The OGCE XRegistry service (http://www.collab-ogce.org/ogce/index.php/XRegistry) has been added to the NMI nightly build system. See http://nmi-s003.cs.wisc.edu/nmi/index.php?page=results%2Foverview&opt_project=OGCE for all builds.

OGCE Axis Services Added to Nightly Build

2009-05-29T09:33:00.000-07:00

Nightly builds of the OGCE Axis Services (http://www.collab-ogce.org/ogce/index.php/OGCE-Axis-Services) are now running on the NMI Testbed at the University of Wisconsin. We perform automated builds for Mac OSX and several flavors of Linux. See http://nmi-s003.cs.wisc.edu/nmi/index.php?page=results%2Foverview&opt_project=OGCE for additional information.

OGCE Tutorial at SciDAC

2009-05-22T12:11:00.000-07:00

We will participate in the "TeraGrid Gateways" portion of the SciDAC tutorials, June 19th. See https://outreach.scidac.gov/scidac09/tutorials/ for details.

OGCE Presentation at TG09

2009-05-15T13:27:00.000-07:00

OGCE has an accepted presentation for TG09, Wednesday June 24th, 2:30-3:00 pm. See full TG09 schedule at

http://www.teragrid.org/tg09/index.php?option=com_content&task=view&id=62

TG09 Tutorial on Science Gateways

2009-05-15T13:25:00.000-07:00

OGCE team members will give a Science Gateway tutorial at TeraGrid 09 on Monday, July 22nd. The full abstract is here: http://www.teragrid.org/tg09/index.php?option=com_content&task=view&id=56

E-Science Demos

2008-12-08T09:07:00.001-08:00

We'll be demonstrating OGCE workflow management tools and XMC-Cat (a new cataloging service) at E-Science Conference on Wednesday night.

Abstract: http://escience2008.iu.edu/exhibits/open_grid.shtml

Coordinates: http://escience2008.iu.edu/exhibits/index.shtml

EScience Tutorial Agenda

2008-12-05T11:25:00.000-08:00

This is Sunday, Dec 7 from 8:00 to 5:00 PM (US Eastern Standard Time). You can also view remotely the live broadcast. For instructions, see http://escience2008.iu.edu/multimedia/index.shtml. An archived broadcast will be available from the same URL.

Presentation material is available from http://www.collab-ogce.org/ogce/index.php/Tutorials.

Talks will be given by Marlon Pierce, Suresh Marru, and very special guest star Stephen Simms.

Introduction and attendee feedback
(Talk) Gateways overview (Marlon)
(Talk) TeraGrid: Resources Overview and Getting Started (Simms)

[BREAK]

(Talk/Demo) LEAD portal and workflow (Suresh)
(Demo/Talk) GridChem workflows (Suresh)
(Demo/HO) OGCE and TGUP Portals (Marlon)

[LUNCH]

(Demo/HO) OGCE hands on and simple workflows with XBaya (Marlon, Suresh)
(Talk/HO) Building OGCE portal and services (Marlon)
(Talk/Demo/HO) Building GTLAB gadgets (Marlon)

[BREAK]

(Optional Talk) Web 2.0 for science gateways (Marlon)
(Optional HO) Building the portal, GTLAB, and services
(Optional HO) Using various portals (OGCE, TeraGrid User Portal, LEAD)
(Optional HO) Workflows in depth

Javadocs for OGCE Components

2008-12-04T08:17:00.000-08:00

If you want to make Javadocs for OGCE components (the portal, GTLAB, Axis services, etc), use the command

mvn javadoc:javadoc -f path/to/component/pom.xml

For example, the GTLAB javadoc can be made with the command

mvn javadoc:javadoc -f jsf_standalone/pom.xml

The docs will be located in jsf_standalone/target/site. Load with your browser.

OGCE Swarm Service Talk at E-Science

2008-12-03T12:30:00.000-08:00

Sangmi Pallickara will present the Swarm Job Submission Service at Friday, Dec 12 at the E-Science conference: http://escience2008.iu.edu/sessions/SWARM.shtml.

This talk will be web-cast. See http://escience2008.iu.edu/multimedia/index.shtml for details.

E-Science Gateways Tutorial Web Cast

2008-12-03T12:24:00.000-08:00

Our OGCE and Gateways tutorial at E-Science is Sunday, December 7 from 8:00 am to 5:00 pm. See http://escience2008.iu.edu/tutorials/gateways.shtml. The entire conference (including our tutorial) is being web-cast; see http://escience2008.iu.edu/multimedia/index.shtml for more information.

We will post a more detailed agenda on this blog.

SC08 Demo Time Correction

2008-11-14T17:49:00.000-08:00

The IU booth demo is 1:00-3:00 on Wednesday, November 19th. These are roughly 2 30 minute demos at 1:00 and 2:00, with 30 minute breaks.

OGCE Portal 2.4 Posted

2008-11-14T14:30:00.000-08:00

Version 2.4 is ready. This features the File Manager applet from the TeraGrid User Portal, as well as numerous bug fixes and miscellaneous enhancements. See http://collab-ogce.blogspot.com/2008/09/tagged-preview-of-ogce-portal-24.html for more details.

Tagged SC08 releases of OGCE Axis Services and GTLAB are also available.

OGCE Web Site and Download Reorganization

2008-11-12T10:16:00.000-08:00

The OGCE Web Site is being revised to better reflect the reorganization of our downloadable components. Here are the major download suites:

The OGCE portlet-based Grid portal: this download combines Tomcat, Gridsphere portlet container, and many OGCE portlets developed with OGCE libraries.
The OGCE Axis Web Services Suite: this includes several OGCE services (currently GPIR, the Resource Prediction Service, and the Resource Discovery Service) combined into an integrated, one-step build.
The OGCE Workflow Suite: this suite contains workflow composer and engine (XBaya), the GFAC application factory, XRegistry, and related components.
GTLAB: This is a collection of Java Server Faces tags and supporting code for building Grid portlets and gadgets. The current version supports simple tag pipelining (so you can associate multiple tasks with a single HTML button click). Tags are no longer limited to Grid clients--any thing can be used.
OGCE Gadget Container: this is a preview of our work to build an Open Social and iGoogle-compatible container. We view this as the successor to the portlet standard we have used in the past.

See the web site for more information.

SC08 Demos: 1:00-3:00

2008-11-11T14:06:00.000-08:00

OGCE team will be giving demos in the Indiana University booth at SC08 on Tuesday from 1:00 pm to 3:00 pm. Demos will include

OGCE workflow tools
JavaScript Grid clients
Tag libraries for building iGoogle style Grid gadgets.
Gateway information services
Application portals using Pylons
Demo portals for the life sciences

Please feel free to come by the IU booth for informal demos.

Updated GCE08 Schedule

2008-11-11T14:05:00.000-08:00

The GCE08 Workshop presentation schedule at Supercomputing 2008 in Austin has been updated: http://www.collab-ogce.org/gce08/index.php/Program

Tentative GCE08 Schedule Available

2008-11-03T07:22:00.000-08:00

A draft GCE08 Workshop presentation schedule at Supercomputing 2008 in Austin is now available: http://www.collab-ogce.org/gce08/index.php/Program

The program will be updated as we confirm speakers' travel schedules, but the program is set. Slides and papers will be made available from this URL as they become available.

The Dreaded "GRAM Job submission failed: The job manager failed to open stderr" Error

2008-10-07T11:50:00.001-07:00

The COG will produce the following infamous error

GRAM Job submission failed: The job manager failed to open stderr

if you don't have values in $HOME/.globus/cog.properties set correctly. The "ip" parameter must be set to the real hostname or static IP address of your portal server. That is, it should be something like

ip=123.456.789

You can edit this file by hand, but note it will be overwritten if your rebuild the portal. You should make sure that the <portal.server.ip> value in ogce-portal-only/pom.xml is set correctly.

Nightly Build Update

2008-09-22T11:34:00.001-07:00

The "portal only" release was upgraded to Tomcat 5.5.27, but the build and test scripts on the NMI testbed were still set to use the older Tomcat 5.5.12. This has been corrected.

For more info on the nightly build, see http://www.collab-ogce.org/ogce/index.php/Bugs_email_svn

Nightly Builds OK

2008-09-22T07:44:00.000-07:00

There is a bug in the NMI nightly build scripts that prevents Tomcat from starting. This causes the build to report a failure, but the compilation steps complete successfully.

Tagged Update to GTLAB

2008-09-12T09:16:00.000-07:00

Numerous improvements and bug fixes to the GTLAB tag libraries have been tagged as "GTLAB-2008". These supersede the TG08 tagged version. To get the updates, use

svn checkout https://svn.sourceforge.net/svnroot/ogce/tags/GTLAB-Sep2008

Major changes include

Bug the prevented task inter-dependencies from working correctly has been fixed.
Each GTLAB tag can now be associated with its own resource property file. Previously all tags used the same property file.

Tagged Preview of OGCE portal 2.4

2008-09-12T09:08:00.000-07:00

The OGCE "portal only" release has been tagged as a preview. This version includes numerous bug fixes and updates. To get it, use

svn checkout https://svn.sourceforge.net/svnroot/ogce/tags/ogce-portal-only-2.4-preview

Most updates are courtesy of Lukas Hoffman.

gp-common

* Edited files: portlets/gp-common/src/main/webapp/css/fileBrowser.css
portlets/gp-common/src/main/webapp/javascript/fileBrowser.js
portlets/gp-common/src/main/webapp/jsp/fileBrowser.jsp
* This isn't really a portlet, it just contains files that are used by the GridPort portlets

Interactive Job Submission / jobsubmit-portlet

* Edited files: portlets/jobsubmit-portlet/src/main/webapp/templates/xportlets-jobsubmit.vm
portlets/jobsubmit-portlet/src/main/webapp/templates/xportlets-jobsubmit-help.vm
portlets/jobsubmit-portlet/src/main/java/xportlets/jobSubmitAction.java
* Added *'s for certain fields in the job submission form & a note saying those fields were required.
* Added a way to link to standard output and standard error files
* Added help instructions in "?" viewing window
* If user left stdout/stderr field blank, job output is displayed in portlet when job completes. see 'lukas code' where stdout is mentioned in JobSubmitAction.java and xportlets-jobsubmit.vm
* If user enters path from root to stdout/stderr, there's a link to download the file. This is glitchy though, it only works if filetransfer portlet is connected to correct host, and it doesn't work for relative paths.

File Manager/file-manager and Comprehensive File Management/comp-file-management

* Edited files: portlets/comp-file-management/src/main/webapp/jsp/fileBrowser.jsp
portlets/comp-file-management/src/main/webapp/jsp/view.jsp
portlets/comp-file-management/src/main/webapp/css/fileManagement.css
portlets/comp-file-management/src/main/java/edu/tacc/gridport/portlets/interactive/FileManagementConstants.java
portlets/comp-file-management/src/main/java/edu/tacc/gridport/portlets/interactive/FileManagementPortlet.java
portlets/gp-common/src/main/webapp/jsp/fileBrowser.jsp - identical to fileBrowser.jsp above
portlets/gp-common/src/main/webapp/javascript/fileBrowser.js:
* Added an image href to the file/directory listing
* Files are now sortable by name, filetype, and size. Default is sort by filetype. User can click on a heading to select a sort.
If user clicks on a heading twice in a row, the sort is in reverse order.
* Refresh button went to home directory, now it's refresh current directory.
* Fixed something in FileManagementPortlet.java but I forgot what the problem was.
destListing.setRemoteHost(destResources[0]); //lukas code, previous array size = 1 --> this portlet crashes.
//don't know why this fix works, but it works...

File Transfer Portlet / GridFTP Portlet / filetransfer (Deprecated)

Edited files: portlets/filetransfer/src/main/webapp/gridftp-browser.vm
portlets/filetransfer/src/main/webapp/gridftp-help.vm
portlets/filetransfer/src/main/java/xportlets/gridftp/FileAttributes.java
portlets/filetransfer/src/main/java/xportlets/gridftp/GridFTPClientAction.java
ogce-portal/portlets/filetransfer/src/main/java/xportlets/gridftp/FileListSorter.java
* FileListSorter.java is all my own code, so the directory contains a javadoc html page for this class
* fixed bug where file download & file transfer don't work if filenames contain spaces.
* fixed bug where clicking on a link twice really fast made portlet crash
* fixed two or three "annoying but not fatal" bugs that I don't remember now, although I probably wrote that it was a fix in the source code comments
* Added a "Type" (Filetype field) so the file list matches the information that any Windows directory listing gives you
* Made the "Date Modified" dates look better
* Files/Directories are now sortable by Name, Size, Type, and Date Modified. They stay sorted that way until the user clicks on a heading.
* Sorting is in reverse order when user clicks a heading twice.
* Made icons and file/directory names clickable, for easier access with the mouse. Before, the link to download a file was on one side & the
file name was on the other, which is annoying for the user. Now the user can click directly on the file name or icon to download it, or
directory name/icon to go there.
* Moved things around to make portlet look better. Mostly, moved all buttons and links toward the top and put file listing under them.
* User can now
make a new directory
rename a file/directory
delete 1 or more files at a time
delete a directory
go to any directory in 1 step by typing in the full path name, or path name relative to current directory, or ".." to go up a directory
(typing "dir1/dir2/dir3" and pressing submit is faster than clicking 3 links)
* Added error messages when the commands above fail & display to the user.
* Added help instructions in "?" viewing window
* Luke Hammill fixed problem where if you accidentally transfer a file to itself (same action as: mv fileA fileA) file gets deleted. (fix not in version i sent you)
* back.gif button can now go to '/', which it couldn't before.
* 'Home' link now always goes to directory that showed up when the host was first loaded, which it didn't before.
* You can delete several files at a time using checkboxes.

GCE08 Submission Deadline Extension

2008-09-10T10:39:00.000-07:00

The deadline for submitting papers to GCE 08 has been extended to September 22. See http://www.collab-ogce.org/gce08/index.php/Main_Page for more information.

Condor Installation Example

2008-09-08T15:31:00.000-07:00

The following is an example installation for Condor 6.8.8. This is required to use the Condor and Condor-G portlets. Additional configuration is required to enable Birdbath and Condor-G, so see the portlet notes at www.collab-ogce.org.

Note also that this version of Condor will not work on newer RHEL and Fedora releases, so you will need to get the libstdc++.so.5 library. Do the following as root:

[shell> yum install libstdc++.so.5

Now do the following in the condor-6.8.8 release directory.

[shell> condor_install

Press enter to begin Condor installation

***************************************************************************
STEP 1: What type of Condor installation do you want?
***************************************************************************

Would you like to do a full installation of Condor? [yes]

Press enter to continue.

***************************************************************************
STEP 2: How many machines are you setting up for Condor?
***************************************************************************

Are you planning to setup Condor on multiple machines? [yes] no

Press enter to continue.

***************************************************************************
STEP 3: Install the Condor "release directory", which holds
various binaries, libraries, scripts and files used by Condor.
***************************************************************************

It looks like you've installed a Condor release directory in:
/usr/local/condor
Do you want to use this release directory? [yes] no

Have you installed a release directory already? [no] no

Where would you like to install the Condor release directory?
[/home/mpierce/condor]
That directory doesn't exist, should I create it now? [yes]
Installing a release directory into /home/mpierce/condor ...

[------------------------------Stuff deleted------------------------------]

done.

Using /home/mpierce/condor as the Condor release directory.

Press enter to continue.

***************************************************************************
STEP 4: How and where should Condor send email if things go wrong?
***************************************************************************

If something goes wrong with Condor, who should get email about it?
[mpierce@gw12.quarry.iu.teragrid.org]

What is the full path to a mail program that understands "-s" means
you want to specify a subject? [/bin/mail]

Using /bin/mail to send email to mpierce@gw12.quarry.iu.teragrid.org

Press enter to continue.

***************************************************************************
STEP 5: Filesystem and UID domains.
***************************************************************************

To correctly run all jobs in your pool, including ones that aren't relinked
for Condor, you must tell Condor if you have a shared filesystem, and if
so, what machines share it.

Please read the "Configuring Condor" section of the Administrator's manual
(in particular, the section "Shared Filesystem Config File Entries")
for a complete explaination of these (and other, related) settings.

Do all of the machines in your pool from your domain ("quarry.iu.teragrid.org")
share a common filesystem? [no]

Configuring each machine to be in its own filesystem domain.

Do all of the users across all the machines in your domain have a unique
UID (in other words, do they all share a common passwd file)? [no]

Configuring each machine to be in its own uid domain.

Press enter to continue.

***************************************************************************
STEP 6: Java Universe support in Condor.
***************************************************************************

Enable Java Universe support? [yes] no
OK, Java Universe will be left unconfigured.

Press enter to continue.

***************************************************************************
STEP 7: Where should public programs be installed?
***************************************************************************

The Condor binaries and scripts are already installed in:
/home/mpierce/condor/bin
If you want, I can create some soft links from a directory that is already
in the default PATH to point to these binaries, so that Condor users do not
have to change their PATH. Alternatively, I can leave them where they are
and Condor users will have to add /home/mpierce/condor/bin
to their PATH or explicitly use a full pathname to access the Condor tools.

Shall I create links in some other directory? [yes] no

Press enter to continue.

***************************************************************************
STEP 8: What machine will be your central manager?
***************************************************************************

What is the full hostname of the central manager?
[gw12.quarry.iu.teragrid.org]

Your central manager will be on the local machine.

Press enter to continue.

***************************************************************************
STEP 9: Where will the "local directory" go?
***************************************************************************

Condor will need to create a few directories for its own use

You have a "condor" user on this machine. Do you want to put all the
Condor directories in /home/condor? [yes] no

Do you want to put all the Condor directories in
/home/mpierce/condor/home? [yes]

Creating all necessary Condor directories ... done.

Press enter to continue.

***************************************************************************
STEP 10: Where will the local (machine-specific) config files go?
***************************************************************************

Condor allows you to have a machine-specific config file that overrides
settings in the global config file.

You must specify a machine-specific config file.

Should I put a "condor_config.local" file in /home/mpierce/condor/home?
[yes]
Creating config files in "/home/mpierce/condor/home" ... done.

Configuring global condor config file ... done.
Created /home/mpierce/condor/etc/condor_config.

Press enter to continue.

Setting up gw12.quarry.iu.teragrid.org as your central manager

What name would you like to use for this pool? This should be a
short description (20 characters or so) that describes your site.
For example, the name for the UW-Madison Computer Science Condor
Pool is: "UW-Madison CS". This value is stored in your central
manager's local config file as "COLLECTOR_NAME", if you decide to
change it later. (This shouldn't include any " marks).
gw12condorthing

Setting up central manager config file /home/mpierce/condor/home/condor_config.local ... done.

Press enter to continue.

***************************************************************************
STEP 11: How do you want Condor to find its config file?
***************************************************************************

Condor searches a few locations to find it main config file. The first place
is the envionment variable CONDOR_CONFIG. The second place it searches is
/etc/condor/condor_config, and the third place is ~condor/condor_config.
/home/condor/condor_config exists.
Renaming to: /home/condor/condor_config.old.

Should I put in a soft link from /home/condor/condor_config to
/home/mpierce/condor/etc/condor_config [yes]

Press enter to continue.

***************************************************************************
Condor has been fully installed on this machine.
***************************************************************************

/home/mpierce/condor/sbin contains various administrative tools.
If you are going to administer Condor, you should probably place that
directory in your PATH.

To start Condor on any machine, just execute:
/home/mpierce/condor/sbin/condor_master

Since this is your central manager, you should start Condor here first.

Press enter to continue.

You should probably setup your machines to start Condor automatically at
boot time. If your machine uses System-V style init scripts, look in
/home/mpierce/condor/etc/examples/condor.boot
for a script that you can use to start and stop Condor.

Please read the "Condor is installed... now what?" section of the INSTALL
file for things you should do before and after starting the Condor daemons.
In particular, you might want to set up host/ip access security. See the
Adminstrator's Manual for details.

Using OGCE portlets in Gridshere 3.1 (preliminary)

2008-08-15T14:52:00.000-07:00

We had a request to get OGCE portlets running in Gridsphere 3.1. Below is the way to do this manually. We'll try to make an automated version of this with Maven next.

0. Shutdown tomcat.

1. In the ogce-portal-only directory, run the command mvn clean install -f global-config/pom.xml

2. Remove our versions of hibernate, hsqldb, and ehcache (probably these crept in from GS 2.1--I don't think we need them). Specifically,

rm global-config/common/target/cog-common-1.0/lib/hibernate2-OGCE.jar

rm global-config/common/target/cog-common-1.0/lib/hsqldb-1.7.1.jar

rm global-config/common/target/cog-common-1.0/lib/ehcache-0.9.jar

3. Copy the remaining jars into your Tomcat's shared/lib. Something like
cp global-config/common/target/cog-common-1.0/lib/* /Users/mpierce/GridSphere31/apache-tomcat-5.5.20/shared/lib/

4. Copy the OGCE portlet as is from the ogce-portal-only dir. That is, from ogce-portal-only, run "mvn clean install -f portlets/proxymanager-portlet" and then
cp -r portal_deploy/apache-tomcat-5.5.12/webapps/proxymanager-portlet/ /Users/mpierce/GridSphere31/apache-tomcat-5.5.20/webapps/proxymanager-portlet

5. Create empty files named after the portlets for Gridsphere. This used to be done in $CATALINA_HOME/webapps/gridsphere/WEB-INF/CustomPortal/portlets

Now these apparently go in $HOME/.gridsphere, so do this:

touch ~/.gridsphere/portlets/proxymanager-portlet.2

6. Edit the proxymanager's web.xml file to use the correct namespace for the PortletServlet (i.e., remove the "gridlab" section from the full name):

<servlet>
<servlet-name>PortletServlet</servlet-name>
<servlet-class>org.gridsphere.provider.portlet.jsr.PortletServlet</servlet-class>
</servlet>

7. In proxymanager-portlet/WEB-INF/lib, delete gridsphere-ui-tags-2.1.jar

8. Start tomcat and add the portlet using the Gridsphere Layout Manager.

GCE08 Workshop at Supercomputing 2008

2008-08-05T14:16:00.000-07:00

We are hosting GCE08, the fourth workshop in this series. Papers on portals, gateways, and other scientific user environments are welcome. For more information, see

http://www.collab-ogce.org/gce08/index.php/Main_Page

New GPIR Service URL for GPIR Portlet

2008-07-10T17:55:00.000-07:00

The old TeraGrid GPIR service is being retired and replaced. To point to the new server, edit GPIR's portlet.xml file and replace

http://alpine.tacc.utexas.edu:8080/gpir/webservices

with

http://laredo.tacc.utexas.edu:8080/gpir/webservices

To rebuild this portlet, use the command "mvn clean install -f portlets/gpir-portlet/pom.xml" from the "ogce-portal-only" directory.

Correction to OGCE 2.3 tar download

2008-07-07T08:22:00.000-07:00

The default value for the property <project.home> in ogce-portal-only/pom.xml was incorrectly set. While this can be edited manually, it prevents the portal from building out of the box if one follows the documentation.

Also, the obsolete filetransfer module, which causes the errors described at http://collab-ogce.blogspot.com/2007/12/filetransfer-portlet-build-error.html on some machines, has been removed.

These have been corrected in the download link at http://www.collab-ogce.org/. The version number has been incremented to 2.3.1 to reflect this minor update.

GTLAB TG08 Tutorial Release

2008-06-07T10:40:00.000-07:00

The TG08 tutorial release of GTLAB is now available from http://www.collab-ogce.org/ogce/index.php/GTLAB.

GTLAB provides Java Server Faces components and backing beans that simplify the process of Grid Web application development. You can use GTLAB to develop standalone Web applications, portlets, and Google Gadgets.

OGCE Portal Release 2.3 Available

2008-06-06T14:47:00.000-07:00

OGCE portal release 2.3 is available from http://www.collab-ogce.org/ogce/index.php/Portal_download. This release features major revisions to the XBaya workflow composer as well as minor bug fixes to GPIR and the build system.

The XBaya updates are part of the comprehensive enhancements to the OGCE workflow tools, http://www.collab-ogce.org/ogce/index.php/Workflow.

TG08 Gateways Summary

2008-06-03T14:11:00.000-07:00

Courtesy of Nancy Wilkins-Diehr:

For those attending TeraGrid 08, June 9-13 in Las Vegas we have a
terrific representation of Science Gateways at the conference.

Gateway-related topics are featured in:
14 papers
7 demonstrations
5 posters
5 birds-of-a-feather sessions
3 student competition entries
2 tutorials
1 vis gallery entry
And a face-to-face gateway meeting in a pear tree on Thursday June 12,
3pm.

Full information on the conference can be found at
http://www.tacc.utexas.edu/tg08/ and a listing of gateway-specific
activities at
<http://www.teragridforum.org/mediawiki/index.php?title=Science_Gateways
#Gateways_at_TeraGrid_08>.

Thank you to the many of you on this list who are contributing to making
the conference a success.  I hope to see many of you in Las Vegas next
week.

TeraGrid 08 OGCE Tutorial Outline

2008-06-02T07:49:00.001-07:00

Tutorial is Monday, June 9. We will make slides and material available for download.

8:30-9:30: Intro, building and using the portal, writing simple grid portlets (Marlon Pierce)

9:30-10:00: Workflow suite part 1 (Suresh Marru, Gopi Kandaswamy)

10:00-10:30: break

10:30-11:15: Worflow suite part 2 (Suresh, Gopi)

11:15-11:45: Web 2.0 for gateways (Gregor von Laszewski)

11:45-12:00: Teragrid gateway authorization requirements and GridShib (Tom Scavo)

OGCE Tutorial at TeraGrid 2008

2008-04-29T14:13:00.000-07:00

We will give a 1/2 day tutorial on June 9th at TeraGrid 2008 in Las Vegas. For more information, see http://www.tacc.utexas.edu/tg08/index.php?m_b_c=scienceGateways.

Topics will include building and using the basic portal, using GTLAB to make Grid Web clients, using the OGCE workflow suite of tools to wrap science applications, and Web 2.0 activities for science gateways.

GPIR Service Download Available

2008-04-21T09:54:00.000-07:00

An updated version of the Grid Portal Information Repository (GPIR) Web Service is available for download. This is a standalone repackaging of the GPIR Web Service in older OGCE portal releases.

The GPIR service powers the GPIR portlet in the main portal download. Get the GPIR service if you want to provide your own status information server for your grid.

http://www.collab-ogce.org/ogce/index.php/GPIR

Mac OSX Maven Build Errors

2008-03-24T08:44:00.000-07:00

We have reports of the following build error on Macs:

*******************************
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Project ID: org.apache.maven:maven-parent:pom:5

Reason: Cannot find parent: org.apache:apache for project: org.apache.maven:maven-parent:pom:5 for project org.apache.maven:maven-parent:pom:5

*******************************

Workaround: Download and install the Maven third party jars as described in the "Download" section.

The error does not appear in the Mac nightly build dashboard, so we are trying to discover the cause.