Personal tools
You are here: Home → Developer → Interest Groups → Web User Interface Interest Group → Web User Interface Interest Related Work

Web User Interface Interest Related Work

An overview of the current related work to Kepler Web User Interface

SciencePipes.org Web User Interface (Cornell)

Technology:

  • Java 1.5
  • Hibernate 3
  • Spring 2.5 and Spring Security (Acegi)

Implementation Infrastructure:

  • MySQL (very few MySQL-specific features used)
  • WebSphere App. Server (nothing IBM-specific knowingly used)
  • Eclipse used for development

UI Features:

  • workflow management
    • browse
    • search
    • upload
    • copy
    • version
    • delete
    • download
  • parameter management
    • custom default values
    • custom parameter prompts
    • designating parameters as required
    • expose subset of parameters for new values when workflow is run
  • job management - a job is a workflow that is to be executed with specificied parameters
    • see status
    • cancel job
    • delete job
  • workflow results management
    • see results from a particular job
    • see results from the most recent run
    • output is URL accessible and can be used as a permanent web resource
    • output from a specific job can be referenced individually
    • output from the most recent run of a job can be referenced as a permalink
  • "community" tools
    • tagging
    • favorites
    • rating
    • comments
  • user account management
    • login/logout/remember me
    • create/edit user account
    • password reminder

Backend Features:

  • actor management
    • filters are used to replace normal Kepler/Ptolemy actors with compatible actors that are aware of the output repository
    • not all Kepler/Ptolemy IO actors have replacements yet
    • actor replacements utilize Spring for configuration
  • job engine interface
    • an engine takes a job and runs it in its entirety
    • engines run in any Kepler-compatible JVM
    • scalable by adding more JVMs (on the same machine or other machines)
    • size of thread pools that engines utilize can be customized to the JVM/machine resources
  • workflow repository interface
    • Hibernate/MySQL Implementation
      • MoML storage flexibility
        • stored in DB as BLOB
        • as URL reference
    • obvious potential for other implementations utilizing MetaCat or Fedora Commons
  • output repository interface
    • metadata (size, mime-type)
    • Hibernate/MySQL Implementation
      • content stored in DB as BLOB
  • parameter repository interface
    • Hibernate/MySQL Implementation
    • also handles one-time use job parameters

Hydrant

Technology:

Implementation Infrastructure:

UI Features:

Backend Features:

KFlex 

Detailed Information here:  KFlex

License:

Backend: Open-Source

(same license as Kepler 1.0)

Frontend: OpenSource (Source Code not yet released)

Technology:

Implementation Infrastructure:

UI Features:

  • workflow management
    • create new workflow
    • edit workflow
    • execute workflow
  • workflow editing
    • quite similar to the standard Kepler rich client

Backend Features:

  • Web Service Description Language Interface for Kepler Workflows
  • Headless execution
  • Central Worflow Repository

Online Demo:

http://serv-4101.dfki.uni-kl.de/demos/extern/KFlexClient/KeplerFlexClient.html

 

Screenshots:

KFlex - Simple Workflow

 

 

Document Actions