EdgeServerInstall

Quick Start with Apache Tomcat

Deploy Application and Launch Web Server

The Fusion Edge Server consists of a single .war file called FusionEdgeServer.war.

1. Copy FusionEdgeServer.war into the directory: <TOMCAT_HOME>/webapps
2. Start the Tomcat Server
3. Check the Tomcat <TOMCAT_HOME>/logs to ensure there are no errors in the log files

During the Tomcat start-up process, the war file will be unpacked into a directory of the same name, for example:

<TOMCAT_HOME>/webapps/FusionEdgeServer

On successful launch the Fusion Edge Server product information service can be queried from the following URL:

http://[server]:[port]/FusionEdgeServer/ws/fusion/info/product

The values for server and port must be replaced with the IP address and port number that the web application server is running on. For example, if the web browser is running on the same machine as the web application server and the Apache Tomcat has not had its default port settings modified, then the following address can be used:

http://localhost:8080/FusionEdgeServer

The Fusion Edge Server is now deployed and running in a web container, the URL will result in an empty (white page) - remeber the purpose of the FusionEdgeServer is to host a READ ONLY REST API to your SDMX Structural Metadata, Data, and Reference Metadata. The Fusion Edge server has no User Interface, so the white empty page is a good thing. The REST API of the Fusion Edge Server can be used to browse your content, which should be currently empty.

Deploy Content to the Fusion Edge Server

The Fusion Registry is used to generate the data and metadata content for the Fusion Edge Server. Please refer to the relevant Fusion Registry User Guide for more information. The output of the Fusion Registry is a single file called node.zip. This file should be copied or moved to the Fusion Edge Server’s sweep directory.

The Fusion Edge Server will move the zip file into the processing directory, importing the structural metadata, reference metadata, and data content. The zip file is then moved into the processed directory and the structural information will be available from the Fusion Edge Server’s web services.

The Fusion Edge Server treats each node.zip file as a full replace. The old environment will continue to be available via the web services until the full replacement environment is built. Once the replacement environment is ready, the data, structural metadata, and reference metadata services will all be switched to the new environment at exactly the same instance and the new service will be live. After the environment has been switched, the old environment will be discarded. If the Fusion Edge Server fails to read any part of the new environment, the publish process will fail and the old environment will continue to remain live. The Fusion Edge Server can continue to serve web service queries during the publication process, however the service will respond slower due to the increased CPU requirements of publication.

In order to deploy content to the Fusion Edge server, the file which contains the content needs to be placed in the sweep directory of the Fusion Edge Server.

The location of the Fusion Edge Server Directory defaults to:

<user home>/MetadataTechnology/FusionEdgeServer

On a Windows 10 Operating System this will typically be:

C:\users\<your user name>\MetadataTechnology\FusionEdgeServer

On a Unix Operating System, the likely location is:

/home/<your user name>/MetadataTechnology/FusionEdgeServer

The Fusion Edge Server creates the following directories on start-up, if they do not already exist. The directories are:

• sweep – This folder is periodically polled by the Fusion Edge Server to check for new data
• processing – The Fusion Edge Server copied swept files into this folder for processing
• processed – The Fusion Edge Server moves successfully imported files into this folder, and imports any content from this folder on application start-up
• tmp – This folder is used to store both short lived temporary files, and longer lived cached datasets

Test Web Service

The structural metadata, data, and reference metadata held in the Fusion Edge Server is made available via SDMX compliant web services. The web service entry point for the Node is available at:

http(s)://[server]:[port]/FusionEdgeServer/ws/public/sdmxapi/rest

A test query can be issued, for example:

https://localhost:8080/FusionEdgeServer/ws/public/sdmxapi/rest/dataflow

Modifying Edge Server Directory

The location of the Edge Server Directory can be changed by supplying a Java System variable to the JVM on tomcat launch.

The easiest way to achieve this is to create a new file named setenv.bat (or setenv.sh on Unix environments) and place it in the tomcats bin directory. The contents of this file should state the full location of the properties directory which should be in the appropriate format for your operating system. To illustrate this:

SET JAVA_OPTS=-DEdgeServerDir=c:/dir/MyDirectory

(For Windows systems)

export JAVA_OPTS=-DEdgeServerDir =/dir/MyDirectory

(For Unix systems)

Note: Fusion Edge Server will NOT start if this value is incorrect or if this directory cannot be written to.

Edge Server Runtime Properties

The Fusion Edge Server provides configuration options on various aspects of the Edge Server.

To set these configurations, create a file under the Edge Server Directory with the name: edgeserver.properties.