Difference between revisions of "Fusion Edge Server"

From Fusion Registry Wiki
Jump to navigation Jump to search
(Created page with "'''High-performance data dissemination server.''' A light-weight SDMX data and metadata REST API server designed to be deployed in clusters in the DMZ or at the network edge...")
 
 
(5 intermediate revisions by one other user not shown)
Line 1: Line 1:
 +
[[Category:Fusion Edge Server]]
 
'''High-performance data dissemination server.'''
 
'''High-performance data dissemination server.'''
  
Line 4: Line 5:
  
 
A typical configuration consists of a private [[Fusion Registry Core]] installation and a cluster of between two and four Fusion Edge Servers that drive the actual dissemination services such as web data portals and public APIs. Data is published for dissemination by exporting a ZIP file from the Fusion Registry Core containing all of the data and structures. The ZIP file is pushed to each of the Fusion Edge Servers using any suitable means like FTP or WebDAV. On receipt, the Edge Servers load the new data and start serving it, either immediately or at a defined time.
 
A typical configuration consists of a private [[Fusion Registry Core]] installation and a cluster of between two and four Fusion Edge Servers that drive the actual dissemination services such as web data portals and public APIs. Data is published for dissemination by exporting a ZIP file from the Fusion Registry Core containing all of the data and structures. The ZIP file is pushed to each of the Fusion Edge Servers using any suitable means like FTP or WebDAV. On receipt, the Edge Servers load the new data and start serving it, either immediately or at a defined time.
 +
 +
No database is required.<br>
 +
Once primed with data, Fusion Edge Servers are completely autonomous requiring no connection back through the firewall to services on the private network.
  
 
==Key Use Cases==
 
==Key Use Cases==
−
* Public dissemination services
+
* Driving public dissemination services
  
 
==Specification==
 
==Specification==
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! Header text !! Header text
+
| Application Type || Server
 
|-
 
|-
−
| Apllication Type || Server
+
| User Interface || No user interface
 
|-
 
|-
−
| User Interface || Web user interface accessible using a standard web browser [https://demo.metadatatechnology.com/FusionRegistry/overview.html Live Demo]
+
| API || SDMX-compliant REST API with proprietary extensions, compatible with that provided by the Fusion Registry Core [https://demo.metadatatechnology.com/FusionRegistry/webservice/data.html Data API Example]
−
|-
 
−
| API || SDMX-compliant REST API with proprietary extensions [https://demo.metadatatechnology.com/FusionRegistry/webservice/data.html Data API Example]
 
 
|-
 
|-
 
| Technology || Java web application
 
| Technology || Java web application
Line 23: Line 25:
 
| Compatible platforms || Linux, Windows, Mac and other platforms supporting a Java web runtime environment
 
| Compatible platforms || Linux, Windows, Mac and other platforms supporting a Java web runtime environment
 
|-
 
|-
−
| Minimum operating configuration || The minimim list of components required to deploy a Fusion Registry Core service are:<br>
+
| Minimum operating configuration || The minimim list of components required to deploy a Fusion Edge Server are:<br>
 
The Fusion Registry web app (WAR file)<br>
 
The Fusion Registry web app (WAR file)<br>
 
Java Runtime Environment<br>
 
Java Runtime Environment<br>
−
Java web application server (for instance Apache Tomcat)<br>
+
Java web application server (for instance Apache Tomcat)
−
SQL database (MySQL, SQL Server or Oracle
+
|-
 +
| Content storage || Filesystem
 +
|-
 +
| Configuration maintenance || Configuration is defined and maintained using textual properties files
 +
|-
 +
| Configuration storage || Textual properties files
 
|}
 
|}
  
 
[[Category:Components and Modules]]
 
[[Category:Components and Modules]]
  
−
==Functionality by Edition==
+
==Functionality==
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! style="width:300px"| !! style="width:150px" | Community !! style="width:150px" | Data Essentials !! style="width:150px" | Enterprise !! style="width:150px" | Cloud
+
! style="width:300px"| || Fusion Edge Server
 
|-
 
|-
−
| Structural Metadata Registry || style="background:#00FF55 | Full|| style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
+
| SDMX REST API || Read only SDMX-compliant API for structures and data
 
|-
 
|-
−
| Data Collection || No || One data provider, pull from registered data sources not supported || style="background:#00FF55 | Full || style="background:#00FF55 | Full
+
| Embargo || New data can be uploaded at any time but will only go live when the specified embargo date / time arrives
 
|-
 
|-
−
| Data Integration || No || Registry managed SQL data stores only || style="background:#00FF55 | Full || Registry managed datastores and registered data sources only
 
−
|-
 
−
| Data Storage || No || Registry managed SQL data stores only || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| Data Structural Validation || style="background:#00FF55 | Full|| style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| Data Business Rules Validation using Metadata Technology's proprietary expression language|| Arithmetic rules only || Arithmetric rules only || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| Data Structural Transformation || style="background:#00FF55 | Full|| style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| Time Series Calculations || No || No || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| Data Conversion || SDMX formats only || style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| Data Query Execution Engine || No || style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| Mapped Datasets || No ||style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| Reference Metadata || No || No || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| Audit || No || No || style="background:#00FF55 | Full|| style="background:#00FF55 | Full
 
−
|-
 
−
| Content Security || No || No || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| SDMX REST API || Structures only || style="background:#00FF55 | Full|| style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| Extended REST API || Validation and transformation only || style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
 
−
|-
 
−
| VTL source code repository || colspan="4" | No - Planned for April 2021
 
−
|-
 
−
| VTL execution engine || colspan="4" | No - Planned for 2021/2022
 
 
|}
 
|}
 +
 +
==Related Articles==
 +
[[Edge Server Publication|Publishing content to Fusion Edge Server]]<br>
 +
[[Fusion Edge Server Properties|Configuring Edge Server properties]]<br>
 +
[[Fusion Edge Server Directory|Understanding the Fusion Edge directory structure]]

Latest revision as of 05:46, 16 August 2023

High-performance data dissemination server.

A light-weight SDMX data and metadata REST API server designed to be deployed in clusters in the DMZ or at the network edge for scalable, fault-tolerant public data dissemination use cases.

A typical configuration consists of a private Fusion Registry Core installation and a cluster of between two and four Fusion Edge Servers that drive the actual dissemination services such as web data portals and public APIs. Data is published for dissemination by exporting a ZIP file from the Fusion Registry Core containing all of the data and structures. The ZIP file is pushed to each of the Fusion Edge Servers using any suitable means like FTP or WebDAV. On receipt, the Edge Servers load the new data and start serving it, either immediately or at a defined time.

No database is required.
Once primed with data, Fusion Edge Servers are completely autonomous requiring no connection back through the firewall to services on the private network.

Key Use Cases

  • Driving public dissemination services

Specification

Application Type Server
User Interface No user interface
API SDMX-compliant REST API with proprietary extensions, compatible with that provided by the Fusion Registry Core Data API Example
Technology Java web application
Compatible platforms Linux, Windows, Mac and other platforms supporting a Java web runtime environment
Minimum operating configuration The minimim list of components required to deploy a Fusion Edge Server are:

The Fusion Registry web app (WAR file)
Java Runtime Environment
Java web application server (for instance Apache Tomcat)

Content storage Filesystem
Configuration maintenance Configuration is defined and maintained using textual properties files
Configuration storage Textual properties files

Functionality

Fusion Edge Server
SDMX REST API Read only SDMX-compliant API for structures and data
Embargo New data can be uploaded at any time but will only go live when the specified embargo date / time arrives

Related Articles

Publishing content to Fusion Edge Server
Configuring Edge Server properties
Understanding the Fusion Edge directory structure

Retrieved from "https://wiki.sdmxcloud.org/index.php?title=Fusion_Edge_Server&oldid=5650"