System Properties - Revision history

Vmurrell at 16:48, 30 October 2025

2025-10-30T16:48:17Z

2024-05-13T12:21:40Z

‎Properties which may be Dynamically changed

2023-10-10T14:56:01Z

‎Setting System Properties

2023-10-10T14:55:21Z

‎Setting System Properties

2023-10-04T11:39:53Z

‎Properties which may be Dynamically changed

2023-10-03T15:08:33Z

‎Properties which may be Dynamically changed

2023-10-03T15:08:01Z

‎Properties which may be Dynamically changed

2023-10-03T14:50:48Z

‎Properties which may be Dynamically changed

2023-10-03T14:45:53Z

‎Properties which may be Dynamically changed

2023-10-03T14:45:25Z

‎Properties which may be Dynamically changed

← Older revision		Revision as of 16:48, 30 October 2025
Line 1:		Line 1:
−	~~[[Category:How_To]]~~	+	[[Category:Fusion Registry Configuration]]
−	[[Category:Fusion Registry ~~Install~~]]
	= Overview =		= Overview =

@@ Line 77: / Line 77: @@
 |-
 | TF_ALTERNATE_HALF_YEAR  || false || [[Time_Format_Alternate_Half_Year|Sets the Registry into Alternate Half Year mode]]
 |-
 | HCL_OUTPUT_PERMIT_ALIAS_REF || false || Determine how Hierarchical Codelists should be output.<p>Fusion Registry version 10 only and since version 10.9.4.<p>[[Hierarchical_Codelists_Output_Format| Hierarchical Codelist Output]]
 |}

@@ Line 46: / Line 46: @@
 </pre>
-'''IMPORTANT NOTE:''' Values set by using the Web Service will '''not''' be preserved on a Registry reboot.  It is recommended to supply the System properties as part of the Java Server startup process (for example by the use of setenv in Apache Tomcat).
+'''IMPORTANT NOTE:''' Values set by using the Web Service will '''not''' be preserved on a Registry reboot.  It is recommended to supply the System properties as part of the Java Server startup process (for example by the use of [[Tomcat_setenv_file | setenv]] in Apache Tomcat).
 = Properties which may be Dynamically changed =

@@ Line 45: / Line 45: @@
+}
 </pre>
 = Properties which may be Dynamically changed =

@@ Line 76: / Line 76: @@
 | TF_ALTERNATE_HALF_YEAR  || false || [[Time_Format_Alternate_Half_Year|Sets the Registry into Alternate Half Year mode]]
 |-
-| HCL_OUTPUT_PERMIT_ALIAS_REF || false || Fusion Registry version 10 only and since version 10.9.4.<p>[[xxx]]
+| HCL_OUTPUT_PERMIT_ALIAS_REF || false || Determine how Hierarchical Codelists should be output.<p>Fusion Registry version 10 only and since version 10.9.4.<p>[[Hierarchical_Codelists_Output_Format| Hierarchical Codelist Output]]
 |}

@@ Line 63: / Line 63: @@
 | edi.skipagencycheck.enabled || false || When writing an EDI data file, does not check that the Agencies of the Dataflow and DSD match. When writing an EDI structure file, does not check that cross-referenced components are of the same agency as the DSD. This feature is part of EDI Leniency mode. <p>[[EDI_skipagencycheck_enabled|Ignores the Agency check when evaluating the DSI file]]
 |-
-| edi.dsi.dataflow.enabled || false || When reading an EDI file, determines whether the DSI segment should be used to refer to a Dataflow<br/?[[EDI_dsi.dataflow_enabled|Switches the DSI from refering to the Datafllow]]
+| edi.dsi.dataflow.enabled || false || When reading an EDI file, determines whether the DSI segment should be used to refer to a Dataflow<p>[[EDI_dsi.dataflow_enabled|Switches the DSI from refering to the Datafllow]]
 |-
 |edi.datagroup.identifier || unset || [[Edi_DataGroup_Identifier|Sets how the Registry sets the Group name when reading an EDI data file]]

@@ Line 61: / Line 61: @@
 | edi.forceTimeFormatSeriesAttr.enabled || false || [[Edi_Create_Time_Format|Sets whether a series attribute of TIME_FORMAT should be created]]
 |-
-| edi.skipagencycheck.enabled || false || When writing an EDI data file, does not check that the Agencies of the Dataflow and DSD match. When writing an EDI structure file, does not check that cross-referenced components are of the same aganecy as the DSD. This feature is part of EDI Leniency mode.
+| edi.skipagencycheck.enabled || false || When writing an EDI data file, does not check that the Agencies of the Dataflow and DSD match. When writing an EDI structure file, does not check that cross-referenced components are of the same agency as the DSD. This feature is part of EDI Leniency mode. <p>[[EDI_skipagencycheck_enabled|Ignores the Agency check when evaluating the DSI file]]
 |-
 | edi.dsi.dataflow.enabled || false || When reading an EDI file, determines whether the DSI segment should be used to refer to a Dataflow<br/?[[EDI_dsi.dataflow_enabled|Switches the DSI from refering to the Datafllow]]
@@ Line 75: / Line 75: @@
 |-
 | TF_ALTERNATE_HALF_YEAR  || false || [[Time_Format_Alternate_Half_Year|Sets the Registry into Alternate Half Year mode]]
 |}