Upgrade to a new version - Revision history

Vmurrell at 10:32, 12 November 2025

2025-11-12T10:32:25Z

Vmurrell at 17:01, 13 October 2025

2025-10-13T17:01:27Z

Vmurrell at 17:01, 13 October 2025

2025-10-13T17:01:06Z

Vmurrell: /* Version Specific Instructions */

2025-08-13T11:49:50Z

‎Version Specific Instructions

Vmurrell at 15:52, 4 September 2023

2023-09-04T15:52:03Z

Plazarou: /* Overview */

2020-12-01T15:32:42Z

‎Overview

Plazarou: /* Overview */

2020-12-01T15:31:59Z

‎Overview

Vmurrell: /* Version Specific Instructions */

2020-12-01T15:16:25Z

‎Version Specific Instructions

Vmurrell at 15:15, 1 December 2020

2020-12-01T15:15:54Z

Vmurrell at 15:13, 1 December 2020

2020-12-01T15:13:31Z

@@ Line 1: / Line 1: @@
 [[Category:Updating_Fusion_Registry]]
 =Overview=
 Prior to installing a new version of Fusion Registry you should perform the following tasks:

@@ Line 1: / Line 1: @@
 [[Category:Updating_Fusion_Registry]]
 [[Category:How_To]]
-[[Category:Fusion Registry Install]]
 =Overview=
 Prior to installing a new version of Fusion Registry you should perform the following tasks:

← Older revision		Revision as of 17:01, 13 October 2025
Line 1:		Line 1:
		+	[[Category:Updating_Fusion_Registry]]
	[[Category:How_To]]		[[Category:How_To]]
	[[Category:Fusion Registry Install]]		[[Category:Fusion Registry Install]]

@@ Line 17: / Line 17: @@
 =Version Specific Instructions=
 ==I am upgrading from Version 10.# to later Version==
 Fusion Registry version 10 has improved security, such that passwords are now encrypted with the industry-standard AES256 algorithm.  This offers greatly enhanced protection on passwords stored in the Fusion Registry.  However, this means that downgrading from version 10 to a previous version cannot be performed easily, since previous versions of the Registry will be unable to decrypt the version 10 encrypted passwords.

@@ Line 1: / Line 1: @@
 [[Category:How_To]]
 =Overview=
 Prior to installing a new version of Fusion Registry you should perform the following tasks:

@@ Line 5: / Line 5: @@
 * Export all structures from the Registry via the [https://wiki.sdmxcloud.org/Using_Bulk_Actions_to_Export_Structures Bulk Actions Option]
 * Backup your database schema
-* Stop the Apache Tomcat (or equivalent tool)
+* Stop Apache Tomcat (or equivalent server)
 * Navigate to the webapps folder of the Fusion Registry (for example C:\tomcats\Registry-8080\webapps) and replace the old war file with the new version
 * Delete the FusionRegistry folder in the webapps sub folder
-* Start the Tomcat
+* Start Apache Tomcat
-* Open the registry in a Web Browser in the usual way
+* Open the Registry in a Web Browser in the usual way
 You will see the version number on the Overview page as shown in the example below.

@@ Line 11: / Line 11: @@
 * Open the registry in a Web Browser in the usual way
-You will see the version number on the Overview page as shown n the example below.#
+You will see the version number on the Overview page as shown in the example below.
 [[File:Checkver.PNG|400px]]<br>

← Older revision		Revision as of 15:15, 1 December 2020
Line 87:		Line 87:

	If you wish to preserve your active directory mappings, before performing the upgrade of the Registry, rename the table 'registry_active_directory_mappings' to 'registry_ad_mappings '.		If you wish to preserve your active directory mappings, before performing the upgrade of the Registry, rename the table 'registry_active_directory_mappings' to 'registry_ad_mappings '.
		+
		+	==I am upgrading from Version 9.8.# to 10 or later==
		+	===Overview===
		+	For users migrating from Fusion Registry 9.8 to Fusion Registry 10.0 or later it is important to read this section to understand what changes occurred in version 9.8 that necessitate user action before the new Fusion Registry can be used successfully.<br>
		+
		+	These modifications only apply if you are migrating structures and data from Fusion Registry 9.8 to a later release.
		+
		+	===Edge Environment Audit Table===
		+	The table edge_environment_audit contains a table column called “uid”. This is not permitted in some versions of Oracle and so this table column must be renamed. This table is not particularly important and simply stores the times that Edge files were created.<br>
		+
		+	If you do not wish to preserve the information in this table, simply delete this table. It will be recreated automatically on Registry startup and the table will contain the correct column names.<br>
		+
		+	If you do wish to preserve the information in the edge audit table please perform the following:
		+
		+	* Stop the Fusion Registry
		+	* Modify the table edge_environment_audit so that the column named "uid" is now named "audit_uid"
		+	* Start the Registry

← Older revision		Revision as of 15:13, 1 December 2020
Line 74:		Line 74:

	If you do not perform this manual update then when the Registry 9.1 is started for the first time, the Registry will be unable to read the properties file and the Install Wizard of the Registry will be displayed. Once the Install Wizard has been completed, the new directory structure will be automatically created and a new properties file will be located within it.		If you do not perform this manual update then when the Registry 9.1 is started for the first time, the Registry will be unable to read the properties file and the Install Wizard of the Registry will be displayed. Once the Install Wizard has been completed, the new directory structure will be automatically created and a new properties file will be located within it.
		+
		+	==I am upgrading from Version 9.5.# to 9.6 or later==
		+	===Overview===
		+	For users migrating from Fusion Registry 9.5 to Fusion Registry 9.6 or later it is important to read this section to understand what changes occurred in version 9.6 that necessitate user action before the new Fusion Registry can be used successfully.<br>
		+
		+	These modifications only apply if you are migrating structures and data from Fusion Registry 9.5 to a later release.
		+
		+	===Active Directory Database Table===
		+	The database table 'registry_active_directory_mappings' was introduced in version 9.5.X of Fusion Registry. This table name is too long for those versions of the Oracle database before Oracle version 12.2. This table is now referred to by the Registry as 'registry_ad_mappings '.<br>
		+
		+	The table 'registry_active_directory_mappings' stores the mappings for the LDAP security mechanism. If you are not using LDAP you may simply ignore this upgrade step. If you are using LDAP and have not created custom mappings you may ignore this upgrade step.<br>
		+
		+	If you wish to preserve your active directory mappings, before performing the upgrade of the Registry, rename the table 'registry_active_directory_mappings' to 'registry_ad_mappings '.