Choose timezone
Your profile timezone:
JCOP FWWG, 31 January 2017
News and announcements
- as previously promised, a page was created by the BE-ICS-SDS to summarize the experience gathered during 3.15 upgrades. It is available from the WinCC OA 3.15 Downloads and Validation pages. Contributions from the JCOP community are welcome - they should be emailed to Piotr, and then will be reviewed, edited and added to the page.
- there is a bug in the S7 driver of WinCC OA 3.15, causing a block of manager ~40 minutes after a PLC loses the connection. This is being followed up with high priority with ETM
Status update of WinCC OA 3.15 distribution on Windows
Jonas presented the status of CMM installation packages, pointing out at the reason of the problem - the button to reboot the system after the _ETM's_ part of the installation, yet before CERN patches are applied. Recommendation: not to press this button or use silent installation. According to ETM they were not fully aware that this even happens; being followed up
OPC Foundation Redistributable is now available in CMF, and resolves problem with damaged installations on Windows.
Oracle InstantClient 12 is also now available in CMF, and tested by BE-ICS.
Question: which version of Oracle are required.
Answer: Oracle 12 is required by CtrlRDBAccess. The RDB Archiver would work with Oracle 11 client too, yet ETM supports version 12.
fwRPC component presentation
Matej presented the fwRPC "Remote Procedure Call" component.
Question: What if the procedure being called has a bug or blocks? Will it block the manager? Will the client get a tification?
Response: syntax errors should be handled through a try{}catch{} and propagated back to the client, yet there is no timeout on execution really.
Question: Why there are two CTRL managers for fwRPC
Explanation: one is the fwRPCCore, and then there is one (or may be more) fwRPCWorkers. The Core adds/starts worker manager to the console. It could actually start them without adding to console.
Remark from CMS: "RPC" name may be in conflict with the name of one of the CMS detector.
Explanation: this should be clarified by the function/component prefix, following the JCOP Framework Guidelines (central components should have "fw", while those of CMS would start with "cms"), which should resolve the ambiguity
Discussion about component being distributed and enabled in fwCore-8.0.0
- Piotr explained the motivation behind introducing fwRPC to fwCore (to ease the release of other frameworks, such as UNICOS, PSEN, that are based on fwCore and not complete JCOP Fw distribution. Acknowledged that the introduction of a new major functionality into the Core was premature and require the approval of FWWG.
- Decision to retire the fwRPC component from fwCore and redistribute it as a separate component.
Proposal of the new JCOP Framework web page
A new webpage was presented, with explanation of motivation. It is the automation of the component release process that would assure that the page always contains the latest recommended version of components.
It was proposed to have the release process explained in more detail.
It was proposed that in addition to ZIP files (distributed by EDMS, or by Nexus), one could have other distribution methods such as SVN tags or Git (asked by CMS and ATLAS). To be followed up.
Other matters arising
- Clara reported there is a bug in fwFSM preventing from generating the FSM for some subdomains. A new release being readied. Should be included in the Framework
- ALICE asked about the plans for release of new Framework and components so they could plan the upgrades.
- ALICE asked to clean up the release note and provide, if possible in advance, the list of fixes/features that are planned for a new release of component. Piotr explained that only bugfixes (typically minor) and no new features would come to the Framework till the end of EYETS. The list of planned fixes will be circulated
- Agreed to have JCOP Framework release 8.0.4 soon, incorporating the bugfixes in Cotr
There are minutes attached to this event.
Show them.