[OODT-157] PCS Operator User Interface web application

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.4
• Component/s: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
• Labels: interface operator pcs
• Assignee: Chris A. Mattmann
• Reporter: Chris A. Mattmann
• Created: 14/Mar/11 03:08
• Updated: 25/May/12 21:04
• Resolved: 31/Mar/12 22:46

Description

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:

1. A File Manager Browser webapp, with PCS trace enabled
2. A Workflow Monitor webapp
3. A PCS status monitor
4. 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:

1. Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
2. depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
3. Overlay OODT-155 and OODT-156 on top of the webapp
4. Port the PGE configuration/CAS configuration parts of the webapp to Wicket

Yes, this is another monster issue.

Issue Links

• incorporates: OODT-346 Create a Maven Archetype for Ops UI
• is related to: OODT-434 Finish config pages in PCS Operator Interface