1. EPICS’03 @ Abingdon JoiMint-eLog Matthias Clausen

2. eLog and applications Integration of eLog into applications (JoiMint) Integration of JoiMint-MIME type and JoiMint config files into eLog

3. Requirements for our eLog approach – I Extended Functionality Start from the existing eLog at DESY (TTF-Version) Keeping the following ideas: Write messages, screen dumps and files through central print queues (survive database downtimes) Use Web interface to add and to edit entries Use Servlets to retrieve data from the eLog and to prepare Web displays. Keep the XSLT style sheet to generate the Web edit page

4. Requirements for our eLog approach – II New Functionality Access and display of multiple eLog sources. Storing messages, screen dumps (JPG) and any kind of files into an Oracle database. (Rather than XML files) Support links between messages Support for entries and screen dumps on Unix and Windows (Windows: bypassing default PostScript printer driver) Support command line entries. Write from applications

5. Web Client eLogbooks Servlet: ListEntry Applet set: -eLogbook(s) -From time -To time -Shift Text + Images Prepare request and insert entry in vector Read/ Write Classes extending LogBook Read Text prepare html Sorted Vector Oracle eLog MKS-1 MKS-2 MKS-3 MKS-4 KRYO. Oracle MKK Oracle IT-News TINE Events XML eLogs Text eLogbook: Mutiple Sources Tomcat

6. Example The Applet Select one or more logbooks Select defined time span Type in from and to time Select shift of ‚from‘ day Entrer search string for: Author or subject or text.

7. Example The Web Page The selected log books Automatically entered text file The selected from/ to time Add new entry to your logbook Select your default logbook for entries Entry with screen dump Ascending / decending Add new entry to your log book with reference to this entry. Goto the linked entry Edit this entry (if allowed) Statistical Information: (MySql local on Tomcat Server) Online help

8. Help

9. Web Client Tomcat eLogbooks Servlet: ModifyEntry Html-Link: Activate Servlet With entry ID Text + Images Prepare request and Insert single entry in vector Read/ Write Classes extending LogBook Read Text XML Translator Single Entry Oracle eLog MKS-1 MKS-2 MKS-3 MKS-4 KRYO. Oracle MKK Oracle IT-News TINE Events XML eLogs Text eLogbook Edit Display (read) prepare XML XSL Stylesheet Edit Button depending on write access to source

10. Web Client Cenrtal Oracle Server Printer Spooler Read and Write from/to eLogbook Tomcat Servlet Central Remote print2oracle WindowsUnix Capone epicsmenu (Tcl/tk) Print to queue: oraclelog Unix also allows to print to oraclelog through the Command line interface (lpr –Poraclelog MKS-2:030612-12:00:00.txt)

11. Integrating eLog JoiMint Create entries in JoiMint and save them into the eLog (Oracle) Save JoiMint config files and/or config+data files into eLog Create html links with the MIME type and start JoiMint from eLog entries

12. Post Mortem Query Result The selected log book is: EVENT http links with event information

13. JoiMint config file: (dynamically created by servlet) From http-link to JoiMint Display Link : http://krykpcn.desy.de:8080/examples/servlet/eLogbook.GetJoiEvent? EVENT_N=1055491723& ARCHIVE_S=KRYKSRV& DEVICE_S=SenderstrHENL& ID=EVENT:030613-10:08:43.joi JoiMint config file: (dynamically created by servlet)

14. TINE Data Web Client Tomcat eLogbooks Html-Link: Including: Archive-Server DeviceServer Event-Number eLogbook Display JoiMint Event Displays Prepare Joi-File With Archive-Server DeviceServer Event-Number Send html Image (Joi-File) With MIME Header Servlet: GetJoiEvent JoiMint file With JOI MIME type Start MIME Application JoiMint Servlet: ListEntry Read Link Information Classes extending LogBook Create html + Link Read TINE Events Step I Step II

15. Experience Tomcat is just stable (no crashes ever) Oracle performance extremely good Oracle server in computing center Performance @ DESY: ~ 50 images @ 100k... Which implies 51 interactions with Oracle server... in 2 sec 100 messages (text) from 5 log books (5 interactions)... in 1-2 sec (limits: 50 images / 100 messages configured in config class)

16. Plans - I: Add alarms: Use existing alh-> Oracle functionality and write alarms directly into Oracle Query alarms in eLog Create http links for: JoiMint -> archive data JoiMint -> alarm settings...

17. Plans - II: Add support for cmlog (as source) Line oriented view ( like JLAB eLog) Configure eLogs in (XML) config file Add eLog-sources by Java plugins