[Devel] Re: [OGCE] Question on grid portlet choices (fwd)

An update on the status of OGCE and how it relates to the components it
includes. Basically, the latest release (2.0.4) is a bundle of much of
what you need to get off the ground with a grid portal. As, such I'm
included to start with the bundle and only take the roll-your-own
approach if the situtation demands it.

~jpr

---------- Forwarded message ----------
Date: Wed, 10 Jan 2007 20:09:05 -0500
From: Marlon Pierce
To: John-Paul Robinson
Cc: discuss@ogce.org
Subject: Re: [OGCE] Question on grid portlet choices

That's pretty much it. Version 1.0 aimed at being container independent
(uportal or gridspere) but this was a little complicated (you had to
download and install Tomcat and your container first). In Version 2.0 we
just went with GridSphere as the container and made a single build that
will compile and install everything from a single install command.

We started this "everything in one download" install with the Gridport
project and then took it over and extended it with the OGCE2 2.0. We
decided just to take all of the grid portlets we had in hand. These
portlets show a couple of different ways for building portlets--the
portlets from 1.0 use the Java CoG 4 APIs, for example. These also
support WS-Gram.

One major portlet not in the 1.0 series is the condor portlet that is
included in version 2.0.

GridSphere GridPortlets is a separate project.

I'll check on the mailing list archive. We switched domain hosts and
this might have been a casualty.

Marlon

John-Paul Robinson wrote:
> Howdy,
>
> I've been reviewing the latest update from OGCE (2.0.4) and was triing to
> get a clearer picture on how this bundle relates to some other projects
> (both included in the bundle and not.)
>
> From what I can tell:
>
> * Gridsphere has it's own collection of Grid Portlets
> * OGCE2 doesn't use these grid portlets
> * OGCE2 uses the GridPort project's portlets for similar functionality
> * OGCE2 includes other portlets (some developed by the OGCE team?) to make
> a "complete" out-of-the-box solution
>
> * Installing OGCE 2.0.4 would be like manually installing Gridsphere
> 2.1.5, without the Gridsphere grid portlets, adding in the GridPort 4.0.x
> (the latest), plus some OGCE portlets, plus Sakai.
>
> * The major difference between OGCE2 1.0 and 2.0 is that in 1.0 you had to
> do the bundling yourself and in 2.0 you don't, though you might have less
> control over all the peices that do get installed.
>
> I'm sorry to reask this question. The FAQ comes close to answering this
> but doesn't give me a solid "You should use OGCE2 2.0.4 if you don't want
> to do a lot of integration, but otherwise OGCE2 1.0 contains similar
> versions".
>
> I tried looking at the discuss archives but the on-line link seems to be
> down.
>
> Thanks for taking the time to provide me a bit more confidence before
> getting started on all this and confirming my reading of the material. :)
>
> ~jpr
>
> P.S. What I'm really interested in doing is plugging the MAMS Shib addon
> for Gridsphere 2.1.5 into this stack to I can use this all in a web iso
> environment. I just want to make sure I have the foundations in place. :)
>