Edge Server - Publish Content - Revision history

Vmurrell at 15:32, 11 September 2023

2023-09-11T15:32:21Z

Vmurrell at 13:43, 16 August 2023

2023-08-16T13:43:40Z

Mnelson: /* Static Mode */

2023-01-10T10:51:37Z

‎Static Mode

Mnelson: /* Static Mode */

2023-01-10T10:50:30Z

‎Static Mode

Mnelson: /* Overview */

2022-08-26T14:06:54Z

‎Overview

Mnelson: /* Overview */

2022-08-26T14:06:43Z

‎Overview

Mnelson: /* Overview */

2022-08-26T14:06:07Z

‎Overview

Mnelson: /* Overview */

2022-08-26T14:05:48Z

‎Overview

Mnelson: /* Automating the Process */

2022-08-26T13:17:24Z

‎Automating the Process

Mnelson: /* Amazon S3 */

2022-08-26T13:16:15Z

‎Amazon S3

← Older revision		Revision as of 15:32, 11 September 2023
Line 1:		Line 1:
−
	[[Category:Fusion Edge Server]]		[[Category:Fusion Edge Server]]
		+	[[Category:How_to_FES]]
	== Overview ==		== Overview ==

← Older revision		Revision as of 13:43, 16 August 2023
Line 1:		Line 1:
		+
		+	[[Category:Fusion Edge Server]]
	== Overview ==		== Overview ==

@@ Line 57: / Line 57: @@
 Static mode is termed as such because the Fusion Edge Server loads the [[Edge_Server_Environment|Environment]] on application startup, and the Fusion Edge Server never checks for Environment updates after launch.  The contents of the Fusion Edge Server are static, and can only be changed by restarting the web application server.
-To use static mode,the '''environment.file''' property should be set in the '''edgeserver.properties''' file.  The properties file is located in the Fusion Edge Server [[Fusion_Edge_Server_Directory|home directory]].  The [[Edge_Server_Environment|Environment]] is accessed as a local file or folder, the path to the file or folder can be relative to the home directory.
+To use static mode,the '''environment.file''' property should be set in the [[Fusion_Edge_Server_Properties|'''edgeserver.properties''']] file.  The properties file is located in the Fusion Edge Server [[Fusion_Edge_Server_Directory|home directory]].  The [[Edge_Server_Environment|Environment]] is accessed as a local file or folder, the path to the file or folder can be relative to the home directory.
 Example:

@@ Line 55: / Line 55: @@
 === Static Mode ===
-Static mode is termed as such because the Fusion Edge Server loads the Environment on application startup, and it never changes the Environment after this.  The contents of the Fusion Edge Server are static, and can only be changed by restarting the web application server.
+Static mode is termed as such because the Fusion Edge Server loads the [[Edge_Server_Environment|Environment]] on application startup, and the Fusion Edge Server never checks for Environment updates after launch.  The contents of the Fusion Edge Server are static, and can only be changed by restarting the web application server.
-To use static mode, the contents of the [[Edge_Server_Environment|Environment]] folder is zipped to producing a single zip file.  The zip file is placed on the file system in the home directory of the Fusion Edge Server.  The edgeserver.properties file is configured to define the name of the Environment zip file that the Fusion Edge Server should load on application startup.
+To use static mode,the '''environment.file''' property should be set in the '''edgeserver.properties''' file.  The properties file is located in the Fusion Edge Server [[Fusion_Edge_Server_Directory|home directory]].  The [[Edge_Server_Environment|Environment]] is accessed as a local file or folder, the path to the file or folder can be relative to the home directory.
-The Fusion Edge Server will read the zip file on application startup and load the Environment into memory.  The only way a new Environment can be deployed is by restarting the web application server.
+Example:
 === Dynamic Mode ===

@@ Line 9: / Line 9: @@
 The [[Fusion_Edge_Compiler|Fusion Edge Compiler]] is a command line application which can be used for all 3 steps.
-An [[https://wiki.sdmxcloud.org/images/2/28/FusionEdgeServer_Deployment_Architecture.png Example Architecture]] shows how these steps in a set up which contains multiple servers each with a copy of an Environment.
+An [https://wiki.sdmxcloud.org/images/2/28/FusionEdgeServer_Deployment_Architecture.png Example Architecture] shows how these steps in a set up which contains multiple servers each with a copy of an Environment.
 == Part 1 - Source Data and Metadata Files ==

@@ Line 5: / Line 5: @@
 # [[#Part_1_-_Source_Data_and_Metadata_Files|Source Data and Metadata Files]] - A file system is required with source information (datasets and related metadata) which is to be published. The files are in SDMX format.
 # [[#Part_2_-_Compiled_Environment|Compiled Data and Metadata Files]].  A file system which contains the information from the SDMX files, compiled into an [[Edge_Server_Environment|Environment]]. The files are in a format which can be read by the Fusion Edge Server.
-# Moving the [[Edge_Server_Environment|Environment]]. This step makes the Environment available to the Fusion Edge Server
+# [[#Moving_an_Environment|Moving the Environment]] . This step makes the [[Edge_Server_Environment|Environment]] available to the Fusion Edge Server
 The [[Fusion_Edge_Compiler|Fusion Edge Compiler]] is a command line application which can be used for all 3 steps.

@@ Line 3: / Line 3: @@
 Moving information to the Fusion Edge server requires three steps:
-# Source Data and Metadata Files - A file system is required with source information (datasets and related metadata) which is to be published. The files are in SDMX format.
+# [[#Part_1_-_Source_Data_and_Metadata_Files|Source Data and Metadata Files]] - A file system is required with source information (datasets and related metadata) which is to be published. The files are in SDMX format.
 # Compiled Data and Metadata Files.  A file system which contains the information from the SDMX files, compiled into an [[Edge_Server_Environment|Environment]]. The files are in a format which can be read by the Fusion Edge Server.
 # Moving the [[Edge_Server_Environment|Environment]]. This step makes the Environment available to the Fusion Edge Server

@@ Line 94: / Line 94: @@
 Another technique for copying files is to delete any files in the target Environment that do not exist in the new Environment, and then copy any files which are only in the new Environment.  Then finally copy the new fes_ledger.json file.
-== Automating the Process ==
+=== Automating the Process ===
-The Fusion Edge Compiler does not provide any support for moving an Environment to a file system or URL.  However it does provide support for publishing content to Amazon S3. It is recommended to set up an script to automate the process of publishing a new Environment to the Fusion Edge Server.
+The Fusion Edge Compiler does not provide any support for moving an Environment to a file system or URL.  However it does provide support for [[Fusion_Edge_Compiler#Publish_Content|publishing content to Amazon S3]]. It is recommended to set up an script to automate the process of publishing a new Environment to the Fusion Edge Server.

@@ Line 83: / Line 83: @@
 ==== Amazon S3 ====
-The Fusion Edge Server is given the Amazon S3 bucket, region, secret key, and access key.   The contents of the bucket are expected to be the files and folders of the Environment.
+The Fusion Edge Server is given the Amazon S3 bucket, region, secret key, and access key.   The contents of the bucket are expected to be the files and folders of the Environment.  The Fusion Edge Compiler can be used to [[Fusion_Edge_Compiler#Publish_Content|publish an Environment to Amazon S3]].
 == Moving an Environment ==

Edge Server - Publish Content - Revision history

Vmurrell at 15:32, 11 September 2023

Vmurrell at 13:43, 16 August 2023

Mnelson: /* ​Static Mode */

Mnelson: /* ​Static Mode */

Mnelson: /* Overview */

Mnelson: /* Overview */

Mnelson: /* Overview */

Mnelson: /* Overview */

Mnelson: /* Automating the Process */

Mnelson: /* Amazon S3 */

Mnelson: /* Static Mode */

Mnelson: /* Static Mode */