Installing and Building GTLAB

Installing and Building

GTLAB

GTLAB and OGCE

— OGCE contains multiple sub-projects

— Portlet-based Grid portal (with GridSphere and Tomcat). — Workflow suite (services and add-ins to the portal)

— Information Web services — Gadget container

— Cyberaide JavaScript libraries

— GTLAB

— These are packaged with Maven and include everything you need except Java and (for some services) MySQL.

— We try to make things installable with minimal fuss. — Consistent directory structures across projects

— Edit one config file (pom.xml)

User’s Browser

Portlet, Gadget Containers iGoogle, Facebook

GTLAB Gadgets

TeraGrid Services

(GRAM, GridFTP, INCA) Google GData Services,Twitter Feeds, etc RPS, RDS, GPIR

Services

Various GTLAB

applications deployed

as portlets:

GTLAB Applications as Google Gadgets:

MOAB dashboard, remote directory

MyProxy Example

<h:form id="form">

<h:outputText value="Username:"/>

<h:inputText value="#{resource.username}" required="true"/>

<h:outputText value="Password: "/>

<h:inputSecret value="#{resource.password}" required="true"/>

<h:outputText value="MyProxy Server: "/>

<h:inputText value="#{resource.myproxyHostname}" required="true"/>

<o:submit id="submit" value="Submit" binding="#{builder.body}" action="#{builder.junkAction}" >

<o:multitask id="multi" persistent="true" taskname="#{resource.taskname}"> <o:myproxy id="mypr" hostname="#{resource.myproxyHostname}"

lifetime="2" password="#{resource.password}" port="7512" username="#{resource.username}"/>

Executing Multiple Task

<o:submit id="submit" value="Submit" binding="#{builder.body}"

action="#{builder.junkAction}" >

<o:multitask id="multi" persistent="true"

taskname="#{resource.taskname}">

<

o:jobsubmit id="js"

myfaces="true"

arguments="#{resource.arguments}"

executable="#{resource.executable}"

hostname="#{resource.hostname}"

provider="#{resource.provider}"

stdout="#{resource.stdout}"/>

<

o:filetransfer id="ft"

myfaces="true"

from="#{resource.from}" to="#{resource.to}" />

<o:dependency id="dep" task="ft" dependsOn="js"/>

<o:submit id="submit" value="Submit"

binding="#{builder.body}"

action="#{builder.junkAction}">

<o:multitask id="multi"

persistent="true"

taskname="#{resources.taskname”>

<o:rpsOptimal

resource="task1-resources"

id="rpsoptimal-exec"

myfaces="true"/>

</o:multitask>

</o:submit>

Example with Dependency

<o:multitask id="multi” …>

<o:rpsAddModel resource="task1-resources"

id="rpsAddModel-exec"

myfaces="true"/>

<o:rpsManager resource="task1-resources"

id="rpsManager-exec"

myfaces="true"/>

<o:dependency id="deps-rpsstuff”

task="rpsManager-exec"

dependsOn="rpsAddModel-exec"/>

GTLAB Features

—

Extends Java Server Faces.

o Tag components wrap major COG Abstraction Layer features

o And Web Service clients, GridShib, etc.

o Supports tag inter-dependencies.

—

Allows you to do

standalone

development.

—

Use JSF portlet bridge to

convert

into portlets

§ No new coding, just add/modify XML config files and jars.

§ Process is automated

—

Or

forget about portlets

o Convert into Google Gadgets

o Develop as a Facebook application

Getting GTLAB

—

See

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

—

Y

ou can use your favorite SVN client to check out.

— svn co https://ogce.svn.sourceforge.net/svnroot/ogce/GTLAB

(latest)

— svn co

htt ps://ogce.svn.sourceforge.net/svnroot/ogce/tags/GTLAB-tg09 (tagged)

—

“Latest” will give you easy access to any updates

— “svn update”

No SVN? Get the TAR

—

SourceForge’s SVN/CVS

viewer now provides a

“Download GNU Tar”

option.

—

h

ttp://ogce.svn.sourc

eforge.net/viewvc/ogc

e/GTLAB/ f

or latest.

Levels of Abstraction in GTLAB code

You can use prepackaged gadgets/portlets.

You can develop new applications using

existing tag libraries.

You can make new tags for your services

You can hack or steal the code

—

Note JSF is compatible with JSP, so you can mix

and match.

—

And you can embed JavaScript

— YUI, Scriptaculous user interface goodies.

Tag

Description

MyProxy

Gets a proxy credential (COG)

JobSubmit

Runs remote commands (COG)

FileOperation

Create, delete, list remote files and

dirs (COG)

FileTransfer

GridFTP downloads, 3

_party

transfers (COG)

XSubmissionOutput Format outputs of job and file

operations

ResourceDiscovery

Clients for the RDS

ResourcePrediction Clients for the RPS

MyCommunityProxy Get and decorate TG Community

credentials with Grid Shib

GTLAB Example

Description

MyProxyExample

Get a credential and store in OGCE

global proxy store.

JobSubmitExamples

Various examples showing how to

submit a grid job and get output.

Dashboard Examples Runs showq on Big Red, Cobalt, and

Mercury and formats output.

DirectoryBrowser

Displays and downloads files on a

remote host via GridFTP

MultipleTaskExample Shows how to couple file transfers,

operations, and

GTLAB Gadgets Code Base GTLAB Portlets Code Base Tomcat Web Server

Tomcat Web Server +

Portlet Container iGoogle

Client Aggregator

Compile and deploy into server

Decorate with bridge and container jars, xml config files.

GTLAB gadgets

can also run as

portlets with no

code changes by

using the JSF

Making GTLAB Google Gadgets

—

A Gadget is a standalone application that is integrated

into your personal iGoogle display.

—

They can run on

your Web server

.

—

You can use

SSL/HTTPS

—

Google Gadgets have two versions

—

http

: these use Google’s JavaScript APIs

—

url

: these wrap external applications with Iframes.

Example Gadget Config File

<?xml version="1.0" encoding="UTF-8" ?> <Module>

<ModulePrefs title="MyProxy Gadget Example" scrolling="true"

height="500"/> <Content type="url"

href="http://…/:8080/GTLAB/examples/MyProxyExample.jsf">

</Content> </Module>

Other Gadgets

Providers Tomcat + GTLABGadgets

Grid and Web Services

(TeraGrid, OSG, etc)

Other Gadgets Providers

Social Network Services (Orkut,

LinkedIn,etc)

RSS Feed, Cloud, etc Services

Gadget containers aggregate content from multiple

providers. Content is aggregated on the client by the user. Nearly any web

application can be a

Click “Add stuff” and

then “Add feed or

GTLAB Applications as Google Gadgets:

MOAB dashboard, remote directory

Tomcat +

Portlets and Container

Grid and Web Services

(TeraGrid, OSG, etc)

Grid and Web Services

(TeraGrid, OSG, etc) Grid and Web

Services

(TeraGrid, OSG, etc)

HTML/HTTP

SOAP/HTTP Common science

gateway

architecture.

Aggregation is in the portlet

container.

Users have limited selections of

Making GTLAB Gadgets into Portlets

—

Do all development in

jsf_standalone

directory

— This is where your template tags will be placed

—

When you are ready to convert:

— Download and build the OGCE portal

—

cd GTLAB/transition

—

mvn clean process-resources

—

cd GTLAB/portlets

—

mvn clean install

—

You will need to make small

edits

to portlet.xml,

group.xml, and layout.xml in

GTLAB/portlet/src/main/webapp/WEB-INF/

Various GTLAB

applications deployed

as portlets:

Build GTLAB

—

Unpack or checkout code

—

Cd GTLAB

— All commands are executed from here.

—

Edit properties at the

top of pom.xml.

— Change IP

— Change project.home if you unpack someplace besides $HOME.

—

Run “mvn clean install”

Run Examples

— From GTLAB, start tomcat with ./startup.sh.

— From GTLAB, stop Tomcat with ./shutdown.sh

— Point browser to http://localhost:8080/GTLAB

Next Steps

—

Play with examples.

—

These are really bare bones. Make something

interesting.

—

Make a Google gadget.

—

Mix and match

tags in a pipeline

to make a new

application.

—

Use the dependency tag.

—

Note you can mix and match JSF and JSP if you are

not familiar with JSF.

—

Try making a new tag.

Making a New JSF Page from Tags

—

I recommend starting from the

examples

.

— jsf_standalone/src/main/webapp/examples

—

“Build” the examples with

— mvn –o clean install –f jsf_standalone/pom.xml

—

The “-o” option is used to

build offline

. Will also avoid

unnecessary Maven repository updates.

—

The “-f” specifies only build this specific module.

—

I recommend not futzing with the deployed versions under

portal_deploy.

Making a New Tag

— Run the following command from GTLAB:

— mvn clean processresources Dtag.name=test -Dprojectname=Test -f templateTag/pom.xml — Add -Ddest.dir=/tmp for a dry run.

— Replace “test” with the name of your tag.

— Replace “Test” with the name for your Bean.

— This will make 4 files

— TestBean.java, TestTag.java, TestBeanFactory.java, UITest.java

— Edits also 3 config files

— gtlab-factory.xml, managed-beans.xml, components.xml

Implementing a Tag

—

The place to start is TestBean.java (or whatever

you used for –Dprojectname=…).

—

This includes several inherited methods that can be

implemented.

—

Most important is

submit()

. Use the try/catch

block. This is where the action is.

—

If you want to hook tags into chains, implement

getOutput()

and

setInput()

.

Suggested Tags: A Wish List

—

What can you do in your bean? Anything server-side Java

can do.

—

Some suggestions:

— Implement a tag client to a remote Web service. Amazon has

some interesting ones….

— Implement an RSS/Atom feed client to Twitter, your blog, Facebook, etc.

— Combine the feeds as a mash-up.

— Connect to a database with JDBC.

— Implement a JMS publisher or subscriber.

— Use Google Java APIs to interact with Blogger, Calendar, and YouTube.

Example: Make an INCA Dashboard

—

INCA is used as the testing framework for the TeraGrid.

—

You can get the latest INCA test results from the URL

— ht tp://inca.teragrid.org/inca/XML/kit-status-v1/portal_summary

— See Sangmi’s notes at

htt p://sangpall.blogspot.com/2009/03/being-nice-client-of-inca-service.html

—

You’

ll get back some fine looking XML.

First, Create a New, Empty Tag

mvn clean process-resources \

-Dtag.name=incastatus \

Second, Implement the Bean

—

Main thing is to implement IncaStatusBean’s

submit() method.

—

Code is hard to put in a PPT slide

—

See

Third, Implement a JSF Page

—

Actual tag is shown below.

—

Full example is

http://ogce.svn.sourceforge.net/viewvc/ogce/GTL

AB/jsf_standalone/src/main/webapp/examples/Inc

aStatusExample.jsp?view=log

—

It includes some boilerplate (can be automated).

<o:incastatus id=”mytest"

Here’s the resulting page. You can make into a portlet in a

couple of steps. You can also tie to other tags in a

Next Steps: Make a Pipeline

—

Implement the

setInput() and

getOutput() methods.

—

Pipeline it with the

Resource Description

and Resource Prediction

Service tags.

—

Integrate QBETS tags

— Currently unwritten

—

Integrate with Job

Submission

Find Running Hosts (INCA or RDS)

Find Best Host for YourJob (RPS)

Find Host with Shortest Wait Time

(QBETS)

More Stuff about GTLAB

—

Supports

linear tag dependencies

.

— Removed dependence on COG graph processing (still use the

COG)

— We can support graphs of any tag you care to write.

— Only support pipelines currently, not full DAGs

—

Redesigned to

simplify writing new tags

.

— Extensive use of factories.

— You no longer have to change core code to add a tag

— Templates for 4 Java files and 3 XML config files now can be done in one (mvn) step