Active Archive Facility Components

  • Web server:, managed by central Web management * Gratia collector: * Server/user generating the dynamic pages: * Data is coming form the database, schema:gratia_aaf

Administrator Instructions

These instructions come from the README.txt file in the git repository

Active Archive Facility

src - contains the scripts updating the pages
htdocs - contains html documents (static pages, scripts, css, and the template directory for VO pages)

1. Actions to create a VO section (i.e. add a new AAF customer):
- copy filechunk.php and filesize.php from template (no changes needed)
- link COMPLETE_FILE_LISTING.json to the appropriate json file (e.g. ../../data/filelists/COMPLETE_FILE_LISTING.<VONAME>.json). It does not matter if the file exists.
- copy the help.html and filelist.html files from template and replace variables ($VO)
- make the images, csv and archive sub-directories
- update the admin/admin-content.html file with the timestamp and the list of users as tabular elements (e.g. add a line like <li><a href="/folder_name/">customer_name</a></li>)
+ actions in 2. and actions in 3.

2. Actions to update a VO section monthly (each time new archived pages are added)
- generate a pdf report for the past month (printing the current index)
- update the history.html page using the template and substituting the variables (note that you need also the list of all the previous PDF files) - Done by src/

3. Actions to update a VO section (each time new daily plots are refreshed)
- recreate index.html from the version in template, substituting all the variables - Done by src/

Developer notes

Here some notes or explanations written during development:

Gaining access to the Active Archive code

To gain write access to the code, you need -

  • A valid Fermilab Kerberos principal * A valid services account * Developer level access to the active_archive project in

Once you have the access you can checkout the code using

git clone ssh://

NOTE If your authentication is failing (Permission denied ...) even if you have a valid Kerberos ticket, make sure that SSL is configured to use Kerberos.
E.g. in ~/.ssh/config you have:

GSSAPIAuthentication yes
GSSAPIDelegateCredentials yes