Re: [EXTERNAL] Questions concerning Phoebus

["Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov>]

> When looking at the new trace, it does not show an archive source.

When it can't find any archived data, it removes that data source to prevent looking in vain over and over again.
You can change that via the 'drop_failed_archives' setting, see https://github.com/ControlSystemStudio/phoebus/blob/master/app/databrowser/src/main/resources/databrowser_preferences.properties

> These are my settings. Is something wrong with this?
> org.phoebus.archive.reader.rdb/stored_procedure=archive.get_browser_data

Did you define that stored procedure in MySQL?
Maybe not, or maybe it's failing for some reason?
Check the console log for errors, and try with that setting being empty:

org.phoebus.archive.reader.rdb/stored_procedure=


> We are using the Elog from PSI (https://elog.psi.ch/elog/index.html) 
> and would like to be able to create new entries from Phoebus directly.
> But the Elog only has to APIs: One is a shell command, the other being a python lib.
You'll have to implement the glue code that allows Java to make logbook entries.
Technically, that Java code could invoke a shell command, and that shell command could actually invoke python, but it seems unnecessarily circuitous.
With a python lib, you should have source code to figure out how to actually make logbook entries, for example via some underlying web service.
Once you implement that, there could be a risk that the low-level mechanism like the web service changes on you because it was not meant to be API. So you best contact the maintainer of the elog for a suggested mechanism, if only to then get notified about changes.

-Kay