JCOP FWWG 1 Oct 2019: Improvements to the help system

→ Europe/Zurich
4/S-030 (CERN)

4/S-030

CERN

30
Show room on map

JCOP FWWG Meeting
1 October 2019

 

Proposal for the improved JCOP Framework Help System

- Presentation attached in INDICO.

- Would an upgrade of a component also update the help file? Yes. 

- What if one installs the component int another project path? Think of scattered projects, for instance? This should be technically possible. We'd need to discuss concrete use cases.

- Could one easily register "any other" help file? Yes, it is a matter of calling the "assistant" tool pointing it to where the help collection is and which file one wishes to add.

- In which state is the QtHelp? It is a mature project that is with Qt for a decade or more, hence could be relied on. We should make sure that ETM also commits to using it as WinCC OA help system.

- It was expressed that the feature looks quite promising, in particular the integration with GEDI script-editor, which could be of significant help for new developers

- Agreed that the final decision for the integration of the help will be discussed at JCOP CB, (including the proposals  for deprecation of HTML help, etc). Feedback may also be directed through icecontrols.suppport@cern.ch 

What is new in JCOP Framework 8.4.0

- Presentation attached in INDICO.

The following comments/questions were raised

- fwAccessControl: the new authentication (login) infrasturcture that IT works on will require the use of SIMPLE authentication combined with encryption through ldaps (no DIGEST-MD5). Tested and so far seems to work. For the Egroup-sync the situation is more complex, as there is no stable "schema" for the new LDAP server, hence no testing possible at the moment. In any case, the functionality is well encapsulated and a migration to the new infrastructure should be easy to deploy (starting a new version of the EgroupSync script).

- was there any effort done already to understand the new access control related mehanisms and "secure by default" pollicy announced for WinCC OA 3.17? No, not yet; will be proposed for the JCOP Program of Work for 2020.

-fwDIP: the new option for disabling the bad quality bit is quite controversial; the option is disabled by default anyway; the quality is logged verbosely anyway

- fwRack: is EN/EL aware of the UTF conversions? Not sure  - we may need to follow up. Even though it should not be a huge problem (at least at CMS , french descriptions are not used)

- fwRDBArchiver: ACKed by ATLAS it worked fine; some additional improvements implemented following feedback from ATLAS

- fwWiener: the previous OPC-DA server used to have items for diagnostics, and the OPC-UA Server does not provide them... These were statistical data items captured by the SNMP and CANbus drivers, and it would take a non-negligible effort to have them added to the OPC-UA servers now. The list of items are attached in INDICO. Experiments to consider if these could be safely ignored. 

- SystemOverview and FMC components also implemented most of the required changes (cleanups, XML panel conversion, etc) 

fwCaV: for SCY files with non-ASCII chars an expert option for the on-the-flight conversion to UTF

AOB

- Cristina (CMS) raised the point after the meeting that some people do use the fwUi.ctl library for things other than FSM; clarified that in such cases they must put an explicit #uses ,

- Related to the above: the fwUI.ctl contains functions such as isATLAS() , isCMS(); they should likely be used to the JCOP Fw Core. https://its.cern.ch/jira/browse/FWCORE-3428 spawned

There are minutes attached to this event. Show them.
The agenda of this meeting is empty