1 / 27

The electronic Logbook @ the TTF VUV-FEL Making the next step

The electronic Logbook @ the TTF VUV-FEL Making the next step. R. Kammering -MVP- DESY in Hamburg. Introduction The TTF e-logbook The basic technology How does it look like? Changes since the first version E-logs @ XYZ Security: Authentication, authorization, …

mirra
Download Presentation

The electronic Logbook @ the TTF VUV-FEL Making the next step

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The electronic Logbook@ the TTF VUV-FELMaking the next step R. Kammering -MVP- DESY in Hamburg

  2. Introduction The TTF e-logbook The basic technology How does it look like? Changes since the first version E-logs @ XYZ Security: Authentication, authorization, … Conclusions / The next step Overview

  3. Introduction The days before the electronic … log  [Encyclopædia Britannica]  also called  maritime log instrument for measuring the speed of a ship through water. The first practical log, developed about 1600, consisted of a pie-shaped log chip with a lead weight on its curved edge that caused it to float upright and resist towing. When the log was tossed overboard, it remained more or less stationary while an attached line (marked off with equally spaced knots) was let out behind…

  4. Introduction The 20'th century 2002 - The year of the XML hype 2003 - the elog got standard Today Year 20XX ?

  5. The TTF e-logbook Classic client – server architecture: User program client Web browser client HTML + JPEG or PDF Text + images Text + images Upload, typing Print Combined content e-logbook Web server

  6. XML XML The TTF e-logbook User program client Web browser client 1. Print 1. Request 5. Response e.g. PS HTML PDF UNIX pipe - script XSLT / XSL FO 2. Store convert create JAVA servlets 2. Read 4. Combine content layout 3. Create PS JPEG XML XSL XML Web server servlet engine e-logbook folder e-logbook server

  7. Let’s have a look: External: https://ttfinfo.desy.de/TTFelog-secure Internal: http://ttfinfo.desy.de/TTFelog The TTF e-logbook

  8. The TTF e-logbook Main window Navigation Status info. Integrated shift summary Powerful search Create new entry Generate PDF Automatic hyper linking Edit entry

  9. The TTF e-logbook Edit window Set of (configurable)standard information Spellchecker Mail to an expert File upload

  10. The TTF e-logbook Natural integration of documentation Many supported data formats Complex tree structures possible Short abstract (gets indexed)

  11. TTF VUV-FEL document tree: > 600 entries > 200 Mb (mostly) PDF documents fully integrated into elog (fast access) support for MS/Open Office formats underway The TTF e-logbook

  12. all HTML code ported to JSP (JavaServer Pages) to allow: 1. parameterization of e-logbook specific values 2. one central (XML) conf. file per e-logbook 3. access this values via JSTL (JavaServer Pages Standard Tag Library) from within every JSP files The TTF e-logbook Changes since the first version:

  13. <!--define the name of the logbook, displayed on each page--> <name>DAQ eLogBook</name> … <!--period to create a new shift--> <!--formats are: Y = year, M = month, W = week, D = day, 3 = 3 shifts a day--> <new_shift>M</new_shift> <!--language code, possible values: en, de--> <lang_code>en</lang_code> <!--date formatting, posssible formats are:--> <!--date_fmt>MM/dd/yyyy</date_fmt--> <!--date_fmt>yyyy-MM-dd</date_fmt--> <date_fmt>dd.MM.yyyy</date_fmt> <!--title string for each shift in strftime(3C) format--> <title_date>%B %Y</title_date> <!--Shall text be 'above' or 'beside' the images--> <!--text_pos>above</text_pos--> <text_pos>beside</text_pos> … <!--Background color for overall style of the HTML pages (standard rgb notation)--> <bgcolor>ffffff</bgcolor> The TTF e-logbook Central e-logbook configuration file logbook name shift period language setting date format date title format text layout background color

  14. per e-logbook conf. file allows modular XSL architecture: The TTF e-logbook elog.xsl work.xml conf.xml imports + XSL XML parse keywords get data from conf. HTML … include rules spellchecker oracle.xsl ORACLE include oracle.xsl include final XSL

  15. Storing of shift data to ORACLE DB (JDBC Java Database Connectivity) Acquisition of machine statistics (ORACLE) The TTF e-logbook Further changes: Interoperability Beam statistics Down times

  16. The TTF e-logbook Further changes: Markup functionality (Wiki style) Tables are more readable Bold to emphasize Links Lists to order things Lines to comment

  17. E-log @ XYZ

  18. E-log @ XYZ the mother of all these elogs The TTF elog got popular … Thanks: S. Karstensen, D. Sertore, P. Krejcik and J. Tsai for the snapshots

  19. Some statistics: TTF elog is in operation since: Oct. 2001 > 41000 entries have been made ~ 18Gb graphical data / ~25Mb ASCII text E-log @ XYZ Today >30 TTF like e-logbooks are running on ~12 servers …

  20. E-log @ XYZ ttfinfo.desy.de - Number of unique visitors

  21. Stepwise integration of security: Security: Authenti., authori. 0. No authentication (2002 version) 1. (multiple-) sign on (since 2005) 2. Single sign on (SSO) 3. Cross domain SSO (CDSSO)

  22. Today's security architecture Security: Authenti., authori.

  23. Login procedure Security: Authenti., authori. The DIT (directory information tree)

  24. SSO - possible architecture Security: Authenti., authori.

  25. Conclusions Acceptance of e-logbook is overwhelming Ease for cloning was/is high priority World wide accessibility is very important e-logbook is a must for any kind of remote operation Still much could be done (collaborations?) Conclusions

  26. Security Implement SSO authorization schema Extend authorization to DOOCS … The next step … Elog-core • Extend configurable parameters • Harden automated elog installation • …

  27. Online resources: The TTF e-logbook technology: http://tesla.desy.de/doocs/elogbook e-logbook for testing: http://gan.desy.de/guestelog the central TTF e-logbook server: https://ttfinfo.desy.de Thanks for your attention!

More Related