PCS Operator User Interface web application
-------------------------------------------
Key: OODT-157
URL: https://issues.apache.org/jira/browse/OODT-157
Project: OODT
Issue Type: Improvement
Components: crawler, file manager, pge wrapper framework, push pull
framework, resource manager, workflow manager
Reporter: Chris A. Mattmann
Assignee: Chris A. Mattmann
Fix For: 0.3
We've got quite a nifty Operator User Interface web application at JPL that
we'd like to contribute to the Apache OODT framework. We baked it up on OCO and
used it on some other projects, including NPP Sounder PEATE (and SMAP, in
progress). I'll attach some screenshots, but basically what it consists of is:
# A File Manager Browser webapp, with PCS trace enabled
# A Workflow Monitor webapp
# A PCS status monitor
# A PGE configuration/CAS configuration webapp
The existing version of this app is written is Struts and unfortunately is
pretty messy at the moment. During this porting process, it's my proposal to:
# Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
# depend on pcs/services to implement a Wicket-ized version of the PCS status
monitor and the PCS trace functionality
# Overlay OODT-155 and OODT-156 on top of the webapp
# Port the PGE configuration/CAS configuration parts of the webapp to Wicket
Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
