Tomcat setenv file - Revision history

Vmurrell at 16:50, 30 October 2025

2025-10-30T16:50:57Z

Plazarou: /* Examples */

2023-10-10T14:58:47Z

‎Examples

Plazarou: /* Examples */

2023-10-10T14:57:47Z

‎Examples

Plazarou: /* Examples */

2023-10-10T14:57:36Z

‎Examples

Plazarou: /* Examples */

2023-10-10T14:57:13Z

‎Examples

Plazarou: /* JAVA_OPTS Configuration Parameters */

2023-10-10T14:56:47Z

‎JAVA_OPTS Configuration Parameters

Vmurrell at 07:37, 11 September 2023

2023-09-11T07:37:38Z

Glenn at 10:53, 23 September 2020

2020-09-23T10:53:58Z

Glenn at 10:52, 23 September 2020

2020-09-23T10:52:57Z

Glenn: Created page with "==JAVA_OPTS Configuration Parameters== JAVA_OPTS parameters configure the Java virtual machine, and also allow system parameters to be passed to the Fusion Registry applicatio..."

2020-09-18T17:40:29Z

Created page with "==JAVA_OPTS Configuration Parameters== JAVA_OPTS parameters configure the Java virtual machine, and also allow system parameters to be passed to the Fusion Registry applicatio..."

New page

==JAVA_OPTS Configuration Parameters==
JAVA_OPTS parameters configure the Java virtual machine, and also allow system parameters to be passed to the Fusion Registry application to alter its behaviour.
{| class="wikitable"
|-
! style="width:20%" | Parameter !! Purpose !! Example
|-
| -Xmx || Sets the maximum amount of memory that can be allocated to the Java heap. This should be a minimum of 4GB and ideally about 75% of available memory on the machine. Setting too low may result in Java 'out of memory' errors. || <code>-Xmx4GB</code> sets the maximum heap size to 4GB
|-
| -Xms || Sets the initial amount of memory to be allocated to the Java heap. When running in production, there may be a performance benefit to setting this to the same value as -Xmx which avoids the need to grow the heap as memory demand grows. || <code>-Xms128m</code> sets the initial heap to 128MB
|-
| -server || Improves performance by optimising the way the Java Virtual Machine works. ||
|-
| -DRegistryProperties || System Property: Sets a specific path for the Fusion Registry properties file. If not set, the [[Registry_Properties_File|default location]] is used || <code>-DRegistryProperties=file:\\opt\tomcats\environments\fusion_registry.properties</code> In Linux, sets the properties file location to the path specified.
|-
| -Djson.legacy.enabled=true or -Djson.legacy.enabled=false (default) || System Property: Sets whether the Fusion Registry instance uses the legacy Metadata Technology JSON dialect, or the [https://github.com/sdmx-twg/sdmx-json official SDMX-JSON version 1.0 Structure and Data Exchange format]. 
By default, or if the property is explicity set to ''false'', JSON returned will conform to the official SDMX-JSON specification when: 
* JSON is chosen as a format in the web user interface when exporting data or structures;
* The HTTP 'Accept' header is set to 'application/vnd.sdmx.json' when making a REST web service call; or
* The URL format parameter is set to 'sdmx-json' when making a REST web service call. 

If the property to ''true'', JSON returned will conform to Metadata Technology's legacy JSON format for structures and data. Use this for backward compatibility where existing client-side applications rely on the legacy JSON format.
|| <code>-Djson.legacy.enabled=true</code> Force Fusion Registry to produce and accept structures and data in the legacy Metadata Technology dialect
|-
| -DLicenseFile= (Data Essentials '''only''') || Sets the location of the License file and the Public key which is used in Data Essentials. || <code>-DLicenseFile=file:///C:/tomcats/RegistryProperties/8080_LICENSE/fusionLicense.fl<code> sets the location to a specific location on the C drive
|-
|}

← Older revision		Revision as of 16:50, 30 October 2025
Line 1:		Line 1:
−	[[Category:Fusion Registry ~~Install~~]]	+	[[Category:Fusion Registry Configuration]]
	Configuration for Fusion Registry is principally set by creating a ''setenv.bat'' or ''setenv.sh'' script in the Tomcat ''bin'' directory.		Configuration for Fusion Registry is principally set by creating a ''setenv.bat'' or ''setenv.sh'' script in the Tomcat ''bin'' directory.

@@ Line 52: / Line 52: @@
 The following example shows the setting of a number of [[System_Properties | Registry System Properties]]:<p>
 <samp>
-Test
+set JAVA_OPTS=-Xmx8G -DTF_ALTERNATE_HALF_YEAR=true -DENFORCE_STRICT_SDMX_2.1=true -Dedi.dsi.dataflow.enabled=true
 </samp>

@@ Line 50: / Line 50: @@
 ==Examples==
-The following example shows the setting of a number of [[System_Properties | Registry System Properties]]:
+The following example shows the setting of a number of [[System_Properties | Registry System Properties]]:<p>
 <samp>
 Test
 </samp>

← Older revision		Revision as of 14:57, 10 October 2023
Line 51:		Line 51:
	==Examples==		==Examples==
	The following example shows the setting of a number of [[System_Properties \| Registry System Properties]]:		The following example shows the setting of a number of [[System_Properties \| Registry System Properties]]:
		+	<samp>
		+	Test
		+	</samp>

← Older revision		Revision as of 14:57, 10 October 2023
Line 50:		Line 50:

	==Examples==		==Examples==
−	The following example shows the setting of a number of Registry System Properties:	+	The following example shows the setting of a number of [[System_Properties \| Registry System Properties]]:

← Older revision		Revision as of 14:56, 10 October 2023
Line 48:		Line 48:
	\|-		\|-
	\|}		\|}
		+
		+	==Examples==
		+	The following example shows the setting of a number of Registry System Properties:

← Older revision		Revision as of 07:37, 11 September 2023
Line 1:		Line 1:
		+	[[Category:Fusion Registry Install]]
	Configuration for Fusion Registry is principally set by creating a ''setenv.bat'' or ''setenv.sh'' script in the Tomcat ''bin'' directory.		Configuration for Fusion Registry is principally set by creating a ''setenv.bat'' or ''setenv.sh'' script in the Tomcat ''bin'' directory.

@@ Line 15: / Line 15: @@
 export CLASSPATH="/opt/oracle/ojdbc8.jar"
 </samp>
 ==JAVA_OPTS Configuration Parameters==
 JAVA_OPTS parameters configure the Java virtual machine, and also allow system parameters to be passed to the Fusion Registry application to alter its behaviour.

← Older revision		Revision as of 10:52, 23 September 2020
Line 1:		Line 1:
		+	Configuration for Fusion Registry is principally set by creating a ''setenv.bat'' or ''setenv.sh'' script in the Tomcat ''bin'' directory.
		+
		+	Below are examples for Windows and Linux.
		+
		+	==Windows==
		+	tomcat\bin\setenv.bat<br>
		+	<samp>set "JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx4G -server -DRegistryProperties=file:///C:/Tomcats/Environments/fusion_registry.properties"<br>
		+	set CLASSPATH=c:\oracle\ojdbc8.jar</samp>
		+
		+	==Linux==
		+	tomcat/bin/setenv.sh<br>
		+	<samp>
		+	<nowiki>#!/bin/sh</nowiki><br>
		+	export JAVA_OPTS="-Xms128m -Xmx4G -server -DRegistryProperties=file:\\opt\tomcats\environments\fusion_registry.properties"<br>
		+	export CLASSPATH="/opt/oracle/ojdbc8.jar"
		+	</samp>
	==JAVA_OPTS Configuration Parameters==		==JAVA_OPTS Configuration Parameters==
	JAVA_OPTS parameters configure the Java virtual machine, and also allow system parameters to be passed to the Fusion Registry application to alter its behaviour.		JAVA_OPTS parameters configure the Java virtual machine, and also allow system parameters to be passed to the Fusion Registry application to alter its behaviour.