[
https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152620#comment-13152620
]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1203476 I:
- added 2 properties to the context.xml config:
{noformat}
org.apache.oodt.pcs.trace.excludeList
org.apache.oodt.pcs.trace.enableNotCat
{noformat}
* org.apache.oodt.pcs.trace.excludeList - A comma separated list of product
type *name*s to exclude from the Trace. This has been useful in situations
where there are products that have TONs of recursive dependencies to search
through and you just want to speed up your traces.
* org.apache.oodt.pcs.trace.enableNotCat - This enables products that aren't
cataloged in the FM to be included in a PCS trace tree. This is useful in the
situation where you have e.g., a met extractor config file that's been included
in either the InputFiles or OutputFiles met key, but that hasn't been cataloged
in FM.
> 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
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
