Athenaeum - Remote Athena Version 2.2.3.0 (build 02/Oct/2012 at 13:36:10 CEST)

• Overview
• *** What's New ***
• Web Service at CERN_PRO and CERN_DEV
• Documentation
• Download the latest distribution or Web Service war file
• HowTo Deploy the Worker.
• Google Gadgets:
  • Athenaeum Servers Status:
• WebStart:
  • 
• Android:
  • Android client
• Bugs/ToDos/Requests
• Release History
• Related Documentation and Presentations

Overview

Athenaeum implements client connection to (remote) Athena process via XML-RPC bridge using Athena Python shell. User can execute any Python script on the server and get its results. Plugins allow customised access to Athena functionality.

Documentation

Documentations:

• JavaDoc
• Source
• UML (top-level)
• XML Schema
• XSDDoc
• Ant Build Dependencies

Athenaeum provides several clients. It is preferable to use the Java client because it is the only client implementing some additional features:

• Compression of XML-RPC return messages. That is important mostly for big data transfer.
• Asynchronous XML-RPC messages. XML-RPC message is executed in parallel with the main client thread.

• Java API can be directly called from any Java program:

  
  // Get Athena Client
  PureAthenaClient client = new PureAthenaClient(url, key);
  // Get Script Result as a String
  String result = client.getRemoteString(scriptFile);
  // or
  // Get Script Result as a JAXB Tree
  List result = client.getRemoteTree(scriptFile);
  

• Python API can be directly called from any Python script like as shown in a Python client example.
• PHP API can be directly called from any PHP script as shown in a PHP client example. Script uses PHP XML-RPC implementation.
• C++ API can be directly called from any C++ program. It is devided into two parts:
  • Athenaeum wrapper (src/CPP/wrapper) gives access to remote Athena server and allows to send Python scripts there.

    
    // Get Athena Client
    Athenaeum athenaeum;
    // Get Script Result as a String
    std::string result = athenaeum.callAthena(url, key, scriptFile);
    

  • Athenaeum XSD parser (src/CPP/xsd) allows natural parsing of Athenaeum XML files. It is based on XSD and XercesC packages. C++ files are generated with those commands:

    
    xsd cxx-tree --root-element athenaeum --generate-polymorphic Athenaeum.xsd
    xsd cxx-tree --root-element athenaeum --generate-polymorphic xml.xsd
    

    
    // Parse Athenaeum XML file
    std::auto_ptr a = athenaeum(fileName);
    // Access data
    std::cout << "Athenaeum Server = " << a->server() << std::endl;
    ...
    

• Commands implemented via executable jar-files:

  
  java -jar ${ATHENAEUM_DIST}/lib/AthenaeumCLI.exe.jar
  java -jar ${ATHENAEUM_DIST}/lib/AthenaeumEventLookup.exe.jar
  java -jar ${ATHENAEUM_DIST}/lib/AthenaeumExtract.exe.jar
  java -jar ${ATHENAEUM_DIST}/lib/AthenaeumManage.exe.jar
  

• JSP Web Service is encapsulated in a standard war file which can be deployed in any standard Web Service Container (for example Tomcat). The instance of deployed Athenaeum Web Service is available at http://cern.ch/Athenaeum.

The same data are shared between different Frameworks/Applications implemented in different languages. All data representations are derived (generated) from the XML Schema.

Ant Build files build.xml manages building and testing Athenaeum.

The package distribution is available here (it includes command line client Athenaeum.exe.jar and JSP Web Service Athenaeum.war). Java 1.6+ is required to run. Ant 1.5+ and JWSDP 1.5+ are required to build. XercesC 2.7+ and XSD 2.1+ are required to build and run C++ API.

Public servers are running on several machines, their status is available from Web Page or Google Gadget: .

Bugs/ToDos/Requests

Bugs:

• ...

ToDos:

• ...

Release History

• 0.0.0:
  • Initial release.
• 1.0.0:
  • Can connect to remote Athena Python XML-RPC Server.
  • Can issue a script on the Server, getting back stdout and stderr results.
  • Can create Athena Event Loop Record Source.
  • Can be run in a standalone environment (outside JAS).
• 1.1.0:
  • Athena objects can be associated with JAS Adapters via Proxies.
• 1.2.0:
  • Athena can communicate with Proxies via JAXB Model.
  • Info proxy available.
  • Cool proxy available.
  • XSLT presentation of results available.
  • For Cool, Athena is not needed. PyCool is sufficient.
• 1.2.1:
  • Analysis interfaces added.
  • XML Browser added.
  • New InteractiveServer added, uses key authentication.
• 1.3.0:
  • User can rebuild Athenaeum.
  • Even invalid (but syntacticaky correct) XML can be shown in a Tree View.
  • JAXB model is created only when needed.
  • Text area in the XML Editor has a meaningfull content.
  • User can use her Python script or modify the default one in Proxies.
  • User can modify XSLT stylesheet.
  • All channels are lookt at to find payloads.
  • NTuple creation bug fixed.
  • InteractiveServer can be called specifying part and key.
  • XML-RPC message is securised by MD5 digest.
  • Full or customised Tree View can be shown.
  • Standalone examples and command-line executable are provided.
  • Web Service interface included.
• 1.3.1:
  • Standard set of Cool connection is directly available.
  • Migrated to JAXB 2.0 from JWSDP 2.0.
  • Atlantis Event Schema added.
  • Anal Proxy removed.
  • Event Proxy introduced.
  • Possibility to run localy (without connection to remote Server) and to read XML files.
• 1.4.0:
  • Non-python content of editor can't be send to remote Athena.
  • Non-XML content of editor can't be send used as XSLT.
  • Support for Cool 1.3.0.
  • Decryptage of Tokens (thanks to RD.Schaffer).
  • Support for LAr specific conditions (thanks to RD.Schaffer).
  • C++ wrapper over PureAthenaeumClient introduced.
  • XSD C++ XML Model introduced.
  • Selection based on tags, channels and periods introduced.
  • StandardCool is followed by Cool to allow further selection.
• 1.4.1:
  • Small fixes.
• 1.4.2:
  • It is now possible to restart Athena Server from Athenaeum.
  • Detailed payload analyses is optional.
  • Cool Bridge to Tag Collector started.
  • Migrated completely to Cool 1.3.0.
• 1.4.3:
  • JAXML used to write XML fragments.
  • PAIDA used to write NTuples.
  • LAr ramps and peds accessible.
  • Any script can be send from the Web Service.
• 1.4.4:
  • XMLEditor allows to requests for more details.
  • Detailed Cool requests allowed (in JAS).
  • Servers Status query available.
  • Moved to Apache xml-rpc 3.0.
  • Added support for gziped XML-RPC.
• 1.4.5:
  • WebService has collapsable tables.
  • All LAr payloads are accessible from JAS and WS.
  • Cool folder or a list of tags can be selected.
  • Cool summary task available
  • Possibility to start a new Server added.
  • A Progress bar has been added into Web Service.
  • JAS runs requests in a asynchronous thread.
• 1.5.0:
  • Reports about spend time added.
  • Cool looks also for related hierarchical tags.
  • Cool doesn't reload Athena dictionaries and doesn't start Cool DB connections if they already exist.
  • Situation with LAr payload types improved, but not all are visible yet.
  • Timeout for connection to server introduced.
  • Cool default stopTime moved to 2050.
  • Server password (key) hidden.
  • Users can see the most recent Server log files.
  • JAS plugin can set SSH tunnel.
  • Simple PyCool server supported.
  • Migrated to Cool 2.1.1.
  • DeleteRelation, IsTagLocked and SetTagLockStatus added to Bridge.
  • Google Gadget added.
  • PHP client documented.
• 1.5.1:
  • Tag extraction server added.
  • AMI publishing and querying server added.
  • Cool databases list updated.
  • Web Service remembers Cool parameters (in Cookies).
  • Fixed sharing of stored properties between Cool and StandardCool.
  • Substask running in a thread.
  • Distributed via WebStart.
  • Iterating over channels (another Root/LCG/C++ bug) work-around included.
  • Crash after task (another Root/LCG/C++ bug) work-around included.
• 1.5.2:
  • Crash after second task (another Root/LCG/C++ bug) work-around included.
  • de.schlichtherle.io.ArchiveManager included with disabled ShutdownHook so that it can run on CERN J2EE server.
  • Suport for SQLite databases.
  • Support for command using standard tasks (scripts).
  • Support for LArCaliWaveContainer.
• 2.0.0:
  • JAS functionality removed.
  • Cool LAr payloads encrypted by PoolRoot are tested.
  • help() supported on Servers.
  • log() supported.
• 2.1.0:
  • Further cleaning.
  • Fix to XSLT on the CERN j#EE server.
  • Fix to LAr Cool browsing.
  • Tag Extract added as a standard funcyion, including in the Web interface.
  • Progress bar is working.
  • GetFile added for checking file on the server.
  • Server statistics available.
  • Python client example available.
  • Family of parallel server suported.
• 2.1.1:
  • New "extract" command introduced.
  • GenericServer.py created.
  • Email notification enabled.
  • Site-specific configuration allows to deploy outside CERN (in Chicago).
  • POOLUtils server supported.
  • WAR file available to download.
  • Extract command-line introduced.
  • Skimming suported.
  • Access to (local) AFS fs.
  • Extract command verifies grid certificate.
• 2.2.0:
  • EventLookup server added.
  • JobConfig catalog added.
  • Extract server controled via XML JobConfig files.
• 2.2.1:
  • Extract CLI supports JobConfig uploading.
  • Directory removal possible.
  • WebStart client added.
  • Android client added.
  • EventLookup works from all clients.
  • Remote server management is possible.
  • Reaload button added into WebStart client.
  • CLI allows modification of JobConfig file using Groovy syntax.
• 2.2.2:
  • Worker updatable and installable from Manager.
  • VO SSL certificate handling included.
  • Calls extract logging service.
  • Android saves Root files to SD disk.
  • Worker can be installed from WebStart.
  • Android client default version build for 2.2.
  • Android client exportable to SD storage.
  • Logical collections acceptable in JobConfig.
  • Android client published in Android Market.
• 2.2.3:
  • Configuration from ServiceCatalog

Related Documentation and Presentations

Related Documentation:

• Blog entries:
  • Athenaeum 1.5.1.3 released
  • New Athenaeum command available
  • Athenaeum with Cool Payloads
  • How to run Athenaeum Cool tasks in standalone Athena ?
  • Athenaeum Server Scripts
  • Multithreaded XML-RPC Servers for Tag Extraction
  • How to add Athenaeum functionality to ordinary Web page
  • Athenaeum 2.0.0 released
  • Cool Athenaeum browsing
  • Tag Extraction via Athenaeum
  • Asynchronous Operations on the Extraction Server
  • Family of Athenaeum Servers
  • Three Tier Tag Extraction with Athenaeum
  • Extraction Architecture
  • How Extraction works
  • New extract command
  • Extract and Skim Tags via Athenaeum
  • Portable Athenaeum Command Line Client - PACLC
  • PACLC for Android
  • Wide Access to Event Lookup
  • Automatic installation of Athenaum Workers
  • Android Applications for Particle Physics
  • Athenaeum Command Line
  • Athenaeum Remote Worker Management
  • Athenaeum CLI JobConfig modifs via Groovy Slurp
• Documents:
  • JobConfig XML Slurping
  • Extract Flow
  • Skimming Architecture

Presentations:

• 2005:
  • Cool Browser as Athenaeum plugin in JAS (LAr Week, CERN, Nov'05)
  • Cool Browser as Athenaeum plugin in JAS (Atlas SW WS, LAL, Dec'05)
  • Athenaeum - Une interface JAS au framework Atlas (DevDur, LAL, Dec'05)
• 2006:
  • Using Java Analysis Studio as an interface to the Atlas Offline Framework (CHEP, Mumbai, Feb'06)
  • Lar Online Access to COOL/POOL data - H.Ma (Online database meeting, CERN, Jul'06)
  • Athenaeum - Remote Client to Atlas Offline Framework (Atlas LAL, LAL, Jul'06)
• 2010:
  • Extract Server (Event TAG Developer Workshop, CERN, Mar'10)
  • TAG Services (Atlas SW WS, CERN, Apr'10)
  • ATLAS Tags Web Service calls Athena via Athenaeum Framework (CHEP, Taipei, Oct'10)