Edge Server Publication - Revision history

Plazarou: /* Edge Server Content and Security */

2023-10-25T09:12:49Z

‎Edge Server Content and Security

Vmurrell at 15:34, 11 September 2023

2023-09-11T15:34:47Z

Vmurrell at 15:01, 4 September 2023

2023-09-04T15:01:05Z

Vmurrell at 13:45, 16 August 2023

2023-08-16T13:45:07Z

Mnelson: /* Note */

2022-09-29T08:56:16Z

‎Note

Mnelson at 08:55, 29 September 2022

2022-09-29T08:55:09Z

Glenn: /* Edge Content Size */

2021-04-26T17:18:11Z

‎Edge Content Size

Glenn: /* Generating Edge Content */

2021-04-26T17:17:48Z

‎Generating Edge Content

Glenn: /* Generating Edge Content */

2021-04-26T17:15:19Z

‎Generating Edge Content

Glenn: /* Overview */

2020-09-14T15:21:54Z

‎Overview

@@ Line 34: / Line 34: @@
 = Edge Server Content and Security  =
 <p>
-The Fusion Registry is responsible for generating Fusion Edge Server content when it recives the command to build a publication for the given environment.  The default content, if data and refernce metadata is not included, is to include all structural metadata with the exception of those restricted due to security rules.  Security rules may also result in a subset of lists to be exported, for example if a security rule is applied to a specific Code in a Codelist to make it restricted, then it will not be included in the published Codelist.  If data is included then all datasets will be included, with the exception of those restricted due to security rules.  Security rules may also result in a subset of a dataset to be included (for example if a secuirty rule is provided to make any observation with OBS_CONF=C private, then it will not be included in the published dataset).  The environment definition may provide a finite list of Datasets to include, which will operate in conjuntion with security rules of the Fusion Registry.  If Provision Agreements are set to be excluded from the Publication, then so to are any Content Constraints against the Provision Agreement and any Categorisations that reference a Provision Agreement.
+The Fusion Registry is responsible for generating Fusion Edge Server content when it receives the command to build a publication for the given environment.  The default content, if data and reference metadata is not included, is to include all structural metadata with the exception of those restricted due to security rules.  Security rules may also result in a subset of lists to be exported, for example if a security rule is applied to a specific Code in a Codelist to make it restricted, then it will not be included in the published Codelist.  If data is included then all datasets will be included, with the exception of those restricted due to security rules.  Security rules may also result in a subset of a dataset to be included (for example if a security rule is provided to make any observation with OBS_CONF=C private, then it will not be included in the published dataset).  The environment definition may provide a finite list of Datasets to include, which will operate in conjunction with security rules of the Fusion Registry.  If Provision Agreements are set to be excluded from the Publication, then so too are any Content Constraints against the Provision Agreement and any Categorisations that reference a Provision Agreement.
 </p>
 <p>

@@ Line 1: / Line 1: @@
 [[Category:Fusion Edge Server]]
 = Note =
 Fusion Registry v10 only.  Fusion Registry 11 requires the updated [[EdgeServer|Fusion Edge Server]] to obtain and compile the Environment

@@ Line 1: / Line 1: @@
 [[Category:Fusion Edge Server]]
 = Note =
 Fusion Registry v10 only.  Fusion Registry 11 requires the updated [[EdgeServer|Fusion Edge Server]] to obtain and compile the Environment

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

@@ Line 2: / Line 2: @@
 = Note =
-Fusion Registry v10 only.  Fusion Registry 11 uses Fusion Edge Server Compiler to build the Fusion Edge Server Environment
+Fusion Registry v10 only.  Fusion Registry 11 requires the updated [[EdgeServer|Fusion Edge Server]] to obtain and compile the Environment
 = Overview =

← Older revision		Revision as of 08:55, 29 September 2022
Line 1:		Line 1:
	[[Category:Functions]]		[[Category:Functions]]
		+
		+	= Note =
		+	Fusion Registry v10 only. Fusion Registry 11 uses Fusion Edge Server Compiler to build the Fusion Edge Server Environment

	= Overview =		= Overview =

@@ Line 57: / Line 57: @@
 = Edge Content Size =
-The size of the zip file generated depends on the balance between series and observations with more series each with few observations tending to increase the size. A good rule for estimating the size is <strong>1.5MB per million observations</strong>.
+The size of the zip file generated depends on the balance between series and observations with more series each with few observations tending to increase the size.
 = Download Edge Content =

← Older revision		Revision as of 17:17, 26 April 2021
Line 55:		Line 55:

	The generation of Edge conent is a request which is processed asyncronously, and as such a status report is maintained by the Fusion Registry so that the progress can be tracked. Once the edge content is ready, it can be downloaded via a separate call.		The generation of Edge conent is a request which is processed asyncronously, and as such a status report is maintained by the Fusion Registry so that the progress can be tracked. Once the edge content is ready, it can be downloaded via a separate call.
		+
		+	= Edge Content Size =
		+	The size of the zip file generated depends on the balance between series and observations with more series each with few observations tending to increase the size. A good rule for estimating the size is <strong>1.5MB per million observations</strong>.

	= Download Edge Content =		= Download Edge Content =

@@ Line 54: / Line 54: @@
 |}
-The generation of Edge conent is a request which is processed asyncronously, and as such a status report is maintained by the Fusion Registry so that the progress can be tracked.  Once the edge content is ready, it can be downloaded via a sererate call.
+The generation of Edge conent is a request which is processed asyncronously, and as such a status report is maintained by the Fusion Registry so that the progress can be tracked.  Once the edge content is ready, it can be downloaded via a separate call.
 = Download Edge Content =

@@ Line 2: / Line 2: @@
 = Overview =
-<p>By design, the Fusion Registry does not diretly integrate with the Fusion Edge server, instead it is capable of generating content that can be published to it.  The genearted content consists of a single zip file, as required by the Fusion Edge Server for ingestion.</p>
+<p>By design, the Fusion Registry does not directly integrate with the Fusion Edge server, instead it is capable of generating content that can be published to it.  The genearted content consists of a single zip file, as required by the Fusion Edge Server for ingestion.</p>
 <p>Edge Server 'environments' can be described in the Fusion Registry, the puspose for describing an environment is to enable the Fusion Registry to know what content is should include/exclude from the published content.  There is no direct or indirect relationship between the Fusion Registry and the Fusion Edge Server, so the 'environment' definition is simply to help administrators maintain a packaging definition.</p>
 <p>The Fusion Registry User Interface supports the creation of an environment definition, and can be used to generate the publication file for the Fusion Edge Server.  It is also possible to drive both processes using the Fusion Registry web services.</p>