Tomcat Servers

• Finish migrating to using common configuration (not all servers are using common/conf/server.xml)
• Migrate to using 64 bit OS and 64 bit java to push the memory limit to 4Gb
• Look into tomcat clustering
• Wrap the tomcat application with java wrapper to be able to start/stop a server programmatically
• Figure out why sometimes jar files are lost from classpath (seems to be effecting apps on tomcat07)

Tomcat Server Monitoring

• Enable start/stop/restart servers from this application
• create a java program to register a MBean listener to receive notifications from the memory MBean when the memory goes over a given threshold
• find a way to assess the status of a web application. So far we can tell if an application is running or not according to tomcat, but even if the application is running it might be producing errors
• run a java application inside or outside this web app to run a simple query against the JDBC data sources to make sure they are running

Pipeline Jira FE Jira BE

• Ongoing tuning of Oracle database usage
• Ability to cancel running tasks
• Switch from exchange server to unix mail server
• Tuning of web interface for ongoing data processing (as opposed to MC Tasks)

Data Portal

Data Catalog Jira FE Jira BE

• (in progress Dan) Finish proposed changes to datacat line mode client
  • easier registration of files
  • ability to remove existing files
• (in progress Karen) add meta-data from the web interface

• Improve data catalog interface especially for real data
  • L1 data products arranged by groups rather than folders
  • Look into WebDav/GUI for data catalog

Astro Server

(Simple) Skimmer

Download Manager

• Line mode version of download manager

WIRED

Ops Log

• Make Ops Log use same login system as everything else
• Install latest version from Fermilab
• Enable programmatic entry creation
• Integration between monitoring tools and Ops Log
  • Ability to easily copy plots to ops log and comment on them
  • Ability to find all recent comments on a plot

Ongoing

• Maintainance of confluence/JIRA
  • Upgrade JIRA to latest version (we are far behind)
• Maintainance of Tomcat/CAS/etc
• Oracle performance/tuning
• Switch to new oracle server

Misc

• Stop using SLACDEV database (in progress)
  • Rationalize use of Dev/prod etc, decide if we need other configuration options
    • For ISOC the databases are: Flight, Integration, Test, Nightly

• Make sure all web projects are under cruisecontrol

Infrastructure

• implement links between application (done preliminary version)

Data Quality Monitoring

Scope

This application will provide output histograms and data trends resulting from the Fast Monitoring, Digi and Recon processing. The driving process is the L1Proc; root files from each of these processing steps will be registered with the data catalog and picked up by the application in order to display quality histograms. Separate processes will load Digi and Recon tuple files to ingest them into a database for the data trending.

Status

• It is currently possible to display histograms from Fast Monitoring, Digi and Recon.

• We have a first implementation of the code to ingest trending data into general purpose database tables and managed to produce plots from the web application. The result of this effort was that we need to create new database tables specific to this application.

• Alarm Handling
  • The Fast Monitoring process ouputs an xml file with a list of the alarms/warnings/errors detected on the produced monitoring histograms
  • This file is registered with the data catalog
  • A notification is added to the Logging application which points to the Data Quality Monitoring application
  • The xml file is ingested by the application producing summary and detailed information on the alarms/warnings/errors

• Data Trending
  • Tables to ingest the trending data are available : some 50K quantities at a frequency between 10 seconds and 5 minutes
  • Several copies of the same tables are used to accumulate data at different frequencies
  • Code to ingest the data is available and used as part of the L1Proc.
  • Trending plots are produced from the database

• Plot Description
  • Description can be added to each plot

To-Do List

• Alarm Handling
  • Ingest detailed information from xml file, like which bins produced an alarm etc.
  • Display alarm information on the plots, like warning/alarm limits or arrows on responsible bins

• Data Trending
  • Given the volume of data a database table only approach might be insufficient. We might have to consider a hybrid solution that involves reading data straight from tuple files (less efficient that reading from a db)

• Improve the application's UI
  • User preferences
  • Improvements based on user's feedback

Source Monitoring Jira

Scope

Display ASP data products for a pool of sources.

Status

This is the second implementation of this application. We have developed a set of databases to keep a list of sources and to ingest data to be trended at different frequencies. The sources database can be loaded from xml files used by ASP. Scripts are available to ingest the data from the pipeline at the end of ASP processing.

This is still a preliminary version of the application and needs feedback to better define its scope and use.

To-Do List

• Improve the application's UI
  • User preferences

Data Processing

Scope

This application should provide a quick and intuitive look at the status of data processing from the moment it is being Fast Copied through the various processing steps that lead to the final data products.

Status

A preliminary version of the application has been used during the October Test and it worked pretty well.

• Downlink-RunId database tables have been created
  • with these tables it is possible to extract which run numbers are contained in each downlink
• The progress mechanism has been defined as the number of completed sub tasks for a given process.
  • When new sub tasks are forked off the overall progress might go backwards

To-Do List

• Remove duplication between data processing page and other apps
  • One possibility is to hide queries in functions

GCN/GRB Web front end

Scope

Tabular overview of most recent Noticies and possibility to browse GRB/Noticies.

Status

• Databases have been designed.

Portal

The portal is the icing on the cake. It will be targeted and developed at the very end.

Scope

Provide a rich and highly customizable environment for viewing data from all the above (and below) applications.

Status

We have developed three portlets to prove that we can extract data from external applications. These portlets can provide tables (from Logging and Fast Copy) and pots (from TelemetryTrending).

To-Do List

Do the rest.

Cross Trending/Reports

Scope

This application should give users the possibility to fetch histograms and data trends from all the above applications and to create scatter plots, overlays or tables of data.

It should also be possible to load simple user-written jsp pages as reports. Users can create a list of favorite reports to be processed at different frequencies (say last 24 hours, last week, last month etc.)

A user would write reports in the form of jsp pages with some special tags to embed plots, text, links, etc.
These pages will be registered with the applications.
The application would provide a tabulated lists of all the available reports and a way to generate them on some time period.

Status

A toy version is available for the cross trending part. The Reports are still in the discussion phase.

To-Do List

• Write database tables to store report jsp pages
• Define tags API to embed plots in jsp apges

Data Server

• Get LAT Data Server tied into L1Proc

Data Portal Jira

• Get portal working, at least for items like data processing page, grb summary etc
  • Generate RSS feeds from LogWatcher, Ops Log, JIRA, Confluence etc to display on portal page