Fusion Edge Server 3.0 Static Publication - Revision history

Vmurrell at 15:38, 11 September 2023

2023-09-11T15:38:17Z

2023-09-11T15:37:58Z

2023-09-11T15:37:50Z

2023-08-16T13:46:51Z

2021-06-30T11:43:46Z

‎Step 4: deploy to the Edge Server

2021-06-30T11:42:44Z

‎Step 4: deploy to the Edge Server

2021-06-30T11:41:59Z

‎Step 1: pull all data from your Fusion Registry

2021-06-30T11:39:29Z

‎Step 4: deploy to the Edge Server

2021-06-30T11:38:36Z

‎Step 4: deploy to the Edge Server

2021-06-30T11:37:50Z

‎Step 4: deploy to the Edge Server

@@ Line 1: / Line 1: @@
 [[Category:Fusion Edge Server]]
 [[Category:How_to_FES]]
 The following is a worked example for publishing all publicly accessible datasets from a specified Fusion Registry data warehouse to a Fusion Edge Server 3.0 environment using Static Mode.

@@ Line 2: / Line 2: @@
 [[Category:EdgeServer3Beta]]
 [[Category:How_to_FES]]
 The following is a worked example for publishing all publicly accessible datasets from a specified Fusion Registry data warehouse to a Fusion Edge Server 3.0 environment using Static Mode.

@@ Line 1: / Line 1: @@
 [[Category:Fusion Edge Server]]
 [[Category:EdgeServer3Beta]]
 The following is a worked example for publishing all publicly accessible datasets from a specified Fusion Registry data warehouse to a Fusion Edge Server 3.0 environment using Static Mode.

← Older revision		Revision as of 13:46, 16 August 2023
Line 1:		Line 1:
		+	[[Category:Fusion Edge Server]]
	[[Category:EdgeServer3Beta]]		[[Category:EdgeServer3Beta]]
	The following is a worked example for publishing all publicly accessible datasets from a specified Fusion Registry data warehouse to a Fusion Edge Server 3.0 environment using Static Mode.		The following is a worked example for publishing all publicly accessible datasets from a specified Fusion Registry data warehouse to a Fusion Edge Server 3.0 environment using Static Mode.

@@ Line 34: / Line 34: @@
 Create the directory if it doesn’t exist.
-Create an Edge Server properties file in the FusionEdgeServer ‘home’ directory. The file must be named '''edgeserver.properties''' and should have the following contents:
+Create an Edge Server properties file in the FusionEdgeServer ‘home’ directory. The file must be named '''edgeserver.properties''' and, for this example, should have the following contents:
   app.url=http://<strong>[hostname]</strong>/FusionEdgeServer
   ledger.secret=signature

@@ Line 4: / Line 4: @@
 ==Step 1: pull all data from your Fusion Registry==
-  <nowiki>buildFileSystem.ba</nowiki>t -api "https://[hostname]/ws/public/sdmxapi/rest" -df all -tgt FileSystem
+  <nowiki>buildFileSystem.ba</nowiki>t -api "https://<strong>[hostname]</strong>/ws/public/sdmxapi/rest" -df all -tgt FileSystem
 This will create a directory called ‘FileSystem’ with copies of the structures and data pulled from your Fusion Registry
 ==Step 2: compile the content in the FileSystem directory ready for deployment to your Edge Server==

@@ Line 38: / Line 38: @@
 [hostname] should be the hostname (and port if necessary) where the Fusion Edge Server is deployed.<br>
 Examples:<br>
-  app.url=https://stats.mydomain.org/FusionEdgeServer
+  <nowiki>app.url=https://stats.mydomain.org/FusionEdgeServer</nowiki>
-  app.url=http://localhost:8080/FusionEdgeServer
+  <nowiki>app.url=http://localhost:8080/FusionEdgeServer</nowiki>
 Copy the ‘<nowiki>node.zi</nowiki>p’ into the same directory.

@@ Line 39: / Line 39: @@
 Examples:<br>
 <pre>
-stats.mydomain.org<br>
+app.url=http://stats.mydomain.org/FusionEdgeServer
 localhost:8080
 </pre>