Fusion Edge Server - Revision history

Vmurrell at 12:59, 13 November 2025

2025-11-13T12:59:42Z

Vmurrell at 13:46, 16 August 2023

2023-08-16T13:46:28Z

Glenn: /* Specification */

2020-09-14T15:32:32Z

‎Specification

Glenn: /* Related Articles */

2020-09-14T15:31:28Z

‎Related Articles

Glenn at 15:31, 14 September 2020

2020-09-14T15:31:09Z

Glenn at 15:19, 14 September 2020

2020-09-14T15:19:07Z

Glenn at 15:10, 14 September 2020

2020-09-14T15:10:13Z

Glenn: 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..."

2020-09-14T15:01:31Z

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..."

New page

'''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.

==Key Use Cases==
* Public dissemination services

==Specification==
{| class="wikitable"
|-
! Header text !! Header text
|-
| Apllication Type || Server
|-
| 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 [https://demo.metadatatechnology.com/FusionRegistry/webservice/data.html 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 Registry Core service are:<br>
The Fusion Registry web app (WAR file)<br>
Java Runtime Environment<br>
Java web application server (for instance Apache Tomcat)<br>
SQL database (MySQL, SQL Server or Oracle
|}

[[Category:Components and Modules]]

==Functionality by Edition==
{| class="wikitable"
|-
! style="width:300px"| !! style="width:150px" | Community !! style="width:150px" | Data Essentials !! style="width:150px" | Enterprise !! style="width:150px" | Cloud
|-
| Structural Metadata Registry || style="background:#00FF55 | Full|| style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
|-
| Data Collection || No || One data provider, pull from registered data sources not supported || style="background:#00FF55 | Full || style="background:#00FF55 | Full
|-
| 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
|}

@@ Line 36: / Line 36: @@
 | Configuration storage || Textual properties files
 |}
 ==Functionality==

← Older revision		Revision as of 13:46, 16 August 2023
Line 1:		Line 1:
		+	[[Category:Fusion Edge Server]]
	'''High-performance data dissemination server.'''		'''High-performance data dissemination server.'''

@@ Line 48: / Line 48: @@
 ==Related Articles==
-[[Edge Server Publication|Publishing content to Fusion Edge Server]]
+[[Edge Server Publication|Publishing content to Fusion Edge Server]]<br>
-[[Fusion Edge Server Properties|Configuring Edge Server properties]]
+[[Fusion Edge Server Properties|Configuring Edge Server properties]]<br>
 [[Fusion Edge Server Directory|Understanding the Fusion Edge directory structure]]

@@ Line 14: / Line 14: @@
 {| class="wikitable"
 |-
-! Header text !! Header text
+| Application Type || Server
 |-
 | User Interface || No user interface
@@ Line 37: / Line 35: @@
 {| class="wikitable"
 |-
-! style="width:300px"| !! style="width:150px" | Fusion Edge Server
+! style="width:300px"| || Fusion Edge Server
 |-
 | SDMX REST API || Read only SDMX-compliant API for structures and data
+|-
 |}

@@ Line 28: / Line 28: @@
 Java Runtime Environment<br>
 Java web application server (for instance Apache Tomcat)
 |-
 | Configuration maintenance || Configuration is defined and maintained using textual properties files

@@ Line 4: / Line 4: @@
 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.
 ==Key Use Cases==
-* Public dissemination services
+* Driving public dissemination services
 ==Specification==
@@ Line 15: / Line 18: @@
 | Apllication Type || Server
 |-
-| User Interface || Web user interface accessible using a standard web browser [https://demo.metadatatechnology.com/FusionRegistry/overview.html Live Demo]
+| User Interface || No user interface
 |-
-| API || SDMX-compliant REST API with proprietary extensions [https://demo.metadatatechnology.com/FusionRegistry/webservice/data.html Data API Example]
+| 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]
 |-
 | Technology || Java web application
@@ Line 23: / Line 26: @@
 | 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>
 Java Runtime Environment<br>
-Java web application server (for instance Apache Tomcat)<br>
+Java web application server (for instance Apache Tomcat)
 |}
 [[Category:Components and Modules]]
-==Functionality by Edition==
+==Functionality==
 {| 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"| !! style="width:150px" | Fusion Edge Server
 |-
-| VTL execution engine || colspan="4" | No - Planned for 2021/2022
+| SDMX REST API || Read only SDMX-compliant API for structures and data
 |}