You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Overview

The Web Browser Display (available since 2016.01) can display URLs that has been configured for a topology node in the topology.xml.

Configuration (up to Delft-FEWS 2018.02)

To use the  Web Browser Display, configure it as <explorerTask> in Explorer.xml. For example:

		<explorerTask name="Web Browser Display">
			<iconFile>document.png</iconFile>
			<mnemonic>h</mnemonic>
			<taskClass>nl.wldelft.fews.gui.plugin.webbrowser.WebBrowserDisplay</taskClass>
			<toolbarTask>false</toolbarTask>
			<menubarTask>true</menubarTask>
			<accelerator>ctrl h</accelerator>
			<loadAtStartup>false</loadAtStartup>
		</explorerTask>

Please be aware that you refer to an existing <iconFile> in your configuration!

Configuration (Delft-FEWS 2018.02 onwards)

In Delft-FEWS 2018.02 (and later), a new package (Java Chromium Embedded Framework  - JCEF) is taking care of launching this display. By default, this package is NOT installed and available through the Delft-FEWS libraries and need to be installed separately. 
If you are interested in using the Web Browser Display, please contact Delft-FEWS Productmanagement by e-mail (fews-pm@deltares.nl)
Below, configuration for this display are explained. If you have the Web Browser Display already running, you can skip general steps 2 and 3.

Configuration instructions

If you want to add a new Web Browser Display to your configuration, take the following general steps.

  1. Request for the JCEF package (fews-pm@deltares.nl)
  2. Create <explorerTask> placeholder for it in the Explorer.xml, see example above. 
  3. Extend the <nodes> in the Topology.xml with URLs to display relevant web content (see below: Display Content Example).
  4. Open the *_clientConfig.xml and add the <autoExportModuleDataSet name="jcef" exportDir="Modules"/>, see example below.
  5. Add the jcef.zip file to your ModuleDataSets (Note: you do not need to declare this moduleDataSet in the ModuleInstanceDescriptors.xml, like you would do normally)

 

Changes to the *_clientConfig.xml (SA example)
<?xml version="1.0" encoding="UTF-8"?>
<clientConfiguration xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews
http://fews.wldelft.nl/schemas/version1.0/clientConfig.xsd">
	<clientType>Stand alone</clientType>
	<autoExportModuleDataSet name="jcef" exportDir="Modules"/>
</clientConfiguration>

 

For Stand Alone:

  1. Make sure you apply the edits to the Explorer.xml of your SA application
  2. Add URLs to the <nodes> in the Topology.xml (RegionConfig)
  3. Move or Copy the jcef.zip into your Config/ModuleDataSets folder
  4. Adjust the *_clientConfig.xml of this SA application
  5. Start your Delft-FEWS SA application using the (2018.02 way of) clicking the Desktop (or Start Menu) icon. 

For Operator Client:

  1. Make the configuration changes as in the general steps above
  2. Upload the following files using the Config Manager:
    1. Explorer.xml in the SystemConfigFiles (only if needed)
    2. Topology.xml in the RegionConfigFiles
    3. JCEF package (jcef.zip) to the ModuleDataSetFiles
    4. *_clientConfig.xml in the RootConfigFiles
  3. Close the Configuration Manager application
  4. Start your Delft-FEWS OC application using the (2018.02 way of) clicking the Desktop (or Start Menu) icon.

In both cases (OC and SA) will extract the jcef.zip automatically under the configured "exportDir". If this directory is not present, it will be created. Underneath this exportDir a dedicated directory called jcef will be present and all binaries required for launching the Web  Browser Display can be found here.

This 'extraction on startup' will only take place once, unless the ModuleDataSet file has been changed (in the case of the jcef.zip file, this is not likely). This is the new way of distributing ModuleDataSet files on startup. More info, please check the details here.

Displaying Content

To display content in the Web Browser Display,topology nodes can be extended with optional URLs. In the following example, a SA test application (FEWS-Swiss was used) to show the potential variety.

<nodes id="Web" name="Web">
		<node id="node1" name="FOEN Swiss">
			<workflowId>Import</workflowId>
			<url>https://www.bafu.admin.ch/bafu/en/home.html</url>
		</node>
		<node id="node2" name="Meteo Swiss">
			<workflowId>Import</workflowId>
			<url>https://www.meteoswiss.admin.ch/home.html?tab=overview</url>
		</node>
		<node id="node3" name="Energy SFOE Swiss">
			<workflowId>Import</workflowId>
			<url>http://www.bfe.admin.ch/themen/00490/00491/00494/index.html?lang=en</url>
		</node>
		<node id="node4" name="YouTube (to test movies)">
			<workflowId>Import</workflowId>
			<url>https://www.youtube.com/</url>
		</node>	
		<node id="node5" name="Deltares">
			<workflowId>Import</workflowId>
			<url>https://www.deltares.nl/en/</url>
		</node>
		<node id="node6" name="Rijksoverheid (to test certificates) and redirect to https">
			<workflowId>Import</workflowId>
			<url>http://www.rijksoverheid.nl/</url>
		</node>
		<node id="node7" name="local html">
			<workflowId>Import</workflowId>
			<url>file:///PATH_TO_LOCAL_FILE.html</url>
		</node>		
	</nodes>

After displaying a page, the content can be refreshed using the "F5" shortcut key. This also required when for example images have been changed in the background. The can be refreshed by using the F5 key.

Example display 

  • No labels

Disclaimer