Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Software Projects

For a diagram of the currently deployed infrastructure, see Overview.

NOTICE: The documentation provided below on the "workflow broker" refers to a version of that service which is no longer supported. Much of the page is also lagging (the Ogrescript user's guide is missing entries for a number of new tasks). The following links refer to more recent work:

  • For the most recent description of the workflow engine, see PWE2008.

  • Some guidelines for using version 3.0+: Siege_3.0.

  • For ongoing thoughts concerning the integration of PWE with PTP, see PTPFLOW.

The most up-to-date documentation is now being made available as Eclipse Help Pages (ncsa.eclipse.help plugin) distributed on the PTPFLOW update site.

...

The following (especially Workflow Broker), are out of date:

Libraries

Name

Description

Trebuchet

Multi-protocol file transport library

Ogrescript

Extensible XML scripting language

...

Name

Description

Elf

Robust, extensible container for remotely launched scripts

Trigger Agent

Mananges remote actions

MyLEAD Relay Agent

Handles metadata updates to the MyLEAD Agent; also produces WS Events

Web Services

Name

Description

Workflow Broker

Scalable, high-level control-flow service with parameterization capabilities for generating and managing ensemble-like workflows

Event Repository

Persistent store for accessing historical event info

Host Information Service

Information service holding host-based data

Configuration Tuple Space

Tuple-space-like service for distributed exchange of Configuration descriptionsserialized XML objects

Graphical User Interfaces

Name

Description

Siege

Extensible front-end client based on Eclipse Rich Client Platform

Guides

Work in Progress

  1. Complete integration of Broker into LEAD workflow; see further under MyLEAD Relay Agent (Rossi).
  2. A tuple-space-like service for use in connection with "glide-in" submissions of many-member parameterized workflow nodes (Rossi)
  3. Supporting mechanisms in the Broker and ELF for handling "glide-in" capabilities (Rossi)
  4. A configuration service for storing re-usable execute configurations (Rossi)
  5. Modifications to the broker to support dynamic configuration of execute nodes via matching on such stored configurations (Rossi)
  6. Full implementation of the scheduling module using some combination of MOAB and Batch Queue Predictor (Rossi)
  7. JMS Trigger implementation for Trigger Agent (Rossi)
  8. Fortran Namelist Editing View for Siege (Rossi)

Developers

...

...