Incubator/WEEP

From Globus

More details about the project can be find on the project Web Site

• WEEP Web Site
• WEEP Portal - development server!! (can be down any time!)

Contents 1 Incubator Product Metadata 1.1 Status 1.2 Roadmap 2 Incubator Project Metadata 2.1 Committers 2.2 Mailing Lists 2.3 Installation 2.3.1 Requirements 2.3.2 Ant Tasks 2.4 Running Counter Service Example 2.5 TODO List 2.6 Policies 2.6.1 Guidelines for committers 2.6.2 Guidelines for individual contributors 2.7 Contributors

Incubator Product Metadata

Status

The WEEP project is currently under development at Institute of Scientific Computing, University of Vienna

The status of WEEP is: Newly accepted Incubator Project in January 2007, as defined by the Incubator Process Guidelines found at http://dev.globus.org/wiki/Incubator/Incubator_Process .

Roadmap

Coming Soon.

Incubator Project Metadata

Committers

Christian Kloner
Ivan Janciak
Shannon Hastings
Scott Oster
Ravi Madduri
Amine Belkoura

If you would like to become a committer, guidelines are [here].

Mailing Lists

Developer discussion	archive	subscribe	unsubscribe
User discussion	archive	subscribe	unsubscribe
Announcements	archive	subscribe	unsubscribe
Commit notifications	archive	subscribe	unsubscribe

How to subscribe
How to unsubscribe
Search the email archives

Installation

The WEEP engine consists of several java packages stored in the project's maven2 repository. They can be accessed using specialized tool 'WEEP Starter'. This tool allows to download all required packages, deploy the engine into GT4, start the engine and some other tasks. To use the starter application with the WEEP do the following:

• Download WEEP Starter, unzip the file and go to the './weep' directory.

• Be sure that your environment variables JAVA_HOME, ANT_HOME, GLOBUS_LOCATION, MAVEN_HOME point to the respective installation directories.

Requirements

• Java Runtime Environment (JRE) 5.0 or greater
• Apache Ant-1.6.5

Note: Do not use Apache Ant 1.7.x !

Ant Tasks

The main tasks of the Starter tool are following:

Deploying the WEEP engine to the GT4

ant deploy-globus

Starting HSQLDB

ant run-hsqldb

Starting Dynamic Invoker

Dynamic Invoker is a handy application which provides a convenient way of testing the underlying API of the WEEP engine. A simple example of using Dynamic Invoker with CounterService can be found here.

ant run-invoker

Running Counter Service Example

The example files are zipped in GWA archive which contains:

• WSDL file
• BPEL file

To start the Counter example run the following command from ./modules/client directory:

and run /
-Dtemplate.factory.url= /
http://localhost:8080/wsrf/services/gridminer/weep/ProcessTemplateFactory /
-Dgwa.example.url= /
http://weep.gridminer.org/examples/process_example_0.gwa

TODO List

• 1) Documentation of existing features
  • Examples using:
    • PartnerLinks stuff
    • invoke
    • assign (copy using XPATH,XSLT)
    • flow
    • sequence
• 2) Implement other useful BPEL constructs
  • Priority list:
    • a) full receive support
    • b) looping
    • c) links
    • d) conditions
    • e) ....
• 3) Security and Delegation in workflows
• 4) Comparison paper for BPEL engine implementations
  • Architecture superiority of WEEP over others and find out performance
• 5) WEEP WhitePaper - short overview of the project objectives
• 6) Build a community around WEEP

Policies

In addition to the Globus Alliance Project Guidelines, the WEEP project adheres to the following policies:

Guidelines for committers

• Currently this projects source code is being managed at the GridMiner svn repository.

Guidelines for individual contributors

• If you wish to become a contributer to this project please email Ivan at mailto:janciak@par.univie.ac.at

Contributors

The WEEP project gratefully acknowledges the following contributions

• Peter Brezany
• Malcolm Atkinson
• Joel Saltz