Issues with servers availablity and/or capacity ReportNet situation

ReportNet QC Engine failing Reasons A combination of several dataflows caused the XQuery engines to fail. Code lists exceeded the designed limits. (max ~5000 towards ~500.000) Communication between ReportNet and FME Server Solutions A new QC engine (Xquery) is deployed. Significant performance gains on large data sets. Several dataflows have optimised there QC scripts in ReportNet. Split ReportNet core from QC engines. (WFD has it’s own instance) Renovate the sub system for code lists. In future EEA plans a complete makeover for ReportNet EEA will maintain and optimise the old system while develop and design ReportNet 2.0

WFD-Specific

WFD is highly spatial We integrated FME (Feature Manipulation Engine) into ReportNet. FME allows complex spatial validation and can natively read/write GML,XML,SQL,...

Problems during communication Firewall cuts connections After 30+ minutes ReportNet FME SERVER QC execution at envelope and dataset level FME QC for WFD Waits until validation is performed 6 isolated engines The firewall would cut the connection and not inform the servers (security reason against hackers) -> Leads to memory leaks crashing FME server.

Solution Firewall cuts connections After 30+ minutes ReportNet FME Server will close streaming connections that run for 29 minutes ReportNet FME SERVER QC execution at envelope and dataset level FME Process Initiate or check results DB Store Results Maximum open for 5 min 3 isolated engines Background job’s Continue validation Store results Job queue ReportNet checks every 20min (During four hours) 6 isolated engines 80+ Workspaces 11 schemas on spatial QC -> Heavy!

Testing

Extensive monitoring